1. DuraSpace Summit meeting Baltimore, Md March 13,14 2013

2. …first we need to uncover the myths DuraSpace has teams of developers working on DSpace and Fedora DuraSpace is funded by the Moore foundation and others DuraSpace is DSpace on Fedora Our sponsorship dollars are funding Duracloud Bringing on more projects reduces effort on existing projects

3. Who is DuraSpace? Not for profit 501c3 formed in 2009 Bringing together of the DSpace Foundation and Fedora Commons Organization

4. Our mission DuraSpace is committed to providing leadership and innovation for open technologies that promote durable, persistent access to digital data. We collaborate with academic, scientific, cultural, and technology communities by supporting projects and creating services to help ensure that current and future generations have access to our collective digital heritage.

5. How is DuraSpace organized? DuraSpace Projects DSpaceFedoraVivo Services DuraCloudEducationDspacedirect Funded through sponsorship,RSP program Funded through service revenue and grants

6. Why we are here today? ProjectsDSpaceFedora Together we must develop a sustainable model for these projects

7. Total funds raised from sponsorship $417,750 for Fy2012

8. How are the sponsorship funds spent? ItemDSpaceFedora Staff (Tech lead, exec mgt, outreach, community programs) 244,000( 2.0 FTE)221,666 (1.8 FTE) Travel20,000 Outsourced services20,000 Infrastructure7,000 Indirect cost allocation 45,000 Total336,000313,666 Sponsorship/RSP rev258,750186,000 Net diff(77,250)(127,666)

9. Together we need to increase the level of contribution and engagement for both projects to ensure long term success

10. What do Open Source Projects Need to Thrive? Community contributions and engagement Great developers Effective governance Community support, partnerships, and growth Strategic direction and product roadmap Sustainability planning

11. How does DuraSpace support projects? Executive leadership Technical leadership Community outreach Communications/promotion Business administration

12. How does VIVO fit in? VIVO worked with DuraSpace to develop initial funding and governance It compensates DuraSpace for services provided DuraSpace provides a legal home for VIVO VIVO is working with us to build a sustainable business model

13. How we fit as part of the larger ecosystem of scholarship Our focus is durability and preservation We support the core building blocks for access, management and preservation We provide strategic guidance and technical expertise on many projects that use our software or are important to our community

17. Title Here Title Here, Optional or Unit Identifier DuraSpace Summit: The University Librarian Perspective Tyler Walters DuraSpace Summit Meeting, March 13, 2013

18. $63,705 – digital infrastructure and services (5) DPN DuraSpace Educopia/MetaArchive Cooperative HathiTrust LOCKSS Alliance $59,199 – community convening / issue leadership (6) ARL ASERL CLIR/DLF CNI Educopia/Library Publishing Coalition SPARC $122,904 annual grand total 18 Ex.: VT Libraries’ participation

19. Running the numbers… $122,904 grand total / $17,218,391 (Total 2012-13 Virginia Tech Libraries state budget) =0.007% of Libraries budget (seven one-thousandths of one percent!) $87,500 software developer (salary plus benefits [$75,000 salary and 25% benefits]) $122,904 represents 1.4 FTE software developers and no one else 19

20. For ~$123,000 we get… Shared scanned book / journal repository and research initiatives – HathiTrust Distributed, international digital preservation network based on one software platform – MetaArchive Distributed digital preservation network focused on published literature, development projects coordination, stewardship of software – LOCKSS Alliance Distributed digital preservation network across technology stacks/platforms – DPN Coordination of development projects and stewardship of core repository technologies, DSpace, Fedora, and DuraCloud – DuraSpace 20

21. Communities of practice and knowledge sharing … Research library practices and experimentation (ARL, ASERL) IT-Library collaboration and digital library initiatives (CNI, CLIR/DLF) Library-based publishing services and co-creating service models, technologies etc. (LPC) Advocacy for open access to scholarly and scientific information (SPARC) 21

22. Other real costs? Yes, there are more digital infrastructure/service costs: Other library personnel involved, but they are leveraged with personnel from other libraries participating in a given initiative There are also physical resource costs – ex. as distributed preservation networks grow so too must individual nodes – though this isn’t terribly expensive What do you think of this ROI? 22

23. Table Discussion What have you heard today? What do you have concerns about? What has inspired you? What unanswered questions do you have? March 2013 DuraSpace Summit Meeting

24. We need your help What continued investment do the projects need to be successful? What are ways to increase engagement and contribution in the community?

25. Day 2 Summit Meeting March 2013 DuraSpace Summit Meeting

26. DSpace What does the project need to be successful? Financial contributions Developer contributions Articulation of requirements How to increase engagement with the community? –New models of funding ( membership?) –-Stronger project governance? –Other forms of communication?

27. Breakouts How should we fund the continued management and stewardship of DSpace? What is the best way to increase developer activity on the project? What governance should be put in place for the project?

28. DSpace Futures Meetings Oct / Nov 2012 5 discussions with Sponsors, RSPs, Committers, DCAT Open feedback and discussion of needs / requirements for future versions of DSpace How institutions are using DSpace What meets their needs & where “gaps” exist

29. DSpace Futures Initiatives Official REST API Possible DSpace + Hydra Integration Metadata Improvements (March 20) – Update DSpace to latest Qualified Dublin Core – Other improvements TBD https://wiki.duraspace.org/display/DSPACE/DSpace+Futures

30. Initiative Teams Lead / Co-Leads Steering Committee – may be optional for small initiatives Developers DuraSpace in a supporting / advisory role