...

• Anna Kasprzik
• Brian Lowe
• Violeta Ilik
• Sonja Schulze
• Christian Hauschke
• Mike Conlon
• Marijane White
  
• Don Elsborg

Agenda

1. Updates, intros, review agenda
2. Ontology licenses  See http://bit.ly/2TDpqnl
3. Change Process – draft here: http://bit.ly/2TAaqXg
4. Identifiers – proposal is here:  http://bit.ly/2wEyy17  
   1. Some background from RDA is here:  https://www.rd-alliance.org/system/files/PID-report_v6.1_2017-12-13_final.pdf
   2. discussion
   3. next steps
5. December 3 sprint
   1. New subClasses for items asserted to be skos:Concept.  

      Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1287

   2. Administrative Unit 

      Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1652

6. Future agenda items
   1. Language skills
   2. Projects and Grants
   3. Application ontology
   4. Research object

Notes

Ontology licensing -- everyone feel free to pitch in

Change process

• We never shared this with the rest of the VIVO community

• Is it stale, given the active developer IG?

• Need to review in ontology meeting

• Ontology and annotation as “configuration” of the application

• Marijane as a guest speaker at development regarding ontology

• Steps for change process

• Review here

• Discuss/review with developers -- MJW offered to present to developers

• Discuss review with governance

Identifiers

• Several different use cases (see document)

• Don - with identifiers as object properties, can we assign attributes to them that describe their nature. For example does the target url of the identifier render rdf? This might allow developers to code against it.

• Mike - Yes.  Must be mindful to separate actual real world attributes vs. display/developer type of attributes (annotations)

• Following discussion, the group agreed to prioritize the change management process and continue to discuss the need for changing identifiers.

Open tickets

• Jira 1287 -- Assigning new parent classes to five entities currently with parent class skos:Concept.  The result is an application that appears to work as before, but no longer lists these entities in search results for concepts (a highly desirable operational result). Need reviewers.  Don Elsborg offered to review

• Jira 1612 - what is an AdministrativeUnit - lot’s of discussion around this. Christian noted this is very important to German academic institutions.  Zentrale Einheiten.

• Is this distinguishable from Administrative Department (which also has not yet been added to VIVO, but perhaps is much clearer such as IT, Purchasing, Office of the President.  VIVO currently has Department with sub-class AcademicDepartment, but no corresponding subclass AdministrativeDepartment.

• Individuals in the AdministrativeUnit class are intended to be “place holders” on org charts -- in some org charts we need to be able to say “these orgs are part of that administrative unit and that administrative unit is part of something else” even when the administrative unit has little that indicates it *is* as organization -- no legal standing, no leader, no budget, no employees.  What *is* such a thing.

• Can we have some guidelines regarding when we might add new sub-classes?

• “Administrative Unit” is heavily loaded terminology and might not be a good choice for this class.

• Distinguish from Virtual organization (or not?).  A virtual organization is often used to describe adhoc collections of people who come together for research purposes.  See https://en.wikipedia.org/wiki/Virtual_organization

Action Items

1. In Progress or Review Ontology Issues

...