Catalog View by Sorted by the Statutes

[mavenzer]

As previously mentioned ODD is being utilized more and more as a catalog (quite often by non-technical users)

When users enter the "catalog" section they are instantly presented with everything in ODD (sorted by last added/modified date) the majority of things recently added are usually in the unassigned status and incomplete - this leads to "messy" items usually being listed first that builds a perception that the catalog isn't mature/clean.

The proposal is to sort the default catalog view firstly based on status in the following sequence:

• STABLE
• DEPRECIATED
• DRAFT
• UNASSIGNED
• DELETED

The main reasoning for this is that as users come into the catalog the primary wish is to get an overview of available data (in this case stable is the preferred) and secondly as a technical team, ensure our "customers" have a good perception of the catalog itself.

As always, we can appreciate that design choices are somewhat ambiguous, but we have seen with our internal user base this would be a noticeable improvement in the user experience.

Attaching the screenshot for reference :

I'm more than happy to contribute to implementing the above feature.

[Vladysl]

Hello, many thanks for your feedback.
This action requires some changes on the BE side; I'll implement them this week. (And also, we'll try to release them this week.)

[mavenzer]

@Vladysl Thanks for your response. One query from me: the merge request I have pushed sorts using the status array. Are there any issues or long-term optimization concerns?

[Vladysl]

It will be more clear when the API returns an already sorted response. It would be better when this kind of logic is handled on the API side. But we are open to any propositions; probably I'll take a look at BE code and we can return to this discussion. 

Many thanks for your contribution. 

[mavenzer]

@Vladysl Understood, Server-side implementation is much better than the client side.

[Vladysl]

Implemented in #1707

[RamanDamayeu]

The best will be to implement via #1710 in a long run I guess. But for now let's change to default sorting behavior.

[mavenzer]

Thanks a lot @RamanDamayeu @Vladysl