Ability to check stash-box matches based on last updated date in scene tagger

dunn.gitter · June 9, 2026, 9:32pm

Describe the feature you’d like

I have a large library of content, a small chunk of which I have managed to scrape from stashbox. I would like to be able to slowly work through matching more content, however, there’s currently not a great way for me to track which files I have already attempted to scrape, and which I haven’t. This means that every time I decide to sit down and scrape some content, I either need to remember the sort criteria and which page I was on, or sort by random and just go through and try to scrape everything again (which leads to many duplicate scraping attempts for the same content).

What would be super helpful is if some data about scraping was stored, and could be used to filter. Namely, it would be great if I could sort by last scraped date, and maybe the number of scrape attempts. Also, it might be nice to cache the results of a previous scraping attempt if results were returned (less useful, I think, and maybe less feasible?). Maybe there is also some other data that could be useful if tracked but for my purposes I think these would suffice.

I think an additional section in the “History” tab that contains information about previous scrape attempts (and maybe the actual matches, if any?) would also be nice.

Describe the benefits this would bring to existing users

Implementing this would allow users to more easily filter out content that is not currently linked to any stashbox entries but that they have already previously attempted to scrape. That way, they can focus on scraping content that they haven’t already tried to scrape before, rather than attempting to re-scrape content that previously was not found (unless that is specifically what they are trying to do).

Additionally, users could, for example, leverage the filter to only include content where scraping has previously been unsuccessful but where the last attempt was long enough ago that another attempt might be worthwhile (i.e. I haven’t tried to scrape this particular piece of content in 6 months, maybe someone has added it to stashbox since then).

Is there an existing way to achieve this goal?

I don’t think so, but I’d love to be wrong!

Additional context

dunn.gitter · June 9, 2026, 10:04pm

Additionally, if tracking of previous scrape results is implemented it could pave the way for a subsequent feature request for a periodic scraping job.

The periodic job could be configured similarly to what the filters in the OP could be used for - to scrape content that has never been scraped and/or to re-scrape content which was previously unsuccessfully scraped sufficiently long ago.

This would probably also require a way to review the scrape results from the periodic job and apply the ones that match correctly (or maybe a YOLO mode that just accepts matches if they meet enough criteria)

DogmaDragon · June 12, 2026, 11:36am

Why not save it as a filter?

DogmaDragon · June 12, 2026, 11:36am

github.com/stashapp/stash

Ability to check stash-box matches based on last updated date in scene tagger

opened 06:27PM - 10 Sep 22 UTC

mmenanno

feature request

### Problem Once a scene has been matched, a user typically wouldn't be able to… receive any updates if details have been updated (maybe males were added or titles were fixed), or if the scene was deleted as a duplicate. There is an update function for performers currently but I think it could be improved as well along with adding the scene behaviour, though this issue will focus on the scene side of things as the performer behaviour is likely similar if not the same and could later be extended. I believe the solution for this lives on both Stash and Stash-Box sides. ### Stash Backend Side Currently a `StashID` in Stash is made up of an `endpoint` and a `stash_id`. I believe another attribute should be added to it, to store the lasted `updated_at` time of the external resource. Not hard set on the name but this field could be something like `external_updated_at`. ### Stash-Box Backend Side For the sake of making the process optimal Stash-Box should have a new query `findUpdatedScenes` that takes an array of `SceneUpdateInput` structured something like: ```JSON { "scene_id": "stash_id", "last_recorded_update": "external_updated_at" } ``` This call can return a `updated` Boolean, deleted Boolean, and `Scene` object for each input. - If the `last_recorded_update` is NOT older than the `updated_at` on the `scene_id`, it will return `updated: false` , `deleted: false`, and no scene object - If the `last_recorded_update` is older than the `updated_at` on the `scene_id` but the scene has been deleted, `updated: true`, `deleted: true`, and no scene object - If the `last_recorded_update` is older than the `updated_at` on the `scene_id` and the scene is not deleted, `updated: true`, `deleted: false`, and the updated Scene object ### Stash Frontend Side The scene tagger view will get a new `Batch Check for Updates` button. This will collect all the scenes the user wants to check (whether this is all scenes or just a sub-set) and call back to `Stash-Box` with `findUpdatedScenes`. - If the scene has no updates the scene item will show a message of `No new updates` - If the scene has been deleted the scene item will show a message of `Scene has been deleted` with an external link to the ID so the user can investigate - If the scene has been updated the scene item will show the returned scene object like it normally would on a scrape (it would be nice if we could highlight updates in a different colour, but that would be scope of another issue, since that would also generally improve any scraping, not just updates). Buttons could also be added to `Show only updated` and `Show only deleted` for quick filtering of the list.

dunn.gitter · June 13, 2026, 3:30am

Hmmm maybe I’m misunderstanding or missing something, but I didn’t think that filters saved the page that you were on? I think a filter would ensure the same order for the scenes every time, but not your progress through that order? Also, wouldn’t the order be impacted if new scenes are added?

dunn.gitter · June 13, 2026, 3:34am

I don’t think this linked issue is the too relevant here, it seems to mostly be discussing a way of keeping already matched content up-to-date with the upstream stashbox instance, which isn’t really something that I was considering here. Maybe I’m missing something?