Roadmap

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.

Tip

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

Release 2.6

The 2.6 release is almost finalized! You can see all the details in the 2.6 release announcement page.

Release 2.6.1

Release 2.6.1 will be a bug fix and community translations update for the 2.6.0 release.

General bug fixes and enhancements

  • #13348 - Fix PHP warnings and notices
  • #13366 - A single value autocomplete field creates a new iframe whenever it loses focus

Release 2.7

Accessions

Sponsored by the Government of the Northwest Territories

  • #13315 - Add ability to associate events with accession records

Authority records

Sponsored by an undisclosed institution

  • #13373 - Display warning for duplicate authority record identifiers

Command-line tasks

General bug fixes and enhancements

  • Add CLI option to migration task to run individual migrations

Sponsored by Mills Archive

  • #13361 - Add option to cache:xml-representations to export only EAD or DC XML

Sponsored by the University of Saskatchewan Libraries

  • #13380 - Add CLI task to identify and delete unused access point terms

Wishlist

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:

Tip

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.

Seealso

  • 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?