Skip to content

Add the ability to sort Flow/Source listings #189

Description

@samdbmg

Description
It would be useful to be able to sort the list of Flows and Sources to aid in building UIs - e.g. by providing a query string parameter

Note this is also tracked as https://jira.dev.bbc.co.uk/browse/CLOUDFIT-5486

Use Case
As an NLE TAMS plugin vendor, I'd like to present a useful list of Flows and Sources to the user. However returning them in an unstable order or sorting by pulling the entire list and then sorting clientside lead to inefficiency or bad user experience

Action

  • Write an ADR covering these broad options:
  1. No sorting - all clientside
  2. Sorting by any of the query string parameters already in the spec
  3. Fixed default sort by most recent metadata_updated
  4. Optional sort by metadata_updated
  • Draft the spec changes for one of the simple options

Outcome

  • ADR PR
  • Possibly with spec change...

Activity

  1. added
    enhancementNew feature or request
    specThis issue will generate a specification change
    on Apr 29, 2026
  2. added theissue type on Apr 29, 2026
  3. samdbmg commented on Apr 29, 2026

    @samdbmg
    MemberAuthor

    After some discussion, it seems option (2) is probably more complexity than we want, and fails "TAMS is not a MAM" as a principle. So option (3) or (4) probably make sense.

  4. moved this from Triage to Backlog in TAMS Community Planningon Apr 29, 2026
  5. moved this from Backlog to In Progress in TAMS Community Planningon Jul 6, 2026
  6. self-assigned this
    on Jul 10, 2026
  7. samdbmg commented on Jul 10, 2026

    @samdbmg
    MemberAuthor

    TSC 2026-07-10
    There's now a draft ADR for approaches to this for us to decide on the preferred approach. Review comments very welcome on this one

  8. moved this from In Progress to In review in TAMS Community Planningon Jul 13, 2026
  9. linked a pull request that will close this issueSpecify the sorting of resource listings #224on Jul 14, 2026
  10. moved this from In review to Ready to merge in TAMS Community Planningon Jul 24, 2026
  11. moved this from Ready to merge to Done in TAMS Community Planningon Aug 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestspecThis issue will generate a specification change

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions