Zum Hauptinhalt gehen

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Problem after importing one catalog into another

Colin Chisholm
So I open my main catalog and run an Import Catalog to pull in another catalog into the main catalog.
I can see from the results, this is not really merging the imported catalog into the main catalog!

Specifically the concerns is that: the images cannot be found or relocated via context menu (right click) "Show in Finder" / "Locate..." menu items ... instead, under "Folders" list, the newly added images show under a special "In Catalog" entry (showing as an icon I assume is a Catalog), separate from all the rest of the photos which show under a folder hierarchy under an icon for the hard drive where those images live.

I want to truly merge these two things together, so the imported Catalog will end up as part of the main catalog, with the images in the same hard drive (I am expecting to have to copy photos and then relocate in C1 to do this), and the new "In Catalog" item eventually being deleted.

Is such a merge possible? If so, how would one do that?
0

Kommentare

8 Kommentare

Datum Stimmen
  • Eric Valk
    There are two ways images files of a catalog may be stored.

    One way is called "referenced" - the image files are store in OSX foldders.

    The other way is called "managed" - the image files are stored inside the Catalog itself.

    Capture One shows Managed images in the "In Catalog" part of the Library, and Referenced images in the "Folder" section of the Library. The folders in the Capture One Library are the same folders you see with Finder, and with Finder you can the same image files.

    (The real power of a Catalog lies in its user collections, which allow you to organise images without changing the storage location. But I digress)

    What should happen if one Catalog is imported into another is that managed images remain managed (image files copied inside the new catalog) and referenced images remain referenced (files located outside the catalog)

    I suggest that you check the Catalog that was imported into your main catalog, and see if the images were Referenced or Managed. If they were managed images in the other catalog, then that explains why they are managed images after the import. (occasionally I have imported images from a camera into a catalog, and mistakenly import them as managed instead of referenced - easy mistake to make)

    If however the other catalog has the image files as Referenced, then they should have stayed that way after the import, and you should open a ticket with Capture One support.
    0
  • Jerry C
    The short answer is you can't merge catalogs in the sense that I think you mean. C1 cannot relocate imported variants (images) into albums corresponding to the albums in the catalog you or importing, nor can it import referenced files into folders with the same names and positions in the directory tree that match the source's directory structure. It would be nice if it could, but even if it could, you would have to ensure the structure of the imported catalog matched the related structure of the catalog into which it was imported. This requirement leaves a lot of opportunity for unexpected results and I expect this is why the engineers have stayed away from it. Thus, the import shows up as a separate entry that you have to move around manually.

    Eric raises an important point regarding referenced files staying as referenced files. In this, there is one more thing to be aware of. When you import a catalog with referenced files, the referenced files are not moved. C1 allows you to have referenced files in any location you can locate. When you import a catalog with referenced files, you do have the a couple of options for where the imported files go if you don't want to leave them where they are. You can have C1 locate them as managed files in the catalog into which your are importing or you can have C1 import the files to a new folder. The options are shown in the Import dialog box. There is no option to move files to more than a single folder when importing.

    Jerry C
    0
  • Colin Chisholm
    Eric & Jerry - Very helpful info, thanks!
    I wasn't aware of the referenced vs managed distinction (sounds like how Aperture worked).
    I am trying to figure out my options now.

    Here is the sequence to this point:

    • Master catalog of referenced images exists on my mac.

    • Copied master catalog to a portable drive and used it on a PC: to that copied library I added one new folder of (referenced) images from my vacation.

    • I then exported from the PC that new folder of images as a catalog: obviously that resulted in a new catalog of MANAGED images.

    • That exported MANAGED catalog of vacation photos was imported to Mac master library...as MANAGED images, my position today.


    ASSUMPTION: The folder-export-as-catalog results in a new catalog of MANAGED images, and there doesn't seem to be an option to create an export to a new catalog of REFERENCED images.
    BUT maybe that assumption is not correct: if I leave the "Also include Referenced Originals" checkbox UNchecked, does THAT create a new catalog of REFERENCED images??? I can test,maybe someone here knows?

    So I have two options:
    Case 1 - Assumption was correct: In this case, in my copied library on PC portable drive, delete EVERYTHING EXCEPT the one new folder! Then this catalog can be copied to Mac and imported to master library! Should be REFERENCED images.
    Case 2 - Assumption INcorrect: just re-export folder-as-catalog but leave that checkbox UNchecked. If I then import that catalog on Mac into master catalog, it should be REFERENCED images again!

    I will try some experiments to confirm, but if anyone knows more, please advise to save me some testing!

    Thanks
    0
  • Eric Valk
    I would choose Option 3 😄

    1) With Capture One, open the Master Catalog.

    2) Make a new Folder for your managed images. Select an existing Folder, right click, select "add folder"

    3) Drag the images (image files actually) from "In Catalog" to the new Folder.

    Done.
    0
  • Colin Chisholm
    [quote="Eric Nepean" wrote:
    I would choose Option 3 😄
    ...


    Cool - that would be very easy if it works!
    I will try that tomorrow and advise! 😊
    Thnx
    0
  • Eric Valk
    It has come to mind that there is a bug in the current 12.0x release that causes Capture One to fail to execute if you use it to move an image file from one drive to another.

    This manifests itself if you have two folders on different drives, and you attempt to move an image file from one folder to the other folder.

    I think it also manifests itself if you try to move an image file from the catalog to a folder on a driv different to the one where the catalog file resides.

    The workaround (if you have the problem) is to create a folder on the same drive as the catalog, and move the image files to that folder. Then, close Capture One, copy the folder to where you want it the other drive, move or delete the first folder so Capture One can't find it. Now use Capture One's Locate function to find the new folder. Use the locate function on the folder in the Catalog Library (not on each image).
    0
  • Colin Chisholm
    Hey Eric - thanks again for that last tip.

    So I just tried your idea: and for kicks I did NOT first move/create the managed images on the same drive as the rest of my (referenced) images.

    Good news - it worked with no issues!
    (I have version 12.0.2 FYI).

    So it was super easy.

    Thanks again!!
    0
  • Jerry C
    [quote="Eric Nepean" wrote:

    The workaround (if you have the problem) is to create a folder on the same drive as the catalog, and move the image files to that folder. Then, close Capture One, copy the folder to where you want it the other drive, move or delete the first folder so Capture One can't find it. Now use Capture One's Locate function to find the new folder. Use the locate function on the folder in the Catalog Library (not on each image).


    The problem is not specific to the location of the files relative to the catalog. The bug prevents you from moving any file from one drive or partition to the other. This makes the solution more straigtforward.

    So, the simplest way is to create a folder (if it does not already exist) on the drive you want the referenced files to be located on ultimately and import into that folder. If you want to move the files to other folders on that drive, you can. You just can't move files from one drive/partition to another.

    Jerry C
    0

Post ist für Kommentare geschlossen.