Uploaded image for project: 'OpenMRS Core'
  1. OpenMRS Core
  2. TRUNK-3298

concept_reference_term uuids need to remain consistent across implementations during 1.9 upgrade

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: OpenMRS 1.9.0
    • Fix Version/s: OpenMRS 1.9.0
    • Component/s: None
    • Labels:
      None
    • Complexity:
      Medium

      Description

      As part of the concept_map refactoring, an implementation's existing concept_maps are copied over to the concept_reference_term table, and a new, random UUID is created for each new concept reference term.

      We identified this as a problem for sync and modified the sync module to create (somewhat hacky) upgrade script that will re-standardize concept_reference_term uuids across a sync network:

      https://tickets.openmrs.org/browse/SYNC-265

      However, as Rafal has brought this up again in the context Andy's discussion of the concept dictionary uuids, it has occurred to me that there is a large oversight in our solution--because this is as big of an issue for metadata sharing as it is for sync. That is, if there are two separate implementations using the same (ie MVP) dictionary, after upgrading to 1.9 the conference_reference_terms (the replacement for concept_maps) in the two dictionaries will have different uuids.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                raff Rafal Korytkowski
                Reporter:
                mogoodrich Mark Goodrich
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: