Repository navigation
Optionally set key and/or value column. - #471
Conversation
|
Is this then also usable in metafacture-fix? |
|
Only after we add the corresponding options to |
Thanks, but wasn't ready for review yet. Can you have another look? @TobiasNx: Can you do the functional review? |
|
I will do an functional review. |
dr0i
left a comment
There was a problem hiding this comment.
Can you update ./metamorph/src/main/resources/schemata/metamorph.xsd ? This is the scheme helping e.g. XML editors validating a Morph.
Will do, thanks.
Not only editors, Metamorph itself uses it. I just didn't notice since I had foregone the Morph tests. |
|
I am still not sure about where to add the options: I cannot run this yet: https://github.com/TobiasNx/notWorkingFlux/tree/main/multipleColumnLookup Results in : Expected: |
|
You have to specify the separator |
Options go on the |
|
Okay, i tested it. It seems to work. Great. +1 Since I played around with the same file in different directions with sometimes duplicated values what I would recommend is to document that always the last match is selected: https://github.com/TobiasNx/notWorkingFlux/blob/60a00e538569527d88b69cc518d61b4b9ab9410e/multipleColumnLookup |
TobiasNx
left a comment
There was a problem hiding this comment.
+1 But document the selection of last match.
Do you want to provide a suggestion? This behaviour has not changed, it's always been like this. |
f8873c2 to
cbaf9d3
Compare
References hbz/lobid-resources#1461.