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 
• Dragan Ivanovic 
• Tatiana Walther 
• Christian Hauschke 

Agenda & Notes

1. CERIF2VIVO - Updates and next steps
   1. Descriptions for the infrastructure elements (equipment, service, facility) in CERIF
      
      1. is basically completed by Dragan, waiting for review
   2. Mapping precision
      1. Idea: Why not use the SKOS terms? CloseMatch, exactMatch, etc. https://www.w3.org/2009/08/skos-reference/skos.html
         broadMatch? - https://www.w3.org/2009/08/skos-reference/skos.html#broadMatch
         
      2. Terms of standard vocabularies https://github.com/EuroCRIS/CERIF-Vocabularies, https://github.com/EuroCRIS/CERIF-Vocabularies/blob/master/PersonEmploymentTypes.xml - how to match? Example for employee types from KDSF: https://www.kerndatensatz-forschung.de/version1/technisches_datenmodell/v_1_2/index.html#http://kerndatensatz-forschung.de/owl/Basis#WissenschaftlichesUndKuenstlerischesPersonal
         alkategorie
         
         
2. Wrap-up: CERIF2VIVO at CRIS conference - Dragan Ivanovic 
   1. ~50 people in the session
   2. Q: Wouldn't it be easier to map to a refactored CERIF? A: Yes, but we can't wait. After the refactoring project is over, we have to consider a second run with the new scheme.
   3. Q: Case study to validate this mapping. A: Ideally implement a tool to ingest CERIF data in the future.
   4. FAIR Core for EOSC (Dragan Ivanovic?) - might be an option to put VIVO into the planned mapping service.