Studio tags is a must, at least for determining the sexual orientation of content.

To expand on this request, much like the performer gender, studio tags should have a dropdown selector with fixed values (straight, gay, trans, bi, lesbian, whatever) and must be selected when creating a studio so we can start filtering content based on sexual orientation.

While it would assist in determining the sexual orientation of content, things are not always so binary. Look at Brazzers, which is 99% straight but has been adding trans content more recently. There's always exceptions like that though, if a niche site would be tagged with that niche but then includes a lot of extra content like interviews, I wouldn't personally want those tagged with that niche. But that can be fixed in personal Stash so um I don't know, maybe this comment was pointless.

Another user wrote about issues with labelling studios as having a sexual orientation is not so simple, in more eloquent language than me: https://discord.com/channels/559159668438728723/798641040029777980/1103881921018200135

Studio tags would be reviewed and approved like any other. For studios where there are rare exceptions to a tag it would be up to the community to decide if the tag should be applied. Taking the case of sexual orientation one step further, the studios that have a small amount of mixed content are themselves an outlier, nearly all studios do not have exceptions and we shouldn't exclude this clearly very useful feature because occasionally a studio doesn't 100% match a particular tag. Also sexual orientation is only one example of how these tags could be applied, there are many other tags that could be applied at the studio level and again the community would decide whether a particular tag should be added.

Maista described a possible design for this feature on Discord. I like the idea so I'm writing it down here so we don't forget about it:

• We use our same pool of tags, just allow them to be attached to a studio instead of a scene.
• Studio-attached tags serve as a default suggested tag, automatically added to all "create scene" drafts/edits, but will not be included in "modify scene" drafts/edits.
• These default tags will be opt-out, meaning editors will need to remove these tags within the creation edit or with a follow-up edit later if they do not fit that particular scene.
• These studio-attached tags will not be applied retroactively, meaning existing scenes will be left untouched and any removed tags will not be re-added. In order for older scenes to catch up, we would most likely need to run a BOT script for them.
• Within the draft/edit form, any tags added because they're attached to the studio should be called out in some way. Otherwise, we're modifying the editor's submitted data without their knowledge and not giving them an opportunity to opt-out from adding those tags. But since we'd try to only attach tags to a studio that are "safe bets" to apply to all scenes underneath that studio, it shouldn't be a big deal if a user doesn't notice these inherited tags or if they forget to double-check them for any that need to be removed.

While I wouldn't want a "modify scene" edit to inherit tags from performers and studios by default, it could be useful to apply the same system but only if the editor decides to "opt-in". Then if they're still marked or separated as inherited within the edit form, the editor can decide which suggested tags to keep and which to decline.

As I write up this comment, it occurs to me that we could use this same system for inheriting performer-attached tags into scenes as well. This could speed up the process of remembering and manually adding performer tags that universally apply to every scene that performer ever appeared in.

Following on from 'default' tags for a studio. Eventually I'd like something like 'suggested' tags. Not to be automatically applied but suggestions based on the studio/performer or even combination of performers. These don't necessarily need to come from tags that have been manually applied to a studio/performer since they're just suggestions rather than defaults, but could come from the most often applied tags to that performer / studio. Possibly on an edit rather than a create the 'default' tags above could be used as suggested tags.