Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Identify Potential Data Sources - From spreadsheets to external data repositories, there are a variety of potential data sources that can feed into your VIVO instance.  See VIVO Data - what and from where.  You’ll need to identify which data types and data sources are best aligned with the overall goals for your implementation. See Policy and planning question questions for VIVO data.  It can take some time to evaluate the data content and quality in order to forecast your ingest strategy.  See Data source specifications for implementation and Design of PubmedFetch

...

Map Data To Ontologies -The value of the semantic web lies within the ability to define data using widely accepted ontologies.  See How to plan data ingest for VIVO. Understanding your data in order to accurately map to the VIVO-ISF ontology is an important step.  See VIVO-ISF Ontology. Mapping to an ontology begins as a conceptual design process on a piece of paper or using a diagramming tool such as Vue.  Your final data mapping will occur using a tool such as Karma.  For more details about using Karma to map your data and produce VIVO compliant semantic web data please visit the Using Karma data integration tool page. Your mapping strategy will not only affect the searchability of your data, but also how easily it can be aggregated and reused by other systems. 

...

Manage Ontology Updates - Ontologies can be updated to add or remove terms as a domain becomes better defined.  Ontology changes can be initialized from within your institution (ex. an identifier specific to your institution) or externally (ex. a deprecated term identified by an international standards organization).  The ontology change can be adopted at the level of the the VIVO ontology, or it can be a change done locally within your institution, aka a “local extension”.  For an example, see Ontology Extensions -- Duke.  Local extensions can easily become duplicate ways of defining the same type of information, so it can be helpful to collaborate with the VIVO ontology community when deciding whether or not you need to create a local extension. To the extent that it is relevant to the broader VIVO community, it is important that over time, local ontology extensions get incorporated into the VIVO core ontology.  See Proposed ontology development workflow.

Add New Data & Sources - Data curation is an ongoing task and including new data types or new data sources will most likely be an aspect of maintaining your VIVO instance.  You may find that your initial implementation draws more interest from owners of data repositories you hadn’t considered.  You may want to prioritize new data sources based on the data quality and volume, as well as the number of new ontology mappings required.  As an example, see Activating the ORCID integration.