-
Notifications
You must be signed in to change notification settings - Fork 1
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
feature/mx-1387 update identity provider with assign method #34
Conversation
a5129d1
to
f76ceae
Compare
…mmon into feature/mx-1387-sti-provider
Signed-off-by: Nicolas Drebenstedt <drebenstedtn@rki.de>
…mmon into feature/mx-1387-sti-provider
…ert-koch-institut/mex-common into feature/mx-1387-sti-provider
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.
Nice, like in code documentation and explanations. But ticket ACs are still not met, are you gonna take care of this in another branch?: "add backend identity connector in mex-common to get Item.identifier and item.stableTargetID from backend"
yes, there's gonna be more branches. but in the backend and extractor repos ;) |
mex.common.identity.query
functions with~.registry
register_provider(...)
allows mex-extractors and mex-backend to register their ownIdentityProvider
implementationsget_provider()
gets an instance of the currently configured id providerBaseProvider
to cut sqlite tiesdummy
provider tomemory
mex.common.models.base.FlatValueMap
- that was dead codemex.common.identity.models.Identity
- likemerged_id
stableTargetId