Introduce URL parameter to store fully enumerated reference expressions

[paynejd]

We want to provide 2 options for how the OCL API stores collection references:

• Dynamic: OCL stores what the user submits and, where applicable, is able to dynamically re-evaluate the reference at a later time
• Fully Enumerated: OCL stores the fully resolved references to specific resource versions -- this is similar to how OCL used to persist references before we had support for dynamic references

For example: Given a request to add CIEL:163310 as a cascaded reference to a collection, we can do this is several ways. Here's the concept:

• [CIEL:163310 "HIV viral load status"]
  • Q-AND-A [CIEL:1118 "Not done"]
  • Q-AND-A [CIEL:1067 "Unknown"]
  • Q-AND-A [CIEL:1267 "Completed"]
  • SAME-AS [CIEL:163310 "HIV viral load status"]
  • NARROWER-THAN [SNOMED-CT:364712009]

Ways to add a cascaded reference:

• Using ?cascade=sourceconcepts in the request should be identical to using the $cascade operator in a reference expression without any parameters:

PUT /orgs/KenyaMOH/collections/KenyaEMR/references/?cascade=sourceconcepts
{ "data": { "expressions": ["/orgs/CIEL/sources/CIEL/concepts/163310/"] } }

PUT /orgs/KenyaMOH/collections/KenyaEMR/references/
{ "data": { "expressions": ["/orgs/CIEL/sources/CIEL/concepts/163310/$cascade"] } }

Focusing on the ?cascade=sourceconcepts approach:

• In the old collection model, this stored references to versioned concepts & mappings -- see here: https://app.openconceptlab.org/#/users/paynejd/collections/NewTestDictionary/references

* In the new collection model, this stored references to _**version-less**_ concepts & mappings, which allows this to be re-evaluated in the future to incorporate updates to CIEL -- see here: https://app.staging.openconceptlab.org/#/users/paynejd/collections/NewTestDictionary/references

We want to provide a new URL parameter (saveEnumeratedReferences=true) that will cause OCL to store the fully enumerated versioned references in the new Collection model. This parameter should work with any type of reference expression, not just cascade=sourceconcepts.

Example usage:

PUT /orgs/KenyaMOH/collections/KenyaEMR/references/?cascade=sourceconcepts&saveEnumeratedReferences=true
{ "data": { "expressions": ["/orgs/CIEL/sources/CIEL/concepts/163310/"] } }

[paynejd]

transformReferences=none (default)
transformReferences=resourceVersions
transformReferences=versionlessResources

PUT /orgs/MyOrg/collections/MyCollection/references/?cascade=sourceconcepts&transformReferences=resourceVersions

[paynejd]

Final testing for this will be done using the Dictionary Manager -- Ticket created by OpenMRS squad here: https://issues.openmrs.org/browse/OCLOMRS-1096