The paths are not that simple; if you have a shared folder the important part is not the path relative to that folder, but the path to the folder itself. For example, if we have shared folder, it could called
/Users/sylvester/Shared/Tropy but on your device, it could be called
/Users/jmorgan/Shared/Tropy – so each file in the folder would have a different absolute path on the two devices. If your setup is like that, you’ll need to use a portable, or ‘rebased’ project.
If your shared folder is at the same location on every device, e.g., something like:
/Volumes/University/X/Y/Tropy a regular project would be fine.
Tropy 1.7 is almost ready. There will be another beta release, likely tomorrow, and if we don’t discover any unexpected issues, this will be become the stable version – so later this week, or next week at the latest.
Regarding the different sharing needs, I think a lot of it may be covered already. It depends a little on what exact format you have in mind to show what images where used. By default, you can copy/export items to a JSON format which will include all the metadata, tags, notes, and paths to each photo; if you need something simpler you can use the CSV plugin and a custom template to export only a limited number of fields for each photo. Regardless of the export format, you can always export only a certain range of items (e.g., all items for given tags).
With the archive plugin you’ll be able to combine the exported data with the photos in a zip file (i.e., you basically save the step of adding the actual files to the metadata you exported).
Finally, you might want to take a look at the print feature: you can print or save to PDF any number of selected items (there are handful of print options/variables in the preferences window) – by default this will also include the photos themselves, so this might be useful as a concise overview format.