delete metadatafields from multiple metadataschema #2599
Labels
bug
claimed: Atmire
Atmire team is working on this issue & will contribute back
component: administrative tools
Related to the admin menu or tools
medium priority
Milestone
Describe the bug
There is some inconsistency in deleting metadatafields among multiple schemas. When fields from multiple metadataschemas are ticked/selected than these ticks are not shown after browsing through other schemas and multiple fields are deleted.
We discovered the bug in Dspace Cris aligned to Dspace 7.5 where the functionality of the code should not have been modified a lot and we did not found some similar issue in this board describing this behavior. If someone from the community might confirm that this behavior can be reproduced in recent Dspace?
To Reproduce
Steps to reproduce the behavior:
dc.aa
anddcterms.aab
fields (or some other names/schemas of your choice)dc.aa
dc
vocabulary and confirm that the fielddc.aa
is not markeddcterms
vocabulary and tick ✔️dcterms.aab
Screencast of steps 2 to 8 (without mouse pointer):
Screencast from 06.11.2023 12:49:33.webm
Expected behavior
We are not sure if the intended behavior is that metadatafields can only be deleted among one metadataschema at once
(in this case the first selected schema is wrong and the selection should be reset when going back, e.g. by deselectingAllMetadataField when the component is destroyed (
dspace-angular/src/app/admin/admin-registries/metadata-schema/metadata-schema.component.ts
Line 209 in e62832f
or
that the metadatafields can be selected and deleted among all metadataschemas (in this case the selected ticks are not shown correctly after browsing though multiple schemas).
Related work
The text was updated successfully, but these errors were encountered: