Work around for issue with shared photo folder

1

Hi,

We’re still working on setting up our project within the bounds of our institution’s IT policies, and have learned that the settings do not allow Tropy to directly access our photo folder if it is stored on One Drive/Share point. Our IT is telling us that we must download the folder to our individual laptops to allow Tropy access.

Has anyone come up with a workaround for a project with multiple users where the photo folder must be stored locally? To the best of my understanding, I believe that we could update our locally-stored photo folders from the most recent cloud version and then have identical photo names, etc, but I’m still unsure if there is a way to manage the fact that the folders on our desktop would inevitably have individualized path names, which would impact Tropy’s ability to reconcile. Is it plausible to reset the path name each time a user opens the files? Or if we download a folder that contains both the photos and the most recent version of the Tropy database, would the relative file pathway settings reset for each device?

Thanks in advance - I’m a historian working at the very edge of my tech knowledge, so I hope this even makes sense!

2

In principle, using relative paths to store the paths should work around this issue. For this to work, paths to the photos can be different on each computer, as long as the relative path from the project file to the photos is the same. The most straightforward example is if the project file is in the same folder as the photos (or the same root folder if you use a nested folder hierarchy). For example, if you have the same photo folder, downloaded on two devices you can create the project in the folder on one device, import photos, and then send the project to the other device.