Skip to main content

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

Seperating Catalog file from folders: adjustment, cache,...

oliviersm
Hi all

When I create and open a new catalog in a folder, it creates these three folders as well: "Adjustments", "Cache" & "Originals".

Is it possible to separate the catalog from these folders, but still keeping the lync to them?

I would like to sync solely my catalog via cloud between my laptop & my PC.

Appreciate the assistance.

Cheers,
olivier
0

Comments

6 comments

Date Votes
  • Ian Wilson
    Moderator
    Top Commenter
    It sounds as though you are using "managed" images in your catalog - that is, the images are stored inside the catalog, in the "originals" folder. Have you considered referenced images instead, where the originals are stored in a folder on your computer, but the information about edits, etc is stored inside the catalog? See this short tutorial at about the 1m10s point.

    Ian

    (Edited to add the missing link.)
    0
  • oliviersm
    I'm not. The images are located somewhere else. It's the "cache folder" that gets pretty big which I would want to have stored locally per device as opposed to synced in the cloud. It takes too much space.
    0
  • SFA
    oliviersm wrote:
    I'm not. The images are located somewhere else. It's the "cache folder" that gets pretty big which I would want to have stored locally per device as opposed to synced in the cloud. It takes too much space.


    That folder system IS the catalogue.
    0
  • oliviersm
    I see. Is there no way to relocate the "Cache" folder to a folder separate from the .cocatalogdb files?
    0
  • SFA
    oliviersm wrote:
    I see. Is there no way to relocate the "Cache" folder to a folder separate from the .cocatalogdb files?


    Use sessions instead.

    That way the cache and the edits stay with the original image files. Should you so desire you could then delete the cache as it would be recreated the next time you open that image folder using C1. Obviously that only makes sense if you do not intended to open that session or access those images frequently - in other words they are effectively in an archive.

    But if you want the ability to see the contents of the session (or catalogue as you have it now) at a moment's notice then deleting the previews and thumbnails would be counterproductive.

    Moving them out of the catalogue surely just makes managing the catalogue more difficult and probably slower. It would also likely prevent the ability to edit when you do not have access to the original files should that be important to you. Sessions to not cater for that anyway.

    HTH.

    Grant
    0
  • NN635464888934308424UL
    I have created junctions for this, but that assumes you can tell your backup software to not follow a junction.

    My case was different: I wanted the catalog stored on the massive 6TB RAID, but the cache to be stored on a fast SSD, not part of the RAID. I actually want to back both, so let my backup software follow junctions. In short, I have not tested junctions as a solution to excluding a folder from a backup.

    That said, most backup software that are flexible enough to be told to ignore junctions must be flexible enough to be told to ignore a specific folder.
    0

Post is closed for comments.