Difference between revisions of "Releases/Roadmap"

From AtoM wiki
(Import and export: Added sponsorship info for 10621)
(Search and browse: Added 10733)
Line 157: Line 157:
  
 
* #9655 - Add new search options to better support searching indexed finding aid text
 
* #9655 - Add new search options to better support searching indexed finding aid text
 
+
* #10733 - Add basic support for virtual institutions  - ability to limit scope of search/browse to a single institution and maintain state
  
 
===Security and settings===
 
===Security and settings===

Revision as of 16:37, 5 January 2017

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

Currently we are aiming to release AtoM 2.4.0 in the first or second quarter of 2017.

Accession record enhancements

Sponsored by the University of the Witswatersrand

  • #9897 - Allow accession numbers to be edited by users via the user interface
  • #9915 - Include a setting to disable the accessions mask
  • #9917 - Validate and enforce the uniqueness of identifiers

Administration enhancements

Sponsored by the City of Winnipeg Archives

  • #10378 - Add configurable alert on login indicating number of draft records

Archival description enhancements

Sponsored by the United Nations Archives and Records Management Section

  • #9950 - Include the ability to set if slugs are generated from title, identifier, or reference code (with or without country and repo code included)

Sponsored by the Hamilton Public Library

  • #10330 - Add ability to assign latitude/longitude values to digital object metadata and generate dynamic Google maps from assigned values

Authority record enhancements

Sponsored by the Royal British Columbia Museum

  • #10048 - Provide pagination and "show all" links in authority records linked descriptions list

Sponsored by the Canadian Council on Archives and partners

  • #8642 - Add relation rows to the database schema to associate actors with maintaining repositories

Clipboard

Sponsored by the Canadian Council on Archives and partners

  • #10007 - Add clipboard links to the description updates page
  • #10011 - Add support for other entities on the clipboard page (authority records, repository records)

Command-line tools

  • #10334 - Add CLI tool to delete users

Sponsored by the Royal British Columbia Museum

  • #9964 - Add a type flag to the digital object derivative regeneration task to limit regeneration to thumbnails or reference display copies

Sponsored by the World Bank Group Archives

  • #10055 - Add a flag to the digital object derivative regeneration task to prevent overwriting existing derivatives

Sponsored by the City of Vancouver Archives and Gaia Resources

  • #9960 - Add a DIP object import task to allow Archivematica DIPs to be uploaded to existing descriptions in AtoM

Description updates

Sponsored by Santa Casa da Misericórdia de Lisboa and MoreData

  • #10458 - Improve scalability of the Description updates module by using the search index for all queries
  • #10459 - Add date range search to the Description updates module
  • #10462 - Update the Description updates page layout

Finding aids

Sponsored by the University of Saskatchewan Library

  • #9627 - Allow users to upload a PDF finding aid instead of generating one from AtoM's descriptions
  • #9699 - Improve usability and user interface elements of finding aid management and download options
  • #9700 - Show finding aid links at all levels of description in the hierarchy, instead of just the parent level

Import and export

Sponsored by the Canadian Council on Archives and partners, and the United Nations Archives and Records Management Section

Import

  • #10137 - Add support for large/bulk import via the user interface, using the job scheduler
  • #9992 - Enhance import matching behaviors: use cascading logic to improve matching during imports
  • #10150 - Add new options for update behavior during import when existing matches are found
  • #9995 - Enhance import matching behaviors: add a digital object checksum column to CSV import/export templates and use it on import for first match when importing updates
  • #10016 - Enhance import matching behaviors: add and enhance matching logic for imports of authority records
  • #10017 - Enhance import matching behaviors: add and enhance matching logic for imports of repository records
  • #10054 - Enhance import matching behaviors: add option to skip unmatched records and report in console instead of creating new records when no match is found
  • #10144 - Enhance import matching behaviors: add ability to limit matching to a specific repository or top-level description
  • #10138 - Add ability to include a python transformation script as part of a CSV upload via the user interface
  • #10193 - Add source-name field to archival description Admin area in edit template

Sponsored by the UNESCO Archives

  • #10621 - Import SKOS files asynchronously in multiple formats using EasyRDF

Export

  • #9998 - Add support for large/bulk export of descriptions via the user interface, using the job scheduler
  • #10000 - Add ability to limit archival description export to specific levels of description
  • #10006 - Add ability to exclude draft archival descriptions during export
  • #10013 - Add support for large/bulk export of authority records via the clipboard page, using the job scheduler
  • #8591 - Create an export:repositories task
  • #10015 - Add support for large/bulk export of repository records via the clipboard page, using the job scheduler
  • #10009 - Include help text next to certain export options for better end-user context

Job scheduling

Sponsored by les Archives de Montreal and the Archives Society of Alberta

  • #9945 - Perform all Move operations via the job scheduler

Sponsored by the United Nations Archives and Records Management Section

  • #9986 - Log console output for atom-worker jobs and make it available to the end-user via the Jobs page

Search and browse

Sponsored by the United Nations Archives and Records Management Section

  • #6681 - Add field weighting to archival description searches
  • #9949 - Merge digital object browse page into general search/browse page to allow users to apply facets and advanced search filters on digital objects
  • #9952 - Include advance search panel option to target search to text extracted from digital objects
  • #9953 - Supplement sort options on archival descriptions - add separate sort options for start date and end date
  • #10082 - Improve Elasticsearch mappings for archival descriptions

Sponsored by the University of Saskatchewan Library

  • #9655 - Add new search options to better support searching indexed finding aid text
  • #10733 - Add basic support for virtual institutions - ability to limit scope of search/browse to a single institution and maintain state

Security and settings

Sponsored by the Art Center College of Design

  • #9765 - Add basic support for LDAP integration

Sponsored by the City of Winnipeg

  • #10378 - Add setting to display number of drafts notification upon login

Seealso

For a full list of issues related to the 2.4 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?