# MRI go live
## Praises (to keep motivation up)
* Carolina says "the database is already starting to finally take very good shape. I like the feel, overall." :smile:
* Everyone is happy with the look, feel, and functionality overall!
> **Note:** Not saying that praises are neccessary, sometime we have to do things even if the whole world is against us.
## Timeline
* 2021-01-27: Notify core team password reminders come tomorrow (Gabrielle)
* 2021-01-28: email should be working
* 2021-01-28: geo mountain registry should be working
* 2021-01-29: core team can be involved
* 2021-02-01: mailchimp integration working
* 2021-02-01..2021-02-04: core team testing, fixing from our side
* 2021-02-05: target public release after applying fixes (if necessary)
* 2021-02-01...2021-02-
## Call 2021-02-11
* Verify link validity
* Lift the mailserver limit for sending mails
* ~~Porting staging to production (template changes)~~
* Maybe possible to add a reply-to into the emails?
* ~~Profile~~
* ~~Expertise heading before methods~~
* ~~Research expertise place~~
* Embed production database into find-an-expert
* ~~Gabrielle modifies find-an-expert~~
## Text to be sent on invitation
* (to be filled in by Gabrielle)
* Google doc exists
* Final, final version:
* https://docs.google.com/document/d/1ZMnbpoOcGAvG-Dokk2UCUn2ONEKpVtcPW3Dg0zvazjA/edit?usp=sharing
## Call 2021-02-10
* Can include the MRI database profile links on mountainresearchinitiative.org if ungleich takes over the joomla page
* When production is embedded: today 1800
* Inviting users
* Trigger password reset
* Inject custom html
* Need to merge content from Uni Bern
* Can be send by Thursday (2021-02-10)
* mri@mountainresearchinitiative.org should be the sender
* We can't use that
* But we can rewrite mri@django-hosting.ch to go to mri@mountainresearchinitiative.org
* Setup the alias email [Nico](/ptZc8turQcW9ZaDjhEM9FA)
* Report at end of Q
* dbeaver -> needs to run on a separate VM
* Together with the mailing list offer
* Schedule
* Send out tomorrow 1300 to Gabrielle
* If confirmed, send out to everyone
* Embed production into find an expert
* ~~!) Remove / replace email on profile~~
* Admin login on production -> dashboard empty
* Needs to work for Gabrielle and James
## Call 2021-02-08
* Integration into website started
* Need to adjust headers
* Embedding
* iframe first
* Alternative option: copying layout
* Timeline
* Fix 500 on 2021-02-09
* Sending out mails on 2021-02-10
* Send quote for email list service
* Collect languages people speak
## Additional information 2021-02-02
She confirmed that we don't need to display MRI roles publicly yet, but may wish to in the future: "Yes, for the profile of the individual, perhaps the item 2 and 3 (MRI roles) might be worthwhile displaying (at a next release step is also fine, does not need to be now)."
```
4 MRI ROLES AND INVOLVEMENT IN MRI PROJECTS (MRI Core team; MRI working groups; Synthesis Workshop and MRI Flagship projects, etc.) - NEW TABLE
This would be a separate table and the fields would be updated by the coordination office and not by the members directly.
Field name Content/format Notes Field visible online New Field
1 MRI role Multiple choice (Coordination Office staff; Co-PI (tick which year); SLC-member (tick which year)) new
2 Member of MRI Working Group Multiple choice (Education for Sustainable Mountain Development; Elevation Dependent Climate Change; Mountain Governance; Mountain new
Observatories; Mountain Resilience; Other (text); Notes (text))
3 Involvement in MRI activity Multiple choice (Adaptation at Altitude; Global Assessments; Conéctate-A+; Contribution to IPCC AR6; GEO Mountains; Synthesis Workshops; Other (text); Notes new
(text))
```
## Additional information / input Caroline
* ~~Referring to additonal database comments.docx~~
* ~~All in this document~~
## Call 2021-02-03
* All split off
* Still need to sort disciplines by alphabet
* ~~Cange Inputs / Participation to UN Conventions~~
* ~~to Inputs / Participation to United Nation Conventions~~
* ~~Non-public fields (exists, but not shown/searchable by public)~~
* ~~Career Stage~~
* ~~Year of last degree graduation~~
* ~~Affiliations~~
* ~~To be moved up~~
* ~~Remove the email address~~
* ~~For data protection~~
* ~~Contact form to contact expert~~
* ~~Accessible by public~~
* ~~Via captcha~~
* ~~Semantic / target~~
* ~~Rename Disciplinary Expertise to Disciplines~~
* ~~On the profile page (not to be changed on the search)~~
* Expertise in the profile
## Done items (2021-02-01)
1. Ensure that core team is on production (source: MRI\ core\ team\ emails\ 5Nov2020.xlsx) ~~<mark>I noticed identified that the core-team people missing on MRI Expert DB is because they are not in [MRI-Person Export (11,472 recs) 27Oct2020.xlsx](https://redmine.ungleich.ch/attachments/3749) (the latest snapshot of the current system). But, I would add them manually there.</mark>~~ **Added**
1. ~~Give James Thornton administrative access~~
2. ~~done 2021-01-29, 1307~~
1. ~~Need to remove "Is geomountains member" (redundant, as the entry itself constitutios a geo mountain registry entry) from the geo mountain registry~~
* 2021-01-28
* Removed
1. ~~Import the geo mountain registry from Members_list_live.xlsx~~
* 2021-01-28
* Can be checked at https://mri.django-hosting.ch/mri/expert_management/geomountainsregistry/
1. ~~Introduce mailchimp newsletter synchronisation~~ **<mark>DONE</mark>**
* a) ~~if a user selects the newsletter on django -> ensure that the subscription exists on mailchimp~~
* b) ~~if a user is subscribed to the newsletter in mailchimp -> tick the field in django (this can be a regular celery task)~~
* c) ~~if a user unticks it in django -> remove from the newsletter~~
* ~~2021-02-01~~
## Fixes 2021-02-02
1. ~~for adding photo, could there be a suggestion of Format: .jpg Size: 300x350 pixels <mark>Hopefully, we wouldn't need that now. You can confirm that by setting up your profile picture on https://mri-staging.django-hosting.ch</mark>
2. Need to add a hint at the right places~~
## New items 2020-02-02
1. ~~Splitting Expertise in Advanced search
2. For each expertise category have a search field~~
1. ~~Sorting Expertise categories in the profile by alphabet
4. Display
5. And update~~
1. ~~Text changes -> shortening
2. "I would like to join the MRI Early Career Researchers (ECRs) fellows group (for enrolled students, practitioners, or scholars within 5 years of obtaining last degree).""
2. "I allow the MRI to contact me about my profile and link to it in its communications channels (website, social media, newsletter article). "
2. "I would like to be added to an experts registry for the MRI to connect me with external requests for consultancies, expertise, policy inputs, speaking roles, or interviews."~~
10. ~~Modify "Inputs or participation to un conventions "
11. to "Inputs or participation to UN conventions"~~
1. ~~Remove the newsletter subscription tick box (redundant) (there are two fields - one )~~
4. ~~Remove double "ss" from the models
5. Probably name the models singular
6. Verify for each model in the admin that they are correctly pluralised~~
6. ~~Mountain ranges of expertise BEFORE interests
6. In the profile
7. And in admin~~
9. ~~Visual changes
2. A bit more whitespace between logo and MRI Expert database (top left part)
3. A bit white space before search button (both simple + advanced)~~
10. Billing changes
4. Database hosting instead of Django Hosting
11. ~~Is staff -> does not show "admin" link
3. Missing for Gabrielle and James with staff=true
4. Maybe wrong if on is_superuser or similar?~~
12. Allow Staff to change a password of a user
5. Currently hashes -> need a way to set the password for a user
6. I think in the admin / expert model would be great
7. But does not have to be there
8. Other text fields
9. To be discussed!
9. If "other" field is selected
10. Expertise important field
11. Searchable
12. Maybe joined table of users
13. ~~modify password for ricardohector~~
## Call 2021-02-02
* ORCID can be done, but a bit of work
* Gabrielle can change data in the Disciplinary Expertises parts without problems
* All data on staging is subject to data loss
* Invitation email from DB / mailchimp
* The main/simple search expertise might need a refresh/more intuitive search
## Fixes to be applied / features required
12. Verify that editin expertise in the backend has correct categories
* **Hint from Gabrielle: edit an expert in the back end, using Carolina as an example, the expertise section still does not appear how it should, with the hierarchy in the list of requirements**
* This has one bug left (see below)
* 2021-01-28
* Need to define the correct flow for existing experts to update their profile
* wording and urls
* Also how to send it out individually (mailchimp vs. database )
* 2021-01-29
* Reporting: Add DB export as .csv
* Add DB export as .txt
* Add DB export as .xsls
### Input 2021-01-29
* MRI logo appears a bit small, and the font may not match that of the rest of the website.
* list of areas of expertise sorted alphabetically
### Input 2021-02-01
* Alphabetically sorting
* For expertise (frontend in the js search)
* The categories ( Atmospheric sciences before Cryospheric sciences ) in the backend and in the profile
* In each subsection / expertise section as well
* Mountain ranges of research interest
* Inclduding the science categories
* Expanding sections (?)
* Hiding expertise
* Make "I allow for my profile to be publicly visible in the MRI Expert Database"
* Make users react on it
* Bold or top
* Moving it to the top
* Photo & Profile
* Similar concern regarding the newsletter
* Being able to batch reset passwords
* a django command (?)
* Bounces to Gabrielle
* Rewrite on mri@django-hosting.ch
* geomountains.org
* Copy of MRI
* But distinct page
* mri.django-hosting.ch needs to be embedded on https://mountainresearchinitiative.org/find-an-expert
* ~~Under ORCID, the idea was to link to the ORCID registry or to allow for the person entering their ORCID to automatically connect with the ORCID registry to retrieve details, and have the ORCID logo etc alongside the name/link (this I have I seen in other websites, for e.g. at Frontiers they link directly to my ORCID and has the green ID logo https://loop.frontiersin.org/people/1077313/publications). Here is a link to ORCID on steps for this integration: https://info.orcid.org/documentation/integration-guide/getting-started-with-your-orcid-integration/. So far what we have is people just copy paste their ORCID URL, which is not then presented as an active URL (cannot click on it from my profile to take me to my ORCID profile)~~
* This is a longer item / post release
* Disciplinary expertise section: could we also make the parent category ‘clickable’, in case the colleagues wish to identify with the whole category? E.g., someone can select a check box next to Atmospheric sciences, if they want. Remove Pollution from under atmospheric sciences (throughout DB). All expertise categories need Other (in profile update form), instead of one big Other expertise box at the end.
* ~~Under assessments, could we add a tickable category “Other”, and allow a single line text field there for the colleagues to specify this other assessment, we later see if these can be added to the list)~~ **in TODO**
* ~~Under conventions, please spell out “un” to United Nations (in capital letters)~~ **in TODO**
* ~~Under Mountain Ranges of research interest and expertise, please re-order to make sure we have ‘expertise’ first and before ‘interest’ as people scroll down the expertise panel. (this is true for update profile form but also for search and advanced search). Should people be listing other mountain ranges by separating the content by commas? Or insert a new entry in a new line? Perhaps an instruction could be offered in brackets. Could the text box be made smaller, too?~~ **in TODO**
* ~~Search and Advanced search: This is very cosmetic – but in the search portal, could we have a bit of space between the MRI logo and the word MRI? (a couple of spaces). And same for the “search” button…could there be some spaces between the button itself and the text box above it?~~
* ~~Could the database hosting invoice say "Database hosting" instead of just Django hosting?~~
* ~~James Thornton does not see "Admin" when he logs in, despite having "Staff" checked. He needs admin access as soon as possible. He notes that the table name should be GEO Mountains Registry (not Geo). Also, why do many of the table names have an extra s on the end? Will this go away in the final version?~~
* ~~This is also a problem for me, Gabrielle Vance; I have admin access as App, but I checked Staff on my personal profile but don't see admin when I log in~~
* ~~In Mountain ranges of research expertise and Mountain ranges of research interest, please change "Great Dividing Range" to "Great Dividing Range (Australian Alps)""- I made this change and see it in profile update and search, however, in regular and advanced search this is now at the end of the list of ranges, instead of in alphabetical order~~
Looking at "Role and involvements" in admin, I would like to edit some of the black titles, but don't think I can; could they please be changed to table title "Roles and involvements"
"SLC Member"
"Co-PI Year"
"SLC Year"
"Working Group"
"Other Working Group"
"Working Group notes"
Thank you!
Just got more feedback on expert profiles from Carolina, will need to send as an email as it's an annotated profile image, and add items here as well:
~~We can not display email addresses. We need to implement a “Contact Expert” button and redirect to a contact form instead, if people wish to email this person (could this go to their email as stored in the database, or to mri@mountainresearchinitiative.org?)~~
~~These items on career stage and year of graduation are for the MRI office only, to identify ECRs - not for display~~
~~Could we bring up affiliations to be directly below the person info and above the expertise section?~~
~~Looks a bit odd to have Disciplinary expertise above “Expertise” as a sperate field….maybe we simply call it “Disciplines?~~
~~Mountain ranges of expertise (above (interest) are important to list, I guess this will come up if I fill this field myself.~~
-End Carolina
To clarify re: MailChimp: the initial invitation for current members to update their profiles will come from the database itself, correct? Are we able to send reminders from the database itself? We understand we can send a news flash and reminders to our newsletter subscribers, but they are not all DB members.
I ask because when we thought, previously, that the invitation would be through MailChimp, Grace imported the list of DB experts' emails to MailChimp, which makes our monthly MailChimp bill higher.

### Reporting
The MRI CO needs to be able to:
* Export data in .txt, .csv, .xlsx
* Export changes in .txt, .csv, .xlsx
* Generate and compare quarterly reports
* Generate and compare monthly reports
* Generate reports for specific, designated time periods
* Filter data by the fields in the database structure
* Filter data by month, quarter, and other specified time periods
* Query the database and export the results
* Maybe using https://dbeaver.io/
## Fixes that need clarification / some preparation
* View changes (and approve or decline them? We would appreciate a developer’s feedback on this)
* This has not been implemented and might need a redesign of the app, as there is no "intermediate state" - changes are directly published at the moment
* Receive email notifications of changes at mri@mountainresearchinitiative.org, with the option to add/change additional email addresses
* Need to add a trigger on changes
## Input from Gabrielle (unsorted)
In the admin view, we need to be able to
* see the number of experts and GEO Mountains registry members, which we report on a quarterly, yearly, and multiyear basis;
* total members, new members;
* for more complicated member statistics, it sounds like we can use dbeaver to query I see now that at the bottom of Experts is a total number, which is great
* viewing changes is fine, we don't need to approve or decline them
## Call 2020-01-27
* ~~Geo mountain registry~~ <mark>DONE</mark>
* ~~Need to check for duplicates~~
* ~~Simple import~~
* ~~Members_list_live.xlsx~~
* ~~Need to add a search field for user~~
* ~~Need to remove "Is geomountains member" (redundant, as the entry itself constitutios a geo mountain registry entry)~~
* "I would like to receive monthly MRI Global Newsletters and Newsflashes from the MRI"
* Create a mailchimp integration
* AR ungleich: compare current entries with the ones in the newsletter
* Do not add newsletter members to the database
* Do add members from the database who checked the field to the newsletter
* Check in the current newsletter list if a member is subscribed -> if yes, update the database
* Define where to trigger the initial announcement message from
* From within mailchimp
* From within Django directly
* Or from within Django with interaction of mailchimp
* AR: feedback today
* Backend experts / Expertise bug
* "Disciplinary expertise" - not field, but a HEADING
* Reorder Disciplinary Expertise before Expertise in the profile VIEW
* AR Gabrielle
* AR Gabrielle: need keys and credentials for accessing mailchimp/mailchimp API
* Need to be able to export database ("snapshot")
## Done log
1. ~~It's most important that we can add, delete, edit, and search for experts by name.~~
* Adding, deletion, edit and search is supported in the backend: https://mri-staging.django-hosting.ch/mri/expert_management/
15. ~~able to see the number of experts~~
* See https://mri-staging.django-hosting.ch/mri/expert_management/user/
16. ~~able to see the number of GEO Mountains registry members~~
* See https://mri-staging.django-hosting.ch/mri/expert_management/geomountainsregistry/
17. ~~View members’ profiles~~
* Is possible on https://mri-staging.django-hosting.ch/user/nicoletta/
18. ~~Edit members’ profiles~~
* Is possible after login
19. ~~Link to members’ profiles~~
* Is possible https://mri-staging.django-hosting.ch/user/USERNAME/
20. ~~Edit the profile update form and new member join form~~
* This needs programmatic changes / changes to the database
21. ~~Edit expertise categories based on member feedback~~
* Possible in the backend: https://mri-staging.django-hosting.ch/mri/expert_management/
22. ~~Edit the table 4 MRI ROLES AND INVOLVEMENT IN MRI PROJECTS (MRI Core team; MRI working groups; Synthesis Workshop and MRI Flagship Activities, etc.)~~
* Is possible in the backend: https://mri-staging.django-hosting.ch/mri/expert_management/roleandinvolvement/
23. ~~Edit the table 5 GEO Mountains REGISTRY (separate table connected to #4, above, by a key~~
* Is possible in the backend: https://mri-staging.django-hosting.ch/mri/expert_management/geomountainsregistry/
1. ~~be able to edit the Geo Mountains registry and MRI roles table in the backend~~
* Note Nico: this *should* already be possible -> verify
* https://mri-staging.django-hosting.ch/mri/expert_management/geomountainsregistry/
* https://mri-staging.django-hosting.ch/mri/expert_management/roleandinvolvement/
6. ~~Adding aggregated ranges (source: Aggregated_ranges_Grêt_Regamey_Weibel.xlsx (9.01 KB))~~
* You can check that either in Search i.e https://mri-staging.django-hosting.ch/ or https://mri-staging.django-hosting.ch/create-expertise/
2. ~~Align wording for is public and co. (table points 18/19)~~
* See https://mri-staging.django-hosting.ch/update-profile/
4. ~~Signup page: checkbox for "I would like to subscribe to the MRI Global Newsletter" instead of "Do you want to subscribe to Newsletter?"~~
*. See https://mri-staging.django-hosting.ch/accounts/signup/
8. ~~Allow to edit mountain ranges in admin~~
* https://mri-staging.django-hosting.ch/mri/expert_management/mountain/
~~12. (similar to before) Ensure expertise is correctly classified~~
## Post go live
* Adjust the Joomla template for adjusting the template width
* Google maps API keys
* Resize VM (disk, ram)
* Quote mailing list
* Quote dbeaver (setup, hosting)
* Access statistics?
* Cors header fixes
{"metaMigratedAt":"2023-06-15T18:58:50.077Z","metaMigratedFrom":"Content","title":"MRI go live","breaks":true,"contributors":"[{\"id\":\"9dc011c6-a41a-44b5-a445-1d78ed6821e6\",\"add\":14310,\"del\":3926},{\"id\":null,\"add\":18378,\"del\":7828}]"}