Skip to content

Initially submitted metadata saves in reverse order #3443

@CGillen

Description

@CGillen

Descriptive summary

When creating a collection (work is untested but I expect the same) and adding multiple values to a single metadata field, using Add another, the collection will save successfully but when viewed and going back to the edit page the metadata is in reverse order.

If you add a new value to the reversed field, it will appear correctly at the end of the list. I'm unsure what happens when you add multiple new values.

Expected behavior

Work saves metadata in given order.
This might not be possible until we implement ordered metadata? Not sure why it would change

Related work

Generated from v4 testing
#3416 (comment)

Accessibility Concerns

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugPriority - LowIssues that can be prioritized after High Priority - later in the project timeline

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions