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

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

Open
sleetx opened this issue Oct 7, 2024 · 2 comments
Open

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

sleetx opened this issue Oct 7, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@sleetx
Copy link

sleetx commented Oct 7, 2024

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.

@sleetx sleetx added the enhancement New feature or request label Oct 7, 2024
@echo6ix
Copy link

echo6ix commented Oct 7, 2024

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
Copy link
Author

sleetx commented Oct 7, 2024

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:

  • 2000-2005: Studio X... (self-managed)
  • 2005-2010: Studio XYZ Group... (rolled into a larger entity that manages related studios)
  • 2010-2020: Big Media Network... (sold to this entity, which shut down the original studio in 2012. this company maybe re-publishes some old content under a different name)
  • 2020 - Present: Archival Media Site... (sold to this entity. although "Studio X" no longer exists, their back catalog is available here)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants