Importing images from a non IM database folder within iMatch

[rgdudley]

Previously I have posted about incorporating the iCloud photos folder into my iMatch database.  This works, but with a few oddities (mainly the need to move images out of that folder for editing and adding metadata... and they have to be moved to a folder on another drive ).

However, I think I would be better off removing that iCloud folder from the database... because I don't really want all those occasional images in my iMatch database.   Also, my IM backups are out of date as soon as I click another photo with my iPhone!

BUT it is very convenient to have that folder there when I want to pull some images off icloud photos.   Especially since I can search the database for duplicates etc.

So what is the best approach to do this?  I assume I can:

• 1)temporarily add the icloud photos folder to my iMatch database (but this takes some time to digest)
• 2)copying or moving the desired images to a folder that is within the database
• 3)remove the icloud folder from the database.

Or am I better off doing this outside of iMatch?

[Mario]

I'm not sure I understand that problem you are trying to solve.

Indexing a locally mirrored cloud-folder in IMatch should make no problems at all. Unless iCloud does one of those Apple things that make everything much more complicated. What type of problems do you have with iCloud?

To do anything with images in a folder in IMatch, the folder must be indexed by your database.
You can add the local iCloud folder. Or you copy selected files from a folder iCloud controls to a regular folder already indexed by your database. Or in a fresh folder that you then add to your database.

(...) better off removing that iCloud folder from the database... because I don't really want all those occasional images in my iMatch database.

That's probably already the solution. If you want to curate which of your iCloud images you manage in your DAM, create a separate folder, index it in IMatch and copy the files you want to manage in IMatch into that folder.

You can always copy them back to the iCloud folder if you want to make backups (if you use iCloud for backup).
Use Windows roboycopy which only copies actually modified files, minimizing the amount of files that need to be synched with iCloud.

[6b6561]

In regards to IMatch DB backup being out of sync with iCloud Photo folder.

iCloud Photo is just a directory with pictures being added or removed externally of IMatch. This is a directory that will be out of sync with IMatch DB even in normal operation so I don't see it as a issue that the DB backup wouldn't have all pictures or some pictures missing.

I have my iCloud Photo folder all the time in IMatch and it's always in need of a rescan when I start up IMatch, a quick rescan solves any pictures that are missing or has been added.

The same would apply for a restore, run the restore and once you are up and running, then just go ahead and rescan the iCloud Photo directory and you would once again be in sync.

I'm by the way also including the iCloud Photo folder in my own backup as I'm not 100% confident that there couldn't be a disastrous event in the cloud.

[Mario]

This sounds like I would have expect it to work. Of course cloud-based folders change frequently, but a rescan in IMatch will update the database to match.

I'm by the way also including the iCloud Photo folder in my own backup as I'm not 100% confident that there couldn't be a disastrous event in the cloud.

That's a good idea. Cloud as a 2nd or 3rd level backup is fine. But always keep at least to backups under your control.
If you lose access to your Apple account or it is (temporarily) disabled because of a "violation of terms of service" for some reason, you won't be able to access your files until this is resolved - because they are stored on a computer owned by Apple.

[6b6561]

The iCloud Photo folder behaves quite well, older photos are static, it's just new and deleted photo files that change.

[Mario]

The iCloud Photo folder behaves quite well, older photos are static, it's just new and deleted photo files that change.

That's to be expected. IMatch will automatically rescan the folder to bring in new and updated files. It will not remove no longer existing files from the database, though. This is a safety feature. To remove no longer existing files, rescan the top-level folder manually with <Shift>+<F5>. This also brings in new sub.folders.

If this is an issue, consider to create a curated list of files in a folder outside the iCloud folder hierarchy and add this folder to your database. Then you can control which of the iCloud files you manage in IMatch  and when you bring in changed files from iCloud.