[Feature] Parent studios

[OffspringFan88]

Is there a way currently to add images for series e.g Big Tits at Work and add this under a Studio? At the moment I'm adding the series under studio with the logo or adding them as Tags.

[StashAppDev]

Right now images (galleries) are tied to scenes since a lot of paid sites have both a video and a gallery of images for any particular scene. Are you saying that you want to see all of the galleries from a studio, rather than just the scene?

[OffspringFan88]

No what I mean is can you have another tab like the Studio one and have it as Series.

Sort of like a sub category of the studio, so for instance Brazzers have a lot of different series under their banner, so you could have Brazzers as the studio and then link the different series under their banner.

At the minute I've had to do all the series in Studio to due to them being so many.

[echo6ix]

I think @OffspringFan88 is essentially requesting Parent Studios, which you added to the medium term road map:

Parent Studios
Some studios actually contain other studios. For example Team Skeet would be the parent studio to Teens Like It Big, etc. Add support for this and mock up how this would change the studio list.

[OffspringFan88]

Yes! @echo6ix thats exactly what I meant! Thank you for clarifying.

Would love this to be added down the line!

Do we have an idea on when this would be included in a future release?

[echo6ix]

@OffspringFan88, no idea when this would be included other than when the developer or contributors get to it. I can start mocking up some concepts of how this would change the studio list.

It might be helpful to change the topic to something more accurate of what the dev already acknowledged to be a useful feature request, like [Request] Parent Studios, just so it matches the roadmap description.

[echo6ix]

I made this UI "studio list" concept pretty hastily. Some logos and thumbnails are recycled throughout the concepts even where not relevant, don't read into it other than laziness. I suppose these are also related to #108

Channels, probably a more suitable term to use than studios

One thing I realized when creating these concepts is referring to this section as studios isn't representative of the content. I would recommend renaming the studio section to channels because we're not necessarily creating studios specifically. A channel is broader term than studio and it can be representative of whatever the user wants. We can think of channels as having one or two parts: (a) the parent channel, and (b) the option to hold sub-channels.

Channel/"studio" list page

Both parent and sub-channels are displayed as thumbnail cards in a grid view.

• This concept shows how the user can filter between parent and sub-channels using the filter option.
• Currently Stash displays the logos as full bleed, and some go right to the edge of the card. I personally think the logos look better with padding/margins so that's how I made them in this concept.
• You can see how one channel card has a "cover image", which the user would upload in the per channel edit page. I think this is an elegant way to further customize the channel cards.
• For the default channel logo (when no image is selected for a channel) I used a vector icon, and would recommend FontAwesome if it's possible. Using CSS vector icons lets you easily style the color of the icon and allows for more custom possibilities. Eg. You could let user select a channel hex colour, which is displayed on the stock vector icon when no logo is uploaded. Using a jpg/png locks you into graphic.

A. Parent channel
The parent channel would be like the studio name, network name, an amateur web site, production company, distributor, platform name, etc. The parent channel is the top of the channel hierarchy, and obviously there can only be one parent channel per channel.

B. Sub-channels
Sub-channels are a division of the parent channels, and they can only be assigned to one parent channel. They would be the equivalent of a series produced by a network, or the name of an amateur studio (content creator) hosted on a platform. For example, ManyVids is the platform (parent channel), and the amateur studio name is the sub-channel.

Channel and sub-channel creation, editing channel info, and deletion

• When making a channel the user can select the type of channel: parent channel or sub channel.
• If sub-channel type is selected, the user has the option to assign it to a list of the available parent channels from the database. They can always go back and change these settings by reassigning to a different parent channel, or by changing their channel type to parent.
• If a user wants to delete a channel they should be prompted with a modal window informing them the parent channel has sub-channels attached to it.
• If they choose to continue the parent and all assigned sub-channels will be deleted.

Editing cover image

• The user still has the option to upload a channel cover image in the per channel edit page
• Additionally, the user can also enable/disable a toggle in the per channel edit page to have the cover image use one of the generated scene thumbnails from a scene that is assigned to the channel.
• They can have the cover image use the thumbnail from the last "created_at" scene, a random scene, etc.

Note: These concepts are obviously made for a desktop viewport. Some aspects would need to be revised for a mobile viewport.

Edited: Aug-29. Added more detail in to the above image. I know the organization/arrangement of the edit panel is bad. I just wanted to show the functionality of it.

[OffspringFan88]

