<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Hello,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I wrote a plugin that performs some integrations between ArchivesSpace and our Alma instance:
<a href="https://github.com/duspeccoll/alma_integrations">https://github.com/duspeccoll/alma_integrations</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">It takes as input a Resource provided by the user; it looks in the user-defined field we’ve assigned for Alma MMS IDs to see if one exists, then queries the Alma API to determine if there’s a Bibliographic
record with that ID, and if so, if there are any Holdings records attached to it. From there the user has the option to push metadata changes from ArchivesSpace out to Alma (via MARC export), and to create new Holdings based on a pre-defined list of location
codes we use for Special Collections and Archives materials. If the plugin is creating a new bibliographic record in Alma, it grabs the MMS ID of the new record and adds it to user_defined.string_2 for us.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">This code is functional but it’s not very pretty; I have plans to eventually clean it up and make it less focused on DU’s specific integration use case (i.e. by allowing a user to configure what field the
MMS ID is assigned to). If you’re an ArchivesSpace/Alma shop and don’t mind taking risks, or would like to test it against the Alma sandbox, comments and/or pull requests are welcome!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">cheers,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-k<o:p></o:p></span></p>
</div>
</body>
</html>