Page Comparison

...

Sprint to extend some of the "read only" APIs, to finalize unit/integration testing for existing functionality, to extend the interface, to develop additional loaders, and to begin developing editing capabilities.

Priority things

• Demo video link.
• TODO: exact matches should always show up at the top for autocomplete.
• DONE: Finish implementing dui/code calls in ContentServiceRestImpl for child and root routines
• TODO: Fill in the ContentClientRest calls for new Tree REST APIs
• TODO: Write integration testing for new Tree calls (e.g. ComponentTrees, ComponentTreesForQuery, ComponentTreeChildren, ComponentTreeRoots)
• TODO: Revise unit testing of TreeJpa
• TODO: autocomplete suggestions should always be valid (e.g. remove lucene special characters when setting the value)
• "self" entries need to exist in transitive closure for leaf nodes (for semantic search)
• fix cases where atoms paging shows up but not the filter - has to do with show obsolete/suppressible
• DONE: Add a "are you sure you want to leave the page" feature if people click the back button (see mapping project)
• Consider adding a "configure" routine to all "handlers" so they can configure themselves after they are all instantiated (e.g. if they need access to a metadataservice or a contentservice to function properly)
• DONE: BUG: lower relevance of suppressible data in queries. - should be able to add a boost to suppressible:0
• BUG: support ability to search with quotes, e.g. "heart disease" - this has to do with properly url encoding the query.
• mojo test suite for RRF-single, plus terminology remover
• DONE: Hierarchy -rest layer adds a dummy top for merging 
• DONE: Clients should handle null parameters properly
  
  • BAC: handle for content, metadata, project, security
  • Make a RootClientRest with a precondition check for null or blank
• Finalize REST service for a general concept query (e.g. lucene query, HQL query, or SQL query)
  
  • DONE: Must start with "SELECT " and not contain ";"
    
    • provide appropriate error message via exception if not
  • DONE: Execute the query but check the object type of the first result
    • if doesn't match expected type, fail with an exception.
  • Use timeout => 

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

• Implement NewConceptMinRequirementsCheck and "validation service"
  • Validation check
    • validate(Concept), validate(Atom), validate(Code), validate(Descriptor), validateMerge(Concept,Concept)
  • Validation service (Rest, ClientRest, RestImpl)
    • pre-cache validation handlers (see how this works in MetadataService, etc).
    • validateConcept  /validate/cui/ (PUT) ConceptJpa
      • load all validation handlers and call each validate Concept) method.
    • validateAtom  /validate/aui/ (PUT) AtomJpa
    • validateDescriptor ...
    • validateCode  ...
    • validateMerge /validate/cui/merge/{cui1}/{cui2} - GET
  • DefaultValidationCheck
    • validate atom whitespace
    • validate that a concept has at least one atom and at least one "hierarchical" relationship (to something that exists)
    • update config.properties to use this check
  • Organize validation checks into packages and create classes
    • com.wci.umls.server.jpa.services.validation (DefaultValidationCheck)
    • com.wci.umls.server.jpa.services.validation.umls (NewConceptMinRequirementsCheck)
      • concept has at least one atom and at least one hierarchical rel 
    • com.wci.umls.server.jpa.services.validation.snomed (NewConceptMinRequirementsCheck)
      • see term server project
  • Create an integration (jpa) tests for the validation layer (e.g. put in spreadsheet, normal use, degenerate use, edge cases, etc).
• 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)
• DONE: Finish RF2 loader implementation, test on mini smomed
  • create separate config project for this (e.g. "prod-snomedct").
  • load and depoy to snomed.terminology.tools
  • classifier?
• ClaML Loader (make algorithm).

...