...
The mere fact that data exist does not assure that they will be made available to you, however. It will be important to make contact with the owners or stewards of the data desired for VIVO, and it may not be trivial for them to make data available. It's common for public and private data to be intermingled in systems of record that have been built for functions such as payroll, performance evaluation, or financial accountability. Gaining access to data and permission to display it on the Web often requires building bridges to other units and catching the ear of people with the authority to support your requests. Some of the most successful VIVOs involve closely-coordinated collaborations among central administrators, IT staff, the library, and the research administration office.
Data
...
evolves.
It's easy to focus on a one-time data load, especially in a proof of concept or pilot project. Putting up any kind of information system, especially one with as many different kinds of data as VIVO, requires making a plan for handling updates – both full and partial data removals as well as additions. Many data sources don't maintain the date of last modification so a complete scan is needed to detect change. In some cases data layers can be replaced wholesale in VIVO because they interact or interleave very little with other datasets, which simplifies updating.
...
Starting small and not taking on too many different kinds of data allows you to familiarize yourself with what are often new concepts and new tools. Data are often dirtier than advertised to be, and more will be left to you to clean up in the process of importing into VIVO. If you need to hire technical help, it may take longer than anticipated to find a qualified person familiar with Semantic Web technologies than for routine web development.
For more information
...
on to part 4 of the Tour: VIVO in an information ecosystem