Thanks Alex. We're using 2.3.1. So it looks like it might be a problem with
our (custom) stylesheet.
Best,
Lynn
Lynn,
Which version are you encountering this issue on? I tried reproducing this
issue on the sandbox (http://sandbox.archivesspace.
org/resources/11/edit#tree::resource_11,
Hello ASpacers,
Just a reminder to please review and comment on this DRAFT specification
for creating logical and customizable title or identifier-based URLs in the
ArchivesSpace PUI: https://goo.gl/jjmtLF. Whether or not you have specific
comments, if this feature is important to you, please
Okay, this is beginning to be like the boy who cried wolf. Please disregard
my last email. Another local plugin that I somehow didn't notice on my
first look for a culprit. (A fresh install worked properly and prompted
another look.)
On Thu, Mar 15, 2018 at 10:56 AM, Seth Shaw
Hi folks,
One of my favorite conceptual things about the ArchivesSpace PUI is that it
lets archives publish their accession records in an outward-facing way so
that researchers can have access to these materials right away, even before
they're included in resource records.
I'm pulling together
Hi Cheryl,
I'll also chime in here - I just got (mostly) through converting a ton of
data that were eloquent data exported to tab delimited text/spreadsheet. We
had a LARGE collection we purchased, and that was what we got with it: a
dump of their eloquent data.
I made use of Stead:
Hi Cheryl,
Oof, that’s rough. I have a few questions, if you don’t mind.
1. Can you provide more detail on why EAD export is impossible? I only ask
because they claim EAD export on their website pretty prominently, and it would
be, I think, much easier than doing a migration from proprietary
