Thanks for your explanation, Denis. It makes sense. I think I prefer what I did, keeping it in one catalag. Just making folders (sorry there is no other way than not thinking in folders) with subjects. BTW, do you work with one catalog?
I am still using only one with clients, weddings, football, personal, family and anything. I am at 2'5'' photos at the moment and it is still responsive on the MacPro.
I use a mix of folder organization and Lightroom's way. I do organize by date as of today: .../2''9/2''9-'6-'9 _Small_Event Description/images
The three dots may be:
Photos/Clients/ClientName
Photos/Sports/TypeOfSport
Photos/Family
I keep it as minimalist as possible tough a little like if I had three catalogs at folder level
(Clients,Sports,Family). What fall outside is managed by Lightroom by keywording and or can be in Photos/2''9/2''9-5-27 and so on.
This folder splitting is mainly meant for backup purposes:
Family on 16'GB ext drive
Sports on 5''GB ext drive
Clients on 32'GB ext drive
The important thing to me is that "Photos" do appear in Lightroom as the top level folder so if I have to move all this structure to a new bigger drive with a command having the option to verify the copy bit for bit before deleting the source. Then, I just have to relink the missing "Photos" folder in Lightroom and all the rest fall in place.
You may read sometime "Never move photos outside of lightroom" but this is to be taken with a grain of salt... Corruption happened to me moving within Lightroom massive directory structures from internal to external in the perspective of changing hardware. In such a case, it may be preferable to move the folder structure outside of Lightroom with a software performing validation and then relink the missing structure in Lightroom. What one should avoid is to move some photos from a folder to another, restructuring the folders hierarchy adding some and moving other all that outside Lightroom; Then you can make a real mess having a hard time relinking image by image and folder by folder. On a side note, such corruption never happened to me within internal drives but better safe than sorry.
