-
Notifications
You must be signed in to change notification settings - Fork 0
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
Support for drupal data sync #617
Conversation
…o check partner groups
…es/617 Update requirements file for feature/drupal-data-sync
…jango into feature/drupal-data-sync
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #617 +/- ##
==========================================
+ Coverage 94.18% 94.89% +0.71%
==========================================
Files 124 130 +6
Lines 5693 6588 +895
==========================================
+ Hits 5362 6252 +890
- Misses 331 336 +5 ☔ View full report in Codecov by Sentry. |
@jmcarson I added a "member_group" and "uploader_group" fields to the ResearchCenter and PartnerGroup models. When importing new RC/PartnerGroups, you can leave them blank. When updating existing records, don't change the member/upload groups that are already associated (if any). |
Both this branch and a previous branch that I merged in added a 0024 migration, so Django didn't know which to apply. Delete the 0024 migration from this branch and regenerate it following the 0024 migration that was merged in.
Once we start pulling in all user accounts and associating them with a ResearchCenter or PartnerGroup, the tables will get long. Move them into accordion dropdowns like the uploaders and data access lists.
@jmcarson I also want to verify that we'll get an email whenever a ResearchCenter or PartnerGroup is added or updated. Can you check if that's the case, and if not, add it? |
Add audit code and management command for syncing user, research center and partner group data from the gregor drupal site to the gregor django site.