Difference between revisions of "Releases/Roadmap"
(Added CMHR treeview, CVA date range search) |
m (→Release 2.3: fix spacing) |
||
| Line 27: | Line 27: | ||
* #8384 - Add new customizable inventory page for exploring lower-level descriptions | * #8384 - Add new customizable inventory page for exploring lower-level descriptions | ||
* #8417 - Add facet for "Part of" to better explore child results of top-level descriptions | * #8417 - Add facet for "Part of" to better explore child results of top-level descriptions | ||
| − | + | <br /> | |
''Sponsored by the City of Vancouver Archives'' | ''Sponsored by the City of Vancouver Archives'' | ||
Revision as of 15:07, 9 July 2015
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.3
General usability enhancements
Sponsored by the World Bank Group Archives
- #8383 - Static page navigation enhancements
- #8410 - Add custom formatting to allow users to add hyperlinks to descriptive fields
Sponsored by the Canadian Museum for Human Rights
- #5538 and #6111 - Add keyboard support for search box and autocomplete results
Search and browse enhancements
Sponsored by the World Bank Group Archives:
- #8408 - Add new browse options to right-hand context menu on archival description view pages
- #8384 - Add new customizable inventory page for exploring lower-level descriptions
- #8417 - Add facet for "Part of" to better explore child results of top-level descriptions
Sponsored by the City of Vancouver Archives
- #8648 - Add date range searching to the Advanced search page
Treeview enhancements
Sponsored by the Canadian Museum for Human Rights and the World Bank Group Archives
- #6375 - Add full-width treeview to AtoM
Customization options
Sponsored by the Canadian Museum for Human Rights
- #8466 - Add settings to hide digital object carousel and language menu
Sponsored by the World Bank Group Archives:
- #8412 - Add new setting to select page no. in PDF derivatives
Jobs
- #8227 - arGenerateFindingAidsJob should have user-friendly label name for jobs page, like the Inherit rights job
- #8228 - Finding aid generation should have message when successful with name of related description
Import / export
- #6145 - Remove unnecessary spacing between elements during EAD export
Sponsored by the Council of Nova Scotia Archives
- #8335 - Add support for bulk CSV export from the command-line
Search Engine Optimization
Sponsored by the World Bank Group Archives
- #8354 - Add CLI task to generate XML sitemap for web crawlers
- #8418 - Include scope and content in HTML meta description element for better indexing
CLI Tasks
- #8488 - Add a skip to option for the digitalobject:regen-derivatives task
Seealso
For a full list of issues related to the 2.3 release, see the following links to our issue tracker:
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?