-
Notifications
You must be signed in to change notification settings - Fork 109
[IMPORT] add user matching step #3775
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
base: feat/import-monitorings
Are you sure you want to change the base?
Conversation
…servers mapping for an import
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## feat/import-monitorings #3775 +/- ##
===========================================================
- Coverage 84.51% 84.43% -0.09%
===========================================================
Files 133 134 +1
Lines 10450 10553 +103
===========================================================
+ Hits 8832 8910 +78
- Misses 1618 1643 +25
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Add a mention to "Import" in PR and commits titles ? |
|
OK merci. |
Yep je vais ajouter un paramètre donnant la possibilité de désactiver le mapping.
Pour l'instant, le champ observers_txt est rempli en plus de l'ajout des correspondances dans |
This PR propose to implement an observer matching process.
Basically 🔎
bib_fields.type_field) with the most similar user found in the GeoNature database. The user must verify and complete the mapping.nom_completproperty is used) in the database is based on thesimilaritypostgresql function. A similarity threshold is set to 0.5, i.e. if a match with a similarity value < 0.5 then it is ignored.New import workflow
This diagram shows how the user mapping works as of today developments
PS. There is a typo.. the t_imports field to store the observers mapping is called observermapping and not obsermapping
Things to do 🎯
id_inventortype_widget