-
Notifications
You must be signed in to change notification settings - Fork 51
[FEATURE] Provide structure paths/breadcrumbs to search results #1796
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
Merged
sebastian-meyer
merged 12 commits into
kitodo:main
from
michaelkubina:feature_structure_path
Jan 28, 2026
Merged
Changes from 10 commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
8bd9d18
register new solr field for structure_path
michaelkubina-subhh 9d1ab8c
make displaying of structure_path a plugin setting
michaelkubina-subhh bfd8d2b
compute and index structure_path
michaelkubina-subhh 55aaf2b
retrieve and process structure_path from index
michaelkubina-subhh 57fe90a
index only deepest structures
michaelkubina-subhh 2164450
Merge branch 'main' into feature_structure_path
sebastian-meyer d66f2eb
fix phpstan issue
michaelkubina-subhh 946bebf
fix failing test probably due to camel-case field definition in ext_c…
michaelkubina-subhh b2a6ced
add structurePath field to solr testcase
michaelkubina-subhh b2163ac
Merge branch 'main' into feature_structure_path
sebastian-meyer 56ff77f
Merge branch 'kitodo:main' into feature_structure_path
michaelkubina f539e61
update documentation
michaelkubina-subhh File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Searches now fail with an Oops unless the complete Solr index is rebuilt. I fixed it locally with
self::$fields['structure_path'] = $solrFields['structurePath'] ?? '';.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the report. I opened a new issue: #1851
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dear Stefan,
do you mind checking if the field is actually registered in your LocalConfiguration.php or settings.php respectivly? I believe it isnt. Alternativly you can inspect the "Extension-Configuration" - it should be visible in the "solr"-Tab. Or you manually add
'structurePath' => 'structure_path',to dlf.solr.fields.When there is no such field registered, it should appear after "Maintenence" -> "Flush Cache", as i tried to describe in the migration path to 7.x . Florian did it this way and his configuration was updated.
Searches fail, because in this case it tries to access a field, that has not been applied to your configuration yet. This would have happened to any other field as well, when its not in the configuration.