From AtoM wiki
Revision as of 20:35, 4 September 2018 by Dan (talk | contribs) (Command-line tasks: Add issue #9520)

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

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:

  • #9255: Related descriptions autocomplete fails when used to link lower-level records in large hierarchies
  • #10341: DIPs uploaded to AtoM from Archivematica have mm-dd added to yyyy
  • #10059: Finding aids not deleted when archival description is
  • #11358: Translated fields not shown when editing repository contact information
  • #11398: setting --index with import:bulk doesn't work when importing single CSVs from the command-line
  • #11410: Move and More buttons are not available to Editor user groups when culture is not English
  • #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
  • #11602: Some UI elements of Contact area in Repository edit page not translatable
  • #11605 - "Add new" link for repeating fields in description edit templates cannot be translated
  • #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
  • #11728: Slug incrementation - when duplicate slugs end with a number, AtoM increments the number instead of adding a dash and a new number
    • Sponsored by the Oregon Historical Society
  • #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
  • #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
  • #11653: Deleting an Act associated with a rights statement leads to 500 error on save
  • #11829: OAI-PMH character encoding is invalid
  • #11899: Update insert statement in generate-slugs task
  • #11904: Generic icon that is displayed after metadata-only DIP upload from Archivematica should not be clickable
    • Sponsored by the Simon Fraser University Archives
  • #11960: AtoM will allow descriptions to link to themselves as related descriptions, causing 500 error when attempting to remove
  • #11975: Specify PHP version in AtoM dockerfile
    • Submitted by community user knjko
  • #11993: Correct Accession CSV import issue with PHP7
  • #12023: Archivist's note does not return any search results
  • #12043: CSV import of accessions allows blank accession identifiers
  • #12053: Physical storage data not included in EAD export if it is created in another culture
  • #12111: Fix issues in Docker environment
  • #12117: Language and script data not imported when using "match and update" flag (CSV import)
    • Sponsored by the World Bank Group Archives
  • #12246: DACS template displays warning about missing repository when repo name is inherited; will not allow a repository to be manually added at lower levels
  • #12272: OAI response uses cached XML files even when cache setting is turned off
  • #12319: Rights acts do not display; actionable rights are not being enforced for public users
  • #12370: libxml is not cleared between import jobs in the user interface, leading to repeated errors and warnings from previous imports


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

Archival descriptions

The 2.5 release will add audit logging for archival descriptions - administrators will be able to view a log of all creation and modification events associated with a description (including date of change and the user account associated with the change), as well as a log of all description modification events associated with a particular user account (with links to the affected descriptions). Users will be able to see their own logs, though only admins will be able to see all user logs. Additionally, editors will now be able to run a job that will automatically calculate the date range for a parent description, based on the broadest dates found on any descendant records.

Sponsored by Docuteam and the Bank for International Settlements

  • #12115 - Calculate accumulated dates
  • #12130 - Add new archival description audit log


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


AtoM 2.5 will add support for the Parsedown PHP library, which will allow users to format content using GitHub-flavored Markdown - meaning that italics, bolding, lists, tables, and more formatting will be supported within edit templates. Previous special formatting in AtoM will be removed, but a command-line task to convert existing custom link syntax to the new Markdown link syntax will also be added (see the Command-line tools section below). Parsedown syntax will also be automatically ignored in searches, and Parsedown is smart enough to ignore open ended tags - meaning if you forget to close a bolding element or a table, you won't break your whole site.

Sponsored by Texas A&M University - Cushing Memorial Library and Archives and McMaster University

  • #12148 - Add Markdown support in AtoM


Minor enhancements to the EAD XML import mapping.

Sponsored by Texas A&M University - Cushing Memorial Library and Archives

  • #12172 - Add additional fields to AtoM EAD import and export
  • #12267 - Convert bold, italic, and bolditalic EAD emphasis tag to markdown when markdown is enabled in AtoM

Search and Browse

We have upgraded the Elasticsearch index to use version 5.2 . Additionally, a new Hierarchical browse page option, comprised of a full-screen treeview displaying all records, will be available as an alternative way of browsing site holdings. User will also be able to change the sort direction of results in the sort button (Ascending and Descending). For edits that affect many descendant records, the job scheduler will now be used to make those updates in the background.

  • #10847 - Upgrade Elasticsearch to version 5.x
  • #12000 - Add alternative sort directions to the sort button in search/browse pages
  • #12140 - Include creator name as an option in the Advanced search panel's field drop-down

Sponsored by the Bank for International Settlements

  • #11955 - Add hierarchical (treeview-based) browse page to explore all holdings in AtoM

Sponsored by the University of Strathclyde Archives

  • #11855: Search index is not updated when edits affect descendant records


  • #11980 - Add notification when changing settings so users know the changes have been saved
  • #12139 - Organize identifier-related settings into their own settings page
  • #12160 - Add option to hide login button to Admin options in Visible elements

Sponsored by the National Library of Sweden

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

Command-line tasks

Sponsored by the City of Victoria Archives

  • #11910 - Create command-line task that removes unnecessary actor links at lower levels where inheritance could be used

Sponsored by Texas A&M University - Cushing Memorial Library and Archives and McMaster University

  • #12149 - Convert existing AtoM data to Parsedown syntax

Other additions include:

  • #9520 - Add --slug option to search:populate task

Bug fixes and minor enhancements

  • #7650 - Delete rights should warn user
  • #8345 - Administrator cannot delete "About" static page
  • #9308 - Move "Maximum image width (pixels)" setting to digital object derivatives tab in settings
  • #9839 - Adjust MODS import/export mapping for digital object
  • #10505 - Deleting a creator from an imported record also removes the date
  • #10856 - Sidebar treeview's "xx more" expand button cannot be translated
  • #11177 - Changing "users" menu name breaks user administration page
  • #11186 - Allow key menu item names to be locked
  • #11189 - Output of jobs:list and CSV jobs export via user interface is inconsistent
  • #11449 - Deleting digital object link from record in UI breaks digital object link for other records
  • #11507 - Title of descriptions not displayed on Jobs page when created in a different culture
  • #11639 - Symfony task for building models from schemas doesn't work with PHP 7
  • #11646 - CSV import should not import blank rows
  • # 11855 - Search index is not updated when edits affect descendant records
  • #11963 - Remove unused code from finding aid generation
  • #12167 - Deletions and/or edits to display labels on login, logout, and myProfile menu nodes have no effect
  • # 12232 - Genre browse page lacks results count column


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?