From AtoM wiki

Main Page > Releases > Releases/Roadmap

On this page, you'll find summaries about upcoming releases, and issue tickets related to them. As the releases are finalized, elements on this page will be used to draft the formal release announcements found here.


You can also check out the issues associated with upcoming releases by looking at the Roadmap page in our issue tracker.

Release 2.4.1[edit]

Release 2.4.1 is a bug fix release, that addresses some of the issues reported in the 2.4.0 release. Thank you to our user community for reporting these issues, and helping us to sponsor some of the fixes!

Issues closed in this release include:

  • #11392: Multi-file uploader can cause uploaded digital objects to be publicly accessible
  • #11427: Error screen when logging in through /user instead of /user/login
  • #11537: Notes should be searchable via the global search box
    • Sponsored by the BC Archives
  • #11597: CSV import fails when importing from description view page link in sidebar context menu
    • Sponsored by the University of Manitoba
  • #11669: Lost functionality - Carousel "show all" link used to be parent-specific, now only shows all digital objects in archival unit
    • Sponsored by the Museum of ingenuity J. Armand Bombardier
  • #11721: DIP upload logic incompatible with METS logical structMap
  • #11723: EAD export changes LOD to "otherlevel" on export if terms are edited; affects finding aid layouts
    • Sponsored by the Simon Fraser University Archives
  • #11727: Dates of creation, revision and deletion not displaying in Inventory Finding Aids
    • Sponsored by the Simon Fraser University Archives
  • #11788: Inherited creator names will not return search results for matching lower-level records
    • Sponsored by the BC Archives
  • #11827: OAI-PMH returns cannotDisseminateFormat error when using "oai_ead" metadataPrefix
  • #11828: Authority records left side links shows Creator and Subject when only Creator is expected
    • Sponsored by the University of Strathclyde Archives
  • #11855: Search index is not updated when edits affect descendant records
    • Sponsored by the University of Strathclyde Archives
  • #11860: CSV export from search results adding duplicates
  • #11882: CSV and XML exports including extra records and/or files
    • Sponsored by the World Bank Group Archives
  • #10853: Add more fields to repository CSV import
  • #11538: Consider returning creator histories to global archival description search results


For a full list of issues related to the 2.4.1 bug fix release, see the following links to our issue tracker:

Release 2.5[edit]


In the 2.5 release, users will be able to save a clipboard in one session, and then load it again in the future - with the option to either merge with the current clipboard results, or to replace them. An administrator can also set how long saved clipboards will be preserved in the system.

Sponsored by Simon Fraser University Archives

  • #11360 - Allow users to save and retrieve clipboard results across sessions

Search and Browse[edit]

We have upgraded the Elasticsearch index to use version 5.2 .

  • #10847 - Upgrade Elasticsearch to version 5.x


Sponsored by the National Library of Sweden

  • #11761 - Update slug generation rules include a more permissive option


For a full list of issues related to the 2.5 release, see the following links to our issue tracker:


This project in our issue tracker is where new unsponsored feature requests for Access to Memory (AtoM) can be added. This allows us to log feature requests, and begin discussion about requirements and design without adding confusion to the main AtoM project's issue tracker as to which features will be included in an upcoming release.

See the AtoM Wishlist project here:


Once you've followed the link above, you can click on the "Issues" link at the top of the page to browse all issue tickets in the AtoM Wishlist. You can sort the list of issues by clicking on a column header, and use the Filter drop-down menu to the right to customize the query.

How the Wishlist works

When features are sponsored by an institution, or developed and submitted via community pull request, they will be copied to the main AtoM project in our issue tracker (here), and marked verified in the Wishlist project. Developer discussion, quality assurance testing, and other related updates will be posted to the related development ticket in the main AtoM project.

The tested version tag can be used in the Wishlist's issue description to keep track of when the feature was requested (e.g. which version of AtoM was most recent when the feature request came in)

The target version will only be applied before a Wishlist ticket is verified (closed) and copied to the main AtoM project.


  • We've got information on our main AtoM issue tracker, and how you can use it to submit a bug report here: Resources/Issue tracker.
  • Got questions? Not sure if something is a bug or not, if a wishlist feature might be of interest to the rest of the community, or if something is already on our upcoming development roadmap? Why not make a post in our AtoM User Forum?