Also, once you download the EAD, the parse error tells you on what line the
error occurred; "189" in this case. The problem may not be *right there*
but that will give you a starting point for your search.
On Thu, Jun 17, 2021 at 1:52 PM Valerie Addonizio
wrote:
> I second the tip about
I don't know how much this will help, because I'm not familiar with how
ArchivesSpace integrates with SOLR, but in the past when I ran into a
similar error on another project we needed to increase our SOLR's
maxBooleanClauses configuration (
6XIWYasCu2Aajt9Qqu3OXLiAiFyu6Ufwn67sPl7cHuubelCxakaO0SG9XIJgL1Ax_rrDoK1UkjhXlFI5BzJdHqsSvYA4VRbHeOtDFb51VwZcsbgbY35isi_z2GqZYdMUrN-0s5CdNaXhfU1lo6moX0jewRkb_Qa8FQC7LZDpNbjPyqBuNmiKDFGkGUjf69dXB5HdKuzy_0eUxKrHL7vByHREJTZn7fRUgoUzvCk37LHvRJBj5rcrTPMTWaa4MUqxpSZV4Dhadcf5JZAB07y72yiD-syQFsNtY7-dqWJivx
Agreed. We have 5GB for ArchivesSpace but we rarely touch even close to
that except for really big jobs like generating PDFs of some of our massive
finding aids (1k+ pages). We have 4 processors available but, again, with a
lot of breathing room. That stated, we don't use the PUI.
On Tue, Sep 29,
I don't believe the AS API has a CSV export option, however, I have an XSL
that can turn an EAD into a CSV of archival objects (using the c-levels; it
goes up to 5 levels deep):
https://github.com/seth-shaw-unlv/small-stuff/blob/master/ead-numbered-components_to_tsv.xsl.
You would just need to add
like to talk about this at all.
Seth Shaw
Application Developer
University Libraries, Web and Application Development Services
University of Nevada, Las Vegas
On Mon, May 4, 2020 at 8:50 AM Hoffner, Bailey E. wrote:
> Morning All,
>
>
>
> We’re looking to integra
I wasn't able to attend the Atlas Systems webinar on preparing for
ArchivesSpace 2.7.0. Was the webinar recorded and, if so, when/where will
it be available?
On Thu, Jan 23, 2020 at 1:13 PM Jessica Crouch
wrote:
> [Posted on behalf of our Registered Service Provider Atlas Systems]
>
>
>
>
Side note now that Steve pointed out that port 8081 does work, I recommend
changing the PUI port to "80", the default web port, so users don't need to
add the 8081 port to access your site.
On Tue, Dec 3, 2019 at 10:57 AM Seth Shaw wrote:
> Presuming the OCLC Digital Collec
Presuming the OCLC Digital Collections Gateway is running from an OCLC IP
address, I would check with your systems folks to make sure that host and
port are available outside of your library/campus. I can't reach the
archives.wheatoncollege.edu host address from here.
On Tue, Dec 3, 2019 at 10:42
t;
>
> In that case, for example, we might have one archival object where that
> barcode has been applied. In the Solr index, there will be two documents,
> if and only if that record has been published. But, we can exclude the PUI
> document in the result set with that second part o
gt;
> On Nov 8, 2019, at 10:51 AM, Seth Shaw wrote:
>
> James, I was hoping using the filter as you described would remove the
> duplicate results issue I was having by using the advanced query compound
> search; but I'm seeing the same thing as before.
>
> Running the s
ssue before?
On Fri, Nov 8, 2019 at 7:34 AM James Bullen wrote:
>
> Something like this works for me:
>
> /search type[]=resource type[]=archival_object page=1
> filter={"query":{"comparator":"greater_than","field":"system_mtime","v
Found where I have examples documented:
https://github.com/jasloe/archivesspace-drupal/issues/23. I also describe
my issues with duplicate results on this comment:
https://github.com/jasloe/archivesspace-drupal/issues/23#issuecomment-454869214
.
On Fri, Nov 8, 2019 at 7:24 AM Seth Shaw wrote
To do this you need to use the advanced query parameter which,
unfortunately, is not well documented. There are a few email threads that
describe using the advanced search though:
http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2015-June/001734.html
I've formulated queries
Your guess that "Michigan Women: First & Founders" is causing the failure
is probably correct. ArchivesSpace won't encode those ampersands for you.
We explicitly train our staff to replace ampersands with `` but we
still occasionally see these errors pop up when someone copy/pastes text
and misses
At UNLV we batch export MARC records. The workflow is from before my time
but when I asked about it this was the response:
We have an article that describes the overall workflow (skip to about
halfway through the article) and includes example records in the appendix:
Making date validation a configuration option is a good idea; so those who
want it can keep it but those who need to turn it off, can.
On Fri, Jun 15, 2018 at 8:30 AM, wrote:
> If I may chime in. It would help if AS would allow something like
> February 30, any year as the unknown date. I
. If someone wants to port the code to
Ruby, make the necessary configuration pages, and/or generally improve it;
I think there are plenty of people who would appreciate it.
1:
https://github.com/seth-shaw-unlv/small-stuff/blob/master/cdm-update-as/cdm_link_as.py
On Tue, May 29, 2018 at 9:47 AM, Hughes
We use the API to download PDFs for our website on a regular basis (since
we don't use the PUI) using a script I wrote (
https://github.com/seth-shaw-unlv/small-stuff/blob/master/as-coll-mint/as_coll_mint.py).
See line 210 (
https://github.com/seth-shaw-unlv/small-stuff/blob
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 <seth.s...@unlv.
In our testing of 2.3.1 no new resources are appearing while searching or
browsing (either from import or manually using the Staff UI). If a resource
has an Agent added it doesn't appear in that Agent's list of related
resources. However, all these additions and changes are reflected in the
If your discovery interface supports OAI-PMH harvesting you may want to
consider that as an alternative to the API or webscraping. We plan on
exploring using it with our new Primo discovery interface (once some other
Primo bugs are fixed first).
On Wed, Feb 14, 2018 at 8:45 AM Tang, Lydia
Our library is in the middle of a migration to ALMA and Primo. When we
migrate from AS 1.5.4 to 2.x (probably late December) we plan to start
using the OAI-PMH endpoint for archival resources. Our Special Collections
Metadata Librarian is also looking for ways to reconcile the ArchivesSpace
Agents
Note that the print to PDF process runs the EAD through an XSLT to
create an XSL Formatting Objects (XSL-FO) document which is then
converted into a PDF. This error may refer to line 3255 your
as-ead-pdf.xsl (which lives in the stylesheets subdirectory of the
archivesspace home directory), but
I'm interested in this too. I was doing some python scripting just
this week
(https://github.com/seth-shaw-unlv/small-stuff/blob/master/as-coll-mint/as_coll_mint.py#L85-L117),
if you want to throw that on the prior art pile.
Also for the prior art pile: I know the folks at the Rubenstein (Duke
*Apologies for cross-listing, trying to figure out where best to post
this type of question.*
I just inherited a plugin that adds a "publish" boolean value to an
extent note to allow recording both linear and cubic feet but only
publish one of them
26 matches
Mail list logo
