We’ve had some issues with certain searches in the staff interface ( v2.6.0 )
and I wonder if anyone else has observed this.
We were getting proxy errors on some searches from the Staff web app.
We are adjusting the proxy timeouts in apache to get around this, however,
finding that some
Hi Dave,
Thank you for the suggestion, which somehow had not occurred to me. I will
do some experimenting with it this afternoon! I've identified 470 different
resource records we have that potentially have this problem, so I'm
absolutely looking for the most efficient way to fix this.
Thanks!
This is limited to _published_ AOs, so if you want to get all of them, you’d
probably need to use something like
https://archivesspace.github.io/archivesspace/api/#get-a-resource-tree and then
walk down the tree and get uris/ids manually.
--
Dave Mayo (he/him)
Senior Digital Library Software
No joy then, I’m sorry to say. Honestly, since the API is going to be in the
mix to use eventually, I’d suggest looking at this endpoint:
Hi Dave,
Thanks for your response! Looks like we're running MariaDB 5.5.60.
On Fri, Sep 20, 2019 at 8:58 AM Mayo, Dave wrote:
> It’s possible, but I think to do it in one query requires recursive common
> table expressions – what version of MySQL/MariaDB are you on?
>
> I wrote a thing that’s
It’s possible, but I think to do it in one query requires recursive common
table expressions – what version of MySQL/MariaDB are you on?
I wrote a thing that’s almost this except I was getting container info attached
to the AOs rather than info from the AOs themselves, I can probably find and
Hi all,
I have been trying to figure out a database query that will list all the
archival objects in a resource record's display_strings and their
associated ids in the order that they appear in the resource record. This
has proven more challenging than I thought. I can't find the magical query
