Feature #13268

Add ability to associate accessions with physical storage

Added by Mike Cantelon 8 months ago. Updated 4 months ago.

Status:VerifiedStart date:02/26/2020
Priority:MediumDue date:
Assignee:-% Done:

100%

Category:Accessions
Target version:Release 2.6.0
Google Code Legacy ID: Tested version:
Sponsored:Yes Requires documentation:

Description

This enhancement is part of an ongoing series of tasks designed to start implementing basic support for elements of the Canadian Archival Accession Information Standard (CAAIS ) in AtoM.

This particular enhancement will help implement support for CAAIS element 4.1, on Storage Locations. The implementation guidelines state:

Indicate the physical and/or digital location(s) within the repository in which the accessioned material is stored. Since accessioning represents establishing preliminary control of the records, it is possible that its location may change during the accession process. If this is the case, until the records have a permanent storage location, the accession location would be considered preliminary. Storage locations are based on the in-house practices of each repository.

This element is optional and repeatable.

AtoM's accession module already has a free-text location information field. However, this feature will enhance the existing functionality by adding the ability to associate physical storage locations in AtoM with an accession record. This linking ability will be a M:M relation - many containers can be related to a single accession, and many accessions can be related to a container.

The existing free-text field will be kept, to preserve legacy user data and to add more free-text information on storage location.


Related issues

Related to Access to Memory (AtoM) - Feature #13254: Add the ability to add multiple identifiers to accessions... Verified 02/06/2020
Related to Access to Memory (AtoM) - Feature #13265: Search support for accession alternative identifiers Verified 02/22/2020
Related to Access to Memory (AtoM) - Feature #13262: CSV import for accession alternative identifiers Verified 02/18/2020
Related to AtoM Wishlist - Feature #4540: Link to physical storage interface that is available for ... Verified 01/16/2013

History

#1 Updated by Mike Cantelon 8 months ago

The existing location info field, in accessions, will be left in for backward compatibility.

#3 Updated by Mike Cantelon 8 months ago

  • Status changed from New to Code Review
  • Assignee deleted (Mike Cantelon)

#4 Updated by Steve Breker 7 months ago

CR complete. Looks great!

#5 Updated by Mike Cantelon 7 months ago

  • Status changed from Code Review to QA/Review

Merged into qa/2.6.x.

#6 Updated by Dan Gillean 7 months ago

  • Description updated (diff)
  • Target version set to Release 2.6.0

#7 Updated by Dan Gillean 7 months ago

  • Sponsored changed from No to Yes

#8 Updated by Dan Gillean 7 months ago

  • Related to Feature #13254: Add the ability to add multiple identifiers to accessions, with type and note values added

#9 Updated by Dan Gillean 7 months ago

  • Related to Feature #13265: Search support for accession alternative identifiers added

#10 Updated by Dan Gillean 7 months ago

  • Related to Feature #13262: CSV import for accession alternative identifiers added

#11 Updated by Mike Cantelon 7 months ago

To do: suppress "Location information - This is a mandatory element" warning if they've linked the accession record to a storage location.

#12 Updated by Mike Cantelon 7 months ago

  • Status changed from QA/Review to Code Review

#13 Updated by Mike Cantelon 7 months ago

Fix (to suppress location warning if physical storage linked to accession) merged to qa/2.6.x and cherry-picked to client repo.

#14 Updated by Mike Cantelon 7 months ago

  • Status changed from Code Review to In progress

#15 Updated by Dan Gillean 5 months ago

  • Related to Feature #4540: Link to physical storage interface that is available for archival descriptions should be available for accessions. added

#16 Updated by Dan Gillean 4 months ago

  • Status changed from In progress to Verified

#17 Updated by Dan Gillean 4 months ago

  • % Done changed from 0 to 100
  • Requires documentation deleted (Yes)

Also available in: Atom PDF