Issue resolved. What I neglected to do was add the following to config.rb:
AppConfig[:plugins] = ['local', 'lcnaf', 'aspace-reindexer-main']
Initially 'aspace-reindexer-main' was in a subdirectory plugins/mitre and I
expected that adding the mitre directory would find the files within that
Jerry,
Glad it worked out for you, and apologies for getting your name mixed up as
'Greg'.
Don
Donald R. Mennerich, digital archivist
New York University Libraries
don.menner...@nyu.edu (212) 992-6264
On Mon, Aug 15, 2022 at 6:56 AM Jerry Boggio wrote:
> Issue resolved. What I neglected to
That plug-in does the equivalent of the "Full reindex" process described
here:
https://archivesspace.github.io/tech-docs/administration/indexes.html
So, it is not something you want running upon startup of a production
system, as records will be unavailable until they've been re-indexed,
Hi Don and other ArchivesSpace Users;
Referring to the page Don suggested:
ArchivesSpace Reindexer plugin
This plugin can be used in two ways:
1.On system startup to initiate a reindex
2.Via the api to trigger a reindex
TODO: consider running as a job and making it available that way
Greg,
One easy way to rebuild the index is to install the Lyrasis reindexer
plugin: https://github.com/lyrasis/aspace-reindexer. Once installed, you
can either have it rebuild the index via the startup config or by
the endpoint that the plugin adds to the API. We recently migrated from
3.0.2 to
Hello ASpace Users;
We just upgraded from ArchivesSpace version 2.7.1 to version 3.2.0 and now have
"phantom" records in Resources and Subjects. By phantom I mean records show up
in ASpace, but are not in the database and when trying to view the record
returns:
