stashapp / stash-box

Stash App's own OpenSource video indexing and Perceptual Hashing MetaData API
MIT License
220 stars 63 forks source link

[Feature] Studio ownership history and studio code format #820

Open sleetx opened 2 weeks ago

sleetx commented 2 weeks ago

A common issue with tracking Studio content is understanding the studio's ownership. Over time, studios may operate under different ownership or distribution groups, or the studio goes defunct and their library gets sold to 3rd parties.

I suggest adding a section to the Studio page where we can enter what years the studio was actively releasing content as well as date ranges of their ownership. This will assist in identifying the original source of studio content compared to re-releases. It will also help answer questions like "where can I find this defunct studio's content today?"

In addition, let's add a place to input the studio's scene code format, which can assist with scraping and identification.

echo6ix commented 2 weeks ago

this will assist in identifying the original source of studio content compared to re-releases.

Wouldn't this be creating redundancy since that goal is precisely what #663 -- Release Groups aka Master Release & Versions -- aims to accomplish, using a paradigm that Discogs and MusicBrainz have more-or-less perfected.

Every object has a master release (the original source), and all derivative releases are associated back to the master, creating a historical chain of versions that always flow back to the original source.

Or are you requesting a type of Release Groups paradigm specifically for studios as a way to track their genealogy so to speak? That would be interesting, and probably useful, since I think anytime a studio/site/company changes their name or brand, they should technically get a new corroborating entry to match the change rather than retroactively changing the name associated with past releases. I believe from an archival standpoint that would be the purist/correct way.

sleetx commented 2 weeks ago

Or are you requesting a type of Release Groups paradigm specifically for studios as a way to track their genealogy so to speak? That would be interesting, and probably useful, since I think anytime a studio/site/company changes their name or brand, they should technically get a new corroborating entry to match the change rather than retroactively changing the name associated with past releases. I believe from an archival standpoint that would be the purist/correct way.

Yes this is more about studios as a whole, and being able to identify their status in any given year. I'm thinking of something like a genealogical timeline... It would help give a complete picture of when, where, and why their content is being published or re-published.

Let's take a generic "Studio X" for example, and how StashBox could track the life and ownership of that studio. Here's an example:

Studio X ~ Active: 2000-2012

Ownership timeline: