+1 to this, I raised the point a while ago as https://yabb.jriver.com/interact/index.php?topic=94080.0We agree in principle.
why isn't it just a question of jriver tokenising the value as it stores it in its database? you have to pick various paths as the root for all this content anyway after all so replacing that as $MOVIES_ROOT$ (or whatever) seems like it would be sufficient
We agree in principle.sounds promising, I will live in hope :)
+1 to this, I raised the point a while ago as https://yabb.jriver.com/interact/index.php?topic=94080.0
why isn't it just a question of jriver tokenising the value as it stores it in its database? you have to pick various paths as the root for all this content anyway after all so replacing that as $MOVIES_ROOT$ (or whatever) seems like it would be sufficient
I have not fully thought it through but I think the token approach would meet my requirements in an easy fashion. I would then define the variable locally on my client and could then easily do some search and replace to fix the database. It also addresses the issue when running imports from different clients. The prefix would be recognized and replaced by the variable before storing into the database. This could not be achieved by path substitution. However a regex like path substitution would still be needed to adjust path separators (forward / back slashes).Michael, could you describe in some detail how you are accessing your library from clients? There are many possible permutations and I want to make sure I understand your use case. Thanks.
I will be looking forward to seeing that feature.
Kind regards
Michael
If you are working on this, could you also think about restructuring a file system based on metadata ?
This already exists, check "Library Tools -> Rename, Move & Copy Files", you can re-organize the physical storage of the files according to any tags or expressions.
Michael, could you describe in some detail how you are accessing your library from clients? There are many possible permutations and I want to make sure I understand your use case. Thanks.
Michael, could you describe in some detail how you are accessing your library from clients? There are many possible permutations and I want to make sure I understand your use case. Thanks.
| Library files and covers: | \\mediaserver\shared\ |
| Music files: | \\mediaserver\music_lib\ |
| Video files: | \\mediaserver\video_lib\ |
| Content | Win Drive | Win UNC | Mac OS/X | |
| Library: | S:\ | \\mediaserver\shared\ | ~/mnt/share | |
| Music files: | T:\ | \\mediaserver\music_lib\ | ~/mnt/music_lib | |
| Video files: | U:\ | \\mediaserver\video_lib\ | ~/mnt/video_lib |
| Variable | Windows | Mac OS/X |
| $MUSIC: | T:\ | ~/mnt/music_lib/ |
| $VIDEO: | V:\ | ~/mnt/video_lib/ |
This already exists, check "Library Tools -> Rename, Move & Copy Files", you can re-organize the physical storage of the files according to any tags or expressions.
With the exception of the different path separator \ or / everything looks fine. I appreciate that during scan a clever mechanism to identify the appropriate token need to be found.
You would also need to consider case sensitivity in Linux and case insensitivity with Windows.
Sorry for the lengthy note, but I am trying to give a complete answer: I do have a Linux based server hosting all media files, covers and the libraries. The files are shared by SMB as the majority of the clients are Windows based. Right now I do have the following setup:
The Linux server provides the following SMB shares:
Library files and covers: \\mediaserver\shared\ Music files: \\mediaserver\music_lib\ Video files: \\mediaserver\video_lib\
Under Windows I historically use drive mappings but I am in the process to change to UNC paths. With Mac OS (or other Unixoide systems) I would need to mount the remote paths into the local filesystem.
Content Win Drive Win UNC Mac OS/X Library: S:\ \\mediaserver\shared\ ~/mnt/share Music files: T:\ \\mediaserver\music_lib\ ~/mnt/music_lib Video files: U:\ \\mediaserver\video_lib\ ~/mnt/video_lib
Following the mappings above the same physical file "(1) Sample.mp3" would be found by
Win: T:\CDs\Artist\Title\(01) Sample.mp3
Mac: ~/mnt/music_lib/CDs/Artist/Title/(1) Sample.mp3
With the "token" approach from above, I would set the following variables on the clients:
Variable Windows Mac OS/X $MUSIC: T:\ ~/mnt/music_lib/ $VIDEO: V:\ ~/mnt/video_lib/
Pending on the Client MC would then store the filename as
WIN: $MUSIC, CDs\Artist\Title\(01) Sample.mp3
MAC: $MUSIC, CDs/Artist/Title/(01) Sample.mp3
With the exception of the different path separator \ or / everything looks fine. I appreciate that during scan a clever mechanism to identify the appropriate token need to be found. Probably longest match would be a good approach. You would also need to consider case sensitivity in Linux and case insensitivity with Windows.
Does that make sense?
Regards,
Michael