Author Topic: Auto Update Catalog feature  (Read 8081 times)

Offline KeithRJ

  • Full Member
  • ***
  • Posts: 224
    • View Profile
    • Keith & Vlasta Ross-Jones
Re: Auto Update Catalog feature
« Reply #15 on: August 06, 2020, 03:44:47 AM »
What about an option to set a single folder to watch for updates and then have PM+ update the database.

I use DxO Photolab to develop photos so I continually have to scan to Catalog to get the new photos added. As I develop to just one directory/folder I would like to specify this folder for auto update.

Offline treyneal

  • Newcomer
  • *
  • Posts: 9
    • View Profile
Re: Auto Update Catalog feature
« Reply #16 on: September 28, 2020, 02:23:29 PM »
Coming from years of running Media Pro through multiple iterations (and still nursing that database along) - this feature is implemented by way of watched folders. Essentially the user right clicks for context sensitive options on single folders, one of which is to Auto-Update the folder.  If there are changes to that folder the database is updated as a background process based upon user selected frequency - every 1 minutes, every 5 minutes, never.  Media Pro recognizes the "new" item - file, folder, subfolder but processes it in the background.  This keeps the user from needing to manually activate an update to the catalog for a watched folder(s). While it is likely CPU intensive, it does keep me up to date in a catalog without intervention.

Offline Stenis

  • Newcomer
  • *
  • Posts: 21
    • View Profile
Re: Auto Update Catalog feature
« Reply #17 on: September 03, 2021, 04:02:53 PM »
What is this "catalog target folder" that you speak of?  It would be one thing to have something watch a single (or a few folders) for new additions, but we can't be constantly scanning all of your drives for new files being added.  It would perform poorly.

-Kirk

I know this is an old tread but I think this question is very important and it seems to come back regularly.

I have worked seven years until 2013 with a DAM-software called FotoWare (not misspelled english "Foto" is just norwegian and swedish for "Photo" :-).
Fotoware had an indexing engine they called Index Manager and it was constantly monitoring the filesystem changes for (updates, deletes and appendings).
Usually it took a secound or so for a change to appear i the different indexes and it was always changes done outside the Fotoware system itself.
We had an integration with old legacy SQL-databases that was maintaines with other applications.
Still it´s very fast.

It would not be possible with a non-automatic system like Photo Mechanic's in an Enterprise, depending on the user to maintain sync in the system.
That´s why there has to be an automatic monitoring of file system flags when changes occur in the folders indexed by an Enterprise DAM.

The XMP-catalogs worked pretty much as they do in Photo Mechanic where you point on a folder structures top folder when indexing a catalog.
It would be no problem really to replace Photo Mechanic's indexing service and vise versa with Fotoware's and reindex.
(Of course you have to build schemas and forms that fit the data in FotoWare in order to be able work with the data or forms that  matches Fotowares data in Photo Mechanic. I guess that Photo Mechanic creates the schemas automatically in the background when we build the forms to make it a little more easy than in FotoWare for us.


It´s a little bit unfair to compare an enterprise DAM with a dedicated indexing server perhaps but you also could run Fotoware as a single user application too.
They had a Windows and Mac-application called Fotostation, that could run on an ordinary PC.
Even in that case the changes are monitored automatically.