Content Comparison

...

• DONE: serialization of concepts should include id, terminologyId, preferred name
  • Applies to Description and Relationship
  • Return 0 for Long if not set
  • Return "" for String if not set
• DONE:  Claml loader 
  • make sure transitive closure computation is working

• DONE: BAC: REST APIs - fix @Consumes and @Produces

  • Annotations are now at the class level, with TEXT_PLAIN overrides where parameters or return values are String.
• Transitive closure computer - avoid cycles.
• PG: Finalize integration REST testing
  • DONE: security service
  • DONE: Metadata Service
  • Content Service 
• Loaders 
  • DONE: Make sure snapshot and full create release info
  • BAC: RF2 full - get this working
  • RF2 snapshot
  • DS: RF2 delta
    • Handle other data structures (currently only 4) - need to add sample data  (and headers) too
    • Remember AttributeValue and AssociationReference need handling for both description and concept
    • Need new ContentServiceJpa methods
    • No need for "handle retracted changes"
  • Scale to full RF2
    • Monitor the number of copies of objects
    • BAC: Manage memory usage and optimize commit
      
      • Can delta loader scale to a full sized delta?
        • Load full SNOMED 20140731
        • then load delta SNOMED 20150131
      • Can snapshot loader scale to a full sized snapshot with only a single commit?
        • Consider making description/concept connections merely an id (lose referential integrity, but these could be added qa database)

• PG: History service - handle other data structures

• PG: History service - integration tests.

• BAC: Admin tools - all should use "server" flag except for QaDatabase and Create/Updatedb

  • Only release mojos need to be fixed.

• BAC: QA Admin tool - fill in queries and reuse

  • Add queries for project and for release info

• BAC: Separate "updatedb" into

  • admin project called "db"

  • pass hibernate.hbm2dd.auto as a parameter to the execution

    • call System.setProperty("hibernate.hbm2ddl.auto", hbm2ddlParameter).

    • THEN create the root service.

  • "createdb" profile

  • "updatedb" profile

  • Remove the properties section from pom.xml
  • Update documentation.

• Mojo integration testing

  • Have a setup dev environment mojo

  • Have a teardown dev environment mojo (calls createdb at the end to clean up after itself, leavign an empty Db ready to go).

• Testing

  • Unit Testing
    • coverage, equals/hashcode/copy constructor; lists; algorithms; handlers
  • Mojo Tests

...