Weird – I just verified that this happens this on my local instance, but
haven’t been able to find the thing causing this issue.
Looking in the code, it looks like there might be an in-process or forthcoming
syntax for doing date ranges with this as a keyword?
That's it, Christine. One of our repositories does have an ampersand in the
name. I just tested the other repository in our instance, that does not
have an ampersand in its name, and the report was generated successfully.
Thanks,
Patrick
On Mon, Jul 29, 2019 at 10:49 AM Christine Di Bella <
Hi everyone,
I am having the same issue and I am not sure it is related to the use of
ampersands at all. I created a test accession record and gave it a
collection name of "Test" and unique ID of "123456789" with all other
fields blank and am still getting the error message below. Please note
Dear Kate,
Many thanks for engaging with this and for your helpful suggestions- we're very
grateful for your advice,
Best wishes,
Natalie
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
On Behalf Of Bowers,
Kate A.
Sent: 25 July 2019 17:45
To: Archivesspace Users Group
