Feature/fresnel merge properties experimental #1681
Draft
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.
WIP!
fresnel:mergeProperties, allowing values from multiple fields to be indexed into a single merged field.It kind of works together with libris/definitions#548 and a minor frontend tweak but at this stage it's very much a draft. It's untested and the current behavior is different compared to before when using JsonLd.toCard.
TODO:
librisxl/whelk-core/src/main/groovy/whelk/util/FresnelUtil.java
Line 255 in a99a04f
ElasticSearch.recordToChipinFresnelUtil.applyLens. Assuming we still think it's necessary to include adminMetadata for all linked entities._strcoveragebyLangfields from the index and keep only flattened?_topStrbe just_str? See ff67723