IdImager v5 to Photo Supreme v4 migration

[Chris Walton]

I have reached the position that I must migrate from IdImager. My obvious migration path is to Photo Supreme. I am doing a lot of testing of possible migration processes. I have encountered a problem converting the catalog from IdI to PSu.

If any of the following are available, could you please point me in their direction:

A. A script to convert a catalog from IdIv5 and SQL Server 2005 to PSuv4 Single Edition

B. A script to index the catalog and thumbnail database appropriately, once resident in PSu

C. I can prepare the catalog for export in two ways, via IdIv5 or SQL2005 to a CSV file. Both require search and replace operations to change single quotes to two single quotes, and to change double quotes to single quotes (Approx 1.6m changes). This is to ensure that the resultant file is suitable for import into SQLite. If I convert via IdI, I need to do a search and replace on the record delimiters as well. My installation of IdI no longer supports export to XML. Is there any further technical reason to prefer one conversion over the other?

I enclose detailed information on the issues facing me to achieve this migration. I do not believe they are relevant to this query, except to expand on the background to my request.

[Hert]

Apparently you're running the Server edition;

First make a backup of your IDI-V5 catalog

Option 1;
Your biggest issue is that you're using SQLServer 2005. This because it doesn't support some of the features that the latest PSU Server requires. If possible, upgrade your database to at least SQLServer 2008.

After that, install PSU Server Edition (trial) and let it upgrade your database. Once upgraded; follow this to switch to Single User edition: viewtopic.php?f=57&t=23417

Option 2:
a. In IDimager, enable ICS writing (if not active yet)
b. Write metadata to your images if they don't have ICS in them
c. Install PSU SIngle User edition
d. In Preferences, enable the Synchronize-Read-ICS setting
e. Import the images from the file system

PSU will then re-generate your catalog based on the ICS schema in your metadata

I recommend Option 2 over Option 1. Try it with a small test set first

[Chris Walton]

Thank you.

While I am not likely to use option 1, if it becomes necessary, is SQL Server 2017 Express a suitable database to underpin the proposed migration?

Option 2 is my way forward I think. ICS writing is enabled, and has been for a long time. If the catalog is based on a working (partial) image archive, but is a full catalog of all the images, will option 2 still work? The full archive has been moved to a different disc. Do I have to relocate the catalog to point to the full archive? At present I am still setting up testing, and intend to test every step of the process in detail.

[Hert]

If you import them from the new location then you don’t have to change anything.

[Chris Walton]

Option 2:
a. In IDimager, enable ICS writing (if not active yet)
b. Write metadata to your images if they don't have ICS in them
c. Install PSU SIngle User edition
d. In Preferences, enable the Synchronize-Read-ICS setting
e. Import the images from the file system

PSU will then re-generate your catalog based on the ICS schema in your metadata

I have investigated all the above steps. The problem is in step b. There is no configuration of my installation of IdI that will write metadata back to the images. The only information that gets written back is labels that have an IPTC mapping defined. No information about other labels, catalog structure, label structure, collections or versions is written.

In the process of testing this I have found that I can extract the ICS from IdI by choosing (on a selection of images): Rt click context menu -> Transfer ->Export Select Images to SQLite Database. This generates a database file, IDImager_export.cat.db, which contains the full ICS for the selection. Is it possible to use this generated file to migrate into PSu?

[Hert]

You can enable ICS writing in IDimager V5. It's in the options for synchronization. Once you enable that option, re-write the metadata to the files. If the option was already enabled then your images should already have ICS.

[Chris Walton]

My installation of IdI does NOT write out the ICS to the images under any circumstances. All settings are as appropriate to write the ICS; it just does not work.

(I indicated previously that there is functionality in my setup that no longer works. This is another such failing functionality, and is the key reason I stated that I MUST migrate away from IDImager).

The settings and processing I have tested are:

• ICS writing - enabled

• Allow embedded write to RAW files = enabled

• Automatically write all catalog changes out to the image metadata = enabled

• Write XMP to files and database = enabled

• All image files read-only flag cleared

• Specific writing of metadata to files by Context menu -> Synchronize XMP/IPTC -> Export catalog info to the image's XMP/IPTC

Every stage of processing has been checked by examining the catalog and the files, using DB Browser for SQLite; Exiftool; a text editor; and SQL Server Management Studio.

No information is written to the image files apart from the labels that have a IPTC mapping.

My question stands: Is it possible to use the file generated by context menu -> Transfer ->Export Select Images to SQLite Database; to migrate to PSu?

[Hert]

If you get an export database then I assume it should be possible to open that database in PSU Single Edition. It's been almost 10 years since I last worked in IDimager V5. I don't have it installed anywhere and so can't check it. You'd have to try that. In PSU open the catalog from the Tools->Catalog-Open option from the hamburger menu.

BTW; ICS is written in the metadata of the file, not in the database.
Hence why a remark like

This generates a database file, IDImager_export.cat.db, which contains the full ICS

gets me confused...after all ICS is not written to the database, but to the metadata.

AFAIK ExifTool supports the IDimager ICS schema and so you should be able to see it there. Not sure if ExifTool supports reading embedded XMP for RAW files. https://www.sno.phy.queensu.ca/~phil/ex ... P.html#ics

[Chris Walton]

I was not aware that migration might be as simple as opening an IdImager database in Photo Supreme. I was anticipating having to write a complex query to convert an IdI database in SQL Server 2005 to a PSu database in SQLite. I did not know how close the database schemas for IdI and PSu were.

I did get confused. Working with both ICS and the database schema, I started to regard them as one and the same thing. I apologize for the confusion. When I looked at image files catalogued in PSu, writing of the ICS to the image file was immediately obvious, with only a cursory examination with a text editor. The other tools were not necessary.

When I tried to open a database file containing a test extract from my IdI catalog, it gave me the opportunity to upgrade the database. Choosing this option generated errors, which appear to be due to differences in the two relevant (database) schemas. I am hopeful that I can resolve these by tweaking the structure of the test extract. Do you want to receive normal error reporting of these errors? They are, after all, being thrown because it is an upgrade from a 15+ year old product, and so I anticipate that you may not want these reports.

I last had substantial queries on this forum in 2004. Then, as now, your support for your products is excellent. It is fast, responsive, helpful, and tolerant of the foibles of those of us doing something out of the ordinary. Thank you for this superb level of customer care.