Page History

Current Sprint - Sprint 8 (July 9, 2015 - July 22, 2015)

LexEVS 6.4 Agile Development - Sprint Status - Sprint 8 

Sprint 9 Planning

Upcoming Sprint - Sprint 9 (July 23, 2015 - August 5, 2015)

LexEVS 6.4 Agile Development - Sprint Status

Issue Prioritization

Recent LexEVS Related Bugs and Features (within last week)

LEXEVS-1033, LEXEVS-1034, and LEXEVS-1037 - All 3 issues are failing due to no namespace defined.  This is a low priority. 

Craig will add these 3 issues to the backlog.

LEXEVS-946 - OBI loader issue should be in sprint 9.

LEXEVS-970 - Tracy will test loading NDRFT with OWL2 loader and report any issues.

Recent CTS2 Service Related Issues (within last week)

LEXEVS-1017 and LEXEVS-1029 should be worked on as part of 6.4. 

Issue Grooming

Prioritize JIRA issues (fix version 6.4)

Multi-Index Prototype Status

• Results (Scott)

Prototype is complete and have results to review.

Times shown are better for many areas. 

For multi-index searching, results were slightly higher, but still < 100 ms.

Two questions from NCI came up:

• Will the performance hold up when we use real data.
• When we go to a multi user environment and multi queries, will the performance hold up?

Local XSD Resolution

• Resolution and Priority (Scott)

LEXEVS-1029 was worked on to put in a temporary fix.

NCI has suggested to just point at a local copy of the XSDs being that they don't change often.

We should complete this issue in 6.4.6.3 Deployment Status

• NCI Maven Mirror Update (Cory)

NCI 's Nexus server is no longer blocking the Mayo Nexus Proxy after a restart.The goal is for NCI to be able to build lexevs CTS2 service. Mayo will put the correct CTS2 framework 1.2.0.RC1 artifacts on maven to allow NCI to mirror and build.lexevs-service has be successfully deployed / tested on QA-service successfully now pointing to their Nexus server.

One issue that just came up was that there was a test failing during the build.  This is working at Mayo.  Cory is following up with NCI.

OBI Load

• Update and next steps (Scott)

The OWL1 source was successfully loaded with OWL2 loader.

Scott to send the output from the load to NCI to review the hierarchy.

Possibly note that the content that is too long has a truncated marker on it.

May need to fix the inverse properties.  Inner classes (inverse properties) are not being parsed.

CTS2 Doc Service - NodeJS/NPM versions

• NCI Tech Stack (Gilberto)

The NCI infrastructure group will not support Redis.  If we add Redis, NCI will need to support the entire server upgrade/maintenance.

MongoDB will be supported.  Redis will not be supported.

Our CTS2 service API docs can run without Redis when we upgrade to the latest Node.js and NPM.

Gilberto will follow up if Node.js and NPM will be supported.

VPN and network evaluation

• Update from Gilberto and Jason

External Request

• ?

Scott is continuing to investigate why the OBI load is failing for NCI.  He is looking at NCI DEV.

VPN and network evaluation

• Update from Gilberto and Jason

External Request

• ?

Nothing to report.

Would like it to use the CTS2 API. 

Gilberto asked if it return all relationships?  It can retrieve them but without all of the metadata.

For UI, Scott suggested D3.  Gilberto was looking for something more lightweight.

Need to query for different relations in CTS2.

Craig showed FishEye and all of the current Lucene work that is being committed.

https://ncisvn.nci.nih.gov/fe/graph/lexevs