search

openrif / vivo-isf-ontology

The "VIVO-ISF Ontology" is an OWL2 representation of the VIVO-ISF Data Standard
16 stars 9 forks source link

Explore distinctions among U.S./Canadian/Au/NZ/UK and continental European academic position types #722

Open mconlon17 opened 6 years ago

mconlon17 commented 6 years ago

Originally by Jon Corson-Rikert:

Based on work by Tamy et. al. for NARCIS in the Netherlands, published in part at http://arxiv.org/abs/1304.5743 – the problem being that American/English concepts of instructor, assistant professor, associate professor, and professor don't map well to European titles. Even the concept of a faculty member may not translate intuitively for European universities. Pulls in the thread from Paul on academic tracks described in https://issues.library.cornell.edu/browse/VIVOONT-436 – note http://medicine.kumc.edu/school-of-medicine/pdfa/faculty-mentoring-program/understanding-ranks-and-tracks.html and http://medicine.kumc.edu/school-of-medicine/pdfa/faculty-affairs/faculty-ranks-and-tracks.html as resources on the U.S. system from the University of Kansas

This is an excellent task for an ontology interest group to undertake – not sure if Tamy Chambers from IU, who worked on the VIVO trial implementation in the Netherlands, is still active, but she is one who raised this issue.

Christian Hauschke, TIB commented: FYI: Earlier this year, Elena Liventsova published her bachelor thesis on differences between standard VIVO implementation and German needs: https://serwiss.bib.hs-hannover.de/frontdoor/index/index/docId/803 (only in German). Its focus is on positions and organizations.

https://jira.duraspace.org/browse/VIVO-1106

mconlon17 commented 6 years ago

Medium Impact (but could be low or high, depending on how this is implemented)

If existing position types are removed, and replaced with new types to accommodate a new, more comprehensive, international, position typology, then the impact is high -- most sites are using position types and would need to change them in their triple stores and in their queries.

If existing position types remain, and new position types are added as subtypes or super-types of existing position types, the impact could be low -- the implementation of the issue would be solely to add new types.

If the implementation branches out to include person types, or the change from person types to person roles, the impact is high.