Hi Alan,
In my previous position, we used the update-feed endpoint to trigger updates to
metadata in our digital repository when a related ArchivesSpace record (i.e.
for an object that is digitized) was updated. I can put you in contact with the
lead developer on that project off-list if that
Hi Paige,
You can do this with plugins, by adding extensions in the "schemas" directory
to add to the default behavior for a data model.
Here's an example from my previous institution that extends archival objects so
that component_ids are required:
Hi Mark,
I think it runs on Bootstrap 3, because Bootstrap 4 things that I've attempted
to use in plugins don't work unless I supply the CSS directions myself. -k
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Mark
Cyzyk
Sent:
Hi Ron,
ArchivesSpace doesn't require that both Begin and End fields are populated when
the date type is Inclusive. We have a handful of dates in our database with an
expression of "after" or "post" a particular year, where we've set the Begin to
that year and left the End null. As far as
Hello everyone,
I'm also interested in what others are working on in this area. I have ideas
but none of them are even close to practice yet. thanks! -k
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Natalie
Adams
Sent: Monday,
My sense is that ArchivesSpace is so tied to EAD as a data model that a change
to one couldn't happen without a change to the other. Right now it seems to me
like the best solution for this would be to write a plugin that looks for
either a user-defined text field with the content warning in
Hi Tom,
My first thought would be to bump the JAVA_XMX up. I run my local laptop
testing setup with 3 GB. I don't remember what we set the production instance
at in my last shop, but it was at least 4 (and it took some trial and error to
finally settle on something). -k
Hello,
+1 to all of this. Our current use case seems to go the other way -- at Penn
State the tendency is to have processing archivists provide human-readable date
expressions, and that we would like to generate machine-readable begin and end
dates based on that.
I'm wondering how uncertain