Difference between revisions of "Releases/Roadmap"

From AtoM wiki
(Import/Export: Add #12281)
(Remove 2.8.1 from roadmap now that it has been released)
 
(137 intermediate revisions by 4 users not shown)
Line 11: Line 11:
 
__TOC__
 
__TOC__
  
==Release 2.6==
 
  
===Accession records===
+
==Release 2.9==
  
''Sponsored by the Government of the Northwest Territories''
+
Plans for our next major release will be posted here and added to over time as they develop.
  
* #13254 - Add the ability to add multiple identifiers to accessions, with type and note values
 
* #13262 - Add CSV import support for accession alternative identifiers
 
* #13265 - Add search support for accession alternative identifiers
 
 
===Analytics===
 
 
''Sponsored by the United Nations Archives and Records Management Section''
 
 
* #13284 - Add Google Tag Manager support
 
 
===Authority records===
 
 
''General bug fixes and enhancements''
 
 
* #13157 - Add paging to authority record description relations to avoid editing timeouts
 
 
===Clipboard===
 
 
''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===
 
 
''General bug fixes and enhancements''
 
 
* #13196 - CLI regenerate derivatives task produces error when --slug used with --no-overwrite
 
* #13243 - Regression: identifier and title context lost on link digital object page
 
 
''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
 
 
''Sponsored by the Provincial Archives of Saskatchewan''
 
 
* #13103 - Add --attach-only option to digital object load task
 
* #13126 - Add --skip-nested-set-build option to digital object load task
 
 
''Sponsored by the University of Saskatchewan Libraries''
 
 
* #13152 - Add --replace option to digital object load task to allow uploads to replace existing digital objects
 
 
===Finding aids===
 
 
''General bug fixes and enhancements''
 
 
* #12707 - Finding aids will display custom levels as "otherlevel" instead of using otherlevel value
 
 
''Collaboratively developed / sponsored by Dalhousie University Library''
 
 
* #10591 - Update finding aid XSLTs with formatting improvements
 
 
===Import/Export===
 
 
''General bug fixes and enhancements''
 
 
* #6317 - EAD <repository> will not import properly if it is not nested in a <corpname> element
 
* #13130 - DC XML should include inherited creator(s) at lower levels
 
* #12281 - Add rountrip option to CLI CSV import for better matching
 
* #13204 - An apostrophe in the repository code will cause EAD XML imports to fail
 
* #13246 - Add --limit option to task for caching XML representations
 
 
 
''Sponsored by the WUSTL Bernard Becker Medical Library Archives''
 
 
* #12799 - Add donorNotes column to CSV import template for Accessions
 
 
''Sponsored by the University of Saskatchewan Libraries''
 
 
* #13148 - Add support for command-line bulk authority record CSV export task
 
 
 
''Sponsored by the City of Vancouver Archives''
 
 
* #13183 - Add CSV import for physical locations
 
* #13185 - Add ability to update physical storage data via CSV import
 
 
''Sponsored by the University of Strathclyde Archives and Special Collections''
 
 
* #13244 - Add setting to determine if identifier or reference code is used in DC XML
 
 
===OAI Repository===
 
 
''General bug fixes and enhancements''
 
 
* #13163 - OAI identify command base URL does not respect HTTPS; appends index.php unnecessarily
 
 
''Contributed via community pull request from [https://github.com/rferris Rohan Ferris]''
 
 
* #13025 - Convert UTC time to localtime in OAI requests
 
 
===Physical storage===
 
 
''General bug fixes and enhancements''
 
 
* #13201 - Browse physical storage page does not show values that have not been translated
 
 
''Sponsored by the Government of the Northwest Territories''
 
 
* #13268 - Add ability to link physical storage containers to accession records
 
* #13269 - Add new CSV report for physical storage location reporting
 
 
===Search/Browse===
 
 
''General bug fixes and enhancements''
 
 
* #13186 - Add user-configurable setting for treeview paging limit
 
 
''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
 
 
''Sponsored by the Provincial Archives of Sasksatchewan''
 
 
* #13175 - Improve information object search indexing speed
 
 
''Sponsored by the Mills Archive''
 
 
* #13230 - Date range sorting is broken following Elasticsearch upgrade in 2.5.x
 
 
===Settings===
 
 
* #13105 - Add warning message to security settings page
 
 
''Sponsored by the WUSTL Bernard Becker Medical Library Archives''
 
 
* #12798 - Add Visible elements module for DACS area headings
 
* #13049 - Add DACS Physical access field to Visible elements
 
* #13135 - Add new setting to make full-width treeview collapsible
 
 
 
===Bug fixes and other tickets===
 
 
* #13173 - If identifiers contain syntax that conforms to markdown syntax, the identifier is rendered in markdown
 
* #13174 - Jobs can hang if console output is greater than 64KiB
 
* #13196 - CLI regenerate derivatives task produces error when --slug used with --no-overwrite
 
 
 
<admonition type="seealso">
 
For a full list of issues related to the 2.6 release, see the following links to our issue tracker:
 
* [https://projects.artefactual.com/versions/127 Release 2.6 Roadmap / Overview]
 
* [http://bit.ly/AtoM-26 2.6 issues organized by category]
 
</admonition>
 
  
 
==Wishlist==
 
==Wishlist==
  
This project in our [[Resources/Issue tracker|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.
+
This project in our [[Resources/Issue tracker|issue tracker]] is where feature requests for Access to Memory (AtoM) can be added. This allows us to be aware of and log feature requests related to 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:'''
 
'''See the AtoM Wishlist project here:'''

Latest revision as of 05:49, 15 March 2024

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.9

Plans for our next major release will be posted here and added to over time as they develop.

Wishlist

This project in our issue tracker is where feature requests for Access to Memory (AtoM) can be added. This allows us to be aware of and log feature requests related to 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?