Page Comparison

...

• Switch to a default build of the SAMPLE_2014AB and redo metadata and content tests against that data set.  Then we may be able to have more complete hierarchies and some code data to work with.
• Consider all query-based lookups in ContentServiceJpa and reimplement as lucene lookups instead if it seems that it would improve performance.
• Finalize REST service for a general concept query (e.g. lucene query, HQL query, or SQL query)
  • Must start with "SELECT " and not contain ";"
    
    • provide appropriate error message via exception if not
  • Execute the query but check the object type of the first result
    • if doesn't match expected type, fail with an exception.
  • Use timesout = 

  • query.setHint("javax.persistence.query.timeout", timeout);

  •  
• Implement NewConceptMinRequirementsCheck
  • Requires that a concept has at least one atom and one semantic type.
  • Create an integration (jpa) tests for the validation layer (e.g. put in spreadsheet, normal use, degenerate use, edge cases, etc).
    • It may be desirable to organize integration test packages by terminology (e.g. "com.wci....validation.umls" for UMLS checks ".snomed" for SNOMED checks, etc).
  • Implement the same check also for a SNOMED concept.
• Properly implement terminology remover functionality (e.g. content service rest.removeTerminology).  The content and the metadata objects need to be removed in the right order so as to avoid foreign key constraint errors. (e.g. attributes, definitions, semantic types, tree positions, transitive relationships, relationships, atoms, then atom classes - something like that).  For metadata I think terminology/rootTerminology is the only dependency (remove root terminology first).
  • Then update the mojo test case to remove the terminology (currently commented out)
• Implement SNOMED APIs
  • Model objects (in their own package)
  • jpa layer?

User Interface Enhancements

...