Hi Naomi,

The "Notes" module of an Archival Object in ASpace allows you to indicate 
restrictions on material (Conditions Governing Access and/or Conditions 
Governing Use). As long as there is an Archival Object, you can place a 
restriction at any description level (Collection, Series, File, Item, etc.). Of 
course, this only indicates the existence of a restriction and doesn't enforce 
the restriction itself.

I hope this is helpful!


MSLS in Archives & Records Management
Accessions Coordinator
Rubenstein Rare Book & Manuscript Library
Duke University
leah.t...@duke.edu<mailto:leah.t...@duke.edu> | 

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
<archivesspace_users_group-boun...@lyralists.lyrasis.org> On Behalf Of 
Franklin, Naomi
Sent: Friday, November 11, 2022 1:55 PM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Looking for ways to best handle object 
record culturally sensitive restrictions

Hello, hello.

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!

Cataloguing Manager and Associate DBA
Gilcrease Museum
Archivesspace_Users_Group mailing list

Reply via email to