What Kate said, and also: for anything that we figured out during our
migration, you can check individual EAD files with somewhat better error
reporting by putting them through https://eadchecker.lib.harvard.edu/
--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University
EAD has fewer contraints than ArchivesSpace. Those error messages are not
terribly helpful. At the very end of this article (before the end notes) is a
list of the constraints in AS that will throw an error if your EAD does not
comply:
https://journal.code4lib.org/articles/12239
I think the
Hi everyone,
I don't have access to the server to do a full re-index, but I was able to
access those troubled resource records through the Background Jobs page. Making
edits does make them appear in the search.
Thank you to everyone who helped me on this! I appreciate it very much!
Chelsee
It is probably an empty date tag in the components list. Check to see if it
something like this:
My stuff
This is technically an empty tag since there isn't a date after
"inclusive." AS does not like empty tags. So you will either need to add
title, date, etc. or delete the empty tags. If you
I believe all of the dsc components must have either a unittitle or unitdate.
> On Jan 29, 2019, at 12:16 PM, Ryan Flahive wrote:
>
> Morning Folks,
>
> I’m new to this group as my ArchiveSpace server was just set up a couple days
> ago.
>
> Due to circumstances too lengthy to describe
Morning Folks,
I’m new to this group as my ArchiveSpace server was just set up a couple days
ago.
Due to circumstances too lengthy to describe here, I am manually building this
database from exported EAD files from my Archivist’s Toolkit system. My first
few imports were successful, but then
