Meeting notes for Project Management meeting (10/27/10)

Attendees:

Margaret

Gilberto

Kim

Jason

Traci

Steve

Tracy

Will

LexEVS:

Need to come up with a timeline for the performance testing. When do we want to do the test? How to test with what applications? What is left for setup?

Decision was made to have the test on Thursday afternoon. Kevin has been contact with caDSR for UAT testing.

We need to point DEV Term Browser 2.0 and Report Writer 2.0 to the QA LexEVS API.

Kevin had some scripts that exercised the API.

We want to run caDSR applications.

Spoke with Greg Raley about participating in the performance test on Thursday.He said he still needed to talk to Denis Avdic about it and he was not available on Tuesday. Greg said he will talk to him on Wednesday and let us know. He thought that Denis was working on a test script that would run through the caDSR application functionality that utilized LexEVS. I will check back with him after the meeting.

.

Browsers:

Term Browser:

1.2.1 Patch Release:

[GF#29949] Missing data occasionally
[GF#29966] Handle coding schemes with multiple namespaces

Dealing with multiple namespace (such as NPO)is something we eventually need to do.

There will be a significant change to the browser.

Continuing with the patch release to cover the other issue found by Tracy:

ncit-Bugs][29944] Defined and primitive concepts reversed in NCIt browser.

2.0 Release:

We are currently having an issue with the DEV environment when we try to point to local LexEVS. Norval is working on the issue. In the short term we will need to point DEV to the remote LexEVS on QA for the performance testing.

Nothing really additional to discuss with the 2.0 development.

Report Writer:

Nothing new. Starting work on the 1.2 release of LexEVS QA is finished.

Metathesaurus Browser:

Nothing new. Work will start after 5.1 Data BDA is complete.

Protégé:

Reviewed the remaining trackers and we now have a preliminary scope. There might be an additional bug in the PT/Preferred_Name/rdfs:label synchronization somewhere that would be included in the scope. We are waiting a couple of weeks to start development. Bob and Tim have a couple of tracker assessment tasks to measure the degree of effort to fix some of the items. We are going to nail down the scope in schedule in the next protégé meeting on November 12th.

Strategy meeting tomorrow for Web Protégé. Attendees include Gilberto, Sherri, Bob, Tim, Tania, and myself.

QA:

Have a new QA resource starting next week. 100% allocation for EVS. (Arthur)

Operations:

Packaging wiki today to move to prod.

Data BDA:

N/A

Systems:

Shutdown of LexEVS 4.2 –

caMOD:

Received an update from Sima last week. She said that she is still working on getting the solution to work with the existing code, but I am getting closer to being able to display something that she is hopeful will look like vocabulary tree.

Kim also got a message from Sima yesterday asking for some assistance and Kim responded:

I can finally display all the trees using a DMTN except the Human Organ tree. But I will work on that after updating the search code.
I started to look at NCIT again. I want to do something like searchByName ("contains" and "exact match" options only) from the SearchUtils.java class. You return a ResolvedConceptReferencesIteratorWrapper object from searchByName() which I do not want to use.
I think that I can do something similar but return a list of concepts from the ResolvedConceptReferencesIteratoriterator instead. Then I can use the concept list to compare it with each node within a single tree. My original code compare results of a synonym search to each node so this would reuse most of the existing code.
What do you think about this approach?

caDSR:

Sentinel tool is now in QA.