Order archive item values and display set values by interface slug in the API and in the list view

[jmsmkn]

That way, the presentation of values both in the templates and in CIRRUS should be consistent.

[ammar257ammar]

I am wondering, since the archive item and display set can have multiple interfaces, how the sorting should be applied? based on the slug of the first interface (of item) for example?

[amickan]

This is about the values of display sets and archive items, not about the items themselves. And the values should be ordered by slug, alphabetically in a ascending order.

[chrisvanrun]

There is currently a 'kind' ordering in displaying the CIV representations in lists:

[*values, *thumbnails, *charts, *files, *images, *residual]

This has the previewable values and other direct viewable kind of input/outputs first, and the downloadable as last. I suggest we apply this to the API as well, that way CIRRUS picks it up.