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

Issue/3343 Consolidate admin/settings UI functionalities #3393

Merged
merged 40 commits into from
Aug 15, 2022
Merged

Conversation

t83714
Copy link
Contributor

@t83714 t83714 commented Aug 10, 2022

What this PR does

Fixes

  • Consolidate admin/settings UI functionalities #3343 the following feature will be moved into a central "settings" area (accessible from header once logged in)
  • fixed: publishingState filter is not processed probably in search API
  • Remove legacy code
  • Fixed: dataset metadata editor incorrectly fetch records with cache
  • Allow users to change the publishing status of published dataset #3395
  • make dataset management page "draft" / "published" tab can be navigated via url path
  • make sure file handling edging cases can be handled correctly.
  • fixed an issue of faas function invocation: metadata pre-fill feature should only call data-url-processor & api-url-processor type faas functions
  • fixed indexer API request wrong permission
  • Make source, publishing & "information-security" aspects available from distribution records as well
  • remove 'object/dataset/published/unpublish' & 'object/dataset/published/unpublish' defined in schema version 1.3 for now, to be reintroduced in future as part of the publishing approval process
  • Managing draft & published distribution separate like dataset records & update policies accordingly
  • Allow changing dataset owner in the editing view
  • make UserNameLabel use cache

Checklist

  • unit tests aren't applicable
  • I've updated CHANGES.md with what I changed.

- make `managingOrgUnitId` as optional (configurable) mandatory field
- make UI use magda storage by default
- change default value for "How should the contact point(s) be referenced in the metadata?"
…ds. Therefore, it won't stop indexer from processing requests.
…o `false` (unless all optional parameters are specified)
…ated via url path

- make sure users land on most relevant dataset management tab
- e.g. user should be able to delete interrupted uploads.
- file cannot be deleted while upload is still on-going
- file uploading markers are properly reset when opens a new dataset
- combine separate dataset / api url input area into one
…cessor" & "api-url-processor" type faas function
- 'object/dataset/published/unpublish'
- object/dataset/published/unpublish'
defined in schema version 1.3 for now, to be reintroduced in future as part of publishing approval process
2> Managing draft & published distribution separate like dataset records
- update required distribution permission for metadata editor
- adjust dataset editor exit button position
- fix user policy: user should alway be able to read his own user info
- add dataset owner selector to dataset editor (editing view only)
@t83714 t83714 mentioned this pull request Aug 15, 2022
21 tasks
@t83714
Copy link
Contributor Author

t83714 commented Aug 15, 2022

tested in dev cluster

@t83714 t83714 merged commit e9346b1 into next Aug 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant