NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 4

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

Saved on

compared with

New Version Current

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

Saved on

Key

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

...

NameRolePresent
Wright, Larry NIH/NCI   x
Fragoso, Gilberto NIH/NCI     x

De Coronado, Sherri    

NIH/NCI    x

Safran, Tracy

NIH/NCI    x
Ong, Kim L
IS x
Lucas, Jason R
IS x
Bauer, Scott  Mayo x
Stancl, Craig
Mayo x
Endle,  CoryMayo x
Wynne, Robert    NIH/NCI x
Tran, Tin    NIH/NCI [C]  x
Carlsen, Brian (NIH/NCI) [C] x
Wong, Joanne   

Kuntipuram, Kumar

  x

Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
293JasonCheck into Mayo being designated a trusted site2015.06.03  done

...

Sprint Status

Current Sprint - Sprint 14 (October 1, 2015 – October 14, 2015)

LexEVS 6.4 S13-500 Agile Development - Sprint StatusStatus#SprintStatus-Sprint14

 

Sprint Planning

 

LexEVS 6.4 S13-500 Agile Development - Sprint StatusStatus#SprintStatus-Sprint15

Sprint Planning

  • Sprint 15 (October 15, 2015 - October 28, 2015)
  • JIRA issues to include

 

LEXEVS-1240 -  Searching for parent of a root noted returns the entity with code @@

  • Kim discussed this issue and Tracy suggested this change would affect clients. Tracy will add her comments to the issue.

LEXEVS- 970 Is the overall OWL2 loader issue.

  • TODO :NCI and Mayo to break this down to smaller issues to work on in the next sprint.

 

Issue Prioritization

Recent LexEVS Related Bugs and Features (within last week)

Jira
serverNCI Tracker
columnskey,summary,type,created,reporter,priority,status,versions,fixversions
maximumIssues20
jqlQueryproject = LEXEVS AND (TYPE = bug or TYPE = "new feature" or TYPE ="Improvement" or TYPE ="Inquiry") AND created >= 2015-10-07 AND created <= 2015-10-14
serverId7954a81f-12da-3366-a0ef-97c806660e7c

 

Recent CTS2 Service Related Issues (within last week)

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = LEXEVSCTS2 AND created >= 2015-10-07 AND created <= 2015-10-14
serverId7954a81f-12da-3366-a0ef-97c806660e7c

 

Issue Grooming

Prioritize JIRA issues (fix version 6.4)

Jira
serverNCI Tracker
columnskey,summary,type,created,reporter,priority,status,labels
maximumIssues20
jqlQueryproject = LEXEVS and fixVersion=6.4 AND issuetype = Bug AND (status = Open or status = "Reopened")
serverId7954a81f-12da-3366-a0ef-97c806660e7c

 

 

Property type investigation and Implementation

  • Overview by Scott

Lucene doesn't have a "query" type mechanism.  When "AND"ing these properties together, the results are different than expected. We are looking into how to implement with the latest Lucene 5.3.1. 

TODO: Scott to create a diagram/description of the problem on the wiki (design documents section) to help everyone understand.

Sprint Deliverables

  • 6.3.x
  • Lucene

Mayo to create snapshots for both branches of code

6.3.0.1 - OBI fix and UI dropdown filter on coding schemes

Lucene - latest implementation

VPN and network evaluation

 		Craig pinged the Mayo and NCI personnel and hasn't heard back yet.
Horizontal Coding Scheme searches 
Face-Face Planning 

December 8 - 10 on-site.

There is a wiki link for agenda topics: LexEVS 6.3 and 6.4 Technical Face-To-Face Meetings

CTS2One client should be able to connect to multiple instances of a service.  Can one endpoint provide data to query against another?  How can CTS2 be used in a manner that provides uri's that are not a part of the local resources.  Possible face to face topic. 
Boolean searches in Lucene 5

1) backwards Backwards compatibility, if no extra information is included in the lexevs search call the resultset should be (nearly) the same as we currently get.

  • To the best of our knowledge, this is true.

2) expose Expose the ability to do Boolean queries over different user-specified fields (e.g. presentation & definition) a la https://lucene.apache.org/core/2_9_4/queryparsersyntax.html#Fields.

  • We will need to discuss what the requirements would be.  The boolean query is mainly at the API level of Lucene and isn't exposed.
Search queries

Discuss how to determine whether a search query requires accessing the database opposed to the Lucene index only.

  • You can exercise the resolve as list (and pass in "do not resolve" flag).  This should not resolve and not hit the DB.
  • Resolved concept references are being queried from the DB.

JIRA Issues

Recent LexEVS Related Bugs and Features (within last week)

...