Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • do we want to update all old keys or only the latest key?
    • the consensus was that updating only the latest key did a better job of preserving the history (e.g. for comparison with xtc values).  there was a weak counter-argument that the "configdb rollback" command would not work as naturally (would need to know both the old name and the new name).   
  • the detector name (e.g. trigger_0) shows up twice: once as a database-lookup key ("device") and once in the document with typed-json ("detName:RO", which is useful for converting to xtc).  Do we want to edit both?
    • Yes, it is more natural to edit both.  Matt pointed out that the daq code may overwrite detName:RO, but we weren't certain, and in any event it feels more elegant to have it be correct in the database
  • do we want to create a new key with the changes?
    • Yes, because this does a better job of preserving the history
  • do  we want to create a new document with the new detName:RO?
    • Yes, because this does a better job of preserving the history

Removal is more straightforward: a new key will be created with the appropriate device removed, but history will be preserved in the old keys.

These answers will require changes to Mike Browne's code which Murali has kindly agreed to do.

...