P: Allow Catalog to be stored on a networked drive.

That works, sure. Using XMP as the data sharing mechanism. Why have a catalog then? Why not use Bridge? I guess the nicer LR GUI is enough reason...

So where do you store master files? On a network volume? I guess that works too but might be a tad slow, no? If not, then you still have to fetch the master files manually to all computer that need them, along with the XMP. At this point, why not copy the catalog to all computers? I admit that sharing the XMP is faster than closing LR, copying the catalog and reopening. Stil not an elegant solution.

This is a interesting "workaround", still not integrated to the software...

You have been advocating workarounds all the time and I salute your ingenuity. I also have my little tricks that work and may inspire from this last one you presented. But at the end of the day, the reason why we are talking here is to come up with enhanced features, in LR, built by Adobe, to achieve fluid and reliable collaboration and sharing/replication of our data. Pictures and metadata.

The big discussion was around SQL vs SQL lite. Your proposed "solution" is based on sharing the xml sidecar files over a network, which is even more archaic and bug prone than a centralized database.

Also, it does cover the sharing part but is not helping the master catalog approach. You are essentially proposing to replicate the whole catalog to all computers using the XMP instead of sharing the catalog (or just work with sub sets of the whole catalog). What if I want the whole thing and search through the complete library of images? I use bridge on the network volume or I have to recreate the whole catalog on my computer?

And what about collections?

So long as no-one tries to use Collections 😉

To clarify 'local' catalogs. I'm using external eSATA connected G Tech drives, not local homes (System drive)

Perfect it isn't, but, far more of a collaborative workflow it is.

I have also been able to start the workflow with Photo Mechanic, changing Tags, adding metadata, colour tags and ratings. This then populates through to each connected user.

Edits have to be exported to view edit settings, but Editing is a personal thing. Are you going to want B user finish A users edit off?

I would assume A user would get approval of his or her edit, then finish and export the desired file.

Editing in progress can be send via email, or uploaded, or even published via any number of online services

OK, so I have got 3 users all being able to exchange XMP data, track edits and sync. Caveats being you have to create separate Catalogs on each machine and 'add' images to the library, not move, from a central location.

Ensure that you have write XMP data ticked in your catalog settings.

Create a new catalog locally. This brings into play the idea of backing up etc etc.
Point your catalog to the shared folder you need and add your images.

For added collaboration, export all filters and presets, plug ins and edit prefs. Importing into each LR user (easily done )

Do this for the users you need, ensuring you have XMP write data checked in catalog settings.

Any change made will update your image status either by importing settings from disk



or syncing the desired folder



I have tested this with 3 users on a LAN, ie my running round 3 machines. I can track all edits, track metadata, add and edit metadata, apply edits and export each version (to another server folder called Edits, for example)

The XMP isn't the quickest to update, but it's pretty instant.

Et voila!, LR on shared storage

Any of my recent "normal" shoot. I did a lot of product shoots recently. I need to edit the photos to a degree, then share the results to my "client" (who happens to work with me) so he can rate and select the shots and maybe apply some tentative crops. Then I want the metadata to flow back into my catalog so I can work more on the photos. I have done many projects recently like that.

I am also working on a collective where we want to share images. We can share exports (jpegs, etc.) but it is nice to be able to see the actual dev settings to comment and collaborate on the processing approach.

The only viable way now is to export the files into a new catalog. Share that somehow via a network, a USB key or ftp, dropbox, etc. Then the other user opens that catalog and do his work. Then send me back that catalog and I "Import from Another Catalog" back into mine with the other user's change.

These are just two examples. I don't think I am alone in this situation. If I were, there would not be an export/import function to start with.

This works but has issues:

- The export/import process is a tedious, takes time and does not allow me to continue to work while the images are being changed by the other user. If I do, I either loose my work (it's still in the history but) or end up with a virtual copy on the side that I have to merge manually. If there was a way to import just the metadata or the dev settings independently, that alone would help. A proper merge screen would be great too. Should be possible considering a XMP file is just a "recipe", a list of operations "to do during export" and it would be great to select which steps to take or not from the import.

- The actual sharing of the exported catalog (and master files) has to be done manually outside of LR. I can use ftp, dropbox, etc. But it is still not integrated to LR. Exporting the catalog with the digital negatives help as the photos end up in the same folder as the exported catalog. Then it is just a matter of sharing that folder, no need to "gather" the master files. Still, I wish I could just allow a user to connect remotely to my catalog, browse, edit and see the changes appear instantaneously, without having to Export, copy/send, wait, Import...

I know how to deal with it within the current LR limitations. I don't contribute to that thread to have help on how to deal with LR shortcomings. I just wished there would be an integrated, easy way to collaborate with my team members. Something that would not force me into figuring out a compromise solution...

I realize I might have been spoiled by more robust collaborative systems in a previous life. I still think there is room for improvement...

"You ask to hear about "facilities" that require to access catalogs remotely? I am one, Axiom seem to be another and I work with a bunch of people that would benefit from that."

Again, you've told me you want it, but you haven't really given me a reason why you need it. Can you describe a normal shoot and how you are handing files off to the other users, and how having LR in a 'remote' state would be beneficial.

Aside the obvious tracking of history, edit presets and filters from the LR GUI

I'm concentrating on the users that occupy an office as far as using a network system is concerned. That is more difficult to achieve with LR in it's current state.

I would argue that the 'Online' collaboration you speak of is already totally possible with LR. Ok, you may not have a check in/check out possibility, but publishing RAW files to a central location is more than possible.

You would then get into versioning these edits. A single FTP shared folder where RAW files pop in, you work on them and export them out, or publish an edit back to the FTP.

For anything more robust, you'd not be using LR in my opinion

Elvis, as in the DAM. http://www.woodwing.com/