Filter exhibitions

[gestchild]

What does this change?

For #331

Makes it possible to filter out events by their format type, e.g. format=!{id} or format=!{id-alias}

How to test

• visit https://api-dev.wellcomecollection.org/content/v0/events and note number of results
• visit https://api-dev.wellcomecollection.org/content/v0/events?filterOutExhibitions=true see fewer results
• visit https://api-dev.wellcomecollection.org/content/v0/events?format=!exhibitions see (the same amount) fewer results

How can we measure success?

We have a more flexible way of filtering by formats that follows the same pattern as the Catalogue API.

Have we considered potential risks?

Nothing really

[rcantin-w]

https://api-dev.wellcomecollection.org/content/v0/events?filterOutExhibitions is returning 640 results (same as without the filter) but https://api-dev.wellcomecollection.org/content/v0/events?filterOutExhibitions=true works - is that expected?

[rcantin-w]

Do you remember what these changes are about?

[gestchild]

I split the agent and mocks out so I could directly test that the Elasticsearch client is called with the correct parameters, e.g.

content-api/api/test/events.test.ts

Line 77 in 44e8cdd

expect(mocks.elasticClientSearch).toHaveBeenCalledWith(

[rcantin-w]

Couple questions; I just want to understand for the test changes, not asking for changes. If the query I flagged is as expected then I think it's good to go!

[gestchild]

https://api-dev.wellcomecollection.org/content/v0/events?filterOutExhibitions is returning 640 results (same as without the filter) but https://api-dev.wellcomecollection.org/content/v0/events?filterOutExhibit

No, both methods of filtering should still be working, so we can deploy this without breaking the current filtering on wellcomecollection.org - I'll investigate