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