...

POAgenda

please add or suggest any additional items

...

Proper use of global citation count

(Paul) 

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

• At some point (later this year probably), we will need to represent our affiliations of non-WCMC co-authors in VIVO.
  Naturally, we do not have an authoritative source for this data. What we do have is an assertion from Scopus that at the time the paper was published, a given author had a reported affiliation. 
  This really complicates the standard way for representing people and appointments. I'm not sure we can assume that someone whose affiliation was the same in 2006 and 2008, had that same affiliation in 2007. Or, that a person who had affiliation A in 2008 ceased to have that affiliation if that person had a different affiliation in 2009. This person could have dual affiliations!
  How can we assert affiliation without causing a mess?

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.

Thanks for any feedback!

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 RePORTER or research.gov? (Scripps has looked at this issue recently)
  
  • Annual amendments, side amendments, the new app R01
• Distinctions among North American, British, continental European, Australian and New Zealand academic position types
• The Open Annotation Data Model and its potential use to annotate researcher associations with areas of interest or expertise
• Provenance – what does it mean in the VIVO context, and at what level of detail should we model it?
• From Mike Conlon: "How to represent that a person is no longer associated with the university? It's becoming more obvious that we have many people in VIVO that are no longer at UF. We need information representation, then display, and likely some places where formers are filtered out of displays and lists."
  Nicholas has developed an "active" class – as well as the institutional internal class – so that someone would have both active and institutional internal to be showing up in searches or on menu pages
• Courses and semester classes – can we finalize the Course as a continuing entity that is realized in Semester Class events?
• Radio and TV programs – the collected document nature of a website (e.g., Philosophy TV) vs. an episode as one in an event series; what is the episode – the broadcast or the recorded version that can be viewed anytime
• Events such as testimony before a special congressional panel on a given data, the webpage and URI for the hearing, a linked URI for the the recording or transcript of the testimony of the individual, and any composite compiled and edited report produced from the testimony
• Representing and displaying re-publication or performancecoordination between Elements publication types and VIVO/BIBO types

WebEx Call-in Information

...