rdmorganiser / rdmorganiser/rdmo
`config` app: Allow managers to configure `Plugin` settings via GUI
Open
type:feature-request
- Dominant language
- Python
- Stars
- 133
- Forks
- 60
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 21
Description
Rationale / Begründung
At the moment, plugin settings in RDMO can only be configured by administrators through server-level changes.
Providing managers or editors with a GUI to configure plugins directly would increase flexibility and reduce dependency on administrators. This should cover activation/deactivation, catalog assignment, and adjusting plugin-specific settings (e.g., mappings via .toml files).
Affected
- Managers or Editors (to be discussed)
- Admins
Minimal functionality
- option for site-managers to activate/deactivate plugins for their site
- option for site-managers to assign plugins to specific catalogs
- Simple form element for additional plugin configuration, e.g. an editor for .toml files used by the plugins (similar to views editor)
Nice-to-have functionality
- instead of plain text editor for .toml files, provide a key-value pairs UI (or similiar) for easier configuration
- Support for plugin customization (e.g. endpoints, queries) to allow broader generalization of plugins). Ecample: allow users to add several instances of the same plugin to query different databases
- a project-level page for users to activate/deactivate plugins for a project and it's sub-projects
References / Verweise
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.