Best practice for submitting missing scenes and models?

StashDB
1

I’ve found a studio with a significant number of scenes that aren’t currently in the database. Many of these scenes have models without pages on StashDB either, so I’ll need to add them as well.

What is the best way to handle this situation? Is it possible to create the scene and model pages simultaneously, or will I need to do one, then the other? If the latter, is it better to submit the scene or model first?

Thanks, all.

1 Like
2

The guidelines require that all performers be added to the scene, so the best practice is to create them first. In many cases the performers might already be in the database but due to the limited search capabilities they might be hard to find: it’s a good idea to ask for help identifying them either in the Discord channel called #id-request or in this forum, preferably including a clear image of their face so that we can leverage facial recognition software.

Many new editors create their scenes and performers concurrently, but their scene submissions will often get voted down because of the missing performers and/or stall because their performer submissions were not accepted.

The reason we want performers to be present before the scene is submitted is that we have experienced many editors who submit the scene and then neglect to follow up and add the performer, which leads to a lot of extra cleanup work that should not be necessary.

7 Likes
3

Amazing, thanks for the detailed response. I’ll be sure to take the steps you’ve recommended.

4

Also worth noting here that duplicate performers are a lot easier to clean up compared to duplicate scenes, you just have to wait a minimum of 3 days for the merge edit to pass.

Scenes on the other hand require you to manually copy over any missing info before deleting the duplicate, usually preserving whichever entry has the greater number of fingerprints attached since those aren’t easily migrated.

So if you end up submitting a duplicate performer because you couldn’t find the existing one, don’t sweat it too much. We’ll appreciate the effort put into identifying them but past a certain point you start getting diminishing returns, which is why crowdsourcing that effort through # id-request is often the most efficient route. A lot of the people who hang out in that channel have some very specific tools and tricks they can use to quickly find a match.

3 Likes
5

I’ll just chime in with my process. I have a set of meta-tags (prefixed with “ZZ” so they never match to a StashDB tag), including:

  • ZZ StashDB Performer Pending
  • ZZ StashDB Scene Pending

When I have a new scene with a new performer, I submit the performer and tag both the scene and performer locally with ZZ StashDB Performer Pending. Once the performer is approved, I remove that tag, submit the scene, and tag the scene locally with ZZ StashDB Scene Pending. As the scenes are approved, I re-scrape via fingerprint to add the Stash ID and then remove the ZZ StashDB Scene Pending tag.

I tend to do StashDB submissions in batches rather than onsie-twosies (it’s been a few months), so the tags help me keep track of the status of those submissions.

My other StashDB-related meta-tags include:

  • ZZ StashDB To Submit - New scenes or existing scenes where I more/better metadata (new links, tags, etc.). This indicates that my local scene is fully-organized (has complete metadata, is tagged, and all performers exist on StashDB).
  • ZZ StashDB Incorrect Fingerprint - Track scenes that I’ve identified have incorrect fingerprints in StashDB. I add these to the StashDB Backlog file in Google Drive.
  • ZZ StashDB Not Eligible - Scenes that are not eligible for StashDB based on the guidelines (e.g. full movies).
4 Likes