-
Notifications
You must be signed in to change notification settings - Fork 44
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
Concept mappings: Can't define multiple matches #345
Comments
ps: Here's some version info: iQvoc version: |
Just to add some more background information: When I try to reproduce this issue in version 4.8.2 on http://try.iqvoc.net it works just fine. I can define multiple matches without running into the reported behaviour. So this might be a problem with 4.9.0... |
I can confirm that. Running Iqvoc 4.8.2 locally works just fine. Must be an 4.9.0 specific issue. |
Thanks for the report. I'll check that. |
Should be fixed with 19a5ba9. I also fixed a bug with job creation for non iqvoc federation sources. Can you confirm that? Feel free to reopen this issue if there are any further problems. |
If you edit a concept and define multiple matches, they are instantly scheduled for deletion after you hit the save button (see screenshots). They'll be gone after publishing the new concept version.
If you just define a single match it will be saved just fine. If you then create a new version of the concept afterwards and define another (additional) match, the first one will be purged right after you hit 'save' (there's also a message telling you it's scheduled for deletion).
So as it seems to me there's only the possibility to create one single match per concept? If this was the case in practice it would be a rather painful limitation. So I wonder if this is actually a bug or a feature?
The text was updated successfully, but these errors were encountered: