Academic Preservation Trust

Introducing APTrust

HOW THE DISCUSSION BEGAN In the beginning…

This we believe*…

• Explicitly for preservation. Always and forever

• Leverage intentional interdependence

• Leverage investments that we are making separately

• Enables the digital copy to become the copy of record

• Ensures the durability and accessibility of the scholarly record for future generations

*From Aug 2011 meeting to discuss possibility of a regional repository

WHAT IS APTRUST?Who do we say we are…

APTrust is…a consortium committed to using a Fedora-based repository to aggregate curated [academic] content as part of a long-term preservation strategy

Added Value we see so far…

• Commitment to scalable, long-term preservation

• Disaster recovery services• Aggregated content • Community-building

APTrust Partners

Columbia University University of North Carolina

Duke University Notre Dame

Emory University North Carolina State University

Johns Hopkins University Stanford University

University of Maryland Syracuse University

University of Michigan University of TX Austin

University of Virginia

APTrust Consortium

Business & Marketing Strategy

Governance, Policy, & Legal

Framework

Repository Implementatio

n Plan

Preservation & Collection

Framework

WHERE DOES APTRUST FIT?The repository landscape as we see it…

Personal RepositoryAPTrust

Repository

Institutional Repository

e.g., SSOAR

e.g., CERN

e.g., ACM

Repository Landscape

ResearcherInstitution Discipline Specific

Personal Repository

Institutional Repository

APTrust Repository

Winnowing of Content

APTrust Aggregation

Univ 2

Univ 3

Univ 1

UVA

*Admin and simple user retrieval

APTrust Access*

DPN’s ReplicatingNode Framework ApTrust

Node

SDR Node

Node TBD

INITIAL WORKING ASSUMPTIONSevolving working assumptions…

Content AssumptionsPartner-determined collection strategy

Preservation/basic content formats

Single and aggregate content types

Metadata determines future access

IP rights provided by submitters

Simple web-based access (off)

High barrier to de-accessioning

System Architecture Assumptions

Replicate content at two additional sites

Replicating node for DPN

Regular audits of content

Local solutions remain independent

Blacklight, SOLR, Fedora, cloudsync, et al

THE CURRENT STATEplans, timelines, etc.

UVa’s Implementation TeamCENTRAL IT

James HiltonKen RuggaberTim Sigmon

UNIVERSITY LIBRARY

Karin WittenborgAndrew CurleyBradley DaigleRobin RuggaberMartha SitesAdam SorokaDonna Tolson

Start-up Business Plan

UVa Resource Contributions• Project management and business functions• 2 software engineers and project director until

March 2014• Repository infrastructure

Partner Resource Contributions• $20,000 each for start-up

aptrust.org info@aptrust.org@tweet/aptrust

Timelines

Milestones May 2012Additional Software Engineer Summer 2012Interim Project Manager April 2012Project Director Summer 2012Full Production December 2013

Next Steps

University Librarians

Content/Preservation

Liaisons

Technology Liaisons

Questions?