I'm currently testing the ASP3 demo version to see if it would be a good option for organizing and working with my photos.
I'm working with photos in two locations, on my Mac laptop and on a Linux file server.
The most recent photos I keep on the laptop, and then I move the photos in batches 2-3 times a year.
I'm trying to figure out a workflow with ASP3 that would work well with this.
Expermenting and reading the User Guide leads me to believe I should keep the Mac only files in a separate catalog.
(If I keep both remote and local files in the same catalog, the program crashes if I try to select photos that's unavailable due to file server not being connected/available. This might be something for the bug subforum, but I've reported it to Corel Support, so I guess that's fine.)
So, I'm trying to work with two catalogs.
1. A catalog for the remote location/fileserver photos (remote-catalog), and I define moveable path, so I can actually also open the files in ASP3 on Linux.
2. A catalog for the photos stored locally on the the laptop (local-catalog).
Then the issue arises. I'm trying to move files from the local-catalog to the remote-catalog.
I can select the photos in the local-catalog and import them to the remote-catalog. But then that's just indexed with references to the local filesystem. So I create the desired folder on the remote-catalog's server filepath and move the photos there.
So far so good.
... or not. Since I _moved_ the files, the files in the local-catalog are now dead links. (Images with question marks that causes the program to crash if I try to select them.)
So ... is there something wrong in my approach? What would you do differently?
