Digital text repositories (1/2)

2. Digital text repositories (1/2) • Who? • General public, digital text repository editors/curators • Goals/ use cases • Exploring the repository/finding digital items • Cataloging, including creating links to other resources manually and/or automatically • make accessible rep’s content (expose and share the entities related to the content) • What? • Textual data with metadata • What kind of data (here, metadata)? • Some reps would link to encyclopedia entries on the author, the subject of the work, the period of composition • Some reps (traditional/scholar) curate at the level of books/volumes, others (community/volunteers) at the level of ind. “works” (eg. a poem) • All reps are quite flexible wrt. metadata implementation (not much legacy data to handle) • FRBR talk: , the reps’ core business is preparing/making available new manifestations (digital editions), they should be able to link to works/editions/(print) manifestations defined elsewhere

3. Digital text repositories (2/2) • Value of linking: • Links to context (works, authors, and topics) are crucial for exploring the repository • Links to existing descriptions are crucial for being able to re-use existing metadata and make own cataloging faster • Value of linked data technology • Maintain networks of resources to help discovery/selection • Making stable and typed references to external resources • Allow embedding shared identifiers very easily, which in turn greatly facilitate discovering relevant pieces of context data • automatic alignment tools could boost cataloging • Issues • Adopting & sharing identifiers, using data links as a means for re-use, representing (and identifying) relevant provenance data • Related cases • Open Library Data, Subject Search, Bibliographic Network

4. Digital preservation (1/2) • Who? • Curators of digital objects [probably] • Goals • Support planning and realization of digital preservation • What? • Digital objects subjected to preservation actions • What kind of data • Technical data: format info, tools, preservation events and agents • Links between versions of digital objects • Vocabularies of interest • Preservation vocs from LC • OAI-ORE (complex digital objects) • DOAP for software agents

5. Digital preservation (2/2) • Use case • Finding objects based on preservation criteria, running/tracking/checking preservation actions • Value of LD technology • Mutualizing preservation data across descriptions of specific digital items, linking objects together (“global environment”) • Sharing data across institutions (“authorities” for formats, event types, etc.) • Issues • Scalability and persistence • Coverage of existing vocabularies not complete • Related usage • Tech data could be used for other cases than preservation

6. Publishing 20th cent. Press archive (P20) (1/2) • Who? • Scholars and students, Archivists, Journalists, general public • Service Providers • Goals • Provide every item (collection, folder, document, page and search result) a persistent identifier for citation and linking • Provide context: metadata + link to other data relevant to the domain • To support the use of a standard image and metadata viewer • What? • newspaper clippings about persons, companies, subjects and wares, organized in thematic folders • What kind of data • Bibliographic data (source and date of an article) • Context data (name of a company) • Use cases • Users browse and search archive using metadata (e.g. autosuggest service using authority file). They can cite/link to every item. They view folders and documents with their page images and some metadata attached. Additional info from other sources is either included (wikipedia) or pointed to (VIAF). • Institutional users and service providers (like Europeana) can harvest the data

7. Publishing 20th cent. Press archive (2/2) • Value of LD technology • Good vocabularies to represent aggregations (OAI-ORE) • Availability of external sources to enrich own metadat • RDFa for publishing metadata for man + machine • Vocabularies of interest • OAI-ORE, SKOS, FOAF, RDA (persons), EXIF, adhoc vocabulary • Issues • Repr of adhoc aggregation (search results) • Fast generation of RDF from DBs • End-user display of rich data (aggregations) • No Mapping from LOD data to specific formats (ORE -> METS for viewer) • Capturing order of documents • Related use cases • NDNP (Chronicling America) as similar case, Europeana (data consumer), VIAF (consumed data)

8. Subject search (1/2) • Who? • [general public?] • Goals • Better use subject vocabularies for web search • Make subject data better accessible (not just simple HTML) for machines and humans: linkage and modelling for re-use • What? • Subjects, works, web pages about these. • What kind of data • Subject data • Bibliographic data

9. Subject search (2/2) • Use case • Starting from a simple string-based web search user is able to refine by selecting one controlled subject, which gives access to work pages which allow to get books. • Value of LD technology • Modelling languages (OWL) • stable, unambiguous, globally-dereferencable, content-negotiable HTTP URIs • Issues • URI patterns for real world objects, web documents and topics • Human-readable URIs (sensible "names for things”) • Articulation of metadata useful to scenario (links between findable “local” works and authority subjects) • Concepts as seen by content provider vs. concepts as seen authority provider • Keeping to simple subjects (no coordination/skos-xl:Labels) • Related use cases • Vocabulary merging