Academic Preservation Trust
Introducing APTrust
In the beginning…
HOW THE DISCUSSION BEGAN
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
Who do we say we are…
WHAT IS APTRUST?
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
Implementation
Plan
Preservation &
Collection
Framework
The repository landscape as we see it…
WHERE DOES APTRUST FIT?
Repository Landscape
Institutional
Repository
APTrust
Repository
e.g., ACM
Personal
Repository
e.g., CERN
e.g., SSOAR
Institution
Researcher
Discipline Specific
Winnowing of Content
Personal Repository
Institutional Repository
APTrust
Repository
Univ 1
APTrust
Access*
Univ
2
APTrust
Aggregation
UVA
Univ 3
DPN’s Replicating
Node Framework
SDR
Node
ApTrust
Node
Node
TBD
*Admin and simple user retrieval
evolving working assumptions…
INITIAL WORKING ASSUMPTIONS
Content Assumptions
Partner-determined collection strategy
IP rights provided by submitters
Metadata determines future access
Single and aggregate content types
Preservation/basic content formats
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
Blacklight, SOLR, Fedora, cloudsync, et al
Local solutions remain independent
plans, timelines, etc.
THE CURRENT STATE
UVa’s Implementation Team
CENTRAL IT
James Hilton
Ken Ruggaber
Tim Sigmon
UNIVERSITY LIBRARY
Karin Wittenborg
Andrew Curley
Bradley Daigle
Robin Ruggaber
Martha Sites
Adam Soroka
Donna 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
@tweet/aptrust
[email protected]
Timelines
Milestones
Additional Software Engineer
Interim Project Manager
Project Director
Full Production
May 2012
Summer 2012
April 2012
Summer 2012
December 2013
Next Steps
University Librarians
Technology Liaisons
Content/Preservation
Liaisons
Questions?