Monday September 6, 10 AM US Eastern Time

Connection Info

See #ontology in vivo-slack for link.  To join vivo-slack, go to http://bit.ly/vivo-slack 

Resources

Ontology Interest Group Google Folder https://drive.google.com/drive/u/0/folders/1RGBh4fDZdzpJdwyiUMO8OPWwkcmVYrI0

Google Doc for meeting notes: https://bit.ly/3vuN5cC

VIVO Ontologies on Github:  https://github/vivo-ontolgy 

OBO Slack https://join.slack.com/t/obo-communitygroup/shared_invite/zt-kpkvg7x3-kz7DeGoYKiY~VGWKO0voQg

Attendees

• Ralph O'Flinn 
• Mike Conlon 
• Melanie Wacker 
• Brian Lowe 
• Philip Strömert 
• Christian Hauschke 

Agenda

1. Work in Progress
   
   1. AEON - https://github.com/tibonto/aeon
   2. LANG – https://github.com/vivo-community/language-ontology
   3. ORG – https://github.com/mconlon17/organization-ontology
      1. Quality vs. Contextual Role vs. Disposition vs. data properties: Can be discussed using the homepage qualities in ORG ontology. Quality does seem to be feasible because a website is not "naturally" an official website of an organization. Maybe easier to use subclasses like "homepage", "wikipedia page" etc. 
      2. ORG comments in spreadsheet
   4. ADO - https://github.com/vivo-ontologies/academic-degree-ontology
   5. IDO – https://github.com/mconlon17/identifier-ontology
2. Annotating the VIVO ontology
3. Next meeting: October 4, 2021. 

Notes

How about the import workflow in VIVO

1. AEON
   1. Currently starting with AEON in VIVO. Annotation settings have to be done. Christian Hauschke and Philip Strömert will work on this.
   2. Potential clashes have to be identified (event org)
   3. SHACL shapes would be useful to define uses for events in VIVO.

2. how to incorporate new ontologies into VIVO

   1. Christian will invite Dragan Ivanovic to discuss the role out of ontology modules into the software.

   2. Possiblee topics:
      1. Interdependencies between ontology and the application (and its respective development).
      2. Documentation (where?, how?)
      3. Ontological change management
         1. how do we make the data changes
         2. look into how the do it at COB (SSSOM mapping templates, using skos:exactMatch/closeMatch/relatedMatch)
         3. migration can probably not be done in an overlapping fashion
            1. the existing VIVO ontology must be made smaller → deprication management
            2. external data conversion from old format to new one and then import in a vanilla VIVO
            3. all this needs analysis of existing data
3. how to transition, what are the steps what is the testing scenario
4. how to deal with needing only a subset of a suitable ontology module or other restrictions on the ontology in VIVO
   1. Mike: this is all to be done on the application level
      1. maybe add an annotation to be able to produce a subset/submodule or SHAQL shapes