There’s a current Destroyal edit for a scene whose fingerprints are genuinely chaotic – multiple durations, many single-submission hashes, significant spread across submitters.
When two entries appear to be duplicates, but the fingerprint situation is messy enough that it’s unclear what “correct” even looks like, is there an established approach? Destroying both and creating a fresh entry seems appealing in theory, but I don’t know if that’s sanctioned practice or whether there’s a preferred process.
The typical rule of thumb for duplicate scenes is to delete the entry that has fewer (assumedly) correct fingerprints. That way we preserve the greater variety of hashes and affect fewer users who had previously saved / submitted from their local Stash.
In the rare case where we know what video the majority of “bad” fingerprints came from, and that video isn’t already covered by StashDB, and there are no eligibility concerns, we have previously decided to save that entry instead by overwriting its data to match the fingerprints. But that has only happened in very narrow circumstances, typically when the editor who originally created an entry mis-identified their local video, scraped data from a scene that didn’t match the initial fingerprints, and someone caught the error before things got messy with other duplicates and tangled fingerprints.
Nothing about the linked example sounds worth saving to me. It’s very likely that some of the longer fingerprints are from the full movie instead of the single scene, but those fingerprints don’t make up an obvious majority of those submissions. Even if somebody takes the time to track down a copy of the full movie to confirm which fingerprints match, it’s both easier and cleaner to delete the current entry and submit a new one.
(Assuming the full movie is eligible for StashDB, which I haven’t taken the time to check. I’m pretty sure Wicked used to offer downloads of the full movie when MindGeek managed the website, but I don’t think they do anymore since Gamma took over. Someone more familiar with the studio might correct me on both counts though.)
As for the “good” scene from this example, I see zero reason to delete it as well. There’s a smaller number of “bad” fingerprints attached to it, but so do most scenes on StashDB. Just because that scene had a duplicate doesn’t make the situation any different from the others.