Feature #7388

Allow alternative ids to be imported via CSV for AtoM

Added by Mike Gale about 6 years ago. Updated over 5 years ago.

Status:VerifiedStart date:10/15/2014
Priority:MediumDue date:
Assignee:Sarah Romkey% Done:

0%

Category:CSV import
Target version:Release 2.2.0
Google Code Legacy ID: Tested version:2.2
Sponsored:Yes Requires documentation:

Description

There are now two new columns in our CSV template: alternativeIdentifiers and alternativeIdentifierLabels. As the names imply, it will fill in the alternative id fields in an archival description. Further, you can pipe these columns together to provide multiple alternative labels per archival description.

e.g. alternativeIdentifiers: alt_id1|alt_id2
alternativeIdentifierLabels: My Label 1|My Label 2

One restriction is there must be the same number of labels as there is alternative ids, otherwise we throw an error.


Related issues

Related to Access to Memory (AtoM) - Feature #6107: Add alternate number field Verified 12/11/2013

History

#1 Updated by Dan Gillean almost 6 years ago

  • Description updated (diff)
  • Requires documentation set to Yes

This relates to the alternative Identifier fields added to AtoM in 2.1 - https://www.accesstomemory.org/docs/2.1/user-manual/add-edit-content/archival-descriptions/#add-alternative-identifiers-to-an-archival-description

This will need to be documented for 2.2 in several places. First, in the CSV import documentation - here, or near here: https://www.accesstomemory.org/docs/2.1/user-manual/import-export/csv-import/#other-data-entry-notes

Mentions of the column/field will need to be added to the RAD and ISAD template pages as well

Finally, mention of this and links to related documentation should be made in the main section on the archival description page, linked above. As well, we should try to provide a new 2.2 sample CSV with the field included.

#2 Updated by Dan Gillean almost 6 years ago

  • Private changed from Yes to No

#3 Updated by Sarah Romkey almost 6 years ago

  • Status changed from QA/Review to Document
  • Priority changed from Low to Medium

COOL it works! Marking as document so that I remember it needs documentation.

#4 Updated by Dan Gillean almost 6 years ago

FYI, you don't have to use the Document status, if the new "Requires documentation" field is checked. In fact, this may prevent us from seeing which issues are actually verified. To check on doc stuffs, I've added a custom query to sidebar - here it is as well:

It organizes the issue tickets marked as requiring documentation by release. When you document something, simply go in, uncheck the field, and add links to where the documentation appears. Just a thought!

#5 Updated by Sarah Romkey almost 6 years ago

  • Status changed from Document to Verified

Right, good point! Marked as verified.

#6 Updated by Dan Gillean over 5 years ago

#7 Updated by Dan Gillean over 5 years ago

  • Requires documentation deleted (Yes)

Also available in: Atom PDF