Notes from Slack are a good starting point for populating the wiki.
My goal is to come up with one good way of automating data entry with some sanity checking, using a technology that many people do or can understand, which we can support.
Michel: First part of effort should be documentation; compile recipes for how people can ingest from a variety of technologies.
Possibility of using simple, tabular database ahead of triplification.
Ralph: if people can get their data into our simple table format, we can turn it into triples.
William: Are there proposals for more generalized approaches?
Ralph: want to make sure that whatever gets produced doesn’t feel heavy and is something that the person starting out can easily use.
Andrew: common pattern to normalize data into database tables that reflect VIVO entities. Would be good to compare those tables and get to a “supported” set of database schemas for the staging area.
Have supported tooling for these schemas
William: another database schema is another barrier to entry.
Brian: My priorities for data ingest would be built-in tools to build a VIVO from publicly-available data sources (ORCID, PubMed, CrossRef, etc.) before worrying about simplifying the process of transforming your own institutional data.
William: this is a tall order; Symplectic Elements already does a lot of this.
Rachid: not everyone can afford Elements.
Elements Harvester is open source (the harvester from Elements to VIVO)
Ralph: wiki landing page coming in the next day or so.