It uses JRuby
On Dec 14, 2021, at 11:19 AM, Steele, Henry wrote:
I’m not sure who supports this now—HM?—, but I wanted to check about the Yale
EAD exporter’s potential vulnerability. It’s a plug-in but also has a stand
alone application
On Dec 13, 2021, at 2:01 PM, Blake Carver
I’m not sure who supports this now—HM?—, but I wanted to check about the Yale
EAD exporter’s potential vulnerability. It’s a plug-in but also has a stand
alone application
On Dec 13, 2021, at 2:01 PM, Blake Carver wrote:
Nope, older versions should be safe as well.
Andrew Morrison wrote on 2021-12-14 13:27:13:
> Does anyone know if there is a way set up an ArchivesSpace user so they can
> query the API but they are blocked from logging-in to the staff interface?
My understanding is that this is not possible.
ArchivesSpace does not expose any way to limit
Hello,
Does anyone know if there is a way set up an ArchivesSpace user so they
can query the API but they are blocked from logging-in to the staff
interface?
Thanks,
Andrew.
___
Archivesspace_Users_Group mailing list
I don't think user preferences affect the drop-down displayed when you
start typing. That's hardcoded to sort by title (I agree that relevance
would be better.)
You could try prefixing with a Solr index field name. For example, to
only list resources which have the word /cheese/ in their
The /search/repositories endpoint searches for repositories, so
filtering that to only return locations will always return no hits. To
search globally, say for a location with a barcode of 123456789, you
could use something like this:
/search?q=123456789=1_size=100[]=location
All search
Hi Isobel
In versions 2.8.0 (maybe 2.8.1) forward, there are additional options to set
browse/search sort order that also affect the typeaheads. Go to the dropdown by
your username in the top right and set the default sort column and direction in
either the global or repo settings (depends on
