You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From Discord, there was some discussion surrounding edge cases for how we want our scene titles formatted. Specifically, there's some confusion around situations where the title as displayed on the website (via CSS) uses different casing compared to the title grabbed from the scraper (via page source or API).
The working consensus has been to defer to the formatting grabbed by the scraper. This is my preference as well, since the internal formatting is much more likely to stay static through multiple website redesigns, strengthening its case as the "original official title" we're looking for.
I would mostly update the unconfirmed guideline for Correcting Scene Titles, but we could also use a clarification that some exceptions exist in Preferred Scene Titles while linking back to that same page.
The text was updated successfully, but these errors were encountered:
From Discord, there was some discussion surrounding edge cases for how we want our scene titles formatted. Specifically, there's some confusion around situations where the title as displayed on the website (via CSS) uses different casing compared to the title grabbed from the scraper (via page source or API).
The working consensus has been to defer to the formatting grabbed by the scraper. This is my preference as well, since the internal formatting is much more likely to stay static through multiple website redesigns, strengthening its case as the "original official title" we're looking for.
I would mostly update the unconfirmed guideline for Correcting Scene Titles, but we could also use a clarification that some exceptions exist in Preferred Scene Titles while linking back to that same page.
The text was updated successfully, but these errors were encountered: