• Like


Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Charleston Conference: VIVO, libraries, and users.

Uploaded on

A presentation on what VIVO is, why it is implemented in the library, and how the interface is influenced by the user and user behaviors. …

A presentation on what VIVO is, why it is implemented in the library, and how the interface is influenced by the user and user behaviors.

Note: The animations are not working in this upload.

More in: Education
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide
  • Presentation Goals: To provide a general overview of VIVO: semantics, profiles, search. How libraries fit in. Why semantics and how it can create a federated search, browse, and visualizations
  • VIVO is funded by the NIH, specifically the NCRR (National Center for Research Resources).Stimulus money from the American Recovery and Reinvestment Act (ARRA)
  • Cornell – UF – NIH grantInternational – National Science Library, Chinese Academy of Science (3 instances, visiting scholar at CU translating materials) and University of Melbourne in Australia (Research data and records registry).3 releases, a successful conference in Queens, and have garnished the interest of many universities, USDA, Star Metrics, CTSAs, SUNY and FL state schools
  • What is VIVO?It’s a semantic web application with rich profiles that display publications, teaching, service and professional affiliations. Faceted search for fast and meaningful results.--------- Foster team science by providing tools for identifying potential collaborators. Improve collaboration by creating tools using this information for enhancing new and existing teams. Not limited to science – at Cornell, VIVO covers all disciplines across the entire institutionTalking points: Profiles are largely created via automated data feeds, but can be customized to suit the needs of the individual. Information is open source (free) and is stored in a framework that allows for exporting to other applications. Profiles are richer in content than typical [web pages or] social networking sites and will rank higher in general internet searches.
  • Semantic/ontology definitions (below RDF), Elly in RDF example for visual, point out links.
  • Simple semantic advantageSemantic web: describes methods and technologies to allow machines to understand the meaning or "semantics” of information on the web. -- W3C director Sir Tim Berners-LeeOntology: a formal representation of the knowledge by a set of concepts within a domain and the relationships between those concepts.-- Wikipedia
  • Who uses VIVO? In addition to the faculty and researchers, it’s also useful to funding agencies, students, and administrators. These users will come from within and outside of the participating institutions.The technology is versatile and flexible making it responsive to innovation and user needsTalking points: VIVO is useful to many different users and audiences. Users will come from within and outside of the participating institutions.The technology is versatile and flexible enough to easily accommodate changes based on new and innovative demands that users make as they utilize VIVO.
  • Faceted search, simple and flexible, based on ontology hierarchy.
  • Authoritative data, diverse formats, filter out private informationCentralizes the information into a pool to draw on (the bucket)Talk about verified dataTalking points: Much of the data in VIVO profiles is ingested from authoritative sources so it is accurate and current, reducing the need for manual input.Private or sensitive information is never imported into VIVO. Only public information will be stored and displayed. Data is housed and maintained at the local institutions. There it can be updated on a regular basis. There are three ways to get data: internal, external, individuals. Internal is authoritative!Examples of internal data – Faculty reporting, course listings, grants, directoryExamples of external sources – PubmedManual – affiliations, geographic locations
  • Since VIVO stores profile information drawn from a variety of sources in a single, flexible format, it can be easily “re-skinned” or “re-purposed” to present specialized views into the institution.For example:Graduate Programs in the Life Sciences - geared toward a specific user – prospective graduate students in the life sciencesCALS Research Portal - Or a filtered view for a specific departmentCALS Impact statements- repurposed in a CMS (Drupal), development onlyFaculty profiles in Classics - have a dept pulling faculty profiles into Common Spot
  • How is this data stored?Talking points: Simple formatBased on triplesShared ontology, giving meaning to names and terminologies
  • Example – Mike Conlon.See URI for Mike - html view (human readable), marbles RDF view (application use), straight-up RDF (machine readable)
  • RDF browser of Mike’s information…. person, thing, etcKeep going, you get more data.Machine and human readableSemantically labeled data, not just text.
  • Feel for the VIVO ontology, Point out examples of relationships or Susan Riha.
  • Individual, institution, network
  • National exemplarsearch, browse, share as RDFvisualization – Katy Borner at Indiana UniversityMapped to the much larger world of the semantic web.Anyone running VIVO will provide this RDF data with a unique namespace. Marked from an institution and considered authoritative data.VIVO enables authoritative data about researchers to join the Linked Data cloud
  • Part of the solutionLibraries are posed to meet participation challenges due to their role on campus as information resource and technology centers.Librarians are subject matter experts, understand their user’s needs and institution’s research environment. In VIVO-funded institutions, the librarians are the ones negotiating with the owners of local data sources to explain what data we need and why we need it. The library is a stable and natural home for VIVO, but the implementers need to work closely with the institution’s administration and faculty.
  • So what do librarians DO?Identification of content types – ontology ;development and interface refinementWe negotiate with the owners of local data sources to explain what data we need and why we need it.We provide local and national support and training through the development of documentation, presentations and help-desk servicesUsing the vivoweb.org website we liaise with potential collaborators – giving demos and answering questionsCreating a community of supportAnd delivering usability feedback to the technical team.Marketing – through demonstrations, conferences, workshops and the development PR materials designed both to attract new participants and to assist participants with local adoption
  • Notes to self: Need to create a diagram like in the Mental Models book and pull more features out .Mental Models: Aligning Design Strategy with Human Behavior, Indi Young, Rosenfeld Media, Brooklyn, NY 2008
  • Weighted by frequency of keyword and priority
  • Development guided by user analysis and feature list from scenarios.
  • Download, Adopt, and Implement:  VIVO is open source and is available for download. Provide Data:  You can participate by providing machine readable data for research discovery.  Bibliometric and funding data are of great interest to the research community. Develop Applications: Many software applications can benefit from using information that will be provided by the national network. External application development:enhanced search, new collaboration capabilities, grouping, finding and mapping scientists and their work. Anything that will leverage VIVO and the semantic cloud.


  • 1. A Closer Look at VIVO
    Presented by:
    Ellen J. Cramer Ph.D.
    Research Associate
    Cornell University
  • 2. VIVO Collaboration:
    Cornell University: Dean Krafft (Cornell PI), Elly Cramer (Co-PI), ManoloBevia, Jim Blake, Nick Cappadona, Brian Caruso, Jon Corson-Rikert, Elizabeth Hines, Huda Khan, Brian Lowe, Joseph McEnerney, Holly Mistlebauer, Stella Mitchell, AnupSawant, Christopher Westling, Tim Worrall, Rebecca Younes. University of Florida: Mike Conlon (VIVO and UF PI), Chris Barnes, Cecilia Botero, Kerry Britt, Amy Buhler, Ellie Bushhousen, Linda Butson, Chris Case, Christine Cogar, Valrie Davis, Mary Edwards, Nita Ferree, Chris Haines, Rae Jesano, Margeaux Johnson, Sara Kreinest, Meghan Latorre, Yang Li, Hannah Norton, NarayanRaum, Alexander Rockwell, Sara Russell Gonzalez, Nancy Schaefer, Dale Scheppler, Nicholas Skaggs, Matthew Tedder, Michele R. Tennant, Alicia Turner, Stephen Williams.  Indiana University: Katy Borner (IU PI), KavithaChandrasekar, Bin Chen, Shanshan Chen, Jeni Coffey, Suresh Deivasigamani, Ying Ding, Russell Duhon, Jon Dunn, PoornimaGopinath, Julie Hardesty, Brian Keese, NamrataLele, Micah Linnemeier, Nianli Ma, Robert H. McDonald, AsikPradhanGongaju, Mark Price, Yuyin Sun, Chintan Tank, Alan Walsh, Brian Wheeler, Feng Wu, Angela Zoss.   Ponce School of Medicine: Richard J. Noel, Jr. (Ponce PI), Ricardo Espada Colon, Damaris Torres Cruz, Michael Vega Negrón.  The Scripps Research Institute: Gerald Joyce (Scripps PI), Catherine Dunn, Brant Kelley, Paula King,  Angela Murrell, Barbara Noble, Cary Thomas, MichaeleenTrimarchi.  Washington University School of Medicine in St. Louis: RakeshNagarajan (WUSTL PI), Kristi L. Holmes, CaerieHouchins, George Joseph, Sunita B. Koul, Leslie D. McIntosh.  Weill Cornell Medical College: Curtis Cole (Weill PI), Paul Albert, Victor Brodsky, Mark Bronnimann, Adam Cheriff, Oscar Cruz, Dan Dickinson, Richard Hu, Chris Huang, ItayKlaz, Kenneth Lee, Peter Michelini, Grace Migliorisi, John Ruffing, Jason Specland, Tru Tran, VinayVarughese, Virgil Wong.
    This project is funded by the National Institutes of Health, U24 RR029822, "VIVO: Enabling National Networking of Scientists".
  • 3. Overview
    What is VIVO?
    Why the library?
    User experience (UX)
  • 4. VIVO history… born in the library
    • Originally developed at Cornell University in 2004 to support Life Sciences
    • 5. Reimplemented using RDF, OWL, Jena and SPARQL in 2007
    • 6. Now covers all faculty, researchers and disciplines at Cornell
    • 7. Implemented at University of Florida in 2007
    • 8. Underlying system in use at Chinese Academy of Sciences and Australian Universities
    In September 2009, seven institutions received $12.2 million in funding from the National Center for Research Resources of the NIH to to enable National Networking with VIVO
  • 9. iClicker Question 1
    Had you heard of VIVO before the conference?
  • 10. VIVO is:
    An open-source semantic web application that enables the discovery of research and scholarship across disciplines in an institution.
    Populated with detailed profiles of faculty and researchers; displaying items such as publications, teaching, service, and professional affiliations.
    A powerful search functionality for locating people and information within or across institutions.
  • 11. iClicker Question 2
    How familiar are you with the Semantic Web?
    Very (part of my everyday work)
    Moderately (can explain it to others)
    Mildly (understand the concepts)
    Not at all (new to me)
  • 12. Semantic web: describes methods and technologies to allow machines to understand the meaning or "semantics” of information on the web. -- W3C director Sir Tim Berners-Lee
    Ontology: a formal representation of the knowledge by a set of concepts within a domain and the relationships between those concepts.-- Wikipedia
  • 13. VIVO’s semantic advantage
    Everything has its own URI
    All data has standard format
    Data modeled as bidirectional relationships
  • 14. VIVO users
    …and many more!
  • 15. iClicker Question 3
    Who are you?
  • 16. Faceted search, browse, and ontology hierarchy
  • 17. Data, data, data
    VIVO harvests much of its data programmatically from verified sources
    • Reduces the need for manual input of data
    • 18. Provides an integrated and flexible source of publicly visible data at an institutional level
    External data sources
    Internal data sources
    Individuals may also edit and customize their profiles to suit their professional needs.
  • 19. Repurposing and re-using data
  • 20. Linked Data
    • Stored in Resource Description Framework (RDF) triples
    • 21. Uses the shared VIVO Core Ontology to describe people, organizations, activities, publications, events, interests, grants, and other relationships
    • 22. Incorporates Friend-of-a-Friend (FOAF) and Bibliographic Ontology (BIBO)
    • 23. Supports local ontology extensions for institution-specific needs
  • Mike Conlon’s VIVO profile
  • 24. Mike Conlon’s VIVO profile as Linked Data
  • 25. has author
    taught by
    crop management
    research area
    research area for
    headed by
    CSS 4830
    head of
    faculty appointment in
    faculty members
    features person
    Earth and Atmospheric Sciences
    featured in
    Cornell’s supercomputers crunch weather data to help farmers manage chemicals
    Detailed relationships for a researcher
    has author
    Andrew McDonald
    Mining the record: Historical evidence for…
    academic staff
    author of
    research area
    author of
    research area for
    academic staff
    Susan Riha
  • 26. Visualizing relationships
  • 27. NIH VIVO Network Exemplar
    Scripps VIVO
    WashU VIVO
    Ponce VIVO
    Triple Store
    Prof. Assn.
    Triple Store
    Cornell VIVO
    Triple Store
    Triple Store
    Linked Open Data
  • 28. iClicker Question 4
    Which one of these features is most important for VIVO to be successful?
    Publications ingest
    Visualization of relationships
    Collaboration tools
    Search/browse the network
  • 29. Overview
    What is VIVO?
    Why the library?
    User experience (UX)
  • 30. Why Libraries?
    • Are a trusted, neutral entity
    • 31. Have a tradition of service and support
    • 32. Strive to serve all missions of the institution
    • 33. Are technology centers and have IT and data expertise
    • Have skills—information organization, instruction, usability, subject expertise
    • 34. Have close relationships with their clients (buy in)
    • 35. Understand user needs
    • 36. Understand the importance of collaboration and know how to bring people together
    • 37. Have knowledge of institution, research, education, clinical landscape
  • Library staff as facilitators
  • 38. iClicker Question 5
    How do you feel about the directions libraries and publishers are moving in?
    Excited by the new opportunities
    Scared my job is in jeopardy
    I don’t think it’s going to change that much
    Anything goes…..
  • 39. Overview
    What is VIVO?
    Why the library?
    User experience (UX)
  • 40. Our Process
  • 41. Audience Analysis – Mental Model
  • 42. User Scenarios
    Site management
    Linked data
  • 43. Features based on users and scenarios
  • 44.
  • 45.
  • 46. User testing and Morae
  • 47. Earlier feedback with InfoMaki
  • 48. iClicker Question 6 - InfoMaki
    … A
    … B
    … C
    … D
  • 49. iClicker Question 7 - InfoMaki
  • 50. iClicker Question 8 - InfoMaki
    … A
    … B
  • 51. Overview
    What is VIVO?
    Why the library?
    User experience (UX)
  • 52. Discussion/questions
    In our new state of information overload, how should librarians connect people with information? Is it the role of the librarian to connect people with people?
    What ways are your libraries fostering collaboration?
    In light of collaborative team science/research, how do you envision the role of the library changing within the university setting?
  • 53. THANK YOU!