LexEVS Meeting Minutes

Meeting Name: / LexEVS Technical meeting / Location: / 11-10
Date: / 02/17/2010 / Time: / 1:00 PM CST
Facilitator: / Craig / Attendees: / Craig, Scott, Cindy, Kevin, Deepak, Mike, Russ, Larry, Musharaf, Satya, Gilberto, Sherri, Kim, Dave, Jason, Tracy, Frank, Steve
Conf. Line / 866-365-4406, #5388249, Centra ID Mayo_LexGrid2
Topic / Discussion Points / Action Items
·  Status (Craig) / ·  Continuing design documentation – data access layer available soon / · 
·  Browser Issues (Jason/Larry) / ·  No pressing issues
·  Lucene issues have been addressed. / ·  Jason will test lucene on staging server
·  Gforge #26492 (http://gforge.nci.nih.gov/tracker/?func=detail&atid=1850&aid=26492&group_id=491) (Kevin/Tracy) / ·  Questions posted to Gforge regarding this issue. Has been open for a while – how best should we handle this. Started from multiple statuses. Now load both status attributes. Issue is only having space for one so chose not to populate at all, which means data not sent correctly. May have to introduce rules for setting as active or inactive attributes.
·  Options include - can we have a consolidated status if there are multiples? – can it be defined in the source to identify an active or inactive flag
·  Status is a string and active is a Boolean. We need to give the loader some rules to know when to set active or inactive attribute
·  Would be good to learn what users are experiencing with status
·  Possibly create mapping preferences
·  Possibly a post processing script to handle per environment
·  Users are not interested in local conventions. Want terminology shield them from one terminology to another. Want same indicator – easy to use mechanism – either modify load process or modify way data is gathered. A flag to tell them the viability of the data – global indicator suitability of use.
·  This will be part of the next Lex EVS release
·  Will remain as bug until work around is applied but will also add as a feature request / ·  Tracy to update bug with current work around and will create a feature request
·  LexEVS Revision Overview (Satya) / ·  Revision API
·  May need to revisit CTS2 requirements to review use case and provide group an update/example at a future date.
·  More of this information can be found on the Confluence Wiki
·  Will caBIG users want to use this? / ·  Needs further discussion – how to export revisions to a Delta – built into the thesaurus
· 
·  / ·  / · 
·  Other Topics? / · 
Adjourn / Thanks for your participation!

LexEVS_20091202_MeetingNotes.doc Page 1 of 3 2/18/2010