NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 5

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.

...

Sprint Status

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

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

Sprint Planning

Sprint 10 Planning

Upcoming Sprint - Sprint 10 (August 6, 2015 - August 19, 2015)

LexEVS 6.4 Agile Development - Sprint Status


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") AND created >= 2015-07-29 AND created <= 2015-08-05
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-07-29 AND created <= 2015-08-05
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
serverId7954a81f-12da-3366-a0ef-97c806660e7c

 

Issues to look at this sprint:

  • LEXEVS-1033
  • LEXEVS-1034
  • LEXEVS-1037

6.3 Deployment Status

  • Documentation/updates
    • DNS Changes/Updates
    • CTS2 Value Set Client updates
    • Heroku updates

DNS changes may happen this Thursday or Friday.

If there are issues reported with the DNS switch, it will be switched back to the LexEVS 6.2 URL.

VPN and network evaluation

  • Update from Gilberto and Jason
 No updates.

External Request

  • ?
 None.
Working with Coding Schemes

When dropping a coding scheme, validate that the index is removed and make sure we test that the metadata.xml file is updated accordingly as well.

When updating an index, make sure that the metadata.xml be updated correctly.

Administration of loading metadata in the GUI is cumbersome.

The last loaded value set is at top (or bottom) of the list and hard to find (page through) - in GUI and CLI.  Resolved VS and Mappings are loaded as coding schemes.

They would like a list of just coding schemes, or resolved value sets, or mappings.

This type could be captured in the index.
Sprint DemosIt was suggested that if there was test code to deploy or demos to show at the end of the sprint, we should do that during this weekly meeting.

JIRA Issues

Recent LexEVS Related Bugs and Features (within last week)

...