...
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.