Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Scott: SNOMED Transitivity table, Tree update, external users

• Majority of time on the transitivity table issue.
• Started to look at the tree extension.
• External user support - many different users.

Cory: AMIA poster

• Feedback updates made.
• 2nd version sent for review - due by Thursday.

Craig: Project Plan, Poster

• Initial version sent to team.
• Browser team needs to identify issues to be in 6.3 (OWL2 and Namespace issues needed.).
  
  • Jason to let us know the timeline.
• Some OWL 2 issues will need more discussion, but others can be acted upon right away.
• Deployment tasks - based on 6.2 release, is it possible to be able to deploy faster, easier - and will that help deployments going forward?
  • PTEs are better defined.
  • Additional documentation can help with the PTEs (better communication)
  • Make sure all requirements are captured completely.
  • Permissions need to be captured/documented.
  • If process is still changing - we may need to respond in a similar way as we did for 6.2.
  • Need a level of commitment from the NCI deployment team to focus on the deployment.

MetaBrowser had lock - couldn't use the indexes. Jacob changed permissions and it resolved the issue. (Happening on Stage)

Group permissions on specific groups needed to by applied. Storage team notified and they will change users when the indexes are being written (different Tomcat users).

PTE updated to include change of permissions command.

No notices that this has been applied up the tiers. (It is running on QA).

SNOMED - time spent performing loads locally at Mayo - transitivity load happening every time. Cannot duplicate error seen at NCI. Reviewed the SQL output - there is nothing that stands out that would identify a problem.

There is a QUIT command - not sure why it is there, so investigating why it is needed.

Local install is set to all defaults, so nothing specific has changed (or is changed for the load).

Learning about how MySQL works to determine of there are any problems associated to DB config.

May need to consider having Kevin take a look

Several ongoing external support discussions.

Recent user:

Wants to use the GEM loader as we describe in the documentation.

• GEM loader hasn't been updated for a very long time. ** we should not list it as available
• This GEM loader was tested in the past, but never used.
• Currently use MRMAP for RRF.
• Kevin located the GEM loader on Mayo SVN. Suggest that we post GEM loader to Git and make it available to users (identify that it does not currently work)

Also was interested in using the GUI for authoring.

Possible interest generated from Git? Other reasons?

There is a risk that the hierarchy will change to support this tree update.

Running this against the NPO file

to look at issues that may exist.

Possibly look at zebrafish (small enough).

Namespace issue is holding up the update.

There should be a supported coding scheme for each supported namespace in LexEVS.

Scott will revisit and confirm the underlying issue.