add support for user attributes on user accounts

[richard-jones]

• Issue: https://github.com/DOAJ/doajPM/issues/4317

---

Add attributes to user accounts

In preparation for Editorial Workflow, this adds the ability for users to have attributes which describe their capabilities

This PR...

• has scripts to run
• has migrations to run
• adds new infrastructure
• changes the CI pipeline
• affects the public site
• affects the editorial area
• affects the publisher area
• affects the monitoring

Developer Checklist

Developers should review and confirm each of these items before requesting review

• Code meets acceptance criteria from issue
• Unit tests are written and all pass
• User Test Scripts (if required) are written and have been run through
• Project's coding standards are met
  • No deprecated methods are used
  • No magic strings/numbers - all strings are in constants or messages files
  • ES queries are wrapped in a Query object rather than inlined in the code
  • Where possible our common library functions have been used (e.g. dates manipulated via dates)
  • Cleaned up commented out code, etc
  • Urls are constructed with url_for not hard-coded
• Code documentation and related non-code documentation has all been updated
  • Core model documentation has been added to if needed: https://docs.google.com/spreadsheets/d/1lun2S9vwGbyfy3WjIjgXBm05D-3wWDZ4bp8xiIYfImM/edit
  • Events and consumers documentation has been added if needed: https://docs.google.com/spreadsheets/d/1oIeG5vg-blm2MZCE-7YhwulUlSz6TOUeY8jAftdP9JE/edit
• Migation has been created and tested
• There is a recent merge from develop

Reviewer Checklist

Reviewers should review and confirm each of these items before approval
If there are multiple reviewers, this section should be duplicated for each reviewer

• Code meets acceptance criteria from issue
• Unit tests are written and all pass
• User Test Scripts (if required) are written and have been run through
• Project's coding standards are met
  • No deprecated methods are used
  • No magic strings/numbers - all strings are in constants or messages files
  • ES queries are wrapped in a Query object rather than inlined in the code
  • Where possible our common library functions have been used (e.g. dates manipulated via dates)
  • Cleaned up commented out code, etc
  • Urls are constructed with url_for not hard-coded
• Code documentation and related non-code documentation has all been updated
  • Core model documentation has been added to if needed: https://docs.google.com/spreadsheets/d/1lun2S9vwGbyfy3WjIjgXBm05D-3wWDZ4bp8xiIYfImM/edit
  • Events and consumers documentation has been added if needed: https://docs.google.com/spreadsheets/d/1oIeG5vg-blm2MZCE-7YhwulUlSz6TOUeY8jAftdP9JE/edit
• Migation has been created and tested
• There is a recent merge from develop

Testing

For testing the migration, the csv files located in this CL google drive folder can be used https://drive.google.com/drive/u/0/folders/1kbDPodh1ZrhrzuccXfHVWbyg8c0iX8Sh

For testing the feature and regression, all the tests from the User Management testbook can be used
https://doaj.github.io/doaj-docs/feature/4317_user_attributes/testbook/index.html#user_management/user_management

Deployment

Configuration changes

N/A

Scripts

N/A

Migrations

python portality/migrate/4317_user_attributes/apply_user_attributes.py [country csv] [language csv]

You will need to have the country csv and language csv provided at migration time, these come from a private editorial spreadsheet.

You may also supply --dry-run on initial migration to determine that it will take correctly.

Monitoring

N/A

New Infrastructure

N/A

Continuous Integration

N/A

[usman-cottagelabs]

Open Requirement in TestQuality

• Test Create a new user.
• Test Edit your own user account (publisher).
• Test Edit your own user account (admin).
• Test Edit another user's account.
• Test User account with journals/applications.
• Test User account without API role.

[usman-cottagelabs]

1 bug found. See the Issue itself for the bug.

[usman-cottagelabs]

@richard-jones
QA complete on this ticket. Bug resolved. See Issue.