Agenda

please add or suggest any additional items

Updates

Discussion Topics

Collaborative ontology development tools

(Jing) Goals are to have a common workspace for the official VIVO ontology and for extensions to it that are under development.  The VIVO team at Hopkins will be a decentralized effort and they will need collaborative tools even for their own purposes.

Proper use of global citation count

(Paul) 

We are ingesting citation counts. Does it seem odd to anyone else that the citation count seems to belong in two places - the label and the hasGlobalCountValue? I couldn't find another case where repeating data in the label and a traditional data property is necessary. See the bolded RDF below.
<rdf:RDF>
 <rdf:Description rdf:about="http://vivo.med.cornell.edu/individual/n6652">
 <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Thing"/>
 <rdf:type rdf:resource="http://purl.org/spar/c4o/GlobalCitationCount"/>
 <c4o:hasGlobalCountSource rdf:resource="http://vivo.med.cornell.edu/individual/n4674"/>
 <c4o:hasGlobalCountDate rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2013-04-19</c4o:hasGlobalCountDate>
 <c4o:hasGlobalCountValue rdf:datatype="http://www.w3.org/2001/XMLSchema#int">18</c4o:hasGlobalCountValue>
 <rdfs:label>18</rdfs:label>
 </rdf:Description>
 <rdf:Description rdf:about="http://vivo.med.cornell.edu/individual/n4674">
 <rdfs:label>Scopus</rdfs:label>
 </rdf:Description>
</rdf:RDF>
Here is how this looks if you click on the link from the document record:
https://dl.dropboxusercontent.com/u/2014679/citationcount.png

Modeling institutional affiliation

(Paul)

About a year ago, I put in a JIRA ticket to ask how we should model co-author affiliation:
https://issues.library.cornell.edu/browse/VIVOONT-444 (moved to DuraSpace JIRA VIVOONT-5)

That seemed to be a real stumper, because the fix version was delayed until post-1.6. At the time, I put in the ticket our publication ingest wasn't working and the Scopus API was outputting XML showing institutions in a big lump rather than tied to each author. Now though both of those roadblocks have been overcome. Also, unlike before, I have a not terrible approach to this. But I'm not sure if it's ideal.

For every author in the data, there is a Scopus-normalized institutional name (e.g., the author lists "Weill Medical College of Cornell University" and Scopus maps that to "Weill Cornell Medical College"), and a Scopus-generated institutional identifier (e.g., 60007997). In cases of multiple affiliations, you will see multiple institutional names and identifiers.

Here's the approach:
1. Create an object property for InformationResourceInAuthorship called ScopusInstitutionalAffiliationID.
2. ScopusInstitutionalAffiliationID has a range of foaf:organization.
3. Give foaf:organization has a data property of ScopusAffiliationName.

This will be really useful for us if we can bring these data in: it will populate our Dashboard, we can see how often our faculty actually list our institution, and we can identify patterns of inter-institutional collaboration.

discussion

Review and prioritization of changes for VIVO 1.6

see VIVO Ontology v1.6 Issues

Other recent issues

WebEx Call-in Information

To join the online meeting

Call-in Information