Yes!! This is exactly what I’d love to see! Great concept even if you made it quickly it still looks great!! From: echo6ix <notifications@github.com> Sent: 29 August 2019 03:41 To: stashapp/stash <stash@noreply.github.com> Cc: OffspringFan88 <markwindass@hotmail.com>; Mention <mention@noreply.github.com> Subject: Re: [stashapp/stash] [Request] Series images (#115) I made this UI "studio list" concept pretty hastily. Some logos and thumbnails are recycled throughout the concepts even where not relevant, don't read into it other than laziness. I suppose these are also related to #108<#108> Channels, probably a more suitable term to use than studios One thing I realized when creating these concepts is referring to this section as studios isn't representative of the content. I would recommend renaming the studio section to channels because we're not necessarily creating studios specifically. A channel is broader term than studio and it can be representative of whatever the user wants. We can think of channels as having one or two parts: (a) the parent channel, and (b) the option to hold sub-channels. Channel/"studio" list page [studio concept]<https://user-images.githubusercontent.com/37937507/63905857-94a34d00-c9e3-11e9-8de0-82a1cd8a699c.png> Both parent and sub-channels are displayed as thumbnail cards in a grid view. This concept shows how the user can filter between parent and sub-channels using the filter option. A. Parent channel The parent channel would be like the studio name, network name, an amateur web site, production company, distributor, platform name, etc. The parent channel is the top of the channel hierarchy, and obviously there can only be one parent channel per channel. [parent channel page]<https://user-images.githubusercontent.com/37937507/63905984-01b6e280-c9e4-11e9-833e-c1f937bcc114.png> B. Sub-channels Sub-channels are a division of the parent channels, and they can only be assigned to one parent channel. They would be the equivalent of a series produced by a network, or the name of an amateur studio (content creator) hosted on a platform. For example, ManyVids is the platform (parent channel), and the amateur studio name is the sub-channel. [subchannel page detail]<https://user-images.githubusercontent.com/37937507/63905998-0c717780-c9e4-11e9-9a5c-9c0a8e561db6.png> Channel and sub-channel creation, editing, and deletion * When making a channel the user can select the type of channel: parent channel or sub channel. * If sub-channel type is selected, the user has the option to assign it to a list of the available parent channels from the database. They can always go back and change these settings by reassigning to a different parent channel, or by changing their channel type to parent. * If a user wants to delete a channel they should be prompted with a modal window informing them the parent channel has sub-channels attached to it. * If they choose to continue the parent and all assigned sub-channels will be deleted. [subchannel page edit]<https://user-images.githubusercontent.com/37937507/63906002-109d9500-c9e4-11e9-8e73-3e7de664e910.png> Note: These concepts are obviously made for a desktop viewport. Some aspects would need to be revised for a mobile viewport. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#115?email_source=notifications&email_token=AM7TR3JHGPDHLMOLS7F2WXDQG4ZJ5A5CNFSM4IPGFPLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5NBJPA#issuecomment-525997244>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AM7TR3KF3MALR6YEETDNLITQG4ZJ5ANCNFSM4IPGFPLA>.

[echo6ix]

I didn't fully explain the concept of the channel tags in the attached image. The channel tags should just be a list of the top tags used (by count) associated with the scenes that are assigned to said channel.

When I first created it I was thinking of displaying the proposed "studio tags" that would be used for the auto file based tagging feature, but the aforementioned idea is better.

[echo6ix]

Here's another updated version of a channel page, specifically a "sub-channel."

Stuff I added in this concept:

Country flag

• Users can select a country for a channel from a drop-down list in the channel edit panel.
• The country flag is displayed in the attached image, and clicking it would take you to the channel list grid view page, and automatically filter all channels by country. This could be useful for sorting foreign channels.

Performers panel
This displays all the performers in any scenes associated with a channel. I don't know how this wasn't on my original concept. It's basically the equivalent of the "models page" on any porn web site. Clicking a performer would take you to all their scenes assigned to the channel.

[OffspringFan88]

Loving all of this @echo6ix.

This is pretty much what I've been looking for as a lot of my collection includes scenes belonging different series.

[Leopere]

This is a great issue!

[GernBlanston12]

Nice! Don't forget to extend the concept to vanilla tags, like "Lingerie" with sub-tag "thong", that would be cool.

Can they be nested/recursive? ex: "Adult Time -> Pure Taboo (sub) ->Future Darkly (sub of sub)"

[echo6ix]

Nice! Don't forget to extend the concept to vanilla tags, like "Lingerie" with sub-tag "thong", that would be cool.

@GernBlanston12 This is discussed in the road map, but states the concept needs to be fleshed out. Do you want me to start a new thread for it?

EDIT. I made a new thread to flesh out the concept of tag aliases aka sub-tags #121

[GernBlanston12]

Thanks, I was just thinking the two issues would have a lot of common architecture in their solves, whatever that turns out to be. With regard to inherited tags, for example, if I tag anything "thong", it would also tag the video with "lingerie" (i.e., "thong" is a sub-category of "lingerie" if I set it up that way). This also works well for sub-sites to internet studios ("Future Darkly" is sub of studio tag "Pure Taboo") as well as in the future perhaps accounting for series-to-studio relationships for DVDs. Parent tags should be accessible by regular means: I should still be able to tag a video with studio Pure Taboo, without having it show up with Future Darkly, but whenever I tag it with Future Darkly, it should add tag Pure Taboo. It's an "All beagles are dogs, not all dogs are beagles" sort of thing. Child tags, OTOH, imply always that the video should be parent-tagged as well, and this should be automated.

I guess it's as simple as: You create a "parent tag" list for each tag, and UI in the tags tab to add parent tags to individual tags on your list. Once there are entries on a tag's parent tag list, every time that tag is associated to a video, the program checks the "parent tag" list for that tag, and automatically tags the video with any parents on its list. You could also make a sweeper that would look over previous tag entries at program start, for new items on the various parent-tag lists. Or, you could make it part of cleanup to go through all tags associated to videos and add parent tags as necessary.

[echo6ix]

On Discord there was brief discussion about the concept of a "DVD object" or "Movie Collection" that would be a compilation of individual scenes that belonged to a movie.

I think this might integrate seamlessly with the above primary channel/sub-channel paradigm I've proposed to supersede and expand upon the current Studio page functionality. For example,

Primary channel name	Sub-channel name
Devil's Films {tag:studio}	Best of Bald Beavers {tag:movie}
Devil's Films {tag:studio}	Best of Internal Injections {tag:movie,blu ray}
Devil's Films {tag:studio}	Creampie Orgy Series {tag:series}
Brazzers {tag:web site}	Mom's In Control {tag:series}
Brazzers {tag:web site}	Pornstars Like It Big {tag:series}
PornHub {tag:platform}	{blank / no sub-channels}
ManyVids {tag:platform}	{Performer channel name here}
Reality Kings {tag:web site}	Reckless In Miami {tag:series}
Reality Kings {tag:web site}	Moms Bang Teens {tag:series}

Assigning scenes to a "movie" could be as easy as it is to assign a scene to a Studio or Gallery in the apps current state.

Functionally the user would:

• Choose an existing primary channel or create a new one.
• Create a sub-channel of the above primary channel called Whatever.
• Scene > Scene Edit > Drop-down filter list of channel/sub-channel names > Select Whatever.

Voila. A simple way to make a set of scenes into a movie using the channel/sub-channel paradigm.

Edit:

Channel image (logo/cover art) aspect ratio and size

Some users may have a cosmetic issue with the aspect ratio of the channel image if they use a movie's covert art for the channel. In my concept the channel cover art avatar is a 1:1 ratio image. Movie posters are typically 2:3 aspect ratio.

This could be addressed many ways. One idea is to change the channel cards/cover image aspect ratio from whatever it currently is, something like 1:1, to 2:3 aspect ratio. If the user wants the image to be displayed larger that option already exists with Custom CSS.

Other channel possibilities

I think this primary channels/sub-channels feature could be a robust way to organize and present studios, networks, platforms, movies, dvds, web-sites, etc with one all-encompassing and versatile paradigm, rather than cluttering the app and development by creating many independent niche enhancements for specific use-cases. Other possible enhancements to this paradigm might be:

• nested channels beyond one level
• ability to filter the main channels page by tags. for example, filtering by tag='movie' or tag='blu ray' to show all the users movies or more specifically just their blu rays.
• add metadata fields, such as director

[echo6ix]

I'm not sure I've done a good job articulating what channels would be, but I think it would probably be best to think of them as "playlists" or "smart playlists" that can contain "folders" in hierarchies. It might be easier to visualize how this would work using a treeview.

Channels
├── Studios
│   ├── Brazzers
         ├── MGB
│   └── Bang Bros
├── Amateurs
│   ├── collection name
│   ├── collection name
│   └── collection name
├── DVDs
│   ├── Title
│   ├── Title 2
│   └── Title 3
├── Amateur

This paradigm lets the end user precisely organize their content subjectively to their needs, rather than locking everyone into a rigid "studios" only page, "dvd" only page, etc. -- which in my humble opinion clutters the UI experience with a rigid organizational paradigm the user may not even use.

In the above treeview example, all those objects are terms the end-user would have created and organized. Another user may decide they don't won't so many nested studios and would have them all displayed under the umbrella of a primary channel called "Studios", "Networks", or whatever.

These channels could have attributes, such as an associated avatar(s), URL, tags, etc.

Where an end-user now selections a studio to associate with a scene, they would instead selection any of the available channels with a few exceptions, such as channels that act as "smart playlists", where a smart playlist would basically be a short-cut of a custom query using something like query-syntax from #185

TLDR Basically, organizing videos isn't much different from organizing audio. We attach metadata to both, and create playlists and smart playlists to organize them into collections based on their metadata, based on manual placement, or based on perceptual attributes.

[WithoutPants]

Would a scene still have a single channel/studio under this paradigm?

[echo6ix]

@WithoutPants That's a good question and it demonstrates that my channels suggestion was evolving more into a multi-node playlist paradigm and getting away from simply assigning a scene to a studio or it's subsidiary studio.

Everything I've said on this thread after this post is more about playlists than studios and if it's possible, I would split this thread starting here into a feature for multi-node playlists.

My idea was getting too convoluted and it's clear Stash needs a dedicated section for users to manage and browse networks, platforms, studios, websites, and all their subsidiary nodes.

To answer the question: (1) A scene should be able to belong to more than one playlist. (2) But a scene typically belongs to only one studio node. I think you can find exceptions with movies or video clips having more than one studio with the rights. But that exception to the rule doesn't change anything about studio management and presentation.