...
An example may be helpful here. First, the The following spreadsheet would be very easy to load into a VIVO describing cartoon characters:
| id | name | height | age |
|---|---|---|---|
| 1 | Goofy | 89 cm | 11 |
| 2 | Elmer Fudd | 60 cm | 45 |
| 3 | Roadrunner | 140 cm | 2 |
You can readily imagine a storing the information about each character – id, name, height, and age – in one structure.
A spreadsheet of book publication data, however, would be more complicated:
...
VIVO needs to store the book, each author, and the publisher as independent entities with bi-directional relationships among them, written as triple statements. Even the publication date information is stored as a separate entity or object, in large part because a precision needs to be stored along with the year.
The details are not important now – but bear in mind that much of the work of data ingest centers around breaking data that typically arrives in one , typically composite format into the separate entities and explicit relationships among them that together describe comprise VIVO's data model and provide the flexibility for query and retrieval that mark one of VIVO's primary advantages over more fixed storage models.
Types of data sources for VIVO
| Children Display |
|---|