You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Agenda

please add or suggest any additional items

Updates

  • Brown
  • Duke – congratulations on the launch of http://scholars.duke.edu
  • Florida
  • Johns Hopkins
  • Memorial University
  • NARCIS 
  • North Texas
  • Scripps – 
  • UCLA –
  • Weill Cornell – 
  • Cornell Ithaca – 

Discussion Topics

Collaborative ontology development tools

(Jing)

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:Description>
</rdf:RDF>
Here is how this looks if you click on the link from the document record:

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

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.

Review and prioritization of changes for VIVO 1.6

  • Publication types and coordination between Sympectic Elements publication types and VIVO/BIBO types
  • Artistic Works 
  • Research grants – what are the differences between grants, awards, and contracts?  How do NIH and NSF (and other funding agencies) model grants, so that VIVO can align data harvested from NIH RePORTER or research.gov? 
    • Annual amendments, side amendments, the new app R01
  • Distinctions among North American, British, continental European, Australian and New Zealand academic position types
  • Courses and semester classes – can we finalize the Course as a continuing entity that is realized in Semester Class events?
  • Representing and displaying re-publication or performance

Other recent issues

  • Former titles of organizations
    • will it work for Brown, as Nicholas suggests, to create a separate organization with the then-current title and link to it from the current organization with the hasPredecessorOrganization property?

WebEx Call-in Information

  • Topic: 2013 Bi-weekly VIVO Ontology Call
  • Date: Every 2 weeks on Wednesday, from Wednesday, January 23, 2013 with no end date
  • Time: 11:00 am, Eastern Standard Time (New York, GMT-05:00)
  • Meeting Number: 648 855 983
  • Meeting Password: (This meeting does not require a password.)

To join the online meeting

Call-in Information

  • No labels