-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FGS/Solr Config Precludes "Islandora Collection Search" from Working #213
Comments
|
Yes, that's true @noahwsmith. However, I believe that in ISLE v1.1 all of the described edits are already in place, but within The Fedora logs warn that I hate it when that happens. I wish this were an ERROR rather than a WARNing. It really should not be tolerated. I'm going to reset my staging server, re-introduce my "fix", and see what happens. There is still one small bit of mystery here to unravel. |
Ok, terrific, so it sounds like the issue might be that this line is extraneous If this is verifiable we can probably modify that file as it is pulled into the system as we do for these config variables: Another option would be to submit a patch to DGI and see if they'll update their repo. Cloning an ICG version would just put us on the hook to continue to maintain it. |
OK, here's the rest of the story, so far... 17) Eureka! Fixing the "...imported more than once..." appears to have fixed this problemI found that in a pristine ISLE v1.1 stack
Then I repeated Steps 2 through 16, with abbreviated, updated results posted below.
Now, let's see how our
Conclusions
|
I think this might be hard to fix, but it's worth filing a ticket on their repo for it: https://github.com/discoverygarden/islandora_transforms @McFateM - do you mind summarizing it there so that it gets on their radar? They might have a suggestion or work around, as you're probably not the only on who will run into this. Thanks! |
Issue description
I believe that our current FGS/Solr config in ISLE v1.1 does not work properly with the optional "Islandora Collection Search" module. This module introduces a Solr field typically named "ancestors_ms", and this field is used to identify which collection(s) an object belongs too. In a pristine ISLE v1.1 instance there are warnings in the Fedora logs that I believe are indicative of the system's inability to successfully generate this Solr field in newly ingested or re-indexed objects.
For an issue, describe steps to reproduce the issue
Sorry for the length...
Solr RELS-EXT Warnings
Steps to repeat this error are as follows:
0) Made a fork and local clone
First I forked the
ISLE
to https://github.com/McFateM/ISLE-1, then cloned theISLE-v1.1
branch of that fork to my staging server,DGDockerX.grinnell.edu
.1) Upgraded my staging server to
Docker version 18.09.3, build 774a1f4
2) Cleaned up Docker and confirmed
Confirmed. No traces of previous Docker elements left.
3) Did a
docker-compose up -d
on an UN-MODIFIED clone of ISLE v1.1The Fedora logs (I viewed them using Portainer) showed this warning, but none others:
Containers > isle-fedora-ld > Logs
4) Complete the site build
5) Checked the Fedora logs again
Having done NOTHING but spin up the new site, the Fedora logs reported one set of warnings (like the group shown below) for each of the 13 "standard" objects now in the repository.
Containers > isle-fedora-ld > Logs
This is the same set of warnings I've been seeing for the past week.
6) Added a random object to the repository
I selected a .png image and added it to the
islandora:sp_basic_image
collection. I enteredBasic Image Test
as the object's title. A new group of warnings was generated:Containers > isle-fedora-ld > Logs
The new object appears to behave as it should, and in spite of the warnings, it appears to have a full-complement of data in Solr. However, my concern stems from introduction of the
Islandora_Collection_Search
module, as it relies on a simple modification to the FGS/Solr config in order to transform and subsequently index 'parent' data gleaned from RELS-EXT. My hypothesis is that these warnings become significant ony if/when the aforementioned module is engaged.To test this hypothesis I...
7) Added the
Islandora_Collection_Search
module to my site8) Returned to the site as User 1 (Administrator) and added the
Islandora Collection Search
blockThe path for making this change was: https://dgdockerx.grinnell.edu/#overlay=admin/structure/block
I saved the aformentioned block into
Sidebar first
and returned home to https://dgdockerx.grinnell.eduThe
Islandora Collection Search
block appeared in the left-hand sidebar.9) Used the new search block to look for "test"
This is a Solr search through all collections. It returned one object, my image from Step 6.
10) Configure the
Islandora Collection Search
At https://dgdockerx.grinnell.edu/islandora/search/test?type=edismax#overlay=admin/islandora/tools/collection_search I accepted the default
Ancestor field: ancestors_ms
, setGSearch Endpoint: http://dgdockerx.grinnell.edu:8081/fedoragsearch/rest
, setGSearch User: fgsAdmin
, setGSearch Password: ild_fgs_admin_2018
, and checked ALL of the remaining boxes before concluding by clicking theConfigure
button to submit the form.11) Cleared the Drupal cache and searched again
Then I returned to the site and repeated Step 9 for
All collections
. Results were the same... my one item was returned.12) Test again with the object's parent collection selected
Repeating Step 9 but with
Basic Image Collection
selected. This returned 0 objects! Me thinks I smell a fish.13) Turn on generation of
ancestors_ms
infoxmlToSolr.xslt
and restart the stackRemove the comment markers from the three lines that now read:
Then...
14) Check that
foxmlToSolr.xslt
changes are presentConfirmed.
15) Re-index all content
Visit http://dgdockerx.grinnell.edu:8081/fedoragsearch/rest?operation=updateIndex and click on
updateIndex fromFoxmlFiles
. The screen should showUpdated number of index documents: 14
.16) Check the Fedora logs in Portainer again
Visit https://portainerx.grinnell.edu/#/containers, click on
7 Containers
, and the "logs" icon forisle-fedora-ld
.Bad news... more warnings, including:
While all of these warnings are troublesome, it's my belief that the
Failed to transform...
warnings are what's keeping the sytem from generating theancestors_ms
field that Solr needs to makeIslandora Collection Search
work.I'll continue this story as I try to find the root cause of these warnings and find a fix for this condition. I'll start with trying to identify and eliminate the original "duplicate" include warning...
RELS-EXT_to_solr.xslt is included or imported more than once
which is still present in the logs.What's the expected result?
Newly ingested objects, or those re-indexed using FGS/Solr, should have a populated
ancestors_ms
field so that they show up in Solr searches that are restricted to look only within an appropriateparent
collection. This is the primary purpose of theIslandora Collection Search
module.What's the actual result?
The warnings included in the description above, and no
ancestors_ms
field for the module to key on.Additional details / screenshots
None at this time.
The text was updated successfully, but these errors were encountered: