Resources

Attendees

Agenda & Notes

  • CERIF2VIVO
    • Types are added in a first draft by Tatiana Walther
    • Dragan will look if the list of types are complete
    • Mapping precision will be expressed by SKOS vocabulary: https://mapping-commons.github.io/sssom/spec/#predicates
    • Christian: What are next steps?
    • Philip: In line 20 mapping from data property to a class is hard to do, how are we going to do that? How do you specify gender in VIVO?
    • Christian: This ontology has property has gender and you are related to instance of class of gender.
    • Brian: I have never seen VIVO that uses gender. This came with VCards. They might did it in the version we picked. The range is uri. Choose the uri is implied. This is from VIVO ontology.
    • Philip: we can add another comment column, we don't want to map it because it is not used in VIVO yet, we should note that.
    • Christian: Lets go one step back. How do we deal with equivalency?
    • Anna: Don't we have a standard way to do so? On vivo ontology materials there was something about abstract roles and styles.
    • Anna from chat Ontology Design Choices and Practical Ontology Design Principles in the VIVO context#Contextnodes
    • Jose: reasoning and transformations. We have a matching, but don't necessarily have need equivalency to resolve it between two instances (if it is just for transformations). We can use SKOS and people who build this will understand that later. I will look for other strategies for ontology mapping. Spreadsheet contain types null and blank. The ones that blank are not created mapping yet or that are impossible mappings?
    • Christian: would you agree that we should create human readable structure first to create machine-readable mapping later?
    • Jose: Yes. If you need reasoning, then it should be a bit formal, but now it is not the case.
    • Philip: Our use case is transformation: get data from CERIF format to import it into VIVO.
    • Christian: If there are converters then people would have to make decisions based on local context. It is enough that we are doing this now. What would be the next step now? Somebody would have to go through every row of this eight tables and mark it somehow.
      Should we do that independently, maybe at least 2 people? First can mark green and second reviewer check that again. How would you do it?
    • Brian: If we would like to do that the same like on development side, then once the comments are resolved, then two people should independently check that. If that is possible, then that would be nice.
    • Jose: We have two people and we use simple column scheme and people work together and mark columns and then next group just review these cells and approve/reject that. Maybe we can do peer review?
    • Christian: my approach is second person look at this only if first person is not sure.
    • Jose: We can use simple colour scheme green - ok, yellow - adjustments , red - completely wrong/ should be discussed.
    • Christian: it sounds like a good idea, but I am not sure if this is realistic. In general it was how me and Tatiana did that together. It was pretty quick.
    • Brian: If we don't schedule we won't do it. We should put it in our calendars.
    • Christian: Who will do it?
    • Jose: Everyone
    • Christian: I will spend at least 2 hours on this. I will try to ask other people to participate in this. I think we agreed on this.
    • Christian: It should be more fun to do that in pairs.
  • VIVO Ontology Editor: There was a new interface for the VIVO ontology editor by Muhammad Javed et al.:
    https://github.com/cul-it/scholarsVitro/tree/feature/ontology-editor, a screenshot is on slide 13 of https://zenodo.org/record/1000484.
  • VIVO 1.13: Issues with relevance to this group?
  • Versioning and release management


  • No labels

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