<html xmlns:v="urn:schemas-microsoft-com:vml" 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=us-ascii">
<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;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.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><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hello everyone,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have a dream of making the published resource records and their components in our ASpace instance available in our library’s Summon instance, and my plan is to do so using OAI-PMH. The configuration instructions on GitHub say that “<span style="font-family:"Segoe UI",sans-serif;color:#24292E;background:white">Harvesting
the ArchivesSpace OAI-PMH server without specifying a set will yield all published records across all repositories.” </span> Am I correct in thinking that “all published records” would mean published resources, resource components, accessions, digital objects,
and agents. Is there a type of “publishable” record that I am forgetting? <o:p>
</o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">At the moment, the only “set” of published information that I’m thinking of having Summon exclude is agents. If you’ve already made these kinds of decisions and you can think of a positive, downside, or implication I may be overlooking,
I’d appreciate hearing from you. Obviously, I’m trying to think this through to make sure I don’t have Summon suck in a bunch of stuff we don’t want them to.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Alston Cobourn<o:p></o:p></p>
<p class="MsoNormal">Processing and Digital Assets Archivist<o:p></o:p></p>
<p class="MsoNormal">Texas A&M-Corpus Christi<o:p></o:p></p>
<p class="MsoNormal"><a href="mailto:Alston.cobourn@tamucc.edu"><span style="color:#0563C1">Alston.cobourn@tamucc.edu</span></a><o:p></o:p></p>
<p class="MsoNormal">361-825-2300<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>