(Added) I see Léonie has already answered 😁 .
jtbnyc wrote:
Do you mean that I should assemble the images for export into a new project and then export that project rather than tagging a group of individual images and exporting those? I tried the individual image export as a library and it worked (Thank you!!) but I want it to be as simple as possible.
Each works. Depends on what you want to have in the new Library.
My suggestion: Put the Images in an Album (a regular Album), select the Album, and export it as a Library. The new Library will contain every Project that contains an Image in the Album. Then you can re-organize this Library to meet your needs, without messing up whatever organization you have in your current Library.
After you are satisfied with the new Library, you can delete the Album in the old Library (or not -- Albums contain what I'm going to start calling "replicates"; they take up very little storage).
jtbnyc wrote:
BTW: I went to the genius bar (NYC 14th St) with this problem and no one could make it work, they all decided it was an app error that needed a patch.
The Apple Store "Geniuses" have a lot of ground to cover. Generally they do an excellent job. Their understanding of any particular app is, however, understandably shallow. The expertise freely given on this forum is deep. Please tell them you found a solution and recommend that they consult here for issues they cannot resolve.
--Kirby.
(Special note for Léonie and others: What do you think? "Duplicate" is a second object; "Replicate" is an instance of the same object. I came across this (with a minor change) in looking into using DevonThink. Fwiw, in ten years users will be as familiar with duplicates, replicates, albums, smart albums, and folders as they now are with files and folders.)
Message was edited by: Kirby Krieger