A sample of what my database looks like.. Here's a screenshot showing what the 'forms' look like in the databases that I created. Note that I created this application long before there...

OldCADuser Loc: Irvine, CA

Here's a screenshot showing what the 'forms' look like in the databases that I created. Note that I created this application long before there were readily available commercial tools like this on the market. I've had people suggest that I look at something a bit more modern, but I've go much time and effort invested in this that it just wouldn't be worth the time or effort.

Anyway, I hope this shows what's possible on your own. Note that most of the various fields, any and all of which can be used when doing a search, should be self explanatory. Note that 'Item' is the file name of the image and 'Archive' is the name on the DVD-ROM label. As for the metadata, if I need to access that, I go to the original image file and extract what I need, when I need it. Also note that all images are saved as uncompressed JPG images:

John

Julian Loc: Sarasota, FL

OldCADuser wrote:

Here's a screenshot showing what the 'forms' look ... (show quote)

Nice layout. Because of my type of work, I created a data base that actually accesses the metadata, thus providing many additional search fields; now I am able to determine how many images were captured with a specific focal-length lens, shutter speed, camera model, etc. Keywords are also assigned to each image to further expand the search fields. Perhaps too much detail for many but it seems to work well for me.

Ourspolair

Julian wrote:

Nice layout. Because of my type of work, I created a data base that actually accesses the metadata, thus providing many additional search fields; now I am able to determine how many images were captured with a specific focal-length lens, shutter speed, camera model, etc. Keywords are also assigned to each image to further expand the search fields. Perhaps too much detail for many but it seems to work well for me.

That is a sensible approach, IMO.

Ourspolair

Nicely done. Thanks for sharing.

AzPicLady Loc: Behind the camera!

I had a very thorough database that I used for years. However, it was in an old DOS program that eventually wouldn't translate to Windows. So it's gone. What program are you using to do this? I've tried XL, but somehow it doesn't do all the same things. I've tried other dbase programs that don't allow all the search parameters I had in the old system. And, I have 40 years of work that now have to be redone!

Julian Loc: Sarasota, FL

AzPicLady wrote:

I had a very thorough database that I used for years. However, it was in an old DOS program that eventually wouldn't translate to Windows. So it's gone. What program are you using to do this? I've tried XL, but somehow it doesn't do all the same things. I've tried other dbase programs that don't allow all the search parameters I had in the old system. And, I have 40 years of work that now have to be redone!

Microsoft Access is a very powerful database program, still available.

AzPicLady Loc: Behind the camera!

Julian wrote:

Microsoft Access is a very powerful database program, still available.

I've actually tried it. I started one but found it unsatisfactory. Don't remember why right now.

rmalarz Loc: Tempe, Arizona

Like yourself, I started cataloging my photos long before Ps or Lr. Having a computer background led me to use SQL. With the advent of the internet I have a server wherein my data is stored and access is from pretty much anywhere.
--Bob

OldCADuser wrote:

Here's a screenshot showing what the 'forms' look ... (show quote)

df61743 Loc: Corpus Christi, TX

The free LibreOffice also has an SQL database, an acceptable alternative to Microsoft Access.

pithydoug Loc: Catskill Mountains, NY

Julian wrote:

Nice layout. Because of my type of work, I created a data base that actually accesses the metadata, thus providing many additional search fields; now I am able to determine how many images were captured with a specific focal-length lens, shutter speed, camera model, etc. Keywords are also assigned to each image to further expand the search fields. Perhaps too much detail for many but it seems to work well for me.

LR has the same capabilities and more for $10 a month plus Ps.

rmalarz Loc: Tempe, Arizona

That's true. However, I'd prefer to have a database that is not tied to a particular processing program.
--Bob

pithydoug wrote:

LR has the same capabilities and more for $10 a month plus Ps.

OldCADuser Loc: Irvine, CA

My advice is to create an archive where you can access all your images quickly and easily, and then have some sort of database to keep accurate records. After a few years you'll realize that this database, and the images, will become a sort of dairy of your family's life. My wife and I are constantly using the database as a place to look up such things as family events, travel experiences even such things as whenever we have any work done on the house, I document it with photos and they go into the database just like birthday and Christmas pictures. That way, we have a record of when we did this or that to the house. After awhile it becomes just part of everyday life, something interesting happens, take a few pictures, document them and later you're got a chronological record of your family's experiences.

John

OldCADuser Loc: Irvine, CA

An update: I just passed 55,000 images in my archive, 55,026, to be exact.

OldCADuser Loc: Irvine, CA

Another update: I just surpassed 57,000 images in my archive, after our recent trip to Texas, which accounted for 273 of those images.