rdmo
rdmo copied to clipboard
rdmorganiser
A tool to support the planning, implementation, and organization of research data management.
I learned something today about reverse proxy setups... ``` # our docs at https://rdmo.readthedocs.io/en/latest/deployment/gunicorn.html location / { proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header Host $http_host; proxy_pass http://unix:/run/gunicorn/rdmo/rdmo.sock; } ```...
`/admin/accounts/role//change/` allow to create sites and users which makes no sense there and should be removed (using hardcoded permissions in the admin class).
### Description / Beschreibung On `/admin/accounts/role/` "all Sites" is shown for "EDITORS" even when the user is only editor of one site.
It appears that if you import a project which uses a catalogue that the importing RDMO instance doesn't know, another random catalogue is used instead without even showing a warning....
It would be helpful if there could be a warning if the same attribute is accidentally linked to two or more questions in a catalog.
Right now `csrftoken` is hardcoded (https://github.com/rdmorganiser/rdmo/blob/main/rdmo/core/static/core/js/core.js#L6), in the new front-end this should be taken from `settings.CSRF_COOKIE_NAME` and `settings.CSRF_HEADER_NAME`.
Refs: - https://redux.js.org/usage/migrations/migrating-rtk-2 - https://redux.js.org/usage/migrating-to-modern-redux
We should check if `Content-Security-Policy`, `Strict-Transport-Security`, `X-Permitted-Cross-Domain-Policies`, `Feature-Policy`, `Permissions-Policy`, and `Cache-Control` can or should be used with RDMO and update the documentation accordingly.
### Rationale / Begründung A project hierarchy with multiple nodes is not displayed properly. Probably, by changing the ordering it can be improved.  ### Affected Users ### Minimal functionality...
Metadata
Owner
Metadata
A tool to support the planning, implementation, and organization of research data management.