Ordering metadata fields with multiple values · Issue #4781 · samvera/hyrax
Julie: Specifically, Hyrax Maintenance WG is trying to determine if there is a way to use Resource Type to flexibly define if there are instances when there should be multiple versus single values for a given field
Ryan: Assuming ordering is possible, does Maintenance want to set multiple value ordering parameters based on a given Resource Type? (yes)
In Valkyrie sets, ordering of multiple values is by default
Conceivably it may be simpler to have ordering for all multiple value fields
Currently, multi-valued fields e.g. creator loads in different orders every time and this is causing issues with Google scholar indexing
Creator, Contributor, and Title are the fields where ordering is most important, when those fields contain multiple values
Ordering Subject and Keyword values are less important
It could be a source of confusion to only have ordering a specific fields for limited Resource Types; it also isn’t necessarily dependent on Resource Type.
Multi-value ordering as a toggle-able on/off feature is not probably something that would be accomplished during the first phase of setting up this feature
This will have implications for batch ingest and legacy content migration
Action item: Add comment to the effect that SMIG recommends that Creator, Contributor, and Title are the fields where ordering is most important, when those fields contain multiple values - across all Resource Types. Also, that this would be applied to all multi-value fields.