Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

When VIVO does consume data from another reporting system, it's worth trying to capture any display preferences captured at the time that the researcher conducts his or her review of their profile and signs off on its accuracy.  By reflecting the same choices on what to include and/or the selection or ordering of publications, VIVO will reflect the larger information ecosystem at the institution and minimize the data entry and review effort required of researchers.

Organizational complexities

Entire colleges or departments may decide that they do not want to appear in VIVO.

  • Frequently this can overcome by limiting the types of data that will be ingested.
  • In other cases it may be necessary to nuance ingest processes for the same data source to address differing requirements on what data each was willing to share, and when.

Don’t compete with my web page

Individuals and departments or centers frequently invest considerable effort in carefully designed and curated web pages. It has proven helpful at Cornell to offer a version of organization and people pages featuring a prominent image of the preferred, hand-curated web page.  VIVO is functioning in this case as rich, contextual search results that visually more attention and traffic to the preferred page, reinforcing rather than competing for prominence.

Further resources

The 2011 Implementation Fest at Washington University and 2012 Implementation Fest at the University of Colorado both featured extensive presentations on policy and planning issues prior to adoption and during VIVO implementation.