Re: [atom-users] Missing CSV and UI fields for RAD?

[Dan Gillean]

Hi Katrina, 

I will do my best to provide answers! 

Cast, Credits, and Signatures

Unfortunately, I think you're right - they will import, but they will not export. These fields were added to AtoM via a community pull request. They were added to the user interface and to the CSV import, but the developer did not add them to the export, or to the EAD XML import/export. It would likely be a small piece of development to add them to CSV export, but so far no one has sponsored such development. 

Appraisal

Nope! Sorry, I'm not sure how that snuck into our example CSV. AtoM's underlying data model was built against ISAD, and the CSV templates share many of the same fields. This one relates only to an ISAD(G) field, ISAD 3.3.2  appraisal, destruction and scheduling. The RAD standard has no equivalent field. As such, this column *would* import, but the data would only be visible on the ISAD template view, not in RAD! 

I've filed a bug ticket for us to remove this in the future: https://projects.artefactual.com/issues/12484

Related materials

The RAD standard has a field called RAD 1.8B18 - Associated materials. In AtoM's CSV template, the CSV field is called relatedUnitsOfDescription (the name is drawn from the corresponding field in the ISAD template - AtoM was originally built around the ICA standards, and support for RAD was added later). 

This is a free-text field, and is distinct from the autocomplete field available in the AtoM user interface called "Related descriptions," which can be used to link a description to another description held in the same AtoM instance. Unfortunately, there is no import for that field - though I imagine we could design one that would accept a slug as a parameter, and use pipe separators for multiple values. That would require development sponorship or a community-submitted code contribution for us to include in a future release, however. 

Title and Statement of responsibility

In the CSV and AtoM's user inteface, there are several separate elements, rather than a combined one. CSV fields, with corresponding RAD standard field name and number: 

• title
• alternateTitle (RAD Parallel title(s), 1.1D)
• radOtherTitleInformation (RAD other title infomration, 1.1E)
• radTitleStatementOfResponsibility (RAD statement of responsibility, 1.1F)
• radTitleStatementOfResponsibilityNote (RAD title notes - statement of responsibility, 1.8B5)
• etc (there are other title notes)

Digital objects and CSV imports

There are 2 fields you can add to the CSV for digital objects:

• digitalObjectPath
• digitalObjectURI

Both are used to link a single digital object to the current description. The digitalObjectPath column expects a file path to an object that you've added to your AtoM server. In this case, the objects must be on the same server as AtoM, in a directory accessible to you from there - so if your AtoM instance is installed at /usr/share/nginx/atom, you could create a temporary folder called images (for example) and add your digital objects there. In that case,  if you had an image in that folder called image01.jpg and you wanted to link it to a new description via CSV import, then your digitalObjectPath value might be /usr/share/nginx/atom/images/image01.jpg. It's been a minute since I tested this, but it's also possible you can just drop the absolute path, and just reference the subdirectory - i.e. you could try adding just images/image01.jpg to the digitalObjectPath column and see if that works. 

