AtoM's Governance, Development and Future
•Descargar como PPTX, PDF•
2 recomendaciones•477 vistas
These slides accompanied a presentation by Dan Gillean and Sara Allain of Artefactual Systems, delivered as part of AtoM Camp Cambridge, a three-day boot camp held at St John's College, Cambridge University, May 9-11, 2017 For more information, see: https://wiki.accesstomemory.org/Community/Camps/SJC2017 In this session, we looked at the history of the AtoM project, the current governance and maintenance model for AtoM that Artefactual Systems maintains, as well as several other open source business models and stakeholders as we consider ways in which governance and maintenance might look different in the future. Finally, we looked at the state of the application at present with an eye to the future - exploring how changes in international standards and web technologies provide an opportunity to consider what AtoM 3 might look like. The session was followed by open discussion.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a AtoM's Governance, Development and Future
Similar a AtoM's Governance, Development and Future (20)
Más de Artefactual Systems - AtoM
Más de Artefactual Systems - AtoM (16)
Último
Último (20)
AtoM's Governance, Development and Future
- 1. AtoM’s Governance, Development, and Future Looking Ahead https://commons.wikimedia.org/wiki/File:Wooden_signpost_at_the_crossroads.jpg
- 2. First, we look back…
- 3. AtoM’s Development 2002 0.2-ALPHA ICA/CIT report: Market Survey of Commercially Available Off-the-Shelf Archival Management Software (January 2003) ICA/CDS OSARIS report v1 ICA/CDS, ICA/CIT, UNESCO discuss how to advance OSARIS project ICA/CIT: OSARIS Functional Requirements report UNESCO Grant to ICA: Online Guide to Archival Sources Related to Human Rights Violations Peter Van Garderen (Artefactual) hired to build open source application Technical analysis begins 0.1-ALPHA 2008
- 4. 2005: Open Archives System The original project vision submitted by Peter Van Garderen, December 9, 2005
- 5. ICA-AtoM 1.0-beta • Released at the 2008 ICA Congress in Kuala Lumpur, July 21-27 • Distributed as a demo CD • Workshop and presentation given
- 7. ICA-AtoM Project Goals The purpose of the ICA-AtoM Project is to provide free and open- source software: • that enables institutions to make their archival holdings available online, especially those who could not otherwise afford to do so • that manages archival descriptions in accord with ICA standards • that provides multi-lingual interfaces and content translation features • that supports multiple collection types • that is fully web-based, user-friendly and follows accessibility best practices • that is flexible and customizable • that is useful to both small and large institutions alike • that supports single or multi-repository implementations
- 8. ICA-AtoM Proposed Governance Model Software Release Manager Support & Training Manager ICA-AtoM Steering Committee UsersDevelopers Funding Donors ICA Archival Community Finance & Legal Manager Communications & Marketing Manager ICA-AtoM Member Institutions Service Providers & Subcontractors ICA Branches & Sections ICA-AtoM Software DRAFT FOR DISCUSSION. Version 3. May 20, 2008
- 9. AtoM’s Development 20142008 0.X-BETA 1.0-BETA FIRST NON-BETA RELEASE 1.1 2.01.31.2 TRILLIUM THEME
- 10. AtoM’s Development 20192013 1.x 2.22.0 2.42.3 JOB SCHEDULER 2.0.1 2.1.1 2.1 2.2.11.3.1 CLIPBOARD AtoM 2.4 • Full bulk import / export via the user interface • Search index improvements • Authority records and repositories on the Clipboard
- 11. Development Philosophy Community-based development Bounty model of business • Standards-based • Open source / Creative Commons • Multilingual support • Generalize specific use cases • Include all features in public release • Iterative development via multiple contributions over subsequent releases • Maintain: documentation, software, wiki, etc. • Produce additional resources (e.g. videos, presentations, webinars) • Participate in user forum • Offer additional paid services • Always include development in public project Read more: https://wiki.accesstomemory.org/Development/Philosophy
- 12. Now we look around… https://pixabay.com/en/audience-crowd-people-persons-828584/
- 13. https://pixabay.com/en/audience-crowd-people-persons-828584/ The Open Source Ecosystem Leading implementers Private companies Non-profit organizations Funding agencies Developers Users Standards organizations
- 14. https://pixabay.com/en/audience-crowd-people-persons-828584/ The Open Source Ecosystem Standards organizations How does the creation or modification of standards relate to the development of open-source tools? Should standards be created with software development in mind?
- 15. https://pixabay.com/en/audience-crowd-people-persons-828584/ The Open Source Ecosystem Funding Agencies Funding agencies play a key role in open-source software development, but what is their role once the tools have been developed?
- 16. https://pixabay.com/en/audience-crowd-people-persons-828584/ The Open Source Ecosystem Leading implementers Developers Users Developers work for non-profit organizations or private companies. They may also work for leading implementers, or simply be technically-minded users. Leading implementers are institutions that provide community support, funding and/or development. These tend to be universities and research institutions. Having a large pool of users is a sign of software maturity and stability.
- 17. https://pixabay.com/en/audience-crowd-people-persons-828584/ The Open Source Ecosystem These organizations provide sustainability for mature open- source software tools by offering software development and release management, hosting, tech support, data migration, training, consulting, documentation, user forums and other critical services. However, finding a viable business model can be a challenge. Private companies Non-profit organizations
- 18. Open-source Business Models When grant funding ends or doesn’t cover all costs, there are different ways of making open-source software viable and self-sustaining. Here are three common models: • Membership model • Bounty development model • Services model https://commons.wikimedia.org/wiki/File:Exchange_Money_Conversion_to_Foreign_Currency.jpg
- 19. Membership Model The software is free and open-source but purchase of a membership allows users to gain access to certain privileges or services. Some membership models mean that only members get access to certain types of documentation, training materials, issue reporting systems and/or member-only user forums. Other membership models provide privileges such as a role in governance, discounts on training and meeting events, but don’t restrict documentation etc. Examples: • Lyrasis (ArchivesSpace, CollectionSpace) • BitCurator Consortium • DuraSpace (DSpace, Archivematica, DuraCloud, Fedora) • Islandora Foundation • Open Preservation Foundation (JHOVE, Jpylyzer, FIDO, xcorrSound) https://commons.wikimedia.org/wiki/File:Exchange_Money_Conversion_to_Foreign_Currency.jpg The money raised is used to support continued development and software release management.
- 20. Bounty Development Model The software is free and open-source but development of new features and enhancements depends on one or more institutions providing funding. The new features and enhancements are added to subsequent public releases of the software. Sometimes called “Professional Open Source.” Examples: • Artefactual Systems (Archivematica, AtoM) • Data Curation Experts (Hydra, Blacklight, Fedora) • DiscoveryGarden (Islandora) • Hudson Molonglo (ArchivesSpace) https://commons.wikimedia.org/wiki/File:Exchange_Money_Conversion_to_Foreign_Currency.jpg
- 21. Services Model The software is free and open-source, but there are organizations that provide related services such as hosting, technical support, data migration, consulting, training and customization. These organizations may or may not be the lead developers of the tools. Examples: • Artefactual Systems (Archivematica, AtoM) • DuraSpace (DSpace, Archivematica, DuraCloud, Fedora) • DiscoveryGarden (Islandora) • Cottage Labs (Hydra, Fedora) • AVPreserve (Archival Management System, Exactly, Fixity + other tools) • KEEP Solutions (RODA, DSpace + other tools) https://commons.wikimedia.org/wiki/File:Exchange_Money_Conversion_to_Foreign_Currency.jpg
- 22. Other Open-source models https://commons.wikimedia.org/wiki/File:Exchange_Money_Conversion_to_Foreign_Currency.jpg Franchising model: The software is free and open-source, but the name and logo(s) are proprietary and can only be used with permission. The owners of the name and logo(s) sell the rights to organizations to provide technical support, hosting and customization services. Proprietary add-on / “freemium” model: The software is free and open-source, but organizations develop proprietary add-ons or plugins or have “enterprise” or “professional” versions that add more functionality or scalability.
- 23. https://pixabay.com/en/audience-crowd-people-persons-828584/ Where Do You Fit In? Leading implementers Private companies Non-profit organizations Funding agencies Developers Users Standards organizations
- 25. Non-backwards compatible changes in dependencies… • PHP Framework • Version used in AtoM 1.4 (deprecated in 2012) • Current Symfony version: 3.3 • Search index • Version used in AtoM 1.7 (deprecated in Jan 2017) • Current ES version: 5.3
- 27. And Major Changes Coming in our International Standards…
- 28. Provide an opportunity for AtoM’s evolution “Veil Nebula - NGC6960” by Ken Crawford - https://en.wikipedia.org/wiki/Veil_Nebula#/media/File:Veil_Nebula_-_NGC6960.jpg
- 29. AUR A AtoM Upgrade/Rewrite Analysis Artefactual’s internal task force to begin considering possible technologies and development patterns for a next- generation version of AtoM. • Highlight biggest current bottlenecks • Research emerging technologies and standards • Develop proposed models for implementation • Consider upgrade paths • Begin researching funding and community support options
- 30. AUR A AtoM Upgrade/Rewrite Analysis Initial architecture proposal for discussion, July 28, 2016
- 31. AUR A AtoM Upgrade/Rewrite Analysis Initial design goals: • Use well-supported, stable open-source technologies • Modular not monolithic • Support linked data • Separate front and back-end • Scale to hundreds of millions of records • Build permissions, accessibility, and internationalization in from the start • Full multi-repository support • Address the challenge of federation (contributing to portals, etc)
- 32. But these are just our ideas. http://www.publicdomainpictures.net/view-image.php?image=173836&picture=water-drop-macro-view
- 33. We can’t do this without you. https://pixabay.com/en/audience-crowd-people-persons-828584
- 34. • How should we fund the project? • How should we govern the project? • How should we build the project? Issues to consider:
Notas del editor
- The impulse that eventually led to the creation of ICA-AtoM first came out of collaborative discussions between the ICA’s Committee on Descriptive Standards, Committee on Information Technology, and UNESCO. In 2001, a draft report was prepared by an ad-hoc committee from ICA-CDS to describe some of the functional requirements necessary for the online presentation of finding aids that conformed to the ICA standards. The draft report references this theoretical system as OSARIS – the Open Source Archival Information System – which became an ongoing topic of conversation between the groups throughout 2002. In November 2003, after performing a survey of existing Archival Management systems, the Committee on Information Technology released an updated report on the functional requirements for the OSARIS project, with the hopes of eventually supporting the development of such a system. Without a clear source of funding however, the project stalled shortly after that until in 2005, UNESCO provided the ICA with a grant to support the creation of an Online Guide to Archival Sources Related to Human Rights Violations. The ICA and UNESCO decided to use this project as an opportunity to move the OSARIS project forward, and create an open source, web-based application for description and access that would support the ICA standards. In late 2005, Peter Van Garderen of Artefactual Systems was hired to implement this vision. After a thorough technical requirements analysis process, the very first alpha versions of the application were made in late 2006. There was great interest in the prototype, and a desire to prepare a 1.0 version of the application in time for release at the 2008 ICA conference in Kuala Lumpur, but more resources were required to carry the project forward. Fortunately, institutions such as The Hogeschool Van Amsterdam Archiefschool, Direction des Archives de France, the World Bank Group Archives, and the United Arab Emirates Centre for Documentation and Research all made contributions that allowed the project to continue. Sources: http://www.icacds.org.uk/eng/minutesjune2002.pdf http://www.icacds.org.uk/eng/madridreport.pdf (Also from June 12-15 2002) Where all the reports are: http://www.icacds.org.uk/eng/reports.htm http://www.icacds.org.uk/eng/rioreport.pdf (December 2002) ICA/CIT market survey from 2003 of archival mgmt. software: http://www.ica.org/sites/default/files/ICA_Study-12-Survey-of-archival-management-software_EN.pdf International Council on Archives Committee on Descriptive Standards. Report of the Ad Hoc Committee for Development of a Standardized Tool for Encoding Archival Finding Aids. October 2001. Accessed September 21, 2016. http://www.icacds.org.uk/eng/encoded.pdf
- Meanwhile, in May of 2008, leading up to the 1.0-beta launch at the ICA Congress, a steering committee was formed to begin considering the long-term maintenance of the application as interest in the project grew. The Committee held its first meeting at the Dutch Archiefschool in Amsterdam in May 2008. There it drafted the following Project Purpose and Values statement:
- At the Amsterdam meeting in May 2008, the Committee also began discussion about the project's organizational structure and business model but these were not finalized at that time. This is the proposed Governance model that had been circulated at the first and second meetings of the ICA-AtoM steering committee.
- The impulse that eventually led to the creation of ICA-AtoM first came out of collaborative discussions between the ICA’s Committee on Descriptive Standards, Committee on Information Technology, and UNESCO. In 2001, a draft report was prepared by an ad-hoc committee from ICA-CDS to describe some of the functional requirements necessary for the online presentation of finding aids that conformed to the ICA standards. The draft report references this theoretical system as OSARIS – the Open Source Archival Information System – which became an ongoing topic of conversation between the groups throughout 2002. In November 2003, after performing a survey of existing Archival Management systems, the Committee on Information Technology released an updated report on the functional requirements for the OSARIS project, with the hopes of eventually supporting the development of such a system. Without a clear source of funding however, the project stalled shortly after that until in 2005, UNESCO provided the ICA with a grant to support the creation of an Online Guide to Archival Sources Related to Human Rights Violations. The ICA and UNESCO decided to use this project as an opportunity to move the OSARIS project forward, and create an open source, web-based application for description and access that would support the ICA standards. In late 2005, Peter Van Garderen of Artefactual Systems was hired to implement this vision. After a thorough technical requirements analysis process, the very first alpha versions of the application were made in late 2006. There was great interest in the prototype, and a desire to prepare a 1.0 version of the application in time for release at the 2008 ICA conference in Kuala Lumpur, but more resources were required to carry the project forward. Fortunately, institutions such as The Hogeschool Van Amsterdam Archiefschool, Direction des Archives de France, the World Bank Group Archives, and the United Arab Emirates Centre for Documentation and Research all made contributions that allowed the project to continue. Sources: http://www.icacds.org.uk/eng/minutesjune2002.pdf http://www.icacds.org.uk/eng/madridreport.pdf (Also from June 12-15 2002) Where all the reports are: http://www.icacds.org.uk/eng/reports.htm http://www.icacds.org.uk/eng/rioreport.pdf (December 2002) ICA/CIT market survey from 2003 of archival mgmt. software: http://www.ica.org/sites/default/files/ICA_Study-12-Survey-of-archival-management-software_EN.pdf International Council on Archives Committee on Descriptive Standards. Report of the Ad Hoc Committee for Development of a Standardized Tool for Encoding Archival Finding Aids. October 2001. Accessed September 21, 2016. http://www.icacds.org.uk/eng/encoded.pdf
- A successful open-source project is not something that arises in isolation. Most, if not all, of the components in this diagram have some kind of role to play in any o/s project.
- I’ve put up a question here to which I don’t really know the answer. What do you think?
- Funding from some kind of government agency or non-profit organization is the way that many o/s projects get their start. For example, Archivematica had some seed funding from UNESCO, and AtoM was originally developed with funding from the International Council of Archives. However, it’s been about 7 years since these sources disappeared. In Canada, there are very few sources of government grants for the kind of work we do. However, we often get hired to do development work by other organizations that are eligible for government grants. For example, the Canadian Council of Archives recently applied for federal grants which they then used to hire us to develop enhancements to Archivematica and AtoM.