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.
Contents
Release 2.6[edit]
Clipboard[edit]
Sponsored by the Bernard Becker Medical Library Archives at Washington University in St. Louis
- #12800 - Add JSON-LD export of AtoM clipboard items for third-party integrations
Digital objects[edit]
Sponsored by the Oregon Historical Society
- #12902 - Replace flowplayer with an HTML5 media player and update default derivative generation
- #12903 - Add new option to Digital object regen-derivatives task to allow regenerating only video file derivatives
OAI Repository[edit]
Contributed via community pull request from Rohan Ferris
- #13025 - Convert UTC time to localtime in OAI requests
Search/Browse[edit]
Sponsored by the Bernard Becker Medical Library Archives at Washington University in St. Louis
- #12797 - Make "Browse digital objects" link on description view page context sensitive
Seealso
For a full list of issues related to the 2.6 release, see the following links to our issue tracker:
Wishlist[edit]
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?