Monday November 1, 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

• Melanie Wacker 
• Brian Lowe 
• Christian Hauschke 
• Anna Kasprzik 
• Dragan Ivanovic 

Agenda

1. Mapping VIVO2CERIF - Christian Hauschke, Dragan Ivanovic
   1. if CERIF refactoring is excluded, an updated mapping of the mapping tables CERIF2VIVO) is not extensive work
   2. mapping should be done in a mapping language or similar, so the mapping can be used to build a CERIF compliant export 
   3. Maintenance is still an open question 
   4. First try: Someone goes through the doc and comments on all changes of the VIVO ontology. If that is not possible, we will split the responsibility for the first review.  
   5. Christian will post a call for action to the ontology channel.
   6. Next steps will be discussed when the document is completely reviewed by four eyes.
2. CRIS2022: https://eurocris.org/cris2022-conference-call-proposals, Deadline Feb 15.
3. Brian and Dragan were discussing how to go forward with old VIVO Ontology issues
   1. Suggestion: We suggest to open a new github organization called "VIVO Ontology". On a date yet to be determined, we will fork the VIVO-ISF repository named "VIVO Core Ontology" into this organization and replace the ontology with the latest version in the vivo-project/vivo repository. This repository will be the future home of the VIVO ontology and its modules, where new issues will be created and addressed. This will allow for separate handling of ontology and software related issues. 
   2. We will post that to slack, mailing lists and decide on it in the next VIVO IG.