Pages: [1]   Go Down

Author Topic: too many catalog in LR  (Read 1443 times)

alifatemi

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 278
    • ali fatemi photography
too many catalog in LR
« on: June 03, 2014, 04:33:47 pm »

I just start running large format studio. every customer comes, I creat a new catalog under his or her name but I predict after one years, there are so many cataloge for so many customers; having lots of catalogue won't be problematic? if yes is there other choice?
Logged

digitaldog

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 20630
  • Andrew Rodney
    • http://www.digitaldog.net/
Re: too many catalog in LR
« Reply #1 on: June 03, 2014, 05:18:43 pm »

Simple, use ONE catalog. Keep each customer in a folder, and/or build smart collections to track them etc.
Logged
http://www.digitaldog.net/
Author "Color Management for Photographers".

john beardsworth

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 4755
    • My photography site
Re: too many catalog in LR
« Reply #2 on: June 03, 2014, 05:38:43 pm »

And use fields like job number which can be easily searched.
Logged

fdisilvestro

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 1852
    • Frank Disilvestro
Re: too many catalog in LR
« Reply #3 on: June 03, 2014, 07:04:05 pm »

Hi, you will hardly reach any practical limit either by having one catalogue with all your clients images or having a separate catalogue for every client.

Having said that, I would also recommend working with one catalogue, unless there is a specific reason to do it (there are a few). My other recommendation is to put the LR catalogue and LR cache in a SSD or high performance disk.

Ligthroom catalogues (*.lrcat files) are self contained databases (SQLite databases) where the data is organized in tables and can handle large amounts of information. There is a theoretical limit of 140 TB, which I don't think should worry any photographer at present times.

As previous posters said, you can separate your clients by using appropriately the collections, keywords, etc.

Why would I use more than one catalogue? First reason is if you work in a multi-user environment where concurrent edits to images occur. Without getting too technical, SQLite is not adequate for multiuser updates. Even in these environments, you must consider first the option to export the images to be edited by another user as catalogue (from the main catalogue) and then import the updates when finished.

On the other hand, if you really want to stick with your idea of having individual catalogues for every client, then the limit is what your OS can handle (since every catalogue is a single file), practically tens of millions in every folder, so again nothing to worry about.

If you go this way, you'll lose the ability to group and search through all your images at once and increase the risk of mismanage the files, not to mention the backup and LR update version processes which can turn into nightmares.

Regards
Pages: [1]   Go Up