These slides were presented by Dan Gillean, AtoM Program Manager with Artefactual Systems, to provide an update on the AtoM 2.5 release and long-term AtoM3 news to the UK regional AtoM users group meeting held in Glasgow on May 17, 2019. For more information on this group see:
https://wiki.accesstomemory.org/Community/Groups/UK
Fore more information on the AtoM 2.5 release, please see:
https://wiki.accesstomemory.org/Releases/Release_announcements/Release_2.5
Unleash Your Potential - Namagunga Girls Coding Club
AtoM Community Update: 2019-05
1. AtoM 2.5 and beyond
http://www.spitzer.caltech.edu/uploaded_files/images/0007/9905/sig10-009a_Lrg.jpg
AtoM UK Users Group – 2019-05-17
Dan Gillean - Artefactual Systems
AtoM Community Update
2. Web based: Once installed, you only need a
modern web browser and an internet
connection to connect to the application from
anywhere
Standards-based: AtoM implements existing
national and international archival content and
metadata transmission standards and best
practices, so your data is standards compliant
and interoperable
Multilingual: Supports translations of both
content and user interface elements, can be
used as a multilingual catalogue
Multi-repository: Can be used as a portal site,
content aggregator, or union catalogue to
provide access to content from multiple
institutions
What is AtoM?AtoM stands for
Access to Memory
It is a web-based, open
source application for
standards-based archival
description and access in
a multilingual, multi-
repository environment.
3. 20192013
1.x
AtoM’S DEVELOPMENT
2.22.0 2.42.3
JOB SCHEDULER
2.0.1 2.1.1
2.1
2.2.11.3.1
CLIPBOARD
AtoM 2.4
• Full bulk import / export via the user
interface
• Search index improvements
• Authority records and repositories on
the Clipboard
2.4.1
25. • How should we fund the project?
• How should we govern the project?
• How should we build the project?
Issuestoconsider:
26. AURA AtoM Upgrade/Rewrite Analysis
Artefactual’s internal task force to begin
considering possible technologies and
development patterns for a next-
generation version of AtoM in 2016.
• Highlight biggest current bottlenecks
• Research emerging technologies and
standards
• Develop proposed models for
implementation
• Consider upgrade paths
• Begin researching funding and
community support options
28. Initial design goals:
• Use well-supported, stable open-source technologies
• Modular not monolithic
• Support linked data
• Separate front and back-end
• Scale to hundreds of millions of records
• Build permissions, accessibility, and internationalization in from the start
• Full multi-repository support
• Address the challenge of federation (contributing to portals, etc)
AURA AtoM Upgrade/Rewrite Analysis
30. AtoM3Planningmeeting,August2018:
Kings’College,London
• 12 participants from 5 development
companies represented
• Additional participation from Digirati,
AIM25, and UK AtoM User Group
members via teleconference
• Hosted by King’s College in London,
UK, August 23-25, 2018
• Opportunity to discuss first steps in
setting up AtoM3 as a multi-vendor,
international effort
33. AtoM3Planningmeeting,August2018
Proposal is to start by seeking funding for Proof of
Concept research to prove the value of 3 propositions:
1. We can convert AtoM2 data to linked data
2. LD will allow archivists to enrich their data in ways
that are not possible with traditional data entry
3. LD will allow the federation of data from multiple
points, making portal sites and union catalogues
easier to create and richer in content
This would allow for us to then build a prototype in a
future project phase to test scalability and technical
architecture assumptions