 |
Page History
...
| # | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
|---|---|---|---|---|---|---|
| 39 | Kevin | Demo of REST service exposed in Mayo value set browser | deferred | |||
| 53 | Craig | Update the project plan according to Tin's schedule | open | |||
| 54 | Tracy | Will try the NCI Thesaurus again. To follow up with Scott if this continues to load slowly. Will also test the new MedDRA load features. LexEVS-569 (NCIt took 22 hours to load). MedDRA load completed and needs examined | 09/24/2013 | open | ||
| 55 | Pradip | Pradip to get a lexbig.jar to Kim | done | |||
| 56 | Scott | Provide PTE Links to Tin for URI Resolver and CTS2 Service | done | |||
| 57 | Kim | Update JIRA item 581 and set to deferred | done | |||
| 58 | Scott | Update MedDRA to use the old URI. - This was tested and works. | 09/19/2013 | done | ||
| 59 | Scott | Contact Tracy about the details of the MedDRA active/inactive status implementation | open | |||
| 60 | Scott | Commit an interim fix for the Thesaurus xml export | open | |||
| 61 | Rob | To get files for Scott to do test load of the NCI Thesuarus | open | |||
| 62 | Kevin/Scott | To coordinate getting content from third party for wiki update | open | |||
| 63 | Kevin | Initiate discussion for Mayo on JIRA item #585 | open | |||
| 64 | Scott | Communicate to Craig on the possible government shutdown. | opendone | |||
| 64 | Kevin | To follow up on URI's on OWL2 with Harold. | open | |||
| 65 | Gilberto | To let Mayo know when SFTP site goes live | open |
...
| Area of Interest | Details |
|---|---|
| Loader Evaluation status | MedDRA and OWL2 load status. Will commit uri update – scott. Flagging of LLT's in MedDRA that are on longer active needs to be checked. Need to use this set the Active/Inactive. Scott to contact Tracy on this issue Will we be changing uri's for OWL2 – ping Harold. Kevin to follow up. Other work items have been noted. One issue outstanding that Gilberto will report on later. May use a different representation for the associations. . |
| 6.1 QA and Deployment | Stalled at the URI Resolver. Will keep the remote API. going up the tiers while the other deployments go up the tiers. Expectation is that all will be through QA early next week. |
| 5.1 and 6.0 MedDRA patch | Update requested. Multiple versions would cause an exception if there was a null passed in for version. Would like this to default to PRODUCTION tagged terminology or a terminology that is the only version of the terminology. The new loader does add a new URI for MedDRA, but a coding scheme uri would have to be a parameter. We could force the new loader to go back to the old URI. Scott to update MedDRA to use the old URI. 5.1 and 6.0 security jar is an NCI issue. Norval may try to apply a patch. |
| JIRA #492 | We need a status on this item. Would like to export from something newer than 5.1. Scott will commit an interim fix. |
| Release artifacts | Where will these artifacts be kept (formerly uploaded to Gforge). Gilberto waiting for a reply from the support about the SFTP site. Nearly ready to go live. |
| External Collaborator wants to add to the wiki | Kevin reported we have someone who has offered to document embedding lexevs in a web app. What is the protocol. Gilberto suggested he send his documentation for us to post. Otherwise he will have to get an LDAP account. Gilberto to follow up with Ann Wiley. Kevin/Scott to coordinate the upload of content. |
| Documentation | LexEVS Development Project and Design Documents |
| Readiness Review | Question to Larry Brem about preparations. Larry would prefer to do this without a meeting. Email is sufficient. Financial plan will be handled by Larry Brem. |
| Thesaurus load time | Rob will get files or file names to Scott |
| JIRA #585 | Question open on the '?' search for contains. Mayo will discuss and respond with analysis of implementation. (Kevin) |
| Memory requirements for 6.1 as opposed to 6.0 | 25% more memory in RAM requirements. 2GB is what we have on our DEV server. Updating Lucene could be an option. Going to 2.9 would not be painful. Going to 4 could mean extensive code change. |
| Next Week | Possible Gvt Shutdown. Preparations are underway. One possibility is that parts of EVS will remain up. Deployments may not happen. Work communications via Government email will cease after Monday if this happens. Scott to communicate to Craig on this matter. |
...
