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
Metadata Registry create new metadata schema doesn't appear without reload #1081
Labels
bug
high priority
performance / caching
Related to performance, caching or embedded objects
usability
Milestone
Comments
@artlowel : Assigning to you (or your team to review). To me, it sounds like a caching issue. Placing this as low priority for now, as it works but is annoying |
tdonohue
added
Estimate TBD
and removed
needs triage
New issue needs triage and/or scheduling
labels
Apr 16, 2021
tdonohue
added
the
performance / caching
Related to performance, caching or embedded objects
label
Jul 28, 2021
tdonohue
changed the title
Metadata Registry create new metadata schema
Metadata Registry create new metadata schema doesn't appear without reload
Jul 28, 2021
tdonohue
added this to To Do
in DSpace 7.5 release (OLD - Migrated, see note above)
via automation
Oct 11, 2022
Hi @tdonohue, I want to take this task. |
Merged
8 tasks
alanorth
added a commit
that referenced
this issue
Sep 8, 2023
Fix to Metadata Registry create new metadata schema doesn't appear without reload #1081
alanorth
added a commit
that referenced
this issue
Sep 8, 2023
[Port dspace-7_x] Fix to Metadata Registry create new metadata schema doesn't appear without reload #1081
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
high priority
performance / caching
Related to performance, caching or embedded objects
usability
Describe the bug
On Metadata Registry page, when creating a new schema, the new schema is not listed after successful submit.
Name-field keeps old value.
To Reproduce
Create a new schema.
Expected behavior
New schema should list as last entry, both Namespace- and Name-fields should be empty.
Temporary solution
Reload.
The text was updated successfully, but these errors were encountered: