<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<div>Kevin,</div>
<div>I would be interested in working out MARC import mappings or hearing from people with similar projects. I currently use scripts to convert our marcxml to the aspace jsonmodels and import via API, since the base mappings skip things like 856. FWIW I am
mapping our 856 to build digital objects or EAD location fields (based on indicators and subfields to determine which are which).</div>
<div><br>
</div>
<div>Nancy</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div style="font-family:Tahoma; font-size:13px">
<div style="font-family:Tahoma; font-size:13px">
<div style="font-family:Tahoma; font-size:13px">Nancy Kennedy</div>
<div style="font-family:Tahoma; font-size:13px">Smithsonian Institution</div>
<div style="font-family:Tahoma; font-size:13px">
<div>kennedyn@si.edu</div>
<div>202-633-0619</div>
</div>
</div>
</div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Kevin W. Schlottmann
<kws2126@columbia.edu><br>
<b>Sent:</b> Friday, May 1, 2020 3:04 PM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> [Archivesspace_Users_Group] MARC importer to handle URLs in 555 and 856 fields?</font>
<div> </div>
</div>
<div>
<p class="x_MsoNormal" style="line-height:12.0pt; background:#FFEB9C"><b><span style="font-size:9.0pt; font-family:"Calibri",sans-serif; color:#9C6500">External Email - Exercise Caution</span></b></p>
<div>
<div dir="ltr">
<div>Hi all,</div>
<div><br>
</div>
<div>The metadata standards subgroup of the Technical Advisory Council (TAC) has been reviewing the published mappings for the MARCXML resource importer. One question that came up in our discussion was the handling of URLs in the MARC 555 and 856 $u subfields.
Both of these fields use the subfield $u to point to external web pages; in the archival context these are often links to full finding aids. The current MARC importer ignores these two fields. (We will add that fact to the mappings, to make explicit that
MARC data in these fields will be lost on import.)<br>
</div>
<div><br>
</div>
<div>We are reaching out to the community, and see 1) if there is interest in opening a ticket to request the 555 and 856 fields be added to the importer, and if so 2) willingness to help spec out the desired default behavior.<br>
</div>
<div><br>
</div>
<div>We ask for 2) because these fields are used in many different and specific ways, and one concern we have is that any default behavior will serve only a small subset of use cases, while most institutions would have to work out local customizations. In short,
this may be a place to leave well enough alone. <br>
</div>
<div><br>
</div>
<div>Best,</div>
<div><br>
</div>
<div>Kevin<br>
</div>
<br>
<div>-- <br>
<div dir="ltr" class="x_gmail_signature">Kevin Schlottmann<br>
Head of Archives Processing<br>
Rare Book & Manuscript Library<br>
Butler Library, Room 801<br>
Columbia University<br>
535 W. 114th St., New York, NY 10027<br>
(212) 854-8483</div>
</div>
</div>
</div>
</div>
</body>
</html>