<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=Windows-1252">
<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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hello, hello.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’m seeking advice for how to best handle archival object record restrictions in ASpace. During a recent consultation of an archive collection, a number of photographs were identified with being culturally sensitive thus needing to be not
only restricted to public access, but also internal access. In our efforts to be NAGPRA compliant and to follow the wishes of the Tribe, I need to determine best method(s) of restricting these records based on the options available in ASpace. I cannot find
any previous conversations around this topic, and am wondering if others have had to restrict records for similar reasons before or restrict in general. My institution migrated our archive data to ASpace from TMS (The Museum System) a little over a year ago,
so we’re still becoming familiar with the ins and outs of ASpace. We have procedures established for handling NAGPRA/Culturally Sensitive materials in TMS, but not yet ASpace. I welcome any thoughts and suggestions. Thanks!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best,<o:p></o:p></p>
<p class="MsoNormal">Naomi <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt">Cataloguing Manager and Associate DBA<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">Gilcrease Museum<o:p></o:p></span></p>
</div>
</body>
</html>