Uploaded image for project: 'Unsupported: OpenMRS Concept Collaborative'
  1. Unsupported: OpenMRS Concept Collaborative
  2. OCC-97

Spike on suitability of using Apache Solr to re-implement the OCC Server



    • Type: New Feature
    • Status: Ready for Work
    • Priority: TBD
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: OCC Server
    • Labels:
    • Complexity:


      See https://wiki.openmrs.org/x/rA8z and https://wiki.openmrs.org/x/Kw8z for more background on the OCC idea.

      Executive summary:

      • we want to allow people to share concepts from their data dictionaries in a central repository
      • you can download other people's concepts, but that really means making your own copy of someone else's concept. (Your new copy is then shared, so there are two copies of the concept in the repository.)
      • the server will use a "wisdom of crowds" approach to sorting search results, so if I search for "weight" and 20 people have shared identical weight concepts, that will be the top hit.

      (Because of the way that multiple copies of concepts get stored on the server, we eventually need to be able to handle 1 million-plus concepts.)

      We have an existing codebase for this, but we have concerns about its scalability and maintainability. We want to look at the feasibility of re-implementing that server component in a tool built for that purpose (Apache Solr) rather than writing document management, indexing, etc, ourselves.

      Things we need to spike on:

      • Export a concept from OpenMRS as XML and store that document in Solr. (Sample XML for OpenMRS 1.6 and 1.7 is in a comment on OCC-56. Use the 1.7 example.)
      • Example of leveraging Solr to query for "concepts that are structured in a similar way, and match a search term"
      • Handle the fact that different versions of OpenMRS have changes to the data model for Concept, so the XML isn't quite the same - e.g., defining a schema within SOLR that is a superset of all versions or otherwise allows for the variability between versions.
      • Extra credit: Demonstrate how the server can manage part of the schema (e.g., tags, lookup terms, and/or lists of linkages) to better organize concept documents in the OCC and allow for additional search options without exposing OCC clients to these extra metadata. For example: add an occ-tags field to hide concepts from searches when "hide" is added and/or add an occ-links that can contain UUIDs of other concepts in the OCC


        1. putConcepts1314154291988.xml
          10 kB
        2. putConcepts1314154309458.xml
          70 kB
        3. putConcepts1314154328298.xml
          12 kB
        4. putConcepts1314154336755.xml
          11 kB
        5. putConcepts1314154381568.xml
          51 kB



            darius Darius Jazayeri
            0 Vote for this issue
            5 Start watching this issue