Skip to main content
D
desolation_angel
Participant
November 9, 2023
Open for Voting

P: Upgrade catalog without changing the name

  • November 9, 2023
  • 2 replies
  • 171 views

Lr needs an option, on catalog upgrade, to "upgrade in place", so as not to change the filenaming scheme that the user has already put in place. This could be as unobtrusive/simple as:

 

  1. Duplicate the catalog files
  2. Zip up the copy set with an archive name (user or automatically generated for schema version)
  3. Delete the "copy" files
  4. Upgrade the catalog without changing it's name

 

I have no use for the catalog schema version number unless I'm trying to recover back to a particular version. This would be more useful to me:

Why is this valuable to me? Because I have multiple Lr catalogs and each time they need upgrading I have to do the file management and naming for each catalog in order to retain straightforward naming structures. Otherwise the names start to get out of control (see below). Doing this manually introduces the jeopardy of the user deleting something that they didn't mean to delete...

 

    2 replies

    D
    desolation_angelAuthor
    Participant
    November 9, 2023

    As a user, the only time I'm going to be interested in version names, or previous versions, of a catalog, is in the case of regression/reversion to a previous version of the application (something I don't recall ever having to do–and I've been a user since the beta in 2006). 

     

    Lightroom already has a smarter way to handle catalog versions; the backup system, which creates a zipped file, and stores it in a dated folder, in a specific folder for backups. It's clean and transparent to the user. I would like the option to upgrade catalogs in a similarly clean and transparent fashion. 

      GoldingD
      GoldingD
      Legend
      November 9, 2023

      The change on the end of the previous file name offends you?

      Changing from Lightroom_whatever v11 to Lightroom_whatever v12?, those last 3 characters, v11, vs v12, vs v13?

      Provides a clear statement as to LrC version used for the catalog in question.

       

      No. You are actually wanting to make a more cumbersome file name structure dependant upon folder name to indicate catalog version.

       

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices