rasis.org>
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
On Behalf Of Brian Hoffman
Sent: dinsdag 16 mei 2023 2:27
To: Archivesspace Users Group
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] ID display config options
cluded in the 3.4 release? Thanks again,
Jennifer
On Mon, May 15, 2023 at 1:41 PM Brian Hoffman
mailto:brian.hoff...@lyrasis.org>> wrote:
Hi Tom,
I don’t believe it has worked in 3.3.1 or any previous release. Yes, it should
be working in 3.5 as the work has already been done:
https:
"lost" in the move to 3.4.
Thanks,
Tom
On Mon, May 15, 2023 at 1:00 PM Brian Hoffman
mailto:brian.hoff...@lyrasis.org>> wrote:
Hi Jennifer,
There is an issue with the way those features were implemented, and they won’t
work without some customization in version 3.4.0. There is
Hi Jennifer,
There is an issue with the way those features were implemented, and they won’t
work without some customization in version 3.4.0. There is a fix completed that
will appear in a future version.
Brian
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of
Hi Channing,
asutils is not a gem but a file in the ‘common’ directory. You may just need to
add that directory to your CLASSPATH.
Brian
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Norton,
Channing
Date: Friday, May 12, 2023 at 2:37 PM
To:
Hi Alan,
There is an endpoint that provides a stream of updated records:
http://archivesspace.github.io/archivesspace/api/#get-a-stream-of-updated-records
It is there to enable the indexer to do its work, but perhaps it would work for
your use case.
There is a window during which records can
t 410-704-3340 .
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Brian
Hoffman
Date: Monday, May 1, 2023 at 4:14 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] The best way to implement Solr -
confused by documentation
[ CAUTION: This email is from outs
Library at 410-704-3340 .
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Brian
Hoffman
Date: Friday, April 28, 2023 at 4:34 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] The best way to implement Solr -
confused by documentation
[ C
Hi Eric,
I recommend trying a simpler approach:
First, start solr. For example:
solr start -p 8983
Then cd to where you installed archivesspace and:
solr create_core -c archivesspace -d solr
Once you do that, you should be able to navigate to http://host:8983 and see
the ‘archivesspace’
Hi Brian,
Are you using the backup script to backup your database only, or were you
attempting to backup the Solr index as well? I believe that backing up the Solr
index this way has been broken for some time, and is not actually necessary.
The next version of ArchivesSpace (3.4.0) will have
<< Why does one even have to run a periodic indexer? Aren't there guarantees in
the system that updates are seen through to the index in realtime, do bulk
updates not trigger a refresh of updated records selectively? Reading the code
seems to suggest that updates are queued until processed, does
Hi,
The easiest and recommend way to do this is to place ArchivesSpace behind a
proxy server – typically nginx or apache. The proxy server can handle the
entire SSL layer and you won’t need to expose the Jetty server to the world.
Brian
From:
Hi Kyle,
Not sure if this will help, but your path looks a little unusual. If solr is
installed at `/opt/solr-8.10.0`, then the `solr` executable would typically be
at `/opt/solr-8.10.0/bin/solr`. (Compare with your path apparently being
`/opt/solr8.10.0/solr/bin/solr`.) Perhaps that is the
Hi,
Mizuno is actually never used in a production context, so it would also be fine
to just delete any files you don’t like within the gem’s directory.
Furthermore, after 3.1.1 we made our own version of Mizuno:
https://github.com/archivesspace/mizuno
But 3.2.0 was inadvertently released with
Hi Steve,
This is a known unresolved issue – ArchivesSpace is built on Jruby, the premise
being that it can sit entirely on the JVM and thus be portable as any Java app.
But over the years various gems with extensions have crept into the application
and broken that model – in the case of the
You could also try running this query in MySQL. If you get any results, that
would likely be the problem:
select id, aspace_relationship_position from top_container_link_rlshp where
aspace_relationship_position is null;
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on
Hi Tom,
I share your confusion – I personally do not bother with configsets when I set
up my own solr instances. I think it is an either / or situation – you can use
them if you want, or just create the core you need directly if you have
installed solr natively and have the standard tools:
%
Hi Scott,
It is normal to get a 404 if you make a curl request for the core url, since
the core itself doesn’t have any actions. Try
https://localhost:8983/solr/archivesspace/select
Brian
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of RENTON
Scott
Date: Friday,
Hi Kirill,
That probably means either your instance of solr does not have the ‘core’
specified in your AppConfig[:solr_url] (the last portion of the URL) or your
instance has the core, but the schema is not up to date. You can determine
which is the case by changing the setting
Hi �C the first error in the log (after the warnings) is a known bug that
should be fixed in the next release:
https://github.com/archivesspace/archivesspace/pull/2352
I don’t think that would cause the application to crash though, so there may be
other issues going on.
Brian
From:
Hi,
Have you seen this documentation on configuring ArchivesSpace for HTTPS?
https://archivesspace.github.io/tech-docs/provisioning/https.html
Brian
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Zachary
L Pelli
Date: Friday, July 23, 2021 at 12:16 PM
To:
Hi Peter, James, and Nancy,
I posted a test release (for testing only) that may help with the issue Peter
identified. If anyone wants to test and report back that would be great.
https://github.com/quoideneuf/archivesspace/releases/tag/issue-2275
Brian
From:
Hi Cory,
It might be possible to eliminate the issue with the staff interface by setting
an environment variable. For example:
BUNDLE_WITH="default" ./archivesspace.sh start
I think the issue with the public app is different and is going to require a
follow-up release next week.
I am also
e the note as an XML
fragment, and not accept the edit if it fails. ( I’ve been meaning to get
around to testing this to see if there are any side effects or spurious
rejections from doing this. )
— Steve.
On Apr 19, 2021, at 11:50 AM, Brian Hoffman
mailto:brian.hoff...@lyrasis.org>> wrot
Hi,
We have been trying to understand what to do about cases like the following:
http://sandbox.archivesspace.org/digital_objects/2/edit#tree::digital_object_2
[cid:image001.png@01D73512.22D7F220]
As things are now, ArchivesSpace will allow a value like this, but various
renderings and
Responding to Anna’s original message, I think this issue in JIRA captures what
is probably going on when a two-word search yields more (rather than fewer)
results after filtering by another word:
https://archivesspace.atlassian.net/browse/ANW-1240
From: on behalf of
Blake Carver
Reply-To:
I created an issue for this in JIRA with references to the information shared
by Megan and James.
https://archivesspace.atlassian.net/browse/ANW-1229
Brian
From: on behalf of
James Bullen
Reply-To: Archivesspace Users Group
Date: Monday, March 15, 2021 at 7:49 PM
To: Archivesspace Users
27 matches
Mail list logo
