Populate Search Index issues

18 views
Skip to first unread message

an...@andysteven.com

unread,
Apr 20, 2021, 6:52:12 PM4/20/21
to AtoM Users
Hi there.

Ubuntu 16 and Atom 2.4 - system uptime in excess of 2 years so usually trouble free.

No issues with the system other than we can no longer search on content contained within the General Notes field.  That is when we enter a keyword into the browser global search it does not locate the record.

However if we run the following command in the global or advanced search it locates the record without any issue.

generalNotes.i18n.en.content:"keyword"

If we follow the maintenance commands for php symfony to clear cache and then repopulate it runs fine (one error) but otherwise no issues.

php7.0-fpm, memcached, nginix, atom-worker services all restarted.

Web interface works fine but still unable to get the general search to locate text from the Notes fields.

Is there something else I need to check but otherwise the system appears to work fine - just not providing any results for searches in the usual way we are used to.

Thanks so much

Andy

Dan Gillean

unread,
Apr 21, 2021, 9:24:47 AM4/21/21
to ICA-AtoM Users
Hi Andy, 

As I recall, this was a known issue in release 2.4, that was addressed in later releases. Please see: 
If possible, the best solution would be to upgrade to the latest release. There are a number of other improvements along the way - in the latest 2.6.4 release for example, there are improvements to searches with stop words, and improved alphabetic sorting in search/browse results. 

If you're unable to upgrade, you might be able to apply the related pull request as a local patch. Remember to restart Elasticsearch and PHP-FPM, clear the cache, and re-index if you try this approach - and please make sure you backup your data before making code changes on a production instance

Cheers, 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056
@accesstomemory
he / him


--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/260cc32b-c78c-4e53-8d9c-6ad966d77150n%40googlegroups.com.

an...@andysteven.com

unread,
Apr 21, 2021, 10:28:10 AM4/21/21
to AtoM Users
Thanks Dan.  Really appreciate your helpful response.
I will probably do both - patch and create a clean 2.6.4 build and then move the database across.
Is there specific instructions to take the old database across as I noted that the database is now utf8mb4 so I want to be 100% sure I know the process to take the old database across to the newly built clean install on 2.6.4.

Best wishes.

Andy

Dan Gillean

unread,
Apr 21, 2021, 11:54:53 AM4/21/21
to ICA-AtoM Users
Hi Andy, 

So long as you follow the Upgrade instructions closely - especially the part about dropping and recreating the database before loading your sqldump and running the upgrade task, then the schema migrations should handle the change in collation formats just fine. See step 3 and onward here, for example: 
Cheers, 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056
@accesstomemory
he / him

Reply all
Reply to author
Forward
0 new messages