1. Academic Preservation Trust Introducing APTrust

2. HOW THE DISCUSSION BEGAN In the beginning…

3. 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

4. WHAT IS APTRUST? Who do we say we are…

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

6. Added Value we see so far… Commitment to scalable, long-term preservation Disaster recovery services Aggregated content Community-building

7. APTrust Partners Columbia UniversityUniversity of North Carolina Duke UniversityNotre Dame Emory UniversityNorth Carolina State University Johns Hopkins UniversityStanford University University of MarylandSyracuse University University of MichiganUniversity of TX Austin University of Virginia

8. APTrust Consortium Business & Marketing Strategy Governance, Policy, & Legal Framework Repository Implementation Plan Preservation & Collection Framework

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

10. Personal Repository Personal Repository APTrust Repository Institutional Repository e.g., SSOAR e.g., CERN e.g., ACM Repository Landscape ResearcherInstitution Discipline Specific

11. Personal Repository Institutional Repository APTrust Repository Winnowing of Content

12. APTrust Aggregation Univ 2 Univ 3 Univ 1 UVA *Admin and simple user retrieval APTrust Access* DPN’s Replicating Node Framework ApTrust Node SDR Node Node TBD

13. INITIAL WORKING ASSUMPTIONS evolving working assumptions…

14. Content Assumptions Partner-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

15. 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

16. THE CURRENT STATE plans, timelines, etc.

17. UVa’s Implementation Team C ENTRAL IT James Hilton Ken Ruggaber Tim Sigmon U NIVERSITY L IBRARY Karin Wittenborg Andrew Curley Bradley Daigle Robin Ruggaber Martha Sites Adam Soroka Donna Tolson

18. 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

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

20. Timelines MilestonesMay 2012 Additional Software EngineerSummer 2012 Interim Project ManagerApril 2012 Project DirectorSummer 2012 Full ProductionDecember 2013

21. Next Steps University Librarians Content/Preservation Liaisons Technology Liaisons

22. Questions?