revise Annotations proposal
In this talk, members of the inaugural Boston cohort of the National Digital Stewardship Residency will discuss one piece of our digital preservation test kitchen: our stabs at creating digital workflows that will (hopefully) help our institutions turn digital preservation projects into programs. Specifically, we will talk about how difficult it is to create a general and overarching workflow for digital preservation tasks (e.g. ingest into repositories, format migrations, etc.) that incorporates various technical tools while also taking into account the myriad and unending list of possible exceptions or special scenarios. Turning these complicated, specific processes into a simplified and generalized workflow is an art. We haven't necessarily perfected that art yet, but in this talk, we'll share what has worked for us -- and what hasn't. We’ll also touch on the importance of documentation, and achieving that delicate balance of adequately thorough documentation that doesn’t pose the risk of information avalanche. These processes often create more questions than answers, but we'll share the answers that we (and our mentors) have found along the way!
Managing Annotations with Fedora4 and Triannon ==
* Rob Sanderson, email@example.com, Stanford University Libraries
* Naomi Dushay, firstname.lastname@example.org, Stanford University Libraries
Annotations on content resources allow
the user to contribute knowledge within the digital repository space. Open Annotation provides a comprehensive model for web annotation on all types of content, using Linked Data as a fundamental framework. Annotation clients generate instances of this model, typically using a JSON serialization, but need to store that data somewhere using a standard interaction pattern so that best of breed clients and servers can be mixed and matched . The model is being refined and standardized as part of the ongoing W3C Web Annotation Working Group.
Stanford is using
the Fedora4 for managing the annotations, via a middleware component called Triannon. Triannon receives the JSON data from the annotation client, and uses the Linked Data Platform API implementation in Fedora4 to create, retrieve, update and delete the constituent resources. This component could be used with other LDP implementations, or with some additional development to ease the migration from other linked data sources into Fedora4.
The presentation will focus on the benefits of the approach with respect to following international standards to ease system integration, and lessons learnt regarding the development process.