convert api requests asking for "orderBy=oldest" to the correct value

[andrew-nowak]

What does this change?

There's a discrepancy between the search params shown and used by Kahuna, and what's expected in the grid API. One is orderBy - the default (so not shown in the kahuna params) is upload date, from newest to oldest, which the API phrases as -uploadTime. Next is upload date from oldest to newest; kahuna shows this as &orderBy=oldest; but the media API requires uploadTime.

We've had a handful of errors from the media-api from someone trying to order on "oldest", instead of "uploadTime". After some digging I've found the culprit (a service which tries to convert kahuna search params into media-api queries), but rather than fix it there, it's a simple fix to do inside grid itself, to be more resilient to slightly-wrong but still understandable queries.

How should a reviewer test this change?

Make some API queries, ordering on "oldest" - you should get successful requests, instead of 500s. Also/alternatively, paste a grid URL where you've been ordering by "oldest" into pinboard (note not using the "add to pinboard" button, which already does the right thing).

How can success be measured?

Fewer 5xxs

Who should look at this?

Tested? Documented?

• locally by committer
• locally by Guardian reviewer
• on the Guardian's TEST environment
• relevant documentation added or amended (if needed)

[github-actions]

Deploy build 13269 of media-service::grid::all to TEST

All deployment options

• Deploy build 13269 of media-service::grid::all to TEST
• Deploy parts of build 13269 to TEST by previewing it first
• What's on TEST right now?

---

From guardian/actions-riff-raff.

[bryophyta]

lgtm!

[prout-bot]

Seen on auth, usage, image-loader, metadata-editor, thrall, leases, cropper, collections, media-api, kahuna (merged by @andrew-nowak 8 minutes and 44 seconds ago) Please check your changes!