Analysis of manifest ordering in collection catalogue browse interface

[aeschylus]

I was reminded by looking at some of the placeholder tickets and comparing with existing behaviour that there was a lot of demand for deterministic manifest ordering in the catalogue list. Was this captured anywhere? If so, I think manifest ordering has some implications for the placeholder behaviour as well.

[ggeisler]

@aeschylus Can you elaborate on what you mean by "demand for deterministic manifest ordering in the catalogue list?"

Do you mean consistent ordering of the resources in the load window/catalog? If so, 1) aren't we currently doing that (seems so, based on order in the source file and the actual displayed list in the load window) and 2) do you know of use cases that would suggest this is an important requirement?

I agree that there is a general UX concern if there isn't consistent ordering in that a user could return to the same load window at different times and see manifests in a different order, which could be confusing. But I don't know that we've captured this concern anywhere because I don't remember hearing it as a user requirement.

I'm also not clear what implications this might have for placeholder behavior?