@mogoodrich I haven’t not came across that permission issue, also I have experimented with your dictionary and i’m getting same auth error
Also we at ampath are considering to start using the module immediately, I have been doing some testing to assess if the module is production ready, some of the things I fout out
- If you want to subscribe to multiple dictionaries say A and B, this is only possible if you do one at a time with specific dictionary subscription urls. I had read somewhere in the documentations that importing CIEL concepts will replace all existing concepts with the newly imported concepts that means some local concepts will be lost, however I experimented this by first importing concepts from dictionary A, I then added local concepts on top of A. I went ahead to importing from dictionary B.
After all that, all concepts from dictionary A and local concepts were retained and B’s concepts were added. That means implementations are responsible for managing their local concepts. Also With B’s concepts that already existed in A’s dictionary, concept duplicate exceptions were thrown, I would say this is the expected behaviour.
Importing latest release of a dictionary reimports all the concepts that has already been importing from the previous import. This means if local changes were made to the concepts they will be lost
Rolling back to a previous release is not supported, since dictionary versioning is not yet supported, I have tested this by removing some concepts from my current release and created a newer release, this did not remove these concepts from openmrs
Does the module support existing implementations to start managing their dictionaries in OCL with some kind of one-time upload? . ie we at ampath we would wish to be able to upload all our concepts say in ‘Ampath-starter-template’ dictionary in ocl, be able to create another dictionary by copying the starter template and be able to add more concepts to it from CIEl from which we can then release and subscribe to. Also if this is not yet supported, I would like to request all of you to help brainstorm on a workaround for this
Also we deem it fit that implementations should be able to roll back to their original concepts in case anything goes wrong during concepts import hence need to be able to backup concepts https://issues.openmrs.org/browse/OCLM-69