<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Adrienne,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Here's a link to the plugin that Hudson Molonglo developed, which we've been using for about the past six months in production: <a href="https://github.com/hudmol/yale_onsite_locations" id="LPlnk946638">https://github.com/hudmol/yale_onsite_locations</a>
If you have any questions about it, let us know.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I would love to see this in the ArchivesSpace core code, but we went with a plugin approach last year so that we could get this feature added ASAP to our instance and so that we could test out how it performs (so far, so great!). The plugin adds an "Onsite?"
checkbox to every location, with the default value being set to True. And once you start flipping some locations to Onsite = False, then information is stored in the index to indicate whether the Resource and Archival Object and Top Container records are
stored onsite or offsite. And since Resource and Archival Objects can be linked to multiple top containers, those records can have a hybrid status. So, that's why we now have a facet for "Storage Location", as seen in the attached image. We haven't really
highlighted this new feature to users yet, but I am very interested in seeing how it gets used over time. </div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
We also talked about adding a feature in the staff interface to calculate a note for the collection to indicate which boxes were onsite vs. offsite based on this information, like the "Calculate Date / Extent" function, but didn't wind up adding that to the
plugin, although I still like the idea. </div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
And Olivia, since I was still interested in adding such a note to our EAD, even after all these years (has it been over three years?
<span id="š">š)</span>, I did update our EAD3 export option to include the location information in our EAD files. I did not go with a physloc note, since I agree with you that it would look horrible having that information repeat everywhere if it were to
display in the finding aid, so I went with an option of adding the location URI fragment into an attribute on each container element that is associated with an ASpace location record. Then, since we know which locations that we consider to be onsite vs. offsite,
our nightly export process will add a note to each finding aid in the EAD3 control section. Here's an example: <a href="https://github.com/YaleArchivesSpace/Archives-at-Yale-EAD3/blob/5734391e95a954a99cb03ee54282fd14d028c8e3/brbl-ead/10764.xml#L34-L41" id="LPlnk">https://github.com/YaleArchivesSpace/Archives-at-Yale-EAD3/blob/5734391e95a954a99cb03ee54282fd14d028c8e3/brbl-ead/10764.xml#L34-L41</a>
We aren't using that note for anything right now, but I think that it could be useful for creating our MARC holdings records, as well as for adding to our PDF finding aids, etc. But right now, it's just there so that staff could potentially use it to review
and see if it looks like things are assigned as expected.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Mark</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="_Entity _EType_OWALinkPreview _EId_OWALinkPreview _EReadonly_1"></div>
<br>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div style="margin: 0px; font-style: normal; font-variant-caps: normal; font-weight: normal; font-stretch: normal; font-size: 12px; line-height: normal; font-family: "Helvetica Neue";">
<br>
</div>
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div id="appendonsend"></div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Pruitt, Adrienne
<Adrienne.Pruitt@tufts.edu><br>
<b>Sent:</b> Tuesday, January 26, 2021 3:52 PM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Offsite boxes and ASpace</font>
<div> </div>
</div>
<div dir="ltr">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Hello, all,</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
This question - of making onsite/offsite locations visible to users - has come up at Tufts, and it looks like Yale, at least, has solved it. (Hooray!) If anyone has a good solution for this (plugin or otherwise), would you mind pointing me to it?</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
Thank you very much!</div>
<div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div id="x_Signature">
<div>
<div style="font-family:Tahoma; font-size:13px">
<p class="x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<b>Adrienne Pruitt </b><span style="font-size:9pt">| Collections Management Archivist<b></b></span></p>
<p class="x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:9pt">Digital Collections and Archives</span></p>
<p class="x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:9pt">Tufts University</span></p>
<p class="x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span style="font-size:9pt"><a href="https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fexchange.tufts.edu%2Fowa%2Fredir.aspx%3FC%3Dt5B1d8GNpPJJzaAAvUfcGAPuBinqgxXyoK8_O0ggQHCOYyG6Tc_XCA..%26URL%3Dmailto%253aadrienne.pruitt%2540tufts.edu&data=04%7C01%7Cmark.custer%40yale.edu%7C29395ca0ea394c7f06fd08d8c23c41d7%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637472911359825173%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=wX39F6MDBD%2FG8pgHhJ1a0YgTsOBznznsTrIL6ztV8iI%3D&reserved=0" originalsrc="https://exchange.tufts.edu/owa/redir.aspx?C=t5B1d8GNpPJJzaAAvUfcGAPuBinqgxXyoK8_O0ggQHCOYyG6Tc_XCA..&URL=mailto%3aadrienne.pruitt%40tufts.edu" shash="P9KDpuz7J5uz4eL5lFa5gvrQ3He88gdZuuc0urRJqFXqOUEqhOzBjO3JEOHtvF8ns4EMeDmPVUEVLMydqbI7EJ8iGaQjK2m5Sv09ybd/7Fp7BuO00HGpd+3npB+swm7JoJn4CNR89zxE3JysUGfjOpL1HgQy3VYy+6IxHrFMcZI=" target="_blank" rel="noopener noreferrer" style="color:rgb(149,79,114)"><span style="color:windowtext">adrienne.pruitt@tufts.edu</span></a> |<span style="background:white">617-627-0957</span></span></p>
</div>
</div>
</div>
</div>
<div id="x_appendonsend"></div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Custer, Mark
<mark.custer@yale.edu><br>
<b>Sent:</b> Friday, November 17, 2017 3:35 PM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Offsite boxes and ASpace</font>
<div> </div>
</div>
<div lang="EN-US">
<div class="x_x_WordSection1">
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
Hi Olivia,</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
Hear, hear!!! <span style="font-family:"Segoe UI Emoji",sans-serif">š</span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
Just a quick note to say that this is something that weāve discussed at Yale, as well, and I think that we might start to address it via a plugin at some point (it would be a nice feature to go directly into the core code, but in order for that to happen, Iād
think that the Location module would need to be updated so that staff could indicate which locations were the offsite ones without having to add that data to a config file). </p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
Also, I believe that the location information is already in the PUI index, so it would just be a matter of choosing when/where to display that data. I donāt think that thereās a good EAD solution, unless you implement a specific way to use the physloc note,
as you mentioned, but even then youāve got to do some grouping since those boxes are often repeated in a finding aid, and any top-level, auto-generated note should be easy to read.</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
Hereās what Iād like our ASpace PUI site to have (eventually):</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<ul type="disc" style="margin-bottom: 0in;margin-top:0in">
<li class="x_x_MsoListParagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:0in; mso-list:l0 level1 lfo2">
We could configure which locations are offsite (for us, weād just need to add 3 location IDs to an array of offsite locations). In the future, though, it would be nice if you could use the Location module in ASpace to designate this rather than doing it in
a configuration file; and anything thatās not tagged as being offsite would then be inferred to be on site.</li><li class="x_x_MsoListParagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:0in; mso-list:l0 level1 lfo2">
Each top-container landing page would have an automatically generated note indicating that the materials were stored offsite and requires X amount of time to retrieve (and, of course, the part about how long it would take would need to be configurable, as well)</li><li class="x_x_MsoListParagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:0in; mso-list:l0 level1 lfo2">
Each archival object, accession, and resource associated via an instance with one of those top containers would have the same message.</li><li class="x_x_MsoListParagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:0in; mso-list:l0 level1 lfo2">
Weād also have 2 facets to indicate onsite vs. offsite (or, available today vs. needs X amount of lead time, whatever would make the most sense). How handy would that be to exclude āoffsiteā archival components if youāre only going to be in town for a day
or two?</li><li class="x_x_MsoListParagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:0in; mso-list:l0 level1 lfo2">
If a resource or accession had any offsite material attached to it, then an auto-generated note would display at the top level description, indicating as much (e.g. Boxes 1-3 and 5 in this collection require five business days to retrieve, upon receipt of request)</li></ul>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
All that said, it would be great to have the same info available in the staff interface, too.</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
Have any other institutions tackled this problem already? For now, we really only indicate this by manually adding notes to our MARC Holdings records, and Iād love not to repeat that practice in our finding aids for the reasons you mentioned, Olivia.</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
Mark</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org]
<b>On Behalf Of </b>Olivia S Solis<br>
<b>Sent:</b> Friday, 17 November, 2017 12:39 PM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> [Archivesspace_Users_Group] Offsite boxes and ASpace</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
Hello all,</p>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
We're trying to figure out a situation that can't be uncommon. We've got a lot of onsite boxes. We've got a lot of offsite boxes. Researchers need to request offsite boxes a week in advance. Many of our collections have nebulous access restrictions like, "Portions
of this collection are stored offsite". I want clarity for our researchers.</p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
We're slowly carrying out a shelf read project and soon will know exactly where every box is. How have some of you all who have all of your containers anchored to locations communicated that something is offsite to researchers?</p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
We publish EAD records to a regional consortium and are working on setting up Aeon to integrate with it and, eventually, the ASpace public interface.<br clear="all">
</p>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
I have thought about adding a physical location tag for all archival objects that have associated offsite boxes stating such, but I don't like this for a couple of reasons:</p>
</div>
<div>
<ol type="1" style="margin-bottom: 0in;">
<li class="x_x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:0in; mso-list:l1 level1 lfo1">
It will look horrible. Whole series and collections that are stored offsite will have this repetitive information in archival object after archival object.</li><li class="x_x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:0in; mso-list:l1 level1 lfo1">
It will not automatically update when the box moves. For various logistical reasons, many of our boxes move around a lot or are slated to move to new locations. The whole point of having box location information in a database is that we only will have to change
the information in one place.</li></ol>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
Even if there's not a good EAD solution, we can point researchers to the public interface. I've not much experience with the public interface, but should it be difficult to customize the box display so that you can see building information associated with a
box?</p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
I'm just curious how other institutions have tackled this problem. I'd like it to be readily apparent to researchers when they need a week to access a box.</p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
Thanks!</p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
Olivia</p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
</div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
-- </p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:9.5pt; color:black">Olivia Solis, MSIS</span><span style="font-size:9.5pt"></span></p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:9.5pt; color:black">Metadata Coordinator</span><span style="font-size:9.5pt"></span></p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:9.5pt; color:black">Dolph Briscoe Center for American History</span><span style="font-size:9.5pt"></span></p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:9.5pt; color:black">The University of Texas at Austin</span><span style="font-size:9.5pt"></span></p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:9.5pt; color:black">2300 Red River St. Stop D1100</span><span style="font-size:9.5pt"></span></p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:9.5pt; color:black">Austin TX, 78712-1426</span><span style="font-size:9.5pt"></span></p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:9.5pt; color:black">(512) 232-8013</span><span style="font-size:9.5pt; color:#888888"></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>