Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make redirect to dataset view optional #4326

Open
3 of 4 tasks
dafeder opened this issue Oct 25, 2024 · 1 comment
Open
3 of 4 tasks

Make redirect to dataset view optional #4326

dafeder opened this issue Oct 25, 2024 · 1 comment
Labels
feature request Good First Issue good issues for first time contributors

Comments

@dafeder
Copy link
Member

dafeder commented Oct 25, 2024

Feature Description

Add a config option to metastore settings to stop forcing a redirect to the datasets view on dataset form submit.

Problem and Motivation

We have a redirect in metastore_admin.module that takes people back to the dataset view after saving a dataset form. This is quite difficult to disable/override, and in many cases may not be the desired behavior. For instance if using a draft workflow, the dataset author may not have permission to see that page at all.

Potential Benefits

More flexibility in user experience for different use cases.

Target Audience

  • End Users
  • Developers
  • Administrators
  • Other

Possible Implementation

Add a config option and a checkbox in one of the admin forms, check for this before adding the redirect in the submit function.

@dafeder dafeder added feature request Good First Issue good issues for first time contributors labels Oct 25, 2024
@janette
Copy link
Member

janette commented Nov 4, 2024

Editors without access to the content overview page would need to rely on the local tasks menu to get to the datasets they manage. We don't currently expose these links in our decoupled frontend so would need to test this config with dkan_js_frontend uninstalled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Good First Issue good issues for first time contributors
Projects
None yet
Development

No branches or pull requests

2 participants