Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Update] Clarify Existence of Studio-Specific Exceptions and Conventions #65

Open
AdultSun opened this issue Oct 22, 2023 · 0 comments
Open
Labels
update section Update to existing documentation

Comments

@AdultSun
Copy link
Collaborator

We could use some clarification in Correcting Scene Titles and/or Preferred Scene Titles regarding the existence of studio-specific conventions we have developed over time. Most of these studio-specific title conventions function as an extension to the existing language for appending something like - Scene 2 at the end of a title when appropriate. Even though we prefer unaltered "original official" titles from the studio, we allow exceptions for differentiating ambiguous titles from within a studio.

For example, repeat appearances on Jesse Loads Monster Facials almost always share the exact same scene title since they just use the performer's name. This is complicated by the fact that JLMF's public website is difficult to navigate, with users required to find and manually copy most scene information from the homepage instead of the dedicated scene page that only includes a scene title and trailer. Since the title slug of the studio link includes a number for repeat appearances, we've taken to renaming these scenes to follow the pattern Performer Name 2, Performer Name 3, etc. to help differentiate scenes that can be very easily confused for each other.

Discussion on Discord has also pointed out a few different examples of gay studios that do not have a single clear, unique title on their website. At least one of these studios uses multiple variations of the title displayed in different areas around the website: one on the scene page, another on the performer page, a third above the comment section, etc. This requires contributors to agree which variation should be considered the "official" title for consistency on StashDB.

Studio-specific conventions are unavoidable for other fields too. Sometimes scene covers and studio codes can be ambiguous as well, requiring a decision to be made on how the guidelines should be interpreted for a particular studio. A similar problem develops with studios who are known for changing scene titles, covers, dates, descriptions, etc. over time as well. While we have more specific guidelines to address these conflicts, it would still be helpful to be able to point out to contributors which studios have a known track record of changing particular fields.

For example, Tonight's Girlfriend replaced all of its scene covers a few years ago, prompting many contributors to attempt replacing "incorrect" images on StashDB after running a fresh scrape. On the other side, sister-network Naughty America didn't have clear "original official" titles for most of its existence (and the closest equivalents aren't helpful as unique identifiers) so its titles exist in a unique situation where fresh scrapes are allowed to replace older titles since the older titles aren't "original official" titles either. But that's difficult to communicate to new users with less experience handling these studios on StashDB.

It would likely be too difficult to maintain a list of studio-specific conventions within the guidelines website, but it would be helpful to have some resource to point to for new users. Perhaps we could add a page describing what we mean when we say "studio-specific conventions", explain how they're expected to be followed just like other unconfirmed guidelines, and maybe link to an issue in this repo dedicated to tracking these conventions. An issue should be much easier to update and maintain compared to the Jekyll docs. Echo6ix has also suggested a couple different options for tracking discussions and conventions within StashDB requiring new features developed for stash-box:

stashapp/stash-box#574
stashapp/stash-box#700

@AdultSun AdultSun added the update section Update to existing documentation label Oct 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
update section Update to existing documentation
Projects
None yet
Development

No branches or pull requests

1 participant