Issues

spreadsheet import error

Repository Processing Note

As a repository manager, I would like the ability to auto-populate Notes fields with information that does not differ between Resources.

As a project manager, I would like to be able to edit component lists in Rapid Data Entry

As a project manager, I would like the ability to export component lists as a spreadsheet for mass edits

Ability to delete multiple components at once

The manage top containers "bulk operations" "update locations multiple locations" zeros out the locations not being edited at the time if they had already been done.

Filter out agent contact information content from the indexer

Who made this... information

Unpublished notes are indexed and searchable in the PUI

As a repository manager or archivist, I would like to be able to restart a background job

RDE Fill Column will not allow a fill to be set for Level of Description

RDE issue – hiding columns causes the Level of Description column to disappear when adding new rows which offsets the remaining fields by one, i.e. they no longer align with their header

saxon-xslt gem is end-of-life and has been replaced by saxon-rb

When using the public interface on a mobile device, text for digital object description and other components extend off screen rather than wrapping or shrinking to fit

Long controlled vocab lists should be easier to browse and re-order

uniq_ao_pos index constraint violation may occur when editing archival objects

As an archivist or researcher I'd like to be able to facet results by language

PUI search should allow narrowing of results by multiple values in the same facet/filter

As an archivist, I would like to be able to add Notes to Accessions.

frontend:devserver now wipes out solr and demoDB due to depends change in frontend:clean

Send feedback link in the default footer goes to an unuseful page of the ArchivesSpace website

External web links should be "live" and actionable

JSON-LD for agent records can result in "We're sorry, something went wrong" errors if a Date of Existence subrecord is utilized without specifying a begin date.