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

Add example for movie libraries splitted by language #22

Open
roboyoshi opened this issue Apr 17, 2019 · 4 comments
Open

Add example for movie libraries splitted by language #22

roboyoshi opened this issue Apr 17, 2019 · 4 comments
Assignees
Milestone

Comments

@roboyoshi
Copy link
Owner

roboyoshi commented Apr 17, 2019

Just so it was mentioned or can be tracked somewhere how one might want to go about it and what the Pro/Cons are.

  1. Have all in the same folder
  2. Split them at the higher level (movies-en, movies-fr, movies-de, ....)
  3. Split them at the movie level ('movies/The Movie (Year) [en]', 'movies/The Movie (Year) [jp]'
    ... and maybe more..

Update:

As commented, there is also the option to move the language 1 level higher.. which is useful if you have a lot of different language content (en,de,fr,es,nl,ru,...).

TODO:

  • Extend the README for videos to include the alternative listed here with Pro/Con arguments.
@fionera
Copy link
Contributor

fionera commented Jun 4, 2019

I personally have them in root/video/german/movies/ but I dont know if root/video/movies/german/ is better

@roboyoshi
Copy link
Owner Author

I personally have them in root/video/german/movies/ but I dont know if root/video/movies/german/ is better

@fionera thanks for the comment. While that works pretty well, I think it duplicates too much of the hierarchy if you have a small amount of different languages. But I always like to see practical examples so for some (legit) reason you do it the other way around and that makes me think a bit harder about the problem at hand.. If I'd scale this filetree to ~20 languages, then I'd also argue that your approach would work better. It's therefore a nice alternative that I'll have to keep in mind.

@roboyoshi roboyoshi added this to the 0.3 milestone Jun 18, 2019
@roboyoshi roboyoshi self-assigned this Jun 18, 2019
@roboyoshi roboyoshi changed the title Give example for movie libraries splitted by language Add example for movie libraries splitted by language Aug 16, 2019
@roboyoshi roboyoshi added the :medium A Medium Task label Aug 16, 2019
@fionera
Copy link
Contributor

fionera commented Oct 30, 2020

Another solution would be to have another folder level in the folder of the movie itself. 'movies/The Movie (Year)/en/

@WEKarnesky
Copy link

I think curation for languages is dependent on how much you have and your focus.

'movies/The Movie (Year)/en/ is useful if you have lots of videos in multiple languages and it isn't encoded as a single file.

In other use cases, such as mine, where the focus is the nationality of origin, you have a high quantity of a limited set of languages being tracked, and most videos are only in a single language `root/video/japanese/movies/The Movie (Year)' allows for finding the way you might think of it (e.g. I want a Japanese movie/series). This also accounts for the rare times where two completely different countries make a show with the same name.

Both methods are valid, but different use cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants