Details
-
Task
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Won't Do
-
None
Description
Over time, the names for the canonical reference records will change.
For new installations, it seems clear that the records loaded should be the latest definition.
For existing installations, it seems more complicated.
Examples
I think we have two broad examples:
- Organisations haven't changed the records themselves and may expect the changes to happen automatically
- Organisations that have changed the records, maybe to translate them, and maybe wouldn't want them to be automatically updated and overwrite their own changes
Questions
Should records in existing installations be changed
- When the records have not changed?
- When the records have changed?
I think we also need to decide what we consider changed.
Do we consider the records changed if the total count of records has changed (e.g. a record has been added or deleted)?
Or do we consider each record at a time and consider it changed if the record's name has changed?
Could this depend upon specific information in the records, e.g. the `source` property.
TestRail: Results
Attachments
Issue Links
- relates to
-
MODINVSTOR-431 Settings > Inventory > Mode of issuance. Misc. renaming and source update of existing values
-
- Closed
-
-
MODINVSTOR-713 Enable support for optimistic locking (failOnConflict) in instances/holdings/items (part1)
-
- Closed
-
-
RMB-727 Implement support for optimistic locking
-
- Closed
-