* we disabled `community-submission` requests in Invenio-Config-TUW
* selecting a community through this field would result in some HTTP
  calls returning 400 code responses with vague error messages (which
  are currently ignored in the deposit form JS as well)
* so instead we just hide the field in the UI altogether (the API is
  guarded by the above mentioned settings)
* the CSS selector is pretty bad, but I couldn't identify a much better
  one...

* replace the network request to doi.org

* use more modern test fixtures that take care of initializing the
  app and extensions automatically
* throw out some tests

* as a fallback, initialize a new one

* import new *.{overrides,variables} files from Invenio-App-RDM rather
  than Invenio-Theme if they exist, for more aligned styling

* records can only have a single owner in v12

* also, allow Flask 2.3+

* apparently it's not always initialized

Tsepelakis, Sotirios authored 1 year ago and Moser, Maximilian committed 8 months ago

* The `.overrides` and `.variables` files that belong to rdm's theme are already imported in our custom corresponding file
* This was causing a stack size exceeded error when on app-rdm v12

* also remove Flask dependency, because that's already covered

* it hasn't been true for a while that records can be self-published
  without review

* starting with Invenio-Config-TUW 2024.1.1, the TISS ID is stored in
  the user profile

* lists some user information: name, email, curation consent setting,
  and TISS ID
* allows adding and removing the "trusted-user" role
* of course, only accessible for admins

* Pipfile isn't taken into account when installing Python packages via
  `pip install`, so the Flask-Session-Captcha pin wasn't taken into
  account in our deployment