In contrast, the digitalObjectURI column is used to link to publicly accessible digital objects on the web. When this is done, AtoM will fetch the web version to create local derivatives (i.e. the reference display copy available on the description's view page, and the thumbnail in search/browse results), but it will not store a copy of the master object - instead, it will just save the URL pointing to it, and serve that link to users trying to access the master object via a browser. 

AtoM's requirements for being able to link to remote digital objects using this method are: 

• They must be web-accessible without any barriers to access (no logins, firewalls, VPNs, etc)
  
• They must be HTTP or HTTPS links (FTP links won't work)
  
• They must end in the file extension of the digital object. You can't link to a landing page, unfortunately. 
  

This last point means, for example, that you can't link directly to a YouTube video, for example - YouTube purposefully obfuscates  direct access to the actual movie file (aka the .mp4 or .avi file) so you can't download it directly by right-click and saving. If you were looking at an image on a webage, you would generally want to right-click and select "View image" (or whatever your browser's equivalent option is) to see the direct path to the object that ends in .jpg, and this is the URL you'd want to use in the digitalObjectURI column. 

The digitalObjectChecksum column is only used when a CSV is being used to update a description. If a checksum is present and it is identical to the current checksum stored with an associated description, then AtoM knows that, of the incoming updates in the CSV, a change to the digital object is not one of them, so it skip re-importing and replacing the current digital object. 

I hope that helps! Let me know if you have further questions. 

Cheers, 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

On Wed, Oct 3, 2018 at 12:06 PM Katrina CP <katrina.co...@gmail.com> wrote:

Hello,

Firstly, I just wanted to say how much I appreciate the ability to update descriptions via CSV. This feature in 2.4 has tremendously expedited our ability to publish migrated data from our legacy descriptive database.

When I first started, I drafted these notes to learn CSV labels/UI fields and export/import columns and reference a cheat sheet while working with descriptions:
https://docs.google.com/spreadsheets/d/13LAQm4aMCNBknylPWWq4dynFF59NAW3vQ_tKYNZdkkc/edit?usp=sharing

After compiling the information from the documentation, I cannot seem to answer a few questions:

CSV RAD 2.3

CSV Export

CSV Field

UI Field

Are radNoteCast, credits, and signature inscriptions fields missing from exported CSVs?

BD		radNoteCast	Notes area : Other notes - Cast
BE		radNoteCredits	Notes area : Other notes - Credits note
BF		radNoteSignaturesInscriptions	Notes area : Other notes - Signatures note

Is there a RAD user-interface appraisal field?

BX

BW

appraisal

Is there a CSV field to import/export (1) related materials (notes area) ...

Notes area : Related materials

... and (2) Value (title and statement of responsibility), and (3) digitalObjectPath?

	BU	digitalObjectChecksum
		digitalObjectPath	NA via archival description edit screen. In archival description view page screen click on "more" button at bottom of description>Link digital object (single file) --or-- Import digital object (multiple files).

Any help in answering these questions is appreciated (particularly the ability to link related material via CSV).

Thank you,

Katrina Cohen-Palacios

Adjunct Archivist, York University Libraries

Clara Thomas Archives and Special Collections

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/9d93e691-5d3b-4798-abe5-f89005234e26%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Dan Gillean]

Hi Katrina, 

The digitalObjectPath is not included in the example CSVs, but you can manually add the column (or change the header on the digitalObjectURI column). It is not included on exports either, since it would not be useful for moving data to a different system - instead, the digital object URI is included in the export. There is a previous thread in the user forum where I discuss how you can use the digitalObjectURI column output of an export to figure out what the digitalObjectPath would be - see: 

• https://groups.google.com/d/msg/ica-atom-users/3SRd50y9bEM/sld_BBDjBgAJ
  

Regards, 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

On Thu, Oct 4, 2018 at 9:44 AM Katrina Cohen-Palacios <katrina.co...@gmail.com> wrote:

Hi Dan,

Thank you so much for such complete and throughout answers.

Is there a column for digitalObjectPath in the RAD CSV template? Because I do not see it, nor in exported CSVs.

Completely understandable that certain features needing sponsorship and/or community development -- wasn't sure if I was missing something, etc, as I become better acquainted with CSVs.

cheers,

Katrina

You received this message because you are subscribed to a topic in the Google Groups "AtoM Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ica-atom-users/z5A6LYFADBE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ica-atom-user...@googlegroups.com.

To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAC1FhZLfC5iGXkugE-iby8wi%3DnozOFahg1Y_c%3DDpZo%2BZr3GdaQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Katrina Cohen-Palacios

Master of Information

Master of Museum Studies

katrina.co...@gmail.com

Cell: (647) 460-6223

Twitter, LinkedIn

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAMDw%2BrbSEBmm7We82nkMXVPiQQkuaBPE0n_jzDYFtWwdBK6eMQ%40mail.gmail.com.