NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Old Version 3

changes.mady.by.user Unknown User (stanclcr2)

Saved on

compared with

New Version 4

changes.mady.by.user Unknown User (endlecm)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Immediate Priorities and Problems (Mayo Team)

Scott: 

  • Spent time fixing the installer. Will have all the builds on the SFTP site and links to the builds from the 6.2 release page.
  • Support Item, value sets not resolving on Stage. This was a new problem. Noticed concurrency errors, but not sure why it happened.
  • LEXEVS-688 - would like Kim to provide feedback. Scott feels that no changes necessary.
  • Lucene Investigation - planning this last week and start to look at how to proceed.
  • LexEVS-679 - Documentation for loaders. Scott has updated the JIRA item with the links. Would like to have Rob and Tracy review the documentation to see if there is anything more to add. Loader guide also updated to include more errors. Will also provide links to existing documentation that may satisfy other aspects of what was requested in the JIRA item.

Cory: 

  • CTS2-27 (API Documentation)
    • Deployed service on Protege server.
    • Ports opened and verified.
    • Next step is to request an appscan. (Gilberto will request)
      • Both open ports should be scanned.
      • On production only one port would be open.
  • LEXEVS-581
    • Not needed for 6.3
    • Will update JIRA item.

Kevin:

  • Lucene Planning
  • LEXEVS-636
    • Would time out each time at 6 min 30 sec (on Prod)
    • Will try on Dev to see if there are same results.

Craig: Project Plan for 6.3 and 6.4

  • Lucene planning.
  • 6.3 release.

 

 

6.3 release planning, also 6.4 (Craig, Scott)

For the 6.3 release, the thought is that we may be able to deploy 6.3 to DEV.  Then the TERMs Browser can test/develop with the namespace fix in 6.3.  

  • If we decide to go with this plan, 6.3 may not have to go up the tiers.  This would save considerable time.
  • We would then wait for 6.4 to be complete (targeted for end of September 2015) to be in PROD.
  • When will TERMs Browser be ready to be deployed?  With this plan, they couldn't go to PROD until LexEVS 6.4 was deployed to PROD.
Tree Evaluation – Feedback

Kim will need to provide feedback.

  • Notes above

 

 

CTS2 API documentation

Discuss protege server deployment.

  • Notes above

 

Shady Grove Deployment

Firewall exceptions have been completed.

  • Final testing on point from stage to prod and prod to stage.
  • One final change to term browser - but should be fairly quick.

 

Distributed APIDistributed interfaces - review all that are exposed are surfaced. (Include in 6.3 if possible)
True ContainsConfirmed with Lucene instructor that functionality will be the same as before. Plan to review what exactly we are indexing and if we need to continue to do so. Also plan on reviewing all the search algorithms and decide if they are all still needed.

...