NEW STRATEGIES FOR MSS  Bradley Daigle (@BradleyDaigle) / Mike Durbin -                University of Virginia
What is a manuscript?
What’s a manuscript
What are we dealing with?
Complexity
Manual Processes
Workflow ChallengesDigital orphansAccess rightsHybrid collections
EADs
bring the search to the             user, don’t make the user             have to understand how             we organize d...
New technology, new needs
Instant integration
Single infrastructure
What are we doing?<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="http://ead.lib.virginia.edu/vivaead/publish...
How is this different?Think about finding aids not EADsLet the archivists focus on what they do bestIP landscapes are flex...
Not all rainbows and unicorns
Challenges with integrating search resultsRelational database could get quite largeComplex data storage modelMigration of ...
Looking aheadGranular circulationRisk ManagementCreate virtual collectionsAlternate metadata options for descriptionArchiv...
Data Model ConstraintsUnknowns Metadata   Format   Publication-ready?   Unique ids? Workflows to support   Only “complete”...
Data Model Goals Allow for multiple hierarchies to describe the same resources Allow for metadata in various formats Suppo...
Data ModelFrom Finding Aid                                 Collection                                Component            ...
Data Model                             CollectionFrom Finding Aid                             Compo                       ...
Data Model                             Collection               MARC                                                      ...
Data Model                             Collection               MARC                                                      ...
Data Model                             Collection               MARC                                                      ...
Data Model                             Collection               MARC                                                      ...
Data Model                                            Collectio                                                           ...
Fedora Metadata Philosophy“Catalog in the format that is most suited to your materials but disseminate inthe format that’s...
Metadata Model                                                                R C                                   A     ...
Dissemination Needs and SupportFinding AidsDiscovery UI SupportDiscovery Index Records
IndexingPhilosophy  Based around discovery and presentation needsTechnical Implementation  XSLT-based Fedora Disseminator ...
Discovery InterfaceVIRGO  Blacklight    Ruby on rails    Solr  Custom integrations    Fedora    ILS (Sirsi)    PRIMO
Development ProcessCentered on User Experience  Started with wireframes  Included major stakeholders from the beginningBal...
Development Status“Complete”  Data model  EAD  Fedora processing/ingest  UI enhancements to Virgo (Blacklight)Short term ...
Thank you!Bradley Daigle - bradley@virginia.edu / @bradleydaigleMike Durbin - md5wz@virginia.edu
Archival Data Presentation for Digital Library Federation
Archival Data Presentation for Digital Library Federation
Archival Data Presentation for Digital Library Federation
Archival Data Presentation for Digital Library Federation
Archival Data Presentation for Digital Library Federation
Archival Data Presentation for Digital Library Federation
Archival Data Presentation for Digital Library Federation
Archival Data Presentation for Digital Library Federation
Archival Data Presentation for Digital Library Federation
Archival Data Presentation for Digital Library Federation
Archival Data Presentation for Digital Library Federation
Archival Data Presentation for Digital Library Federation
Archival Data Presentation for Digital Library Federation
Upcoming SlideShare
Loading in …5
×

Archival Data Presentation for Digital Library Federation

1,115 views

Published on

