Feature #7130

Add Cast, Credit, and Signatures RAD other notes fields to template and to CSV import

Added by Dan Gillean about 6 years ago. Updated about 6 years ago.

Status:VerifiedStart date:08/19/2014
Priority:MediumDue date:
Assignee:Dan Gillean% Done:

0%

Category:CSV import
Target version:Release 2.1.0
Google Code Legacy ID: Tested version:2.1
Sponsored:No Requires documentation:

Description

Based on a community pull request: https://github.com/artefactual/atom/pull/22

From the PR: "This implements Cast, Credits, and Signatures as note types that can be imported via CSV import. It also follows the method used by Language Note for creating these note types if they do not yet exist."

Note types are also available in new RAD template descriptions added via the user interface - part of the drop-down menu in the RAD Other notes field.

Cast, Credits, and Signatures are 3 different types of other notes information covered in the Canadian Rules for Archival Description (RAD) standard. The relevant rules are copied below for reference.

In the RAD-example CSV, the new notes fields can be included in a column with the following headers:
  • radNoteCast
  • radNoteCredits
  • radNoteSignaturesInscriptions

A sample CSV that demonstrates how the fields can be included in a RAD CSV import is attached.

IMPORTANT NOTE: At present, these new fields have NOT been mapped to the EAD export - meaning they will not roundtrip. Further development will be required to map the fields to EAD for import/export and roundtripping.


RAD NOTES - CREDITS, CAST, and SIGNATURES

7.8B5a. Credits note. List persons (other than the cast) who have contributed to the artistic
and/or technical production of a moving image document. Preface each name or group
of names with a statement of function. (for Moving images)

7.8B5b. Cast. List featured players, performers, presenters or other on-screen
personnel. (Moving images)

3.8B6. Signatures and inscriptions. Make notes on signatures, inscriptions, or
monograms, etc., which appear on the unit being described. Indicate where such
signatures and inscriptions appear.

4.8B7. Signatures and inscriptions. Make notes on signatures, inscriptions, or
monograms, etc., which appear on the unit being described. Indicate where such
signatures and inscriptions appear. (Graphic materials)
5.8B6. Signatures and inscriptions.
Make notes on signatures, inscriptions, or marks,
monograms, etc. If important, indicate where such signatures and inscriptions appear.
Do not record the actual signature if it has already been transcribed in the description.
(Cartographic materials)
6.8B6. Signatures and inscriptions.
Make notes on signatures, inscriptions, or marks,
monograms, etc. If important, indicate where such signatures and inscriptions appear.
Do not record the actual signature if it has already been transcribed in the description.
(Architecture and technical drawings)

11.8B7. Signatures and inscriptions. Transcribe all signatures not included in the
statement of responsibility, inscriptions, monograms, etc., found on the item according to
1.0C, 1.0E-1.0G, and Appendix A. Specify the location where the signature(s),
inscription(s), etc., appear. If the inscription is in a non-roman alphabet, make a note
indicating the script used. Indicate missing text by the mark of omission (e.g., when the
object is damaged). (Objects)

12.8B7. Signatures and inscriptions. Make notes on signatures, inscriptions, or marks,
monograms, etc. If important, indicate where such signatures and inscriptions appear. Do not
record the actual signature if it has already been transcribed in the description.
(Philatelic records)

example_rad-custom-notes.csv Magnifier (7.55 KB) Dan Gillean, 08/19/2014 12:27 PM


Related issues

Related to Access to Memory (AtoM) - Bug #9763: radNoteCast, radNoteCredits, and radNoteSignaturesInscrip... Verified 04/29/2016

History

#1 Updated by Dan Gillean about 6 years ago

  • Description updated (diff)

#2 Updated by Jesús García Crespo about 6 years ago

  • Target version changed from Release 2.1.0 to Release 2.2.0

#3 Updated by Dan Gillean about 6 years ago

  • Status changed from New to QA/Review
  • Target version changed from Release 2.2.0 to Release 2.1.0

This is a community pull request that I have already done some testing on locally, and ideally would still like to get into the 2.1 release. Bumpting back for further testing. Right now there is a "default context doesn't exist" error that can be fixed with the addition of 2 lines of code - something I think we can take on if we merge this.

#4 Updated by Mike Gale about 6 years ago

The default context does not exist error usually means these lines of code are missing from the top of a task's execute():

    $configuration = ProjectConfiguration::getApplicationConfiguration('qubit', 'test', false);
    $sf_context = sfContext::createInstance($configuration);

#5 Updated by Jesús García Crespo about 6 years ago

  • Assignee changed from Jesús García Crespo to Dan Gillean

Can you share the command line that you are using? I can't reproduce.
I tried with the CSV that you've attached and it worked. My authority record browser is showing the records.

#6 Updated by Jesús García Crespo about 6 years ago

Ok I initialized the context. Curiously, Dan needed but I didn't... not sure why.
Ready for review.

#7 Updated by Dan Gillean about 6 years ago

  • Status changed from QA/Review to Verified

Works. NOTE: This is not available in either the EAD export, or the Elasticsearch index at the moment. So you cannot search for a description based on data found in these new notes fields, and if you export via EAD, the data will not be included there.

#8 Updated by Dan Gillean over 4 years ago

  • Related to Bug #9763: radNoteCast, radNoteCredits, and radNoteSignaturesInscriptions missing from example CSV file added

Also available in: Atom PDF