-
Notifications
You must be signed in to change notification settings - Fork 71
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
Search within a collection #1275
Comments
@mjordan We are doing this via Collection as a facet. Does that suffice, or do you have something else in mind? |
It suffices for me, but since a lot of other Islandora 7 sites use the collection search module, it might be good to hear from some them. I'll ask on the email list. |
I think facets are fine...but some might just want a search when landing on a collection page not after a search...so how about making a view block that uses the id for a filter |
Facets are great, and I love how easy Islandora makes to search my entire repository at once. But almost all of my collections have a use case where the user is visiting just a single, unique collection and would like to search the contents of that collection without having to eliminate all other collections by facet. For a user, it would seem to be best to allow the searching of a single collection to be seamless when visiting that collection. |
Not sure how, but I agree that this would be quite useful for Islandora 8. |
I believe you can do this with views and context.
I hope this is what you all had in mind. I'm fairly new to Islandora and I've been just playing with all the Drupal configurations. I'm also not sure how your "collections" work, I've been doing this with content types, so I hope it's all applicable. |
I did a view/block that I only added on collection pages to list all the members of that collection using the Advanced "Contextual filters" filtering on the member_of field I didn't open it up for searching but you can add that by exposing the form like @bstrakosova mentioned above and adding fulltext or other filter criteria in the regular view |
Great advice! I totally forgot about the Contextual filters. This way we don't have to create View and Context for every collection and just do it all at once. |
How would a member_of contextual filter work if you have multiple layers nested? Ie. a collection with items that have items nested within (such as paged content with pages)? |
good question, can you not give your nested pages two member_of tags, one for the book level and one for the collection level? since they have different models "Paged Content" vs "Page" you can still display only the top level but search all levels I haven't tried that but it should work |
Using multiple member_of tags usually breaks breadcrumbs, so I would advise against it. Another possible option (brain-storming here, this is untested) but I wonder if you can get search_api_solr to index the breadcrumbs as a SOLR field and then build a search with a hidden filter for all items where the root node in question appears in that field. |
we don't have page level metadata and haven't yet implemented ocr so that is why we haven't run across this issue...can another tag be used in place of member_of....we have several tags that have similar functions..because of granularity...we use member_of for direct level up but we also have a "Partner Repository" tag because some of our "Partners" have multiple collections and we would like to be able to target all Partner Objects at the same time |
I guess one way around the issue is to assume that you only want to surface direct children of a collection as opposed to items which are children of children. |
once OCR comes into the picture, I see the need for targeting children of children especially the child pages of books. |
you can also decide how important breadcrumbs are to you....that would make using multiple member_of more feasible, not an ideal situation but still a workable option |
Regardless of breadcrumbs, I think multiple member_of relationships to represent both child and grandchild relationships wouldn't follow with the concept of graph representation. |
You don't have to use the member_of field, you can create new entity
reference field that would point to the collection and use that field in
the View.
Dňa st 25. 9. 2019, 18:54 Eli Zoller <notifications@github.com> napísal(a):
… Regardless of breadcrumbs, I think multiple member_of relationships to
represent both child and grandchild relationships wouldn't follow with the
concept of graph representation.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1275>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALXT3SENOHXMWLLOHMZNJNDQLOJT7ANCNFSM4IXC7EMQ>
.
|
@bstrakosova that is what we did for another reason but it would work here too.... |
@seth-shaw-unlv the https://github.com/discoverygarden/islandora_collection_search module indexes 'ancestors' by walking up the parental chain. Drupal 8 ships with an "Index Hierarchy" search processor already that applies to taxonomies, which we could probably use as a basis for |
As part of the IslandoraCon 2019 use-a-thon a capable team of Islandorians (@alxp, @birkland, Katie Gucer and myself) generated this. It is a work in progress, please review and give us any feedback. |
Here are the work products for the Islandora 8 Collectioneers' submission to the Use-a-Thon:
|
The text was updated successfully, but these errors were encountered: