The content on this wiki is being preserved for historical purposes, but is not being maintained and is probably no longer accurate.

For current information about DPLA, see the DPLA main site.

Technical Aspects Meeting Notes: October 20, 2011

From Digital Library of America Project
Jump to: navigation, search
DPLA Wiki Navigation
About the DPLA
DPLA Website
Main PageBerkman Center
Board of Directors
Steering Committee
Dev portal
Ongoing Work
Workstreams
Audience and ParticipationContent and Scope
Financial/Business ModelsGovernance
Legal IssuesTechnical Aspects
Additional Activities
Beta SprintWorkshopsEvents
Media and Blog Mentions
Possible Models
List of Models
Concept Note
Get Involved
Community PortalSign on
Join the listservListserv archives
Weekly listserv recapsSuggested Resources

Overview

The Technical Aspects workstream identified three key challenges for their work:

  • To clarify the technical deliverables for the DPLA.
  • To collaborate with the groups of people who will be assigned to write code and develop the product.
  • To provide input to the feasibility of decisions from other workstreams

Over the course of their meeting, the group developed a mission statement: “Establish the technical and normative principles of the technological framework that will best support the DPLA’s aims.” The workstream’s main priorities are to:

  • Fund a team who will write code.
  • Establish a set of working guidelines for collaboration with the content workstream.
  • Find a productive primary approach to building a digital library out of existing content before branching out into a second phase with new content.
  • Come up with ways to bring in content from societies that can’t scan it themselves.
  • Establish working ideas of “what is the DPLA?” and turn that into “what could it be?”

Workstream members feel the DPLA needs to demonstrate success very quickly, and hope to produce the “shiny thing” or “killer app” that will demonstrate its vast potential. They identified as three additional work products/deliverables:

  • An open system with APIs and services that enable building user views and localization into the content.
  • Short terminal technical evaluations of the sprint projects to advise feasibility and interoperability.
  • A set of guiding principles to provide to other workstreams and technology partners.

Additionally, the group discussed the following related projects that merit study:

  • User-provided content (YouTube, Flickr)
  • Book scanning & access projects
  • Personal library and citation management tools
  • Collection registries, institutional repositories, museum collections
  • Commercial-mediated content: Amazon, Hulu, Netflix, Spotify, Overdrive, iTunes
  • Indexing services and knowledge bases such as OCLC, Europeana, wikis, and FreeBase


Slides from the October 20, 2011 Technical Aspects meeting can be found here.

Mission Statement

Establish the technical and normative principles of the technological framework that will best support the DPLA’s aims.

Workstream Members

Chris Freeland, Center for Biodiversity Informatics/Missouri Botanical Garden; Biodiversity Heritage Library

Martin Kalfatovic, Smithsonian Institution Libraries

John Blyberg, Darien Library

Aaron Chaletzky, Library of Congress

Tim Dilauro, Johns Hopkins University

Lee Dirks, Microsoft Research Connections

Michael Edmonds, Wisconsin Historical Society

Emily Gore, Florida State University

Jorge Martinez, Knight Foundation

Robert McDonald, Indiana University

Brad McLean, DuraSpace

Carole Palmer, Center for Informatics Research in Science & Scholarship; University of Illinois at Urbana-Champaign

Robert Stein, Indianapolis Museum of Art

David Weinberger, Harvard Library Innovation Lab

Kristina Woolsey, Exploratorium

Pam Wright, National Archives and Records Administration

Personal tools