This is a presentation given to the Digital Library Federation Forum in 2012. It outlines the University of Virginia Library's current strategy for managing archival descriptive data by managing it through a Fedora data model, using Solr and Blacklight for indexing and delivery.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,115
On SlideShare
0
From Embeds
0
Number of Embeds
246
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • Not so much about mass digitization as it is patron requests (a harder problem set)\n
  • \n
  • \n
  • \n
  • Large EADs - search and browse not integrated - separate interfaces - discover through structure\n
  • Large EADs - search and browse not integrated - separate interfaces - discover through structure\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Archival Data Presentation for Digital Library Federation

    1. 1. NEW STRATEGIES FOR MSS Bradley Daigle (@BradleyDaigle) / Mike Durbin - University of Virginia
    2. 2. What is a manuscript?
    3. 3. What’s a manuscript
    4. 4. What are we dealing with?
    5. 5. Complexity
    6. 6. Manual Processes
    7. 7. Workflow ChallengesDigital orphansAccess rightsHybrid collections
    8. 8. EADs
    9. 9. bring the search to the user, don’t make the user have to understand how we organize descriptive information!Made by archivists for archivists
    10. 10. New technology, new needs
    11. 11. Instant integration
    12. 12. Single infrastructure
    13. 13. What are we doing?<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="http://ead.lib.virginia.edu/vivaead/published/document.xsl" type="text/xsl"?><ead xmlns="urn:isbn:1-931666-22-9" id="viu01215"> <eadheader audience="internal" langencoding="iso639-2b" findaidstatus="edited-full-draft" scriptencoding="iso15924" dateencoding="iso8601"countryencoding="iso3166-1" repositoryencoding="iso15511"> <eadid publicid="PUBLIC &amp;#34;-//University of Virginia::Library::Special Collections Dept.//TEXT (US::ViU::viu01215::A Guide to the Papersof John Dos Passos 1865-1998)//EN &amp;#34;viu01215.xml&amp;#34;" countrycode="US" mainagencycode="US-ViU">PUBLIC "-//University of Virginia::Library::Special Collections Dept.//TEXT (US::ViU::viu01215::A Guide to the Papers of John Dos Passos 1865-1998)//EN "viu01215.xml"</eadid> <filedesc> <titlestmt> <titleproper>A Guide to the Papers of John Dos Passos <date era="ce" calendar="gregorian">1865-1998</date></titleproper> <subtitle id="sort">Dos Passos, John, Papers <num type="collectionnumber">5950</num></subtitle> <author>Special Collections Staff</author> </titlestmt> <publicationstmt> <publisher>Special Collections, University of Virginia Library</publisher>
    14. 14. How is this different?Think about finding aids not EADsLet the archivists focus on what they do bestIP landscapes are flexible human and machine actionableAvoid the digitization / description dilemmaNot worry about variable levels of descriptionOptimized for digital surrogates and born digital content
    15. 15. Not all rainbows and unicorns
    16. 16. Challenges with integrating search resultsRelational database could get quite largeComplex data storage modelMigration of legacy content
    17. 17. Looking aheadGranular circulationRisk ManagementCreate virtual collectionsAlternate metadata options for descriptionArchival prioritization of search results
    18. 18. Data Model ConstraintsUnknowns Metadata Format Publication-ready? Unique ids? Workflows to support Only “complete” collections ingested? Editing after ingestion? Editing happen in the repository or out of the repository?
    19. 19. Data Model Goals Allow for multiple hierarchies to describe the same resources Allow for metadata in various formats Support ingest of “finished” EADs but anticipate future edits,replacements and reorganizations
    20. 20. Data ModelFrom Finding Aid Collection Component Component Component Item Item Item Item Item Item Item Item Item
    21. 21. Data Model CollectionFrom Finding Aid Compo Component Compo nent nent Ite Item Ite Item Ite Ite Item Ite Ite m m m m m m
    22. 22. Data Model Collection MARC MARCFrom Finding Aid MARC From Catalog Compo Component Compo Container Container nent nent Ite Item Ite Item Ite Ite Item Ite Ite m m m m m m
    23. 23. Data Model Collection MARC MARCFrom Finding Aid MARC From Catalog Compo Component Compo Container Container nent nent Ite Item Ite Item Ite Ite Item Ite Ite m m m m m m
    24. 24. Data Model Collection MARC MARCFrom Finding Aid MARC From Catalog Compo Component Compo Container Container nent nent Ite Item Ite Item Ite Ite Item Ite Ite m m m m m m
    25. 25. Data Model Collection MARC MARCFrom Finding Aid MARC From Catalog Compo Component Compo Container Container nent nent Ite Item Ite Item Ite Ite Item Ite Ite Digitized m m m m m From Digitization and m Item patron request workflow Digitized Digitized File Digitized File File
    26. 26. Data Model Collectio MARC n From Finding Aid From Catalog Component Comp Comp Container Container Item From Digitization Item Item Ite Ite Ite Ite Ite Digitized and patron request workflow Item Digitized Digitized File Digitized File File Digitized Collectio Item Item n ItemFrom Finding Aid orother collection Item Digitizeddescription source Digitized File Digitized File File
    27. 27. Fedora Metadata Philosophy“Catalog in the format that is most suited to your materials but disseminate inthe format that’s most suited to your use”
    28. 28. Metadata Model R C A Collection MARC M Compo ML Compo X Component Container Container nent D nent EA Ite Item m Ite Item Ite ItemIte Ite m Digitized m m m Item Digitized File Digitized File D Digitized File A DigitizedE L Item Collection Item Item M Item Digitized File Digitized File Digitized File
    29. 29. Dissemination Needs and SupportFinding AidsDiscovery UI SupportDiscovery Index Records
    30. 30. IndexingPhilosophy Based around discovery and presentation needsTechnical Implementation XSLT-based Fedora Disseminator Pulls data from the entire RDF graph to build index records Reindexing would be triggered by editing or submission workflow Solr Index serves to cache collection structure and metadata
    31. 31. Discovery InterfaceVIRGO Blacklight Ruby on rails Solr Custom integrations Fedora ILS (Sirsi) PRIMO
    32. 32. Development ProcessCentered on User Experience Started with wireframes Included major stakeholders from the beginningBalanced competing needs Archivists Asserts the importance of the context, collection and archival descriptive practice. Researcher Wants to be able to find all relevant materials across traditional silos. Web surfer Cares less about where something came from and more about being
    33. 33. Development Status“Complete” Data model EAD  Fedora processing/ingest UI enhancements to Virgo (Blacklight)Short term goals Include large volume of finding aids Implement robust policy support Refine the user interface as neededLonger term goals Place robust archival description tools on top of the Fedora Data Model
    34. 34. Thank you!Bradley Daigle - bradley@virginia.edu / @bradleydaigleMike Durbin - md5wz@virginia.edu

    ×