The Emerging Digital StackCode Irods LOCKSS DSpace Fedora Etc.
The Emerging Digital Stack DPNBackbone Dark Diverse Replication Audit Succession Code Irods LOCKSS DSpace Fedora Etc.
The Emerging Digital StackPreservation TACC SDR APT Hathi Chrono.Repositories DPN Backbone Dark Diverse Replication Audit Succession Code Irods LOCKSS DSpace Fedora Etc.
The Emerging Digital Stack Interntet CLOCKSSPreservation TACC SDR APT Hathi Chrono. PorticoRepositories Meta DPN Backbone Dark Diverse Replication Audit Succession Code Irods LOCKSS DSpace Fedora Etc.
The Emerging Digital Stack Investing in Capabilities Sloan Inst Interntet Access DPLA Dig CRL Publishers Repos Sky CLOCKSSPreservation TACC SDR APT Hathi Chrono. PorticoRepositories Meta DPN Backbone Dark Diverse Replication Audit Succession Code Irods LOCKSS DSpace Fedora Etc.
DuraSpace Summit Meeting“The Role of DuraSpace in Managing Community Source Software” Part 2: Presented by Michele Kimpton, DuraSpace Chief Executive Officer & Jonathan Markow, DuraSpace Chief Strategy Officer
…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
Who is DuraSpace? Not for profit 501c3 formed in 2009Bringing together of the DSpace Foundation and Fedora Commons Organization
Our missionDuraSpace 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.
How is DuraSpace organized? Funded through Funded through servicesponsorship,RSP program revenue and grants DuraSpace Projects Services DSpace Fedora Vivo DuraCloud Education Dspacedirect
Why we are here today? Projects DSpace FedoraTogether we must develop a sustainable model for these projects
Total funds raised from sponsorship Other $21,000 Fedora$173,000 DSpace $223,750 $417,750 for Fy2012
Together we need to increase the level of contribution andengagement for both projects to ensure long term success
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
How does DuraSpace support projects?• Executive leadership• Technical leadership• Community outreach• Communications/promotion• Business administration
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
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
DuraSpace Summit Meeting“The University Librarian Perspective” Presented by Tyler Walters, Dean of University Libraries, Virginia Tech
Title Here DuraSpace Summit: The University Librarian PerspectiveTyler WaltersDuraSpace Summit Meeting, March 13, 2013 Title Here, Optional or Unit Identifier
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 else30
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 – DuraSpace31
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)32
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?33
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
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?
DuraSpace Summit Meeting“The Fedora Futures project, a case study for future collaboration” Presented by Edwin Shin, MediaShelf & Tom Cramer, Stanford University
AgendaIntroduction1. Why Fedora Futures?2. Project Overview3. Project Roles and Community ParticipationDiscussion
A (Funding) History of Fedora• Original software created 2000–08 with $2.4M from the Mellon Foundation – +$500,000 from UVA Library• Moore Grant: 2007-11, $5.4M• Committers from 10 institutions• 2009–present: DuraSpace’s sponsorship program has provided funding for a tech lead
The Success of Fedora• Architecture is demonstrably Flexible & Extensible• Support for Durability• One foot in the linked data world• A decade of maturity & proven use• Substantial community of adopters, contributors, vendors
Looming Storm CloudsTechnical Organizational• Performance • Small, fixed pool• Fault tolerance of developers• Scalability • Demands outstrip• Complexity applied resources• Aging code base • Lack of vibrancy
New Opportunities• Front-ends: eSciDoc, Hydra, Islandora – Attracting new energy and adopters – Creating new technical demands• Evolved technical environment – Web architectures & horizontal scaling – Linked data• Data management mandates
Fedora Futures Forms…• OR12: Ad hoc meeting• September: – Meet to compare needs and notes – Charter a 3 month investigation• December: – Commit to a three year project – Announce, Invite and Launch
Fedora Futures Objectives• Preserve the strengths of the architecture and community• Address the needs for robust and full- featured repository services (that we now understand very well)• Provide a platform in the repository ecosystem for the next 5-10 years
Technology Overview• Highly scalable• High availability• Flexible storage*• Durability*• Reporting and metrics*• Developer-friendly*• Ease of deployment
Technical Process & Organization• Technical Team – 4 FTEs across 11 individuals, 8 institutions – 12, 2-week sprints• Build-Measure-Learn – Hydra – Islandora – Conferences and Hackfests
Project Roles• DuraSpace• Tech Team/Developers• Fedora Community• Institutional Support
New Challenges• New use cases – sign of success• Changing landscape – data• Evolving developer community• Funding
New Approaches• Sponsorship model• Transition planning• Sustainable funding model
Who is in Fedora Futures so far…• Columbia • University of NSW• DuraSpace • Indiana University• FIZ Karlsruhe • CDC• MediaShelf • USGS?• Oxford • Your name here• Stanford• Smithsonian• UPEI / Disc.Gard.• U of Virginia
DuraSpace Summit Meeting Day 2“Open discussion on governance,funding and strategic direction of DuraSpace”
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?
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?
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
DSpace Futures Initiatives• Official REST API• Possible DSpace + Hydra Integration• Metadata Improvements (March 20) – Update DSpace to latest Qualified Dublin Core – Other improvements TBDhttps://wiki.duraspace.org/display/DSPACE/DSpace+Futures
Initiative Teams• Lead / Co-Leads• Steering Committee – may be optional for small initiatives• Developers• DuraSpace in a supporting / advisory role
DuraSpace Summit Meeting Day 2“Open discussion on governance,funding and strategic direction of Fedora”
Agenda Setting Direction for the MorningObjectives and Development ProcessRoles and BudgetGovernanceNext Steps
Moving Toward a SustainableFuture - Roles, Responsibilities & Financing
Responsibilities– Governance– Product Management– Community Management– Communication & Marketing– Administration– Project Management– Development
Roles• Community• Partners – non-profit and service providers• Steering & Advisory• Product Manager• Technical Lead• Technical Team
Funding• Early Years – Grant Funded – Dedicated Team• Recent Years – stretching the grant dollar – Sponsorship – Community Contributions• Now – Sponsorship – Contributions – Fedora Future Project Resourcing• Future?
Current Players• Community Sponsors & Adopters• Duraspace• Fedora Futures Project Steering Group• Fedora Futures Technical Lead• Fedora Committers• Fedora Futures Tech Team
Finances• Expenses – Indirect Costs – Direct Costs• Current Revenue Sources – Sponsorship – Incremental Project Funds• Net