Unclear folder structure and refresh job result
I am confused (á bit) about the folder structure which is used for the user.
I configured a volume with this path:
/MobileUploads (underneath is an NFS mount)
The idea is to have for each mobile user uploading pictures a separate folder. This works almost exactly as expected; i see the latest uploads ending up here:
/MobileUploads/library/00-Frederic-Mobile/2025/02
Now, why almost? Because i cannot explain the library folder as an additional level - i would have expected this instead:
/MobileUploads/00-Frederic-Mobile/2025/0
But ok, it doesnt hurt - i would still like to understand it, though.
Now i also realized that some of my old mobile photos were missing in this structure underneath this folder:
/MobileUploads/library/00-Frederic-Mobile/2019/04
I wanted to add manually the missing photos to this folder and then run the refresh job - but it does not have any effect. Can i add missing folder into the folder structure or would this have to be created as an external library?
I configured a volume with this path:
/MobileUploads (underneath is an NFS mount)
The idea is to have for each mobile user uploading pictures a separate folder. This works almost exactly as expected; i see the latest uploads ending up here:
/MobileUploads/library/00-Frederic-Mobile/2025/02
Now, why almost? Because i cannot explain the library folder as an additional level - i would have expected this instead:
/MobileUploads/00-Frederic-Mobile/2025/0
But ok, it doesnt hurt - i would still like to understand it, though.
Now i also realized that some of my old mobile photos were missing in this structure underneath this folder:
/MobileUploads/library/00-Frederic-Mobile/2019/04
I wanted to add manually the missing photos to this folder and then run the refresh job - but it does not have any effect. Can i add missing folder into the folder structure or would this have to be created as an external library?