2016-10-06 Data Loader Meeting notes

Date

06 Oct 2016

Attendees

• Mike Conlon

• Ted Lawless

• Rodney Jacobson

Discussion

1. Must be an update
2. People
   1. Sample data.  See https://github.com/lawlesst/vivo-sample-data/blob/master/data/csv/people.csv
   2. People are in orgs.  So need orgs.
   3. Papers are in Journals.  So need journals.
3. Journals
   1. Could load them all, mark the used ones so only they are shown
   2. Could use OpenVIVO as a web service, pull in the ones you need
4. Orgs
   1. Same.  Use OpenVIVO.
5. Named graphs, locking down the data created by the data loader
   1. Pros – separate graph, easy to identify and manage
   2. Cons – prevents updates by people who might want or need to update
6. Configurable options
   1. Settings to control edits at the spreadsheet level, row or column
   2. Can use a local identifier if there is one
   3. The VIVO site to be managed
   4. URI style
      1. n numbers
      2. netids
      3. names for SEO?
7. Person identifiers
   1. Identify by person URI.  Round trip.
8. Python?
   1. Ease.  rdflib.
   2. Want to have it accessible from the admin interface
   3. Mock up in Python, then to Java and Jena
      1. Webapp.  JS calls a web service
   4. Javascript interface that can become part of VIVO
   5. Takes the spreadsheet and returns RDF.  
   6. Second step takes RDF and puts it in VIVO using existing APIs.

Next time

1. Organizing the work
2. Additional scoping