I’ll also add that we here at the Rockefeller Archive Center along with some of
our colleagues at the Bentley Library, Artefactual and the ArchivesSpace team
have been working on putting together a specification for building out the
structured rights statements functionality in ArchivesSpace. I
Hi, Jordan,
The Yale ArchivesSpace Committee considered using the rights records before we
proceeded with developing the machine actionable conditions governing access
and use note. Here is a link to the topic discussion in the AS Google Group
list
To clarify on the MARC exporting, our library uses EBSCO discovery as its
main search box into the library collections, and I would like to include
the archives data that is presently in Archon and ArchivesSpace. Since
Archon can export as a MARC record, EBSCO can use that ... but we need to
be
I noticed that importing EAD with this accessrestrict element:
http://www.w3.org/1999/xlink;
xmlns:xtf="http://cdlib.org/xtf;>Access Restrictions
The collection is without restrictions.
Produces this in ArchivesSpace (1.5.1):
*
Conditions Governing Access
Hi Shannon,
We are in the midst of this as well. Our IT is currently trying to move us
from the ASpace default setup to an Apache environment (also so we can sync
with Preservica). It hasn't been easy as they haven't found any instructions
on how to move ASpace over. I can only share the
Thanks: No attributes in that example, but namespace pseudo-attributes may be
causing the same problem.
( My pre-flight stylesheet removes empty attributes but appears to leave the
namespace declarations. )
— Steve Majewski
On Sep 29, 2016, at 5:25 PM, Lara Friedman-Shedlov
