AtoM wiki - User contributions [en]

Community/Users

2019-04-03T16:58:08Z

Djjuhasz: /* AtoM (2.x) sites */ Remove British Columbia Digitization Coalition's West Beyond the West Portal

{{#pagetitle: Users }}
[[Main Page]] > [[Community]] > Community/Users

On this page you'll find some examples of institutions and organizations using AtoM and/or ICA-AtoM. Don't see your institution on this list? Please feel free to [[Special:UserLogin|add a link]] to your AtoM installation!

==AtoM (2.x) sites==

'''English'''
* [https://archives.rcaf.museum/ Air Force Museum of Alberta Archives]
* [http://www.albertaonrecord.ca/ Alberta on Record: Archives Society of Alberta Portal]
* [https://archives.ambrose.edu/ Ambrose Archives]
* [http://archeion.ca Archeion: Ontario's Archival Information Network]
* [https://archie.library.carleton.ca/ Archives & Research Collections, Carleton University Library]
* [http://anglicanarchives.ica-atom.org/ Archives of the Anglican Diocese of New Westminster and Provincial Synod of BC and Yukon]
* [http://arc.anla.nf.ca/ ARC: the Archival Resource Catalogue of the Association of Newfoundland and Labrador Archives]
* [https://archivescanada.accesstomemory.ca/ ArchivesCanada - the Canadian Archival Information Network Portal]
* [http://archives.canbarchives.ca/ ArchivesCANB: the Council of Archives New Brunswick's archival database]
* [http://www.archives.pe.ca/atom/index.php/ Archives PEI, the Archives Council of Prince Edward Island's description database]
* [http://archives.artcenter.edu/ ArtCenter Archives and the Hoffmitz Milken Center for Typography Archives]
* [http://archivescollection.anu.edu.au/ Australian National University Archives]
* [http://beatoninstitute.com/ The Beaton Institute (Cape Breton University)]
* [https://hbbarchive.ca/ Bishop's University - History beyond Borders project]
* [https://borthcat.york.ac.uk/ Borthwick Institute for Archives - University of York]
* [http://atom.lib.bcit.ca/ British Columbia Institute of Technology Archives & Special Collections]
* [https://archives.cendari.dariah.eu/ CENDARI Archives Directory]
* [https://ccap.uvic.ca Chinese Canadian Artifacts Project]
* [http://searcharchives.coquitlam.ca/ City of Coquitlam Archives]
* [http://searcharchives.vancouver.ca/ City of Vancouver Archives]
* [https://archives.victoria.ca/ City of Victoria Archives]
* [http://winnipeginfocus.winnipeg.ca/ City of Winnipeg Archives]
* [http://claretiansusa.org Claretain Missionaries USA-Canada Province] (archives site not public)
* [https://archives.cliftonbridge.org.uk/ Clifton Suspension Bridge Archives]
* [https://discover.cabhc.ca/ Community Archives of Belleville and Hastings County]
* [http://concordia.accesstomemory.org/ Concordia University]
* [https://onlinecollections.cumberlandmuseum.ca/ Cumberland Museum and Archives]
* [http://helates.cut.ac.cy/ Cyprus University of Technology Library Archives] (Greek)
* [https://findingaids.library.dal.ca/ Dalhousie University Libraries]
* [https://saanich.accesstomemory.org/ District of Saanich Archives]
* [http://atom.doaks.org/atom/ Dumbarton Oaks Research Library and Collection]
* [https://atom-sparc.fitnyc.edu/ Fashion Institute of Technology - Gladys Marcus Library's Special Collections and College Archives]
* [https://fhya.org/ Five Hundred Year Archive (FHYA)]
* [https://archives.franciscanfriars.ca/ Franciscans of Canada Archives West]
* [http://archives.gcu.ac.uk/ Glasgow Caledonian University Archives]
* [http://archive.griffith.ox.ac.uk Griffith Institute Archive]
* [http://archives.hpl.ca/ Hamilton Public Library Local History & Archives Department]
* [https://archives.highgatecemetery.org/ Highgate Cemetary Archives]
* [http://www.highlandparkhistory.org/ Highland Park Historical Society]
* [http://historicalpapers-atom.wits.ac.za/historical-papers-research-archive-library-university-of-witwatersrand Historical Papers Research Archive, Wits University]
* [http://ica.institutomarcelodeda.com.br/ Instituto Marcelo Déda]
* [http://jikn.sikn.go.id/ Jaringan Informasi Kearsipan Nasional] (Indonesian)
* [http://archives.jewishmuseum.ca/ The Jewish Museum & Archives of BC]
* [https://archives.kpu.ca/ Kwantlen Polytechnic University Archives]
* [http://archives.lakeheadu.ca/ Lakehead University Archives]
* [https://libarchives.wlu.ca/ Laurier Archives]
* [http://www.ltiarchives.ca Leeds and the Thousand Islands Archives]
* [http://www.legatum.ufba.br/atom/ Legatum - Sonus et Imago Repository] (multilingual)
* [http://lslirc-tarrarchives.accesstomemory.org/ Lesser Slave Lake IRC Treaty Aboriginal Rights Research Archives]
* [https://archives.mhsc.ca/ MAID: The Mennonite Archival Image Database]
* [http://nanna.lib.umanitoba.ca/ MAIN: Manitoba Archival Information Network]
* [http://archives.mcmaster.ca/ McMaster University Library Archives and Research Collections]
* [http://www.memorybc.ca/ MemoryBC - British Columbia's Archival Information Network]
* [https://memoryns.ca/ MemoryNS, the Council of Nova Scotia Archives' archival database]
* [http://www.gov.pe.ca/paroatom/ Memory PEI - Public Archives and Records Office of Prince Edward Island]
* [http://catalogue.millsarchive.org/ Mills Archive]
* [http://history.missionarchives.com/ Mission Community Archives]
* [https://archives.mtroyal.ca/ Mount Royal University Archives and Special Collections]
* [http://archives.museeheritage.ca Musée Héritage Museum Archives]
* [http://atom.moa.ubc.ca/ Museum of Anthropology, Audrey and Harry Hawthorn Library and Archives, University of British Columbia]
* [http://museumofcroydoncollections.com/catalogues/ Museum of Croydon]
* [https://archives.library.wales/ National Library of Wales - Archives and Manuscripts]
* [https://archives.nyrr.org/ New York Road Runners Archives]
* [http://archives.eclibrary.ca/ Nipissing University and Canadore College Archives and Special Collections]
* [http://archives.nato.int/ North Atlantic Treaty Organization (NATO) Archives]
* [https://atomic.library.tmc.edu/ Nuclear Memories Archive] (Texas Medical Center Library)
* [http://offalyhistoryarchives.com/ Offaly History Archives]
* [https://digitalcollections.ohs.org/ Oregon Historical Society Digital Collections]
* [http://asiapacific.anu.edu.au/pambu/catalogue/ Pacific Manuscripts Bureau]
* [http://atom.prattsils.org/ Pratt School of Information On-site Archives and Special Collections]
* [http://archives.ppcli.com/ Princess Patricia’s Canadian Light Infantry Museum & Archives]
* [http://atom.skagafjordur.is/index.php/ Regional Archives of Skagafj ordur] (English, Icelandic)
*[https://archives.renison.ca/ Renison University College, Florence Li Tim-Oi Memorial Archives]
* [https://rcdcarchives.ica-atom.org/ Roman Catholic Diocese of Calgary Archives]
* [http://search-bcarchives.royalbcmuseum.bc.ca/ Royal British Columbia Museum - BC Archives]
* [http://archives.rncm.ac.uk/ Royal Northern College of Music]
* [https://royalroads.accesstomemory.org/ Royal Roads University]
* [https://www.sjcarchives.org.uk/institutional/ Saint John's College Archives]
* [http://atom.library.moore.edu.au/ The Samuel Marsden Archives, Moore College Library]
* [http://sain.scaa.sk.ca/collections/ Saskatchewan Archival Information Network Collections Database]
* [http://sain.scaa.sk.ca/items/ Saskatchewan Archival Information Network Photographs Database]
* [https://senecacollege.accesstomemory.org/ Seneca College Archives and Special Collections]
* [http://atom.archives.sfu.ca/ SFU AtoM - Simon Fraser University]
* [https://atom.schalifax.ca/ The Sisters of Charity - Halifax Archives]
* [http://squamishlibrary.digitalcollections.ca/ Squamish Public Library - Digital Collections]
* [https://archive.sro.wa.gov.au/ State Records Office of Western Australia]
* [https://archives.sgul.ac.uk/ St George's Archives & Special Collections, University of London]
* [https://stirlingcouncil.ica-atom.org/ Stirling Council Archives]
* [https://archives.trinity.edu/ Trinity University Coates Library Special Collections and Archives]
* [http://archivessearch.twu.ca/ Trinity Western University Archives and Special Collections]
* [http://search.nbca.unbc.ca/index.php/ UNBC Northern BC Archives]
* [http://atom.archives.unesco.org/ UNESCO Archives]
* [http://search.archives.un.org/ United Nations Archives and Records Management Section]
* [http://rbscarchives.library.ubc.ca/ University of British Columbia Rare Books and Special Collections]
* [https://searcharchives.ucalgary.ca/ University of Calgary Archives and Special Collections]
* [http://www.atom.lib.uct.ac.za/ University of Capetown Libraries: Special Collections]
* [http://sca.glos.ac.uk/index.php/ University of Gloucestershire Special Collections and Archives]
* [https://atom.library.miami.edu/ University of Miami Archival Collections]
* [http://archives.unam.edu.na/ University of Namibia Archives]
* [http://search.nbca.unbc.ca/ University of Northern British Columbia Archives]
* [https://biblio.uottawa.ca/atom/index.php/ University of Ottawa - Archives and Special Collections]
* [http://strathclyde.ica-atom.org/ University of Strathclyde Archives]
* [https://sparc.utas.edu.au/ University of Tasmania - Special & Rare Collections online]
* [https://discoverarchives.library.utoronto.ca/ University of Toronto - Discover Archives]
* [http://whistler.ica-atom.org/ Whistler Museum and Archives]
* [https://archivesholdings.worldbank.org/ World Bank Group Archives Holdings]
* [http://atom.library.yorku.ca Clara Thomas Archives and Special Collections, York University Libraries]

'''French'''
* [https://inventaires.archivescommunales-vd.ch/ Archives comunales du canton de Vaud] (Swiss)
* [http://archivesdemontreal.ica-atom.org/ Archives de Montréal]
* [https://archives.uclouvain.be/atom/index.php/ Archives de l'Université catholique de Louvain] (Belgium)
* [http://ratp.histolab.fr/index.php/?sf_culture=fr Archives Groupe RATP ] (French)
* [https://archiveshistoriques.ville.levis.qc.ca/ Archives privées de la Ville de Lévis]
* [http://http://claretains.ca/ Missionaires Clarétains] (archives site not public)
* [https://caspar.cinematheque.ch CASPAR - Cinémathèque Suisse Papier Archives] (French)
* [http://archives.graduateinstitute.ch/ The Graduate Institute IHEID, Geneva] (French)
* [https://legis.cdij.bj/ LEGIS : Base de données des textes de loi en République du Bénin] (French)

'''Brazillian Portuguese'''
* [http://fonte.ufsm.br/ Acervo Arquivístico da Universidade Federal de Santa Maria] (Brazilian Portuguese)
* [http://acervo.cidarq.ufg.br/index.php/iuryy;isad Acervos Arquivísticos] (Brazilian Portuguese)
* [http://icaatom.almg.gov.br/ Acervo Arquivístico da Assembleia Legislativa do Estado de Minas Gerais] (Brazilian Portuguese)
* [http://www.acervomemorial.al.rs.gov.br/index.php/?sf_culture=pt Acervo do Memorial do Legislativo] (Brazilian Portuguese)
* [http://arquivodigital.furg.br/ Arquivo digital da Universidade Federal do Rio Grande] (Brazilian Portuguese)
* [https://atom.tjpe.jus.br/ Arquivo Histórico do Memorial da Justiça] (Brazilian Portuguese)
* [http://arquivomunicipal.caxias.rs.gov.br/ Arquivo Histórico Municipal João Spadari Adami - Caxias do Sul] (Brazilian Portuguese)
* [http://www.cle.unicamp.br/atom-2.2.1/index.php/ Arquivos Históricos do Centro de Lógica, Epistemologia e História da Ciência] (Brazilian Portuguese)
* [http://200.222.27.136/ Arquivo Público do Estado do Rio de Janeiro] (Brazilian Portuguese)
* [http://www.basearch.coc.fiocruz.br/ Base Arch - Fundação Oswaldo Cruz] (Brazilian Portuguese)
* [http://dibrarq.arquivonacional.gov.br/ DIBRARQ - Diretório Brasil de Arquivos] (Brazilian Portuguese)
* [http://atom.poa.ifrs.edu.br/ Instituto Federal Rio Grande do Sul - Campus Porto Alegre] (Brazilian Portuguese)
* [https://www.acervo.pe.gov.br Portal Estadual do Patrimônio Documental de Pernambuco] (Brazilian Portuguese)
** [https://www.acervo.arquivopublico.pe.gov.br/index.php/arquivo-publico-estadual-jordao-emerenciano Arquivo Público Estadual Jordão Emerenciano]
* [https://atom.unb.br/ Universidade de Brasília] (Brazilian Portuguese)
* [http://atom.ufcspa.edu.br/ Universidade Federal de Ciências da Saúde de Porto Alegre] (Brazilian Portuguese)
* [http://atom.ufv.br/ Universidade Federal de Viçosa] (Brazilian Portuguese)

'''Portuguese'''
* [http://arquivoatom.up.pt/index.php/fundacao-instituto-arquitecto-jose-marques-da-silva Arquivo da Fundação Instituto Marques da Silva] (Portuguese)
* [http://fotos.psd.pt/atom/index.php/ Arquivo da Social-Democracia] (Portuguese)
* [http://arquivo.igreja-lusitana.org/ Arquivo Histórico da Igreja Lusitana] (Portuguese)
* [https://arquivo.cdi-maceiraliz.pt/ Arquivo Histórico Fábrica Maceira-Liz] (Portuguese)
* [http://www.ahsocial.ics.ulisboa.pt/atom/ Arquivo de História Social do Instituto de Ciências Sociais da Universidade de Lisboa] (Portuguese)
* [http://arquivo.cm-albergaria.pt/ Arquivo Municipal de Albergaria-a-Velha] (Portuguese)
* [http://arquivodigital.cm-oaz.pt/ Arquivo Municipal de Oliveira de Azeméis] (Portuguese)
* [http://45.33.69.154/index.php/?sf_culture=pt Arquivo Municipal de Sines] (Portuguese)
* [http://arquivo.cm-valedecambra.pt/ Arquivo Municipal de Vale de Cambra] (Portuguese)
* [https://arquivo.cm-viladobispo.pt/ Arquivo Municipal de Vila do Bispo] (Portuguese)
* [http://portal.cehr.ft.lisboa.ucp.pt/arquivos/ PAPIR - Plataforma de Arquivos Pessoais e de Instituições Religiosas] (Portuguese)
* [http://arquivoatom.up.pt/ Universidade do Porto] (Portuguese)

'''Spanish'''
* [http://132.248.192.4:8081 Archivo Histórico de la UNAM] (Spanish)
* [http://www.madrid.org/archivos_atom/ Archivos de la Comunidad de Madrid] (Spanish)
* [http://archivospublicos.cl/ Archivos Históricos de la Universidad Alberto Hurtado] (Spanish)
* [http://archivo.mariategui.org/ Archivo José Carlos Mariátegui] (Perú - Spanish)
* [http://amp.ing.puc.cl/ Archivo de Música Popular Chilena] (Spanish)
* [http://archivospresidenciales.archivonacional.cl/ Archivo Michelle Bachelet Jeria (President of Chile)] (Spanish)
* [http://archivo.plasencia.es/ Archivo Municipal de Plasencia (Extremadura)] (Spanish)
* [http://archivos.cedinci.org/ CeDInCI - Centro de Documentación e Investigación de la Cultura de Izquierdas en Argentina] (Spanish)
* [http://fondomigueldelibes.fundacionmigueldelibes.es/index.php Fondo Documental Miguel Delibes] (Spanish)
* [http://archivosescolares.ing.puc.cl/ Programa de Archivos Escolares] (Spanish)

'''Dutch'''
* [https://archief.onroerenderfgoed.be/ Archief van het Vlaams Instituut voor het Onroerend Erfgoed] (Dutch)

'''Italian'''
* [http://atom.unito.it/ Historical Archives of the University of Torino] (Italian)

'''Swedish'''
* [https://arken.kb.se/ National Library of Sweden - Arken Directory] (Swedish)

'''Greek'''
* [http://nspantelakis.gr/family-archives/ Nikolaos S. Pantelakis Family archives] (Greek)

==ICA-AtoM (1.x) sites==

'''English'''
* [http://www.dart.ipsr.mahidol.ac.th/index.php/n56S2;isad Digital Archive of Research on Thailand]
* [http://archive.womenslibrary.org.uk/index.php/ Glasgow Women's Library Archive Catalogue]
* [http://www.migan.org MIGAN - the directory of Caribbean archival institutions] (English/French)
* [http://ica-atom.tasglann.org.uk/ Tasglann nan Eilean Siar (Hebridean Archives)]

'''Brazilian Portuguese'''
* [http://web2.santamaria.rs.gov.br/arquivohistorico/sistema_descricao_documental/index.php/ Acervo digital do Arquivo Histórico Municipal de Santa Maria] (Brazilian Portuguese)
* [http://icaatom.arquivoestado.sp.gov.br Arquivo Público do Estado de São Paulo] (Brazilian Portuguese)

'''Portuguese'''
* [http://cad.cgtp.pt/ica/ Centro de Arquivo e Documentação CGTP-IN] (Portuguese)

'''Spanish'''
* [http://archivo.ateneodemadrid.es Archivo del Ateneo de Madrid] (Spanish)
* [http://www.madrid.org/icaatom_pub/index.php/ Archivos de la Comunidad de Madrid] (Spanish)
* [http://archivo.plasencia.es/ Archivo Municipal de Plasencia] (Spanish)
* [http://archivocti.uma.es/icaatom/ Base de datos fotográfica del Centro de Tecnología de la Imagen de la Universidad de Málaga] (Spanish)

Please feel free to [[Special:UserLogin|add a link]] to your AtoM installation.

[[Category:Community]]

Development/MediaPlayers

2018-11-27T18:40:20Z

Djjuhasz: /* Final recommendation */

{{#pagetitle:Media players}}
[[Development]] > MediaPlayers

This page will provide an overview of the digital object media player(s) supported in AtoM, which are used to allow users to play access derivative copies of streaming media such as video and audio files in the browser. It was first created on 2018-11-23, and is current as of the AtoM 2.4 and 2.5 releases.

__TOC__

==Early implementation==

The current media library, [https://flowplayer.com/ Flowplayer], was implemented in the [[Releases/Release_announcements/Release_1.0.8-beta|1.0.8-beta release]]. At the time, Flowplayer was a flash-based video player (version 3.1 of Flowplayer was released in [https://sourceforge.net/p/flowplayer/news/2009/04/flowplayer-31-is-out-now/ April 2009]), and version 3.1.5 was added to AtoM in August of 2009, and included in the 1.0.8 release. See development ticket [https://projects.artefactual.com/issues/2187 #2187] in the AtoM issues list for further details.

==Current status==

Since the initial implementation of Flowplayer in AtoM, no major upgrades or changes have been made to AtoM's time-based media playback functionality. Meanwhile, increasing discoveries of security vulnerabilities and zero-day exploits in Flash have led an increasing amount of browsers and platforms to disavow Flash support, starting as early as 2010, when Steve Jobs stated that Apple would not allow Flash on the iPhone, iPod touch and iPad – citing abysmal security as one reason ([https://www.apple.com/hotnews/thoughts-on-flash/ source]). Since then, with increasing security problems being discovered in Flash and the arrival of HTML5 (which supports native video playback), most major browsers have chosen to disable Flash by default.

Flowplayer itself has redesigned its media player and while they do still maintain a [http://flash.flowplayer.org/ Flash implementation], future development efforts have been focused on an HTML5 version of the player. Support for version 3.1.5, which AtoM still uses, has been discontinued for some time. The Flowplayer Flash version has not been actively developed [https://github.com/flowplayer/flash since 2014], and the last major release was [https://github.com/flowplayer/flash/releases version 3.2.18]. At this point, it is likely that support for Flash will be fully discontinued by 2020.

AtoM is in need of an updated open source media player.

==Replacement requirements==

Any new video player replacement for AtoM should:

* Be open source
* Be HTML5-based
* Be able to play audio as well
* Ideally, include a Flash fallback for legacy browser users
* Support a broad range of playback formats
* Be under active development
* Include basic responsive support for different devices and screen sizes
* Support accessibility, including:
** ARIA support for screenreaders
** Keyboard control support
** Subtitle support

==Evaluating options==

In August of 2018, Artefactual explored the current open source HTML5 video player landscape in search of a replacement candidate that met our requirements. We found the following page extremely useful in evaluating the best contenders:

* http://videosws.praegnanz.de/

After exploring the options listed in the site above, as well as any other popular options that met our criteria we could find, we found the following 3 players to be the closest match to our requirements:

'''Able Player'''

* [https://github.com/paypal/accessible-html5-video-player Webpage]
* [https://github.com/ableplayer/ableplayer GitHub code repository]
* [https://ableplayer.github.io/ableplayer/demos/index.html Examples]

'''MediaElement.js'''

* [https://www.mediaelementjs.com/ Webpage]
* [https://github.com/mediaelement/mediaelement/ GitHub code repository] (examples included on homepage)

'''Accessible HTML5 Video Player'''

* [http://paypal.github.io/accessible-html5-video-player/ Webpage] (basically just a big example video player)
* [https://github.com/paypal/accessible-html5-video-player GitHub code repository]

==Final recommendation==

Of the above options, the Artefactual team felt that [https://www.mediaelementjs.com/ MediaElement.js] would be the best fit as a replacement video player for AtoM.

First developed by John Dyer at the Dallas Theological Seminary and released under MIT license, MediaElement.js is a widely-used project under active development, built responsively with a unified API that can fall back gracefully to Flash, which includes ARIA screen-reader support, subtitles, chapters and playlists, keyboard control, and more. The look and feel is skinnable, it requires no additional Javascript library support, and can also support playback of videos hosted on YouTube, Vimeo, and DailyMotion. It also has a [https://github.com/mediaelement/mediaelement-plugins plugin] ecosystem that can further extend functionality, such as adding basic Google Analytics support, preview on hover, and extended playback controls.

Artefactual has prepared initial development estimates for our community based on implementing MediaElement as the replacement for the current Flowplayer.

We selected the H.264/MPEG-4 video format for in-browser video playback due to it's broad support across desktop and mobile browsers and operating systems (e.g. Windows, Mac OSX, iOS, Android). AtoM currently uses the MP3 audio format for in-browser audio playback, which will remain unchanged.

==Development tasks and estimates==

Below you will find a summary of development task and associated cost estimates, prepared by the [http://artefactual.com/ Artefactual] developers based on the decision to use MediaElement as the replacement library.

'''Current as of: 2018-11-23'''

{| border="1" style="border-collapse:collapse;" align="center"
|colspan="3" style="background-color:#BDF3FB;" align="center"|'''Integrate MediaElement Player in AtoM'''
|- style="background-color:#cccccc;"
|'''Subtask'''
|'''Notes'''
|'''Estimate'''
|- style="background-color:#ffffff;"
|Remove Flowplayer
|Work required to extract the current library
|$300
|-
|Add MediaElement player files to AtoM
|Install player to vendor folder and update Copyright file; general configuration
|$300
|-
|Incorporate MediaElement player into AtoM pages for viewing
|Modify the digital object module's showAudio and showVideo components; create the JS file to load the player; CSS changes; testing
|$3,600
|-
|Remove Flashplayer check from AtoM
|Remove current code that checks the user's browser to see if Flash is present
|$300
|-
|colspan="3" style="background-color:#FEC355;" align="center"|'''Generate mp4 reference derivatives instead of flash video (flv) files'''
|- style="background-color:#cccccc;" align="center"
|'''Subtask'''
|'''Notes'''
|'''Estimate'''
|- style="background-color:#ffffff;"
|Update digital object code to create MPEG4 / H.264 reference derivatives instead of Flash video derivs
|Determine default bitrate, size, etc for new derivatives; review and update all affected areas (including regen-derivatives CLI task, digital object code to support CSV imports via web interface and command-line, etc).
|$2,700
|-
|colspan="3" style="background-color:#AEFEE5;" align="center"|'''Develop task to replace existing Flash video derivatives with mp4 files'''
|- style="background-color:#cccccc;" align="center"
|'''Subtask'''
|'''Notes'''
|'''Estimate'''
|- style="background-color:#ffffff;"
|Add new option to the regen-derivatives command-line task to allow regenerating only video file derivatives to mp4 files
|Ensure users have an easy way to update existing derivatives without having to regenerate all derivatives, which could lose custom user derivative uploads
|$1,200
|-
|colspan="3" style="background-color:#F8FAC7;" align="center"|'''TOTAL DEVELOPMENT FEES: $8,400'''
|}

 

===Costs not included in this table===

There are a few administrative costs not included in the table above, which Artefactual would include in any formal quote prepared based on the estimates above. These include:

{| border="1" style="border-collapse:collapse;" align="center"
|colspan="3" style="background-color:#BDF3FB;" align="center"|'''Additional deployment, testing, and administrative costs'''
|- style="background-color:#cccccc;"
|'''Subtask'''
|'''Notes'''
|'''Estimate'''
|- style="background-color:#ffffff;"
|Community support fee
|A 10% fee we add to development projects that are included in public releases, to help offset the costs of Artefactual maintaining the feature through subsequent releases, writing documentation, managing bug fixes, and offering basic community support via the AtoM [https://groups.google.com/forum/#!forum/ica-atom-users user forum].
|$840
|-
|Test site deployment
|Deployment of an instance of AtoM populated with test data, to be used throughout the development project for previewing the feature, and managing testing and feedback
|$600
|-
|Q/A Testing
|Quality assurance testing and analysis throughout the project to ensure the feature meets the deliverable requirements, identify and resolve any bugs, offer implementation improvement recommendations within the project scope, etc.
|$900
|-
|Backporting, deployment, and maintenance
|Backport the new functionality to a stable branch and either deploy it or make the code available to sponsor for local installation, and assist in running the derivatives regeneration task for current flash-based video derivatives
|$1200
|-
|colspan="3" style="background-color:#F8FAC7;" align="center"|'''Total additional administrative project costs: $3,540 '''
|-
|colspan="3" style="background-color:#AEFEE5;" align="center"|'''TOTAL ALL COSTS: $11,940'''
|}

==Collaborative sponsorship opportunities==

Given that the costs of sponsoring this development may be out of reach for some institutions who nevertheless would really like to see this updated functionality added to AtoM, we would like to encourage our community of users to consider ways in which the feature might be sponsored collaboratively.

Coordinating with many institutions with different schedules and availability, as well differing perspectives and feedback, can potentially add complications to a development project. In light of this, for Artefactual to be able to work effectively with multiple dispersed sponsors, we have outlined our requirements for managing such a project below.

===Artefactual requirements for collaborative development===

'''1) Single point of contact''': We require one institution who is willing to act as the project lead, and the main point of contact throughout the project. This simplifies the communication between our team and the sponsors - the project lead institution would act as the go-between with other sponsoring institutions to coordinate scheduling, testing, and administrative communication throughout the project.

'''2) Single point of feedback''': Working with multiple institutions on a collaboratively funded feature can be challenging if we are receiving contradictory input during the testing and feedback phase of the project. Instead, we would ask that the project lead manage internal discussions among the sponsors during the testing phase, and again act as the single point of contact for feedback, so that any contradictions around design, ideal behavior, and change requests can be resolved prior to communicating with our development team.

'''3) Ideally, a single point of payment administration''': Preferably, the project lead can process contributions from any other participating sponsors, so that Artefactual can supply and process a single invoice at the close of the project. We understand that this may not be possible for all institutions, and can explore alternatives with participating institutions if needed.

===Additional deployment costs for co-sponsors===

As with any major feature development carried out by Artefactual, the work will be included in the next major public release for the entire AtoM community to use, and will be immediately available in the 2.5 development branch in our public GiHub [https://github.com/artefactual/atom/ code repository]. However, if the feature were sponsored collaboratively and all participating institutions wanted access to the enhancement prior to the next public release, there may be additional deployment costs for the participating co-sponsors, so Artefactual can assist in making the work available in a stable branch and deploying it for immediate use.

The prices included in the section above entitled "[[Development/MediaPlayers#Costs_not_included_in_this_table|Costs not included in this table]]" assume deployment of the completed feature to a single institution. If co-sponsors wanted to access the feature prior to the next major public release and would like Artefactual's assistance in doing so, there will be additional costs, which we would handle on a time and materials basis for each institution. For institutions hosted by Artefactual, it would be possible to use support tickets to cover deployment costs.

Please feel free to [mailto:info@artefactual.com contact us] if you have any questions.

-----

* [[Development|Back to Development]]
* [[Main Page|AtoM wiki home]]

[[Category:Development documentation]]

Development/MediaPlayers

2018-11-27T18:39:19Z

Djjuhasz: /* Development tasks and estimates */

{{#pagetitle:Media players}}
[[Development]] > MediaPlayers

This page will provide an overview of the digital object media player(s) supported in AtoM, which are used to allow users to play access derivative copies of streaming media such as video and audio files in the browser. It was first created on 2018-11-23, and is current as of the AtoM 2.4 and 2.5 releases.

__TOC__

==Early implementation==

The current media library, [https://flowplayer.com/ Flowplayer], was implemented in the [[Releases/Release_announcements/Release_1.0.8-beta|1.0.8-beta release]]. At the time, Flowplayer was a flash-based video player (version 3.1 of Flowplayer was released in [https://sourceforge.net/p/flowplayer/news/2009/04/flowplayer-31-is-out-now/ April 2009]), and version 3.1.5 was added to AtoM in August of 2009, and included in the 1.0.8 release. See development ticket [https://projects.artefactual.com/issues/2187 #2187] in the AtoM issues list for further details.

==Current status==

Since the initial implementation of Flowplayer in AtoM, no major upgrades or changes have been made to AtoM's time-based media playback functionality. Meanwhile, increasing discoveries of security vulnerabilities and zero-day exploits in Flash have led an increasing amount of browsers and platforms to disavow Flash support, starting as early as 2010, when Steve Jobs stated that Apple would not allow Flash on the iPhone, iPod touch and iPad – citing abysmal security as one reason ([https://www.apple.com/hotnews/thoughts-on-flash/ source]). Since then, with increasing security problems being discovered in Flash and the arrival of HTML5 (which supports native video playback), most major browsers have chosen to disable Flash by default.

Flowplayer itself has redesigned its media player and while they do still maintain a [http://flash.flowplayer.org/ Flash implementation], future development efforts have been focused on an HTML5 version of the player. Support for version 3.1.5, which AtoM still uses, has been discontinued for some time. The Flowplayer Flash version has not been actively developed [https://github.com/flowplayer/flash since 2014], and the last major release was [https://github.com/flowplayer/flash/releases version 3.2.18]. At this point, it is likely that support for Flash will be fully discontinued by 2020.

AtoM is in need of an updated open source media player.

==Replacement requirements==

Any new video player replacement for AtoM should:

* Be open source
* Be HTML5-based
* Be able to play audio as well
* Ideally, include a Flash fallback for legacy browser users
* Support a broad range of playback formats
* Be under active development
* Include basic responsive support for different devices and screen sizes
* Support accessibility, including:
** ARIA support for screenreaders
** Keyboard control support
** Subtitle support

==Evaluating options==

In August of 2018, Artefactual explored the current open source HTML5 video player landscape in search of a replacement candidate that met our requirements. We found the following page extremely useful in evaluating the best contenders:

* http://videosws.praegnanz.de/

After exploring the options listed in the site above, as well as any other popular options that met our criteria we could find, we found the following 3 players to be the closest match to our requirements:

'''Able Player'''

* [https://github.com/paypal/accessible-html5-video-player Webpage]
* [https://github.com/ableplayer/ableplayer GitHub code repository]
* [https://ableplayer.github.io/ableplayer/demos/index.html Examples]

'''MediaElement.js'''

* [https://www.mediaelementjs.com/ Webpage]
* [https://github.com/mediaelement/mediaelement/ GitHub code repository] (examples included on homepage)

'''Accessible HTML5 Video Player'''

* [http://paypal.github.io/accessible-html5-video-player/ Webpage] (basically just a big example video player)
* [https://github.com/paypal/accessible-html5-video-player GitHub code repository]

==Final recommendation==

Of the above options, the Artefactual team felt that [https://www.mediaelementjs.com/ MediaElement.js] would be the best fit as a replacement video player for AtoM.

First developed by John Dyer at the Dallas Theological Seminary and released under MIT license, MediaElement.js is a widely-used project under active development, built responsively with a unified API that can fall back gracefully to Flash, which includes ARIA screen-reader support, subtitles, chapters and playlists, keyboard control, and more. The look and feel is skinnable, it requires no additional Javascript library support, and can also support playback of videos hosted on YouTube, Vimeo, and DailyMotion. It also has a [https://github.com/mediaelement/mediaelement-plugins plugin] ecosystem that can further extend functionality, such as adding basic Google Analytics support, preview on hover, and extended playback controls.

Artefactual has prepared initial development estimates for our community based on implementing MediaElement as the replacement for the current Flowplayer.

We selected the H.264/MPEG-4 video format for in-browser video playback due to it's broad support across desktop and mobile browsers. AtoM currently uses the MP3 audio format for in-browser audio playback, which will remain unchanged.

==Development tasks and estimates==

Below you will find a summary of development task and associated cost estimates, prepared by the [http://artefactual.com/ Artefactual] developers based on the decision to use MediaElement as the replacement library.

'''Current as of: 2018-11-23'''

{| border="1" style="border-collapse:collapse;" align="center"
|colspan="3" style="background-color:#BDF3FB;" align="center"|'''Integrate MediaElement Player in AtoM'''
|- style="background-color:#cccccc;"
|'''Subtask'''
|'''Notes'''
|'''Estimate'''
|- style="background-color:#ffffff;"
|Remove Flowplayer
|Work required to extract the current library
|$300
|-
|Add MediaElement player files to AtoM
|Install player to vendor folder and update Copyright file; general configuration
|$300
|-
|Incorporate MediaElement player into AtoM pages for viewing
|Modify the digital object module's showAudio and showVideo components; create the JS file to load the player; CSS changes; testing
|$3,600
|-
|Remove Flashplayer check from AtoM
|Remove current code that checks the user's browser to see if Flash is present
|$300
|-
|colspan="3" style="background-color:#FEC355;" align="center"|'''Generate mp4 reference derivatives instead of flash video (flv) files'''
|- style="background-color:#cccccc;" align="center"
|'''Subtask'''
|'''Notes'''
|'''Estimate'''
|- style="background-color:#ffffff;"
|Update digital object code to create MPEG4 / H.264 reference derivatives instead of Flash video derivs
|Determine default bitrate, size, etc for new derivatives; review and update all affected areas (including regen-derivatives CLI task, digital object code to support CSV imports via web interface and command-line, etc).
|$2,700
|-
|colspan="3" style="background-color:#AEFEE5;" align="center"|'''Develop task to replace existing Flash video derivatives with mp4 files'''
|- style="background-color:#cccccc;" align="center"
|'''Subtask'''
|'''Notes'''
|'''Estimate'''
|- style="background-color:#ffffff;"
|Add new option to the regen-derivatives command-line task to allow regenerating only video file derivatives to mp4 files
|Ensure users have an easy way to update existing derivatives without having to regenerate all derivatives, which could lose custom user derivative uploads
|$1,200
|-
|colspan="3" style="background-color:#F8FAC7;" align="center"|'''TOTAL DEVELOPMENT FEES: $8,400'''
|}

 

===Costs not included in this table===

There are a few administrative costs not included in the table above, which Artefactual would include in any formal quote prepared based on the estimates above. These include:

{| border="1" style="border-collapse:collapse;" align="center"
|colspan="3" style="background-color:#BDF3FB;" align="center"|'''Additional deployment, testing, and administrative costs'''
|- style="background-color:#cccccc;"
|'''Subtask'''
|'''Notes'''
|'''Estimate'''
|- style="background-color:#ffffff;"
|Community support fee
|A 10% fee we add to development projects that are included in public releases, to help offset the costs of Artefactual maintaining the feature through subsequent releases, writing documentation, managing bug fixes, and offering basic community support via the AtoM [https://groups.google.com/forum/#!forum/ica-atom-users user forum].
|$840
|-
|Test site deployment
|Deployment of an instance of AtoM populated with test data, to be used throughout the development project for previewing the feature, and managing testing and feedback
|$600
|-
|Q/A Testing
|Quality assurance testing and analysis throughout the project to ensure the feature meets the deliverable requirements, identify and resolve any bugs, offer implementation improvement recommendations within the project scope, etc.
|$900
|-
|Backporting, deployment, and maintenance
|Backport the new functionality to a stable branch and either deploy it or make the code available to sponsor for local installation, and assist in running the derivatives regeneration task for current flash-based video derivatives
|$1200
|-
|colspan="3" style="background-color:#F8FAC7;" align="center"|'''Total additional administrative project costs: $3,540 '''
|-
|colspan="3" style="background-color:#AEFEE5;" align="center"|'''TOTAL ALL COSTS: $11,940'''
|}

==Collaborative sponsorship opportunities==

Given that the costs of sponsoring this development may be out of reach for some institutions who nevertheless would really like to see this updated functionality added to AtoM, we would like to encourage our community of users to consider ways in which the feature might be sponsored collaboratively.

Coordinating with many institutions with different schedules and availability, as well differing perspectives and feedback, can potentially add complications to a development project. In light of this, for Artefactual to be able to work effectively with multiple dispersed sponsors, we have outlined our requirements for managing such a project below.

===Artefactual requirements for collaborative development===

'''1) Single point of contact''': We require one institution who is willing to act as the project lead, and the main point of contact throughout the project. This simplifies the communication between our team and the sponsors - the project lead institution would act as the go-between with other sponsoring institutions to coordinate scheduling, testing, and administrative communication throughout the project.

'''2) Single point of feedback''': Working with multiple institutions on a collaboratively funded feature can be challenging if we are receiving contradictory input during the testing and feedback phase of the project. Instead, we would ask that the project lead manage internal discussions among the sponsors during the testing phase, and again act as the single point of contact for feedback, so that any contradictions around design, ideal behavior, and change requests can be resolved prior to communicating with our development team.

'''3) Ideally, a single point of payment administration''': Preferably, the project lead can process contributions from any other participating sponsors, so that Artefactual can supply and process a single invoice at the close of the project. We understand that this may not be possible for all institutions, and can explore alternatives with participating institutions if needed.

===Additional deployment costs for co-sponsors===

As with any major feature development carried out by Artefactual, the work will be included in the next major public release for the entire AtoM community to use, and will be immediately available in the 2.5 development branch in our public GiHub [https://github.com/artefactual/atom/ code repository]. However, if the feature were sponsored collaboratively and all participating institutions wanted access to the enhancement prior to the next public release, there may be additional deployment costs for the participating co-sponsors, so Artefactual can assist in making the work available in a stable branch and deploying it for immediate use.

The prices included in the section above entitled "[[Development/MediaPlayers#Costs_not_included_in_this_table|Costs not included in this table]]" assume deployment of the completed feature to a single institution. If co-sponsors wanted to access the feature prior to the next major public release and would like Artefactual's assistance in doing so, there will be additional costs, which we would handle on a time and materials basis for each institution. For institutions hosted by Artefactual, it would be possible to use support tickets to cover deployment costs.

Please feel free to [mailto:info@artefactual.com contact us] if you have any questions.

-----

* [[Development|Back to Development]]
* [[Main Page|AtoM wiki home]]

[[Category:Development documentation]]

Development/MediaPlayers

2018-11-27T18:38:27Z

Djjuhasz: /* Final recommendation */ Add reason for selecting H.264/MPEG-4

{{#pagetitle:Media players}}
[[Development]] > MediaPlayers

This page will provide an overview of the digital object media player(s) supported in AtoM, which are used to allow users to play access derivative copies of streaming media such as video and audio files in the browser. It was first created on 2018-11-23, and is current as of the AtoM 2.4 and 2.5 releases.

__TOC__

==Early implementation==

The current media library, [https://flowplayer.com/ Flowplayer], was implemented in the [[Releases/Release_announcements/Release_1.0.8-beta|1.0.8-beta release]]. At the time, Flowplayer was a flash-based video player (version 3.1 of Flowplayer was released in [https://sourceforge.net/p/flowplayer/news/2009/04/flowplayer-31-is-out-now/ April 2009]), and version 3.1.5 was added to AtoM in August of 2009, and included in the 1.0.8 release. See development ticket [https://projects.artefactual.com/issues/2187 #2187] in the AtoM issues list for further details.

==Current status==

Since the initial implementation of Flowplayer in AtoM, no major upgrades or changes have been made to AtoM's time-based media playback functionality. Meanwhile, increasing discoveries of security vulnerabilities and zero-day exploits in Flash have led an increasing amount of browsers and platforms to disavow Flash support, starting as early as 2010, when Steve Jobs stated that Apple would not allow Flash on the iPhone, iPod touch and iPad – citing abysmal security as one reason ([https://www.apple.com/hotnews/thoughts-on-flash/ source]). Since then, with increasing security problems being discovered in Flash and the arrival of HTML5 (which supports native video playback), most major browsers have chosen to disable Flash by default.

Flowplayer itself has redesigned its media player and while they do still maintain a [http://flash.flowplayer.org/ Flash implementation], future development efforts have been focused on an HTML5 version of the player. Support for version 3.1.5, which AtoM still uses, has been discontinued for some time. The Flowplayer Flash version has not been actively developed [https://github.com/flowplayer/flash since 2014], and the last major release was [https://github.com/flowplayer/flash/releases version 3.2.18]. At this point, it is likely that support for Flash will be fully discontinued by 2020.

AtoM is in need of an updated open source media player.

==Replacement requirements==

Any new video player replacement for AtoM should:

* Be open source
* Be HTML5-based
* Be able to play audio as well
* Ideally, include a Flash fallback for legacy browser users
* Support a broad range of playback formats
* Be under active development
* Include basic responsive support for different devices and screen sizes
* Support accessibility, including:
** ARIA support for screenreaders
** Keyboard control support
** Subtitle support

==Evaluating options==

In August of 2018, Artefactual explored the current open source HTML5 video player landscape in search of a replacement candidate that met our requirements. We found the following page extremely useful in evaluating the best contenders:

* http://videosws.praegnanz.de/

After exploring the options listed in the site above, as well as any other popular options that met our criteria we could find, we found the following 3 players to be the closest match to our requirements:

'''Able Player'''

* [https://github.com/paypal/accessible-html5-video-player Webpage]
* [https://github.com/ableplayer/ableplayer GitHub code repository]
* [https://ableplayer.github.io/ableplayer/demos/index.html Examples]

'''MediaElement.js'''

* [https://www.mediaelementjs.com/ Webpage]
* [https://github.com/mediaelement/mediaelement/ GitHub code repository] (examples included on homepage)

'''Accessible HTML5 Video Player'''

* [http://paypal.github.io/accessible-html5-video-player/ Webpage] (basically just a big example video player)
* [https://github.com/paypal/accessible-html5-video-player GitHub code repository]

==Final recommendation==

Of the above options, the Artefactual team felt that [https://www.mediaelementjs.com/ MediaElement.js] would be the best fit as a replacement video player for AtoM.

First developed by John Dyer at the Dallas Theological Seminary and released under MIT license, MediaElement.js is a widely-used project under active development, built responsively with a unified API that can fall back gracefully to Flash, which includes ARIA screen-reader support, subtitles, chapters and playlists, keyboard control, and more. The look and feel is skinnable, it requires no additional Javascript library support, and can also support playback of videos hosted on YouTube, Vimeo, and DailyMotion. It also has a [https://github.com/mediaelement/mediaelement-plugins plugin] ecosystem that can further extend functionality, such as adding basic Google Analytics support, preview on hover, and extended playback controls.

Artefactual has prepared initial development estimates for our community based on implementing MediaElement as the replacement for the current Flowplayer.

We selected the H.264/MPEG-4 video format for in-browser video playback due to it's broad support across desktop and mobile browsers. AtoM currently uses the MP3 audio format for in-browser audio playback, which will remain unchanged.

==Development tasks and estimates==

Below you will find a summary of development task and associated cost estimates, prepared by the [http://artefactual.com/ Artefactual] developers based on the decision to use MediaElement as the replacement library.

'''Current as of: 2018-11-23'''

{| border="1" style="border-collapse:collapse;" align="center"
|colspan="3" style="background-color:#BDF3FB;" align="center"|'''Integrate MediaElement Player in AtoM'''
|- style="background-color:#cccccc;"
|'''Subtask'''
|'''Notes'''
|'''Estimate'''
|- style="background-color:#ffffff;"
|Remove Flowplayer
|Work required to extract the current library
|$300
|-
|Add MediaElement player files to AtoM
|Install player to vendor folder and update Copyright file; general configuration
|$300
|-
|Incorporate MediaElement player into AtoM pages for viewing
|Modify the digital object module's showAudio and showVideo components; create the JS file to load the player; CSS changes; testing
|$3,600
|-
|Remove Flashplayer check from AtoM
|Remove current code that checks the user's browser to see if Flash is present
|$300
|-
|colspan="3" style="background-color:#FEC355;" align="center"|'''Generate mp4 reference derivatives instead of flash video (flv) files'''
|- style="background-color:#cccccc;" align="center"
|'''Subtask'''
|'''Notes'''
|'''Estimate'''
|- style="background-color:#ffffff;"
|Update digital object code to create MPEG4 / H.264 reference derivatives instea of Flash video derivs
|Determine default bitrate, size, etc for new derivatives; review and update all affected areas (including regen-derivatives CLI task, digital object code to support CSV imports via web interface and command-line, etc).
|$2,700
|-
|colspan="3" style="background-color:#AEFEE5;" align="center"|'''Develop task to replace existing Flash video derivatives with mp4 files'''
|- style="background-color:#cccccc;" align="center"
|'''Subtask'''
|'''Notes'''
|'''Estimate'''
|- style="background-color:#ffffff;"
|Add new option to the regen-derivatives command-line task to allow regenerating only video file derivatives to mp4 files
|Ensure users have an easy way to update existing derivatives without having to regenerate all derivatives, which could lose custom user derivative uploads
|$1,200
|-
|colspan="3" style="background-color:#F8FAC7;" align="center"|'''TOTAL DEVELOPMENT FEES: $8,400'''
|}

 

===Costs not included in this table===

There are a few administrative costs not included in the table above, which Artefactual would include in any formal quote prepared based on the estimates above. These include:

{| border="1" style="border-collapse:collapse;" align="center"
|colspan="3" style="background-color:#BDF3FB;" align="center"|'''Additional deployment, testing, and administrative costs'''
|- style="background-color:#cccccc;"
|'''Subtask'''
|'''Notes'''
|'''Estimate'''
|- style="background-color:#ffffff;"
|Community support fee
|A 10% fee we add to development projects that are included in public releases, to help offset the costs of Artefactual maintaining the feature through subsequent releases, writing documentation, managing bug fixes, and offering basic community support via the AtoM [https://groups.google.com/forum/#!forum/ica-atom-users user forum].
|$840
|-
|Test site deployment
|Deployment of an instance of AtoM populated with test data, to be used throughout the development project for previewing the feature, and managing testing and feedback
|$600
|-
|Q/A Testing
|Quality assurance testing and analysis throughout the project to ensure the feature meets the deliverable requirements, identify and resolve any bugs, offer implementation improvement recommendations within the project scope, etc.
|$900
|-
|Backporting, deployment, and maintenance
|Backport the new functionality to a stable branch and either deploy it or make the code available to sponsor for local installation, and assist in running the derivatives regeneration task for current flash-based video derivatives
|$1200
|-
|colspan="3" style="background-color:#F8FAC7;" align="center"|'''Total additional administrative project costs: $3,540 '''
|-
|colspan="3" style="background-color:#AEFEE5;" align="center"|'''TOTAL ALL COSTS: $11,940'''
|}

==Collaborative sponsorship opportunities==

Given that the costs of sponsoring this development may be out of reach for some institutions who nevertheless would really like to see this updated functionality added to AtoM, we would like to encourage our community of users to consider ways in which the feature might be sponsored collaboratively.

Coordinating with many institutions with different schedules and availability, as well differing perspectives and feedback, can potentially add complications to a development project. In light of this, for Artefactual to be able to work effectively with multiple dispersed sponsors, we have outlined our requirements for managing such a project below.

===Artefactual requirements for collaborative development===

'''1) Single point of contact''': We require one institution who is willing to act as the project lead, and the main point of contact throughout the project. This simplifies the communication between our team and the sponsors - the project lead institution would act as the go-between with other sponsoring institutions to coordinate scheduling, testing, and administrative communication throughout the project.

'''2) Single point of feedback''': Working with multiple institutions on a collaboratively funded feature can be challenging if we are receiving contradictory input during the testing and feedback phase of the project. Instead, we would ask that the project lead manage internal discussions among the sponsors during the testing phase, and again act as the single point of contact for feedback, so that any contradictions around design, ideal behavior, and change requests can be resolved prior to communicating with our development team.

'''3) Ideally, a single point of payment administration''': Preferably, the project lead can process contributions from any other participating sponsors, so that Artefactual can supply and process a single invoice at the close of the project. We understand that this may not be possible for all institutions, and can explore alternatives with participating institutions if needed.

===Additional deployment costs for co-sponsors===

As with any major feature development carried out by Artefactual, the work will be included in the next major public release for the entire AtoM community to use, and will be immediately available in the 2.5 development branch in our public GiHub [https://github.com/artefactual/atom/ code repository]. However, if the feature were sponsored collaboratively and all participating institutions wanted access to the enhancement prior to the next public release, there may be additional deployment costs for the participating co-sponsors, so Artefactual can assist in making the work available in a stable branch and deploying it for immediate use.

The prices included in the section above entitled "[[Development/MediaPlayers#Costs_not_included_in_this_table|Costs not included in this table]]" assume deployment of the completed feature to a single institution. If co-sponsors wanted to access the feature prior to the next major public release and would like Artefactual's assistance in doing so, there will be additional costs, which we would handle on a time and materials basis for each institution. For institutions hosted by Artefactual, it would be possible to use support tickets to cover deployment costs.

Please feel free to [mailto:info@artefactual.com contact us] if you have any questions.

-----

* [[Development|Back to Development]]
* [[Main Page|AtoM wiki home]]

[[Category:Development documentation]]

Development/MediaPlayers

2018-11-27T00:31:40Z

Djjuhasz: Audio playback is also via Flowplayer

Development/MediaPlayers

2018-11-27T00:29:45Z

Djjuhasz: Link issue #2187; Update first sentence of "Current status" section; Remove mediaplayer API as a requirement

Community/Users

2016-11-03T16:57:19Z

Djjuhasz: Fix link to MAIN: https://main.lib.umanitoba.ca

User:Cynthia

2016-09-21T00:14:42Z

Djjuhasz: Creating user page for new user.

Experienced Project Manager in Information Technology
Experienced professional in Library sector
Experienced professional in managing mass digitisation projects

Development/Philosophy

2016-08-25T01:00:13Z

Djjuhasz: /* Background */ More initial sponsors

{{#pagetitle:Development philosophy}}
[[Main Page]] > [[Development]] > '''Development/Philosophy'''

The following page outlines some of the early history and goals of the AtoM project, and defines our approach to community-driven development, as well as Artefactual's bounty model approach as a company maintaining an open-source project with a clear mandate.

__TOC__

===Background===

The AtoM project was first made possible with support from the International Council on Archives ([http://www.ica.org/ ICA]), [http://en.unesco.org/ UNESCO], [http://www.hva.nl/archiefschool The Hogeschool Van Amsterdam Archiefschool], Direction des Archives de France, the [http://www.worldbank.org/en/about/archives World Bank Group Archives], and the [http://www.na.ae/en/aboutus/aboutna.aspx United Arab Emirates Centre for Documentation and Research]. The [[Releases/Release_announcements/Release_1.0-beta|1.0-beta release]] was freely distributed for testing and feedback in the form of a demo CD distributed to delegates at the ICA congress in Kuala Lumpur, July 21st to 27th, 2008. As Peter Van Garderen outlines in his 2009 paper, "The ICA-AtoM Project and Technology" [1], the original goals of the project were defined in a 2008 Steering Committee meeting as follows:

''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''

<admonition type="seealso">
See the [[Resources/Presentations|Papers and presentations]] section of this wiki to explore some of the early papers explaining the history of the project.
</admonition>

===The current situation===

While the vision of an ICA-organized, publicly accessible Steering Committee to manage the growth and development of the ICA-AtoM project did not materialize in the way originally envisioned, [https://www.artefactual.com/ Artefactual Systems], the original and current lead developers of the application, have remained dedicated to the original aims of the project: the development of a freely available, multilingual, multi-repository archival management system that allows traditionally under-funded institutions access to tools supporting description and access based on national and international standards and best practices. AtoM has continued to grow and develop since the 1.0-beta release in 2008, and October 2013 saw the release of a re-branded and redesigned [[Releases/Release_announcements/Release_2.0.0|2.0.0 version]] of the application, now simply known as AtoM.

[[File:atom-history.png|center|700px|thumb| An overview of the AtoM project's early development]]

Due to the particular nature of the AtoM project's development history and our hopes (along with those of the AtoM community as it has grown over the last 8 years) to see the project continue and its original aims maintained, Artefactual as a company is currently in a somewhat unique position of being a private company maintaining an open-source project that was originally intended to have an international governance body. The continued growth and vibrancy of the AtoM project and its community suggest that these efforts have been worthwhile and successful - this has largely been due to Artefactual taking a '''community-driven development''' approach to improving the application, and what is sometimes called a '''bounty model''' of open-source business structuring as a company. Each concept and its relation to the AtoM project will be explained further below.

===The Bounty model===

To support the original and ongoing aims of the project, AtoM has always been, and will continue to be, released as open source software - currently, we release it under a strong viral license ([http://choosealicense.com/licenses/agpl-3.0/ AGPLv3]) to ensure that the application is not forked or incorporated by someone wishing to charge access to its enhancements. In maintaining our commitment to the original project aims, we also seek in every way we can to lower or remove barriers to the project resources: to this end, Artefactual not only releases the code via our [https://www.accesstomemory.org/download/ Downloads] page and our [https://github.com/artefactual/atom/ code repository], we also make our [https://www.accesstomemory.org/docs/latest/ documentation] available, our [https://www.youtube.com/user/ArtefactualSystems webinar recordings], our [[Main Page|wiki]] resources, our [http://www.slideshare.net/accesstomemory presentation slides], and even as much free support as we can offer via the AtoM [https://groups.google.com/forum/#!forum/ica-atom-users user forum], all free of charge. With every major release, we also budget time to review and address many of the bugs reported to us by our user community, with the hope of seeing the project improve progressively in both large and small ways with each public release.

<admonition type="seealso">
* [[Resources]]
* [[Community/Community_resources|Community resources]]
* [[Development#Development_resources|Development resources]]
</admonition>

To sustain ourselves as a business and be able to continue maintaining and developing AtoM, Artefactual also offer additional [https://www.artefactual.com/services/ paid services] - including application hosting, consultation, training, theming, data migrations, and of course, custom development. This business model is sometimes known as the '''Bounty model''' of open-source development. As a company, we use our resources from these additional services to continue supporting the ongoing maintenance work required to keep the AtoM project sustainable and growing.

===Community-driven development===

Every time we are contracted to develop a custom feature for an institution, we work with the client to ensure the feature respects established national and international standards, and we try to generalize its implementation so it can not only meet the use case of the institution in question, but also be of benefit to the entire AtoM user community. We then include all of these enhancements in the next public release. Whenever possible, we also accept bug fixes and code contributions from our user community, and will handle the review and merging of this code into public releases, as well as its maintenance through subsequent releases, thereby reducing the burden on individual contributors over time. We have a number of [[Development#Development_resources|development resources]] on our wiki to help users get started.

This is the '''community-driven development''' heart of the AtoM project. The growth and direction of AtoM is determined by the individuals and institutions who recognize that open-source software requires maintenance to continue to be viable and relevant in the long-term, and sponsor features, enhancements, and bug fixes that will benefit the project as a whole in addition to meeting their particular institutional or individual needs. This means that AtoM, as an application, is truly what our community makes of it - the current version, like all versions before it, has been made possible thanks to contributions large and small from dozens of institutions and individuals. You can see this on the [[Releases/Release_announcements|release announcements]] we maintain and on the [[Releases/Roadmap|Roadmap]] part of our wiki for the upcoming releases - there we try to acknowledge all the different institutions and individuals that have helped to make the new features possible. This is one of the joys of community-driven development - seeing what we can accomplish as a community when we are all working towards common goals. It also means that institutions with more resources are able to invest in solutions that not only meet their needs, but also benefit the community at large and assist smaller, under-resourced institutions to have access to the same tools and applications. Everyone benefits from any single contribution - whether it is development or contributions to the project in other ways (documentation, user forum participation, papers and presentations, other service providers, user groups, and more). Whenever possible, we try to provide further avenues for connection and dissemination of resources via the user forum and places like the [[Community/Community_resources|Community resources]] section of the wiki.

===Challenges and opportunities===

In contrast however, one of the challenges of this approach is that as a small company, we at Artefactual simply don't have the resources to undertake much of the development and maintenance we would like to see happen without community support. We are already in the process of giving away the majority of our core business products via [https://www.accesstomemory.org/ AtoM] and [https://www.archivematica.org/ Archivematica]; the funds we receive from custom development are released back into subsequent releases via code maintenance, documentation, webinars, conference presentations and workshops, bug fixes, user forum support, release testing and packaging and more - anything left over is used to keep the lights on and our team of archivists, developers, and system administrators doing the work we are passionate about. In Canada where Artefactual is based, there are very few large grants or philanthropic organizations; as a private company we are often ineligible for large grants which other non-profit or institution-based open source cultural heritage applications can access, and need to work with our community partners to coordinate applying for these opportunities.

Community-driven development sometimes means we can't have a long-view of the development roadmap, several releases in advance of the current version. We manage this via '''iterative development''': most of the features in AtoM have been developed collaboratively over subsequent releases, where one institution will sponsor the base implementation, and then we look to future sponsored development to help us refine, improve, and build upon that first implementation. When one institution makes a commitment to the development of a new module, it then lowers the barrier for future institutions with smaller available resource pools to refine and enhance the feature further in the future - but both institutions, and the community at large, benefit from this approach. However, this feature-based approach to development can sometimes mean that core maintenance tasks, such as updating and modernizing AtoM's libraries, frameworks, and dependencies can sometimes be overlooked in favor of new functionality. We are constantly looking for ways to include maintenance work in any development project, and to assist in connecting institutions and individuals with each other so resources can be pooled and the maintenance work required to keep the AtoM project viable in the long-term can be addressed.

===Community growth and looking ahead===

Open-source software has often in the past been described as in terms of "free as in beer" (i.e. price) and "free as in speech" (i.e. creative control) [http://www.howtogeek.com/howto/31717/what-do-the-phrases-free-speech-vs.-free-beer-really-mean/ comparisons]. Sometimes the phrase "free as in puppy" is added to provide the important reminder that all software faces obsolescence risks and requires support and maintenance over time (though we prefer "free as in kitten"). Our community-driven development model means that '''AtoM is only as good as we as a community make it''' - and Artefactual's bounty model of business, aimed to keep as many project resources freely available as possible, means that we are unable to take on many of the development and maintenance activities we would like to see without sponsorship and support from the broader community. Artefactual remains committed to seeking solutions that will allow us to continue maintaining the AtoM project in the short and medium term; in the long-term as we explore the possibilities of future AtoM versions, we remain open and interested in alternative governance models that would see us as a company step back into the role of a third-party service provider. In the meantime, we rely on a spirit of openness, collaboration, and generosity within the AtoM community so that resources can be pooled, goals are collectively established, the application can remain true to its original founding vision and principles.

[[File:atom-sticker.jpg|center|500px|thumb|AtoM: because free kittens should come with free beer]]

To that end we encourage active involvement in the AtoM project in whatever form you find accessible. If you are an institution with resources, know that any feature development or maintenance work you sponsor will benefit all other AtoM users large and small in a subsequent public release. If you have developers working to make customizations in-house, we encourage you to get in touch with Artefactual early in the process, review our [[Development#Development_resources|development resources]], and consider budgeting project time for Artefactual to code review and merge your work into a public release - this ultimately removes the maintenance burden from your institution going forward as AtoM continues to develop, and allows other institutions to use and potentially improve upon your work in the future. If you have limited resources, start discussions in our [https://groups.google.com/forum/#!forum/ica-atom-users User forum] or via [https://twitter.com/accesstomemory Twitter] to identify potential collaborators so you can pool resources and ideas. And of course, there are many ways you can help contribute to the project and the community without money or technical expertise. If you're confident working with AtoM, consider organizing a User Group, meetup, skill-share, workshop, or hack-fest in your area - we'll gladly help you spread the word! If you've developed internal documentation or other AtoM related resources, let us know and we can add it to the [[Community/Community_resources|Community resources]] section of the wiki. If you're attending a conference or other related cultural heritage event, consider preparing a paper or presentation on your use of AtoM, and share those resources with the community. Join us in the [https://groups.google.com/forum/#!forum/ica-atom-users User Forum] - all questions help build the knowledge base of the community, and if over time you are able to assist in answering other user questions, even better! Contribute to our documentation - we've got some resources to get you started [[Resources/Documentation|here]] - or if you have ideas or see mistakes but don't have the time or resources to address them yourself, let us know... everything helps! This is but a small list of examples of all the ways in which you can help to make the AtoM community a rich and vibrant one. Help us think of more!

<admonition type="seealso">
* Learn [[Resources/Documentation/About|about our documentation]], and [[Resources/Documentation/Contribute|how to contribute to it]]
* Learn how to [[Resources/Translation|contribute translations]] to the AtoM project
* Read about our [[Resources/User_forum|user forum]], including our code of conduct, support policy, and more
* Check out the [[Development#Development_resources|development resources]] we have and consider contributing code
* See the list of other community [[Community/Contributors|code contributors]]
* Read about the AtoM issue tracker, and the AtoM wish list
* Explore the [[Community/Community_resources|Community resources]] section of the wiki
* Read about some of our [[Community/Success_stories|community success stories]] and consider sharing one of your own!
* See a list of other [[Community/Users|AtoM users]] and consider adding your own institution!
</admonition>

AtoM has come a long way since its beta public release in 2008 - and its growth and progress would not have been possible without the support of dozens of institutions, individuals, and organizations along the way. Artefactual remains committed to keeping the AtoM project true to its original vision, which remains as relevant today as it was in 2008. It is via our adoption of a community-driven development model and a bounty business model that we have been able to keep the project stable and growing thus far - and ultimately, it is through engagement, collaboration, and generous exchange among all users in the AtoM community that we can continue to see the AtoM project grow and thrive into the future. Thank you for helping us turn AtoM into the vibrant project it now is, and we look forward to defining its next steps with you.

-----

[1] Van Garderen, Peter. "The ICA-AtoM Project and Technology." Presentation delivered at the Association of Brazilian Archivists' Third Meeting on Archival Information Databases, March 16-17 2009, Rio de Janiero, Brazil. ([[File:VanGarderen-ICA-AtoM-2009.pdf|PDF, 1MB ]])

-----

* [[Development|Back to Development]]
* [[Main Page|AtoM wiki home]]

[[Category:Development documentation]]

Development/Philosophy

2016-08-24T00:27:41Z

Djjuhasz: /* Background */ add additional sponsors of AtoM 1.0

{{#pagetitle:Development philosophy}}
[[Main Page]] > [[Development]] > '''Development/Philosophy'''

The following page outlines some of the early history and goals of the AtoM project, and defines our approach to community-driven development, as well as Artefactual's bounty model approach as a company maintaining an open-source project with a clear mandate.

__TOC__

===Background===

The AtoM project was first made possible with support from the International Council on Archives ([http://www.ica.org/ ICA]), [http://en.unesco.org/ UNESCO], [http://www.hva.nl/archiefschool The Hogeschool Van Amsterdam Archiefschool], and Direction des Archives de France. The [[Releases/Release_announcements/Release_1.0-beta|1.0-beta release]] was freely distributed for testing and feedback in the form of a demo CD distributed to delegates at the ICA congress in Kuala Lumpur, July 21st to 27th, 2008. As Peter Van Garderen outlines in his 2009 paper, "The ICA-AtoM Project and Technology" [1], the original goals of the project were defined in a 2008 Steering Committee meeting as follows:

''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''

<admonition type="seealso">
See the [[Resources/Presentations|Papers and presentations]] section of this wiki to explore some of the early papers explaining the history of the project.
</admonition>

===The current situation===

While the vision of an ICA-organized, publicly accessible Steering Committee to manage the growth and development of the ICA-AtoM project did not materialize in the way originally envisioned, [https://www.artefactual.com/ Artefactual Systems], the original and current lead developers of the application, have remained dedicated to the original aims of the project: the development of a freely available, multilingual, multi-repository archival management system that allows traditionally under-funded institutions access to tools supporting description and access based on national and international standards and best practices. AtoM has continued to grow and develop since the 1.0-beta release in 2008, and October 2013 saw the release of a re-branded and redesigned [[Releases/Release_announcements/Release_2.0.0|2.0.0 version]] of the application, now simply known as AtoM.

[[File:atom-history.png|center|700px|thumb| An overview of the AtoM project's early development]]

Due to the particular nature of the AtoM project's development history and our hopes (along with those of the AtoM community as it has grown over the last 8 years) to see the project continue and its original aims maintained, Artefactual as a company is currently in a somewhat unique position of being a private company maintaining an open-source project that was originally intended to have an international governance body. The continued growth and vibrancy of the AtoM project and its community suggest that these efforts have been worthwhile and successful - this has largely been due to Artefactual taking a '''community-driven development''' approach to improving the application, and what is sometimes called a '''bounty model''' of open-source business structuring as a company. Each concept and its relation to the AtoM project will be explained further below.

===The Bounty model===

To support the original and ongoing aims of the project, AtoM has always been, and will continue to be, released as open source software - currently, we release it under a strong viral license ([http://choosealicense.com/licenses/agpl-3.0/ AGPLv3]) to ensure that the application is not forked or incorporated by someone wishing to charge access to its enhancements. In maintaining our commitment to the original project aims, we also seek in every way we can to lower or remove barriers to the project resources: to this end, Artefactual not only releases the code via our [https://www.accesstomemory.org/download/ Downloads] page and our [https://github.com/artefactual/atom/ code repository], we also make our [https://www.accesstomemory.org/docs/latest/ documentation] available, our [https://www.youtube.com/user/ArtefactualSystems webinar recordings], our [[Main Page|wiki]] resources, our [http://www.slideshare.net/accesstomemory presentation slides], and even as much free support as we can offer via the AtoM [https://groups.google.com/forum/#!forum/ica-atom-users user forum], all free of charge. With every major release, we also budget time to review and address many of the bugs reported to us by our user community, with the hope of seeing the project improve progressively in both large and small ways with each public release.

<admonition type="seealso">
* [[Resources]]
* [[Community/Community_resources|Community resources]]
* [[Development#Development_resources|Development resources]]
</admonition>

To sustain ourselves as a business and be able to continue maintaining and developing AtoM, Artefactual also offer additional [https://www.artefactual.com/services/ paid services] - including application hosting, consultation, training, theming, data migrations, and of course, custom development. This business model is sometimes known as the '''Bounty model''' of open-source development. As a company, we use our resources from these additional services to continue supporting the ongoing maintenance work required to keep the AtoM project sustainable and growing.

===Community-driven development===

Every time we are contracted to develop a custom feature for an institution, we work with the client to ensure the feature respects established national and international standards, and we try to generalize its implementation so it can not only meet the use case of the institution in question, but also be of benefit to the entire AtoM user community. We then include all of these enhancements in the next public release. Whenever possible, we also accept bug fixes and code contributions from our user community, and will handle the review and merging of this code into public releases, as well as its maintenance through subsequent releases, thereby reducing the burden on individual contributors over time. We have a number of [[Development#Development_resources|development resources]] on our wiki to help users get started.

This is the '''community-driven development''' heart of the AtoM project. The growth and direction of AtoM is determined by the individuals and institutions who recognize that open-source software requires maintenance to continue to be viable and relevant in the long-term, and sponsor features, enhancements, and bug fixes that will benefit the project as a whole in addition to meeting their particular institutional or individual needs. This means that AtoM, as an application, is truly what our community makes of it - the current version, like all versions before it, has been made possible thanks to contributions large and small from dozens of institutions and individuals. You can see this on the [[Releases/Release_announcements|release announcements]] we maintain and on the [[Releases/Roadmap|Roadmap]] part of our wiki for the upcoming releases - there we try to acknowledge all the different institutions and individuals that have helped to make the new features possible. This is one of the joys of community-driven development - seeing what we can accomplish as a community when we are all working towards common goals. It also means that institutions with more resources are able to invest in solutions that not only meet their needs, but also benefit the community at large and assist smaller, under-resourced institutions to have access to the same tools and applications. Everyone benefits from any single contribution - whether it is development or contributions to the project in other ways (documentation, user forum participation, papers and presentations, other service providers, user groups, and more). Whenever possible, we try to provide further avenues for connection and dissemination of resources via the user forum and places like the [[Community/Community_resources|Community resources]] section of the wiki.

===Challenges and opportunities===

In contrast however, one of the challenges of this approach is that as a small company, we at Artefactual simply don't have the resources to undertake much of the development and maintenance we would like to see happen without community support. We are already in the process of giving away the majority of our core business products via [https://www.accesstomemory.org/ AtoM] and [https://www.archivematica.org/ Archivematica]; the funds we receive from custom development are released back into subsequent releases via code maintenance, documentation, webinars, conference presentations and workshops, bug fixes, user forum support, release testing and packaging and more - anything left over is used to keep the lights on and our team of archivists, developers, and system administrators doing the work we are passionate about. In Canada where Artefactual is based, there are very few large grants or philanthropic organizations; as a private company we are often ineligible for large grants which other non-profit or institution-based open source cultural heritage applications can access, and need to work with our community partners to coordinate applying for these opportunities.

Community-driven development sometimes means we can't have a long-view of the development roadmap, several releases in advance of the current version. We manage this via '''iterative development''': most of the features in AtoM have been developed collaboratively over subsequent releases, where one institution will sponsor the base implementation, and then we look to future sponsored development to help us refine, improve, and build upon that first implementation. When one institution makes a commitment to the development of a new module, it then lowers the barrier for future institutions with smaller available resource pools to refine and enhance the feature further in the future - but both institutions, and the community at large, benefit from this approach. However, this feature-based approach to development can sometimes mean that core maintenance tasks, such as updating and modernizing AtoM's libraries, frameworks, and dependencies can sometimes be overlooked in favor of new functionality. We are constantly looking for ways to include maintenance work in any development project, and to assist in connecting institutions and individuals with each other so resources can be pooled and the maintenance work required to keep the AtoM project viable in the long-term can be addressed.

===Community growth and looking ahead===

Open-source software has often in the past been described as in terms of "free as in beer" (i.e. price) and "free as in speech" (i.e. creative control) [http://www.howtogeek.com/howto/31717/what-do-the-phrases-free-speech-vs.-free-beer-really-mean/ comparisons]. Sometimes the phrase "free as in puppy" is added to provide the important reminder that all software faces obsolescence risks and requires support and maintenance over time (though we prefer "free as in kitten"). Our community-driven development model means that '''AtoM is only as good as we as a community make it''' - and Artefactual's bounty model of business, aimed to keep as many project resources freely available as possible, means that we are unable to take on many of the development and maintenance activities we would like to see without sponsorship and support from the broader community. Artefactual remains committed to seeking solutions that will allow us to continue maintaining the AtoM project in the short and medium term; in the long-term as we explore the possibilities of future AtoM versions, we remain open and interested in alternative governance models that would see us as a company step back into the role of a third-party service provider. In the meantime, we rely on a spirit of openness, collaboration, and generosity within the AtoM community so that resources can be pooled, goals are collectively established, the application can remain true to its original founding vision and principles.

[[File:atom-sticker.jpg|center|500px|thumb|AtoM: because free kittens should come with free beer]]

To that end we encourage active involvement in the AtoM project in whatever form you find accessible. If you are an institution with resources, know that any feature development or maintenance work you sponsor will benefit all other AtoM users large and small in a subsequent public release. If you have developers working to make customizations in-house, we encourage you to get in touch with Artefactual early in the process, review our [[Development#Development_resources|development resources]], and consider budgeting project time for Artefactual to code review and merge your work into a public release - this ultimately removes the maintenance burden from your institution going forward as AtoM continues to develop, and allows other institutions to use and potentially improve upon your work in the future. If you have limited resources, start discussions in our [https://groups.google.com/forum/#!forum/ica-atom-users User forum] or via [https://twitter.com/accesstomemory Twitter] to identify potential collaborators so you can pool resources and ideas. And of course, there are many ways you can help contribute to the project and the community without money or technical expertise. If you're confident working with AtoM, consider organizing a User Group, meetup, skill-share, workshop, or hack-fest in your area - we'll gladly help you spread the word! If you've developed internal documentation or other AtoM related resources, let us know and we can add it to the [[Community/Community_resources|Community resources]] section of the wiki. If you're attending a conference or other related cultural heritage event, consider preparing a paper or presentation on your use of AtoM, and share those resources with the community. Join us in the [https://groups.google.com/forum/#!forum/ica-atom-users User Forum] - all questions help build the knowledge base of the community, and if over time you are able to assist in answering other user questions, even better! Contribute to our documentation - we've got some resources to get you started [[Resources/Documentation|here]] - or if you have ideas or see mistakes but don't have the time or resources to address them yourself, let us know... everything helps! This is but a small list of examples of all the ways in which you can help to make the AtoM community a rich and vibrant one. Help us think of more!

<admonition type="seealso">
* Learn [[Resources/Documentation/About|about our documentation]], and [[Resources/Documentation/Contribute|how to contribute to it]]
* Learn how to [[Resources/Translation|contribute translations]] to the AtoM project
* Read about our [[Resources/User_forum|user forum]], including our code of conduct, support policy, and more
* Check out the [[Development#Development_resources|development resources]] we have and consider contributing code
* See the list of other community [[Community/Contributors|code contributors]]
* Read about the AtoM issue tracker, and the AtoM wish list
* Explore the [[Community/Community_resources|Community resources]] section of the wiki
* Read about some of our [[Community/Success_stories|community success stories]] and consider sharing one of your own!
* See a list of other [[Community/Users|AtoM users]] and consider adding your own institution!
</admonition>

AtoM has come a long way since its beta public release in 2008 - and its growth and progress would not have been possible without the support of dozens of institutions, individuals, and organizations along the way. Artefactual remains committed to keeping the AtoM project true to its original vision, which remains as relevant today as it was in 2008. It is via our adoption of a community-driven development model and a bounty business model that we have been able to keep the project stable and growing thus far - and ultimately, it is through engagement, collaboration, and generous exchange among all users in the AtoM community that we can continue to see the AtoM project grow and thrive into the future. Thank you for helping us turn AtoM into the vibrant project it now is, and we look forward to defining its next steps with you.

-----

[1] Van Garderen, Peter. "The ICA-AtoM Project and Technology." Presentation delivered at the Association of Brazilian Archivists' Third Meeting on Archival Information Databases, March 16-17 2009, Rio de Janiero, Brazil. ([[File:VanGarderen-ICA-AtoM-2009.pdf|PDF, 1MB ]])

-----

* [[Development|Back to Development]]
* [[Main Page|AtoM wiki home]]

[[Category:Development documentation]]

User:Djjuhasz

2016-08-22T22:01:45Z

Djjuhasz: Add image

[[File:djjuhasz.jpg|600px]]

David Juhasz 
Director, AtoM Technical Services, 
Artefactual Systems Inc.

https://www.artefactual.com/portfolio-type/david-juhasz/

File:Djjuhasz.jpg

2016-08-22T22:00:18Z

Djjuhasz: David Juhasz profile picture

David Juhasz profile picture

User:Djjuhasz

2016-08-22T21:59:52Z

Djjuhasz:

[[Image:djjuhasz.jpg|500px]]

David Juhasz 
Director, AtoM Technical Services, 
Artefactual Systems Inc.

https://www.artefactual.com/portfolio-type/david-juhasz/

User:Djjuhasz

2016-08-22T21:51:57Z

Djjuhasz:

David Juhasz 
Director, AtoM Technical Services, 
Artefactual Systems Inc.

https://www.artefactual.com/portfolio-type/david-juhasz/

User:Djjuhasz

2016-08-22T21:44:15Z

Djjuhasz: Created page with "Director, AtoM Technical Services. Artefactual Systems Inc. https://www.artefactual.com/"

Director, AtoM Technical Services.

Artefactual Systems Inc.
https://www.artefactual.com/