11:00 am Eastern time

Agenda

Meeting notes

  • Updates, issues, questions and feedback from particpants on the call
  • Timing of the ontology call: later time for West Coast participants? Alternating week with implementation call?
    • Michaleen fine at this time (only west coast person)
    • 2 hours earlier with Colorado – okay
  • Call for requirements for release 1.5
    • Release 1.4 out – changes documented on the wiki
    • New data you want to import or ingest – how to represent
    • using the ontology Jira component – a number of older issues to work through in upcoming, too
  • http://issues.library.cornell.edu/browse/VIVOFEED-1018 (display ranking of grant personnel not working as hoped)
    • Paul – is this still an issue? If people have different roles (key personnel, investigator, etc)
      changed the display rank of the class – do we respect that?
      part of the application ontology, not the data ontology – still representing
      create an issue (or is there one) to create a displayRank-based ordering in the collated sort
  • http://issues.library.cornell.edu/browse/VIVOONT-430 (Classes for specialities, licenses, and global health specialty)
    • RPS is research profiling system, not clinical – but back end is sometimes used for both POPS and RPS. a relational database running on FatWire, an enterprise CMS. column should be labeled property groups, not class groups – Paul wants a section of the page called "Clinical" may need a property in addition to a class – e.g., has clinical specialty pointing to an instance of Clinical Specialty Specialties, Clinical Expertise, and Board Certifications Specialty – want to tack on the label Clinical Specialty might lock down the field and only let some people edit it definitely a controlled list for Board Certifications – thought of as licenses. we have a class called Licensure clearly some value in relationship to a Medical Practice (a Clinical Organization) via a membership relationship, as on Curt Cole's VIVO page by using a membership role, could have temporal bounds don't need to repeat the specialty information on the role people don't edit their profiles in WCMC VIVO want a global health section of the page – used only about 10% of the case, but an important has come to mean working in developing countries could technically have the same issues as with domestic vs. international do you want separate specialties, or just a separate property? Paul will ask Curt whether the specialties are a separate list or overlap medical specialties
  • Representing languages spoken. See Alex Viggio's email on the ontology listserv
    • lexvoj.org has merged into lexvo.org
    • have created URIs for languages and mappings to DbPedia
    • lingvo ontology seems to extend FOAF with language competencies
    • http://www.lexvo.org/page/term/eng/
    • do they have services? likely, or at least a SPARQL endpoint
      also covers script
  • Versioning of UMLS concepts
    • one URI or different ones for different versions of UMLS? If there is a different URI for each version, our current method of having a isDefinedBy property statement to an untyped URI since we don't know what kind of thing defines it – an annotation property out in the world that we use as an object property

Call-in Information

1. Please join my meeting: https://www1.gotomeeting.com/join/956365752

2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone.

Dial +1 (646) 558-2103
Access Code: 956-365-752
Audio PIN: Shown after joining the meeting

Meeting ID: 956-365-752

last meeting | next meeting

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.