Supposed Improvements in Upgrade Workflow (not)

Report · Oct 14, 2024

I do not like or appreciate the new LrC Catalog upgrade screen. Not one bit. Supposedly an improvement in workflow. In fact quite the composite. This starting at v14.0. I see a programmer design change error as a bug. Oh I just know this will get relocated to Discussion, As Adobe can do no error. Adobe, when you make a design decision this bad, it is a bug. (Yes, they moved it to Discussion while I was editeing, thank you not)

Issues:

Forces a backup I do not choose to create
Forces a backup name I do not desire
Forces a backup location on the same hard drive as the working catalog.
Does not change the name of the working catalog
Does not allow for the user to select a name change for the new (upgraded) catalog

File structure before upgrade:

Upgrade screen presented:

File Structure post upgrade:

And that Folder the backup gets placed in:

Backups should not be placed in the same hard drive as originals
Users should be able to decide when and how backups are made
Not all users choose the LrC backup method. Some choose manual backups, Some choose to use other applications to automate backups
Why has Adobe decided to not modify upgraded catalog names?
The above causes the user extra work flow to relocate, rename, or delete the backup. Causes the user extra work to rename the new catalog.

Fellow members, can you verify a few things

~~In the previous upgrade did we not get to select the new catalog name?~~ (yes we did, see second Idea link below, a member actually did not want it)
Does anyone remember any IDEAS that may have caused this design change?
What am I missing?

Followup: At least two Ideas may have caused this:

Six up votes in the first, two in the second, and Adobe goes and does it?

Additinal follo0wup:

Well at least the new Rename Catalog option works. But we should be able to rename at Upgrade, in that Upgrade screen.

File Structure after using the Rename Catalog option in LrC 14

If we are now going to keep catalog names, then might as well drop all that extra version related text and keep it simple.

Recommendation:

Go back and expand that dialog to allow user decisions, to allow selecting new name, to select if to backup and where to backup, and to select backup name:

Report · Oct 14, 2024

What users can do is rename the catalog as soon as the upgraded one is opened AND delete or move the backup to a desired location.

.The team has opted to make us to the moving and the rename as second steps.

.

Report · Oct 14, 2024

That's exactly what I did - renamed the catalogue and moved the old catalogue to a different location. I don't have any issues with this - it's a no-brainer!



Report · Oct 14, 2024

I wholehartedly agree but would like one additional checkbox in your proposal: "rename folder to match catalog name".

I would also go one step further and have a suggested new catalog name preloaded in the new name text box that strips off all old version numbers (and -2-2-2's) from current catalog name and appends "v-14.0" (or whatever the current release number is) but allows you to over type it if desired.

When I first read about the forced backup and it's location I was immediatly in your camp about not liking being forced to do it and where it is placed. But as I thought about it more and have played with it, I now actually think it is a good design. I'm OK with a foreced backup but If it is an option it should be the default. I'm also OK having it placed as it does. The reason is this. This is not a regular back up that should shoe horn in with the set of normal BU's you may or may not take when exiting LrC. You would probably already have taken one of those before you upgraded anyway. This is more of a "quick fallback" (if needed) idea. Having it right next to the updated version makes it easy to find if needed and and makes it pretty obvious that it was the one that was updated without having to scrollthrough a long list of regular backups trying to figure out which was the last one before you upgraded.