...
Similar to how VIVO adds VIVO ontology-specific customizations for information display and entry, VitroLib adds customizations for the display and addition of BIBFRAME and related ontology information. Being ontology-agnostic, Vitro can support the display and editing of BIBFRAME data, but we opted to explore more usable design that could support catalogers in their workflow than that provided by Vitro which is better suited for an audience that has greater familiarity with ontology editing tools. Furthermore, we refactored code responsible for integrating vocabulary lookups from VIVO into the Vitro layer and wrote implementations for looking up Questioning Authority sources. We also explored how to enable more client-side configuration of property-specific customizations.
Development and Design Process
The design and development of the VitroLib prototype was a collaborative effort that spanned multiple institutions and roles. Early on, we recognized the need for using a user-centered design approach to understand how catalogers approach their tasks and how to support those tasks using a new underlying model and a new interface. We were fortunate in being able to tap into cataloger knowledge using multiple approaches from informal conversations, focused meetings, usability evaluations, and hands-on experiments with the prototype. We'd like to thank all the catalogers who participated in meetings or usability evaluations including the catalogers at Cornell, Harvard, Princeton, Columbia, and Stanford. The sections below include links to more information about the process and lessons learned from our iterative approach to design.
The development process of VitroLib focused on creating custom editing and display interfaces using Vitro's built-in RDF editing and management processes. We quickly realized that much customization would be needed and focused the initial part of our development process on enabling client-side configuration of custom editing forms (where Vitro traditionally uses server-side configuration). We uses this streamlined approach to generate all the custom editing forms used in the prototype. In addition, for the HipHop collection, we relied on feedback from Cornell catalogers to identify core fields that could be used in the initial work/instance/item creation form. When the opportunity to specify how the ontology should actually behave arrived in the form of SHACL metadata application profiles, we constructed a process for querying and translating those profiles into VitroLib configuration for display and editing. Further details on the streamlined customizations and SHACL translation can be found linked in the sections below.
Setup and Installation
The GitHub code repository is available here: Github code repository . A series of VitroLib tutorials are available on YouTube which cover setup and installation and Vitro features that are available in VitroLib.
...