Difference between revisions of "Releases/Roadmap"
m (→Release 2.7: remove empty section) |
(Move 2.6.2 issues to 2.6.3, add security patch notes to 2.6.2) |
||
| Line 11: | Line 11: | ||
__TOC__ | __TOC__ | ||
| − | ==Release 2.6. | + | ==Release 2.6.2== |
| − | Release 2.6. | + | Release 2.6.2 will be a security patch release for the [[Releases/Release_announcements/Release_2.6|2.6.0 AtoM release.]] Patches will also be provided for 2.5.x and 2.4.x releases, for those who would like to patch the security vulnerability but are unable or unwilling to upgrade at this time. |
| − | + | Further details will be included in the official release announcement. | |
| − | + | Related issues: | |
| − | |||
| + | * #13470 | ||
| − | + | ==Release 2.6.3== | |
| − | ==Release 2.6.2 | + | Release 2.6.3 will include bug fixes, security patches, and a replacement for AtoM's previous Flash-based multi-uploader included in the [[Releases/Release_announcements/Release_2.6|2.6.0 release]]. |
| + | |||
| + | ===Digital objects: replacement for multi-uploader used in Import Digital Objects workflow=== | ||
| + | |||
| + | In [[Releases/Release_announcements/Release_2.6|Release 2.6]] and earlier, AtoM's "Upload multiple digital objects" workflow (documentation [https://www.accesstomemory.org/docs/2.6/user-manual/import-export/upload-digital-object/#upload-multiple-digital-objects-to-archival-descriptions here]) relied on a Flash-based uploader utility. As of December 2020, Flash has been deprecated and is now formally no longer supported in all major browsers. | ||
| − | + | The 2.6.3 release will include a new multi-uploader, using [https://uppy.io/ Uppy] as the base library. | |
===General bug fixes and enhancements=== | ===General bug fixes and enhancements=== | ||
| Line 56: | Line 60: | ||
* #13402 - Carousel breaks if user has no permissions to access thumbnails | * #13402 - Carousel breaks if user has no permissions to access thumbnails | ||
| + | |||
==Release 2.7== | ==Release 2.7== | ||
Revision as of 15:33, 27 January 2021
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.2
Release 2.6.2 will be a security patch release for the 2.6.0 AtoM release. Patches will also be provided for 2.5.x and 2.4.x releases, for those who would like to patch the security vulnerability but are unable or unwilling to upgrade at this time.
Further details will be included in the official release announcement.
Related issues:
- #13470
Release 2.6.3
Release 2.6.3 will include bug fixes, security patches, and a replacement for AtoM's previous Flash-based multi-uploader included in the 2.6.0 release.
Digital objects: replacement for multi-uploader used in Import Digital Objects workflow
In Release 2.6 and earlier, AtoM's "Upload multiple digital objects" workflow (documentation here) relied on a Flash-based uploader utility. As of December 2020, Flash has been deprecated and is now formally no longer supported in all major browsers.
The 2.6.3 release will include a new multi-uploader, using Uppy as the base library.
General bug fixes and enhancements
- #13341 - Fix formatting issue when displaying linked physical storage locations
- #13348 - Fix PHP warnings and notices
- #13366 - A single value autocomplete field creates a new iframe whenever it loses focus
- #13382 - Clipboard save message strings are currently not tranlsatable
- #13393 - Editing your own user accounts set the account to inactive on save
- #13398 - reset-password CLI task --activate option not working as expected
- #13407 - Archival description "Calculate dates" button causes page to load very slowly
- #13412 - Updating repository upload limit triggers unnecessary search index update
- #13418 - Archival description identifier counter doesn't increment when the generate identifier link is used
- #13421 - Authority record relationships with descriptions break EAC export
- #13430 - CSV export sometimes includes duplicate columns
- #13439 - CSV import update fallback matching not working in 2.6.x
- #13443 - Error message "You must specify a valid path" in export tasks is unclear
- #13447 - Update available notification displays repeatedly when navigating in the full-width treeview
- #13448 - Running "tools:upgrade-sql" deletes all user passwords if the Argon2i hashing function is not installed
Community code contribution from Jason Hildebrand and PeaceWorks Technology Solutions
- #13441 - Improve Dockerfile layers caching
Sponsored by Dalhousie University Archives
- #13431 - Syntactic error in authority record relationship area labels
Sponsored by the Oregon Historical Society
- #13402 - Carousel breaks if user has no permissions to access thumbnails
Release 2.7
Our next major release. Features described below are currently scheduled for inclusion; more will be added over time.
Accessions
Sponsored by the Government of the Northwest Territories
- #13315 - Add ability to associate events with accession records
Authentication
Sponsored by Simon Fraser University Archives
- #13383 - Support CAS single sign-on
Archivematica integration
Sponsored by Simon Fraser University Archives
- #13351 - Support AIP download from AtoM UI for authorized users
Authority records
Sponsored by an undisclosed institution
- #13373 - Display warning for duplicate authority record identifiers
Command-line tasks
General bug fixes and enhancements
- #13440 - Add ability for tools:expire-data to delete temp files
- #13368 - Add CLI option to migration task to run individual migrations
Sponsored by Mills Archive
- #13361 - Add option to cache XML task to generate only EAD or DC XML
Sponsored by the University of Saskatchewan Libraries
- #13380 - Add CLI task to identify and delete unused access point terms
Digital objects
Sponsored by an undisclosed institution
- #13351 - Download AIP and AIP files from AtoM UI
- #13395 - Add option to include digital objects in clipboard exports
Sponsored by Simon Fraser University Library
- #13388 - Improve digital object metadata display
- #13417 - Digital object preservation copy displays UCT time stamps
Sponsored by the Mills Archive
- #13436 - Add API endpoint to download master digital object
Scalability and performance
General bug fixes and enhancements
- #13435 - Permission denied creating a new child description when Grant "create" on parent
- #13437 - Digital object authorization code is too complicated
Sponsored by an undisclosed institution
- #11556 - Make AtoM's clipboard work with the Varnish Cache web application accelerator
- #13389 - Support ability for reverse proxies like Varnish to cache content that's not in the default culture
- #13415 - An archival description with many descendants loads slowly when the DO carousel is enabled
Settings
Sponsored by an undisclosed institution
- #13411 - Add setting to enable or disable repository "upload limit" widget
Treeview
General bug fixes and enhancements
- #13423 - Full-width treeview fails to load for descriptions with 900K+ children
- #13446 - Clicking on a description in the full-width treeview doesn't update the page URL
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?