Agenda:

1. Introductions

Nicholas Rejack - working with Vivo for 2.5yrs, ontology and data, worked on CTSAconnect - JavaScript Vivo tag cloud, local extensions for Florida

Demaris Murry - implementing ontology in Symplectic Elements - for bringing pubs into Vivo, especially artistic works, and are having challenges in figuring out how to represent works in Elements so that they map across successfully. (Melissa) -- maybe we could invite them to a future call.

Dagobert Soergel -interested in ontologies, working on Buffalo CTSA proposal, in charge of evaluation and infrastructure for CTSA and VIVO

Daniela Bourges - Architect of eagle-i software, using ontologies for ontology-driven applications, participated in CTSAconnect

Lisa Charlong (Memorial U) computing and communications - public engagement managing migration of yaffle to VIVO framework, modeling knowledge mobilization ontology KMY-O

Nivaldo Fernandes (APA) need ontology for psychology, MARKLogic in new version has a triple store so are looking forward to being to work with VIVO via that platform. They are interested in bringing the APA thesaurus into the ontology world. (Melissa) -we’ve done this for other vocabularies in the ISF, and will be interested in generalizing how we do this.

• Beverly (APA) -- have a SKOS representation for the APA thesaurus and are interested in making connections to the new VIVO-ISF ontology -- is a copy available?

• Melissa -- we have a Google code site for the ontology (and an ontology browser) and can do a tour in a future call. (Jon - it will also be available via the upcoming VIVO 1.6 release)

Steve McCauley Brown University, worked on Vivo for a year, uploading faculty data from CVs into VIVO, and some artistic works, and building out the ontology for this purpose

• (Melissa) -- interested in finding commonality in local extensions, and doing an inventory of what people are finding they need, so that we can try and accommodate needs in the ontology centrally. It would be useful to have a list of extensions on our wiki -- suspects that many deal with organizational partonomy

Violeta (Texas A&M) -- interested in working with SciENCV, cataloging subject analysis. Also interested in working with others in the VIVO community on having VIVO URIs serve as a non-MARC authority source for the Program on Cooperative Cataloging

Zac Painter (EPA) - student services contractor working on data maintenance.  EPA is releasing a VIVO instance for office of research and development, Oct-Nov, small ontology fleshing out things that are specific to EPA, many having to do with organizational structure. As other offices jump in to make VIVO an EPA-wide project, there may be different naming conventions. (Jon) The USDA has certainly found a need for different organization names and structures.

Daniel Calto Elsevier, Sci Val Experts, map data to VIVO, a number of customers are implementing VIVO data export (Elseiver is a sponsor for Duraspace vivo incubator project)

Janos Hajagos, Stony Brook, how do we connect across terminologies -- (Melissa) Janos has been instrumental in the CTSAconnect project in linking from ICD-9 (medical diagnosis coding) across to MeSH

2. Working group membership - how do we promote more active participation?

(Melissa) goes along with participation in development -- we need to open up the actual development processes to more community members -- errors that people are finding or requirements that haven’t been addressed. Many of you have skills, and with the end of the CTSAconnect project it will be helpful to have participation both in moving the ontology forward and in helping to identify targeted projects for grant support.

3. Participation in ontology development. Who in the community is interested in aiding the ontology work directly? How do we get more participation, in documentation, error reporting, and extensions in new areas

4. Planning an ontology hackathon. Who is interested? We could have an online meeting this fall, and then a face-to-face meeting co-located with a development hackathon in Feb-March?  An extra day tacked on before or after the 2014 I-Fest?

• APA has offered to host -- they have good meeting spaces and are centrally located in downtown Washington, adjacent to Union Station

• Damaris will explore ideas with Julia

• Dagobert- need to identify specific issues that need to be addressed first, in small groups, for this to be successful, with larger group discussion at the end

• Melissa -- let’s try to identify small groups willing to work on specific pieces

• Lisa -- some of the existing ontology efforts (e.g., humanities and knowledge mobilization) could put forth what has been worked on for review by others, growing out of an inventory

• Open annotation and PROV-O, organizations ontology from W3C, Ontology related to web security, need to figure out how these relate to VIVO-ISF

• Dagobert -- there is also an international digital humanities working group, focusing initially on text mining and metadata encoding but also working some with images. So far they have a list of objects but could likely be enhanced; they are looking for comments by September 27.  “Taxonomy of DH Research Activities and Objects” https://docs.google.com/document/d/1uosCjUW_dpSjdRNxBaFdDY0W-D0dTMHbLwTFuEvbDFg/edit 

• the humanities people in the VIVO community should have a look

• Other potential synergies or focus areas? People likely need to see and get used to the VIVO-ISF ontology changes first

5. Planning the VIVO-ISF ontology move to Git. It will move from SVN on Google Code to a new project here: https://github.com/vivo-project -- we will do that after the eagle-i ontology has been deprecated and the ISF fully integrated into the eagle-i code, likely in a few months.  There are good features on Git for working with ontologies, such as a good issue tracker and ways to generate documentation

6. VIVO 1.6 release status update, incorporation of new vocabularies - humanities, engineering using SKOS

• Brian -- close to a code freeze so can enter a testing phase. Polishing up the data migration and are optimistic that existing data will move seamlessly, but will be testing with more

• (Dagobert) What about migrating the data for the old VIVO ontology to the ISF? (Brian) -- we have a table of rules and software to move the existing data in the triple store. This only deals with data already in VIVO, and there will still need to be updating on a case-by-case data of data ingest tools and other locally-dependent tools.  This has been done with previous releases quite successfully, with typically only quite minor edits needed around the edges.

• Dagobert -- need a human-readable version of the ontology for people who don’t readily deal with OWL files.  The mapping table also needs to be made available in human-readable form, as this will be essential for migrating ingest tools. Since the ISF includes so much more scope that the VIVO 1.5 ontology in terms of what can be represented, we need to provide guidance as to what can now represent

• Jon -- this doesn’t in any way lessen the need for the eagle-i application; it makes the two applications work off a single ontology structure

• Dagobert -- a common stack of data across both eagle-i and VIVO

7. Collaboration and alignment with CASRAI content, upcoming CASRAI workshop (see http://dictionary.casrai.org/)

• We hope to be able to build an ontology representation of the CASRAI dictionary using the VIVO-ISF ontology, annotating as appropriate for CASRAI labels and definitions, and looking at CASRAI data elements that can’t yet be represented

8. Use of ISNI identifiers for organizations (what ORCID has agreed to use), and organization representation requirements (e.g. if ISNI does not provide partonomy for institutions, where does this live?)

• ORCID has recently decided to use ISNI identifiers for organizations in a partnership with Ringold, and given the large adoption of ORCID for people identifiers, we should strongly consider using the same identifiers.

• We haven’t yet seen the implementation -- not sure they have all the synonyms and alternate ids, but particularly not the partonomies -- in thinking how we represent these organizations in a local VIVO we may need to coordinate with them and invite them

• This also overlaps with work by the OBO Foundry (Alan Ruttenberg) and the larger ontology community would be interested

• Do the ISNI people collaborate with the Library of Congress and VIAF name authority efforts? (Violeta) Yes

• How is ISNI updated with new organizations or organization parts? (Melissa) -- ORCID says its easy to do that in a fairly efficient manner, and perhaps we can create temporary identifiers on the fly and then update them as real identifiers are created

Suggestions for the next call?

• The LOC Program on Cooperative Cataloging?  Perhaps when we’re more ready and their initiative to look for additional authoritative identifiers is further along

  
  

WebEx Call-in Information