# 20241127 ## Progress against our quarterly objectives ### Digital Experience #### Improve the user experience of finding information on wellcomecollection.org * Work out best technical approach to All search [#148](https://github.com/wellcomecollection/content-api/issues/148) * Research and answer questions for Events in "All" search [#151](https://github.com/wellcomecollection/content-api/issues/151) * Audit addressable content types for descriptions [#152](https://github.com/wellcomecollection/content-api/issues/152) * Create graphQuery for each content type [#155](https://github.com/wellcomecollection/content-api/issues/155) * Add Events endpoints to API reference [#124](https://github.com/wellcomecollection/content-api/issues/124) #### Deepen engagement with stories * Created designs for discussion for onward journeys from stories * Decided on hypothesis to test * Agreed spec/approach for build #### Undertake a discovery phase for a collection browse experience * Completed recruitment set up for external site users #### Other * Use Content API to populate stories listings [#11226](https://github.com/wellcomecollection/wellcomecollection.org/issues/11226) * Use Vimeo on Highlight Tours [#11408](https://github.com/wellcomecollection/wellcomecollection.org/issues/11408) * Fixed: Image and 'Whats on this page' hierarchy changed [#11052](https://github.com/wellcomecollection/wellcomecollection.org/issues/11052) ### Digital Platform #### Expand and reinforce our digital preservation capabilities * Complete ingesting corporate photography [#5790](https://github.com/wellcomecollection/platform/issues/5790) #### Improve access to our collections for staff and users * Update concept pages to use concept ID for subjects & contributor based concepts behind a [toggle](https://dash.wellcomecollection.org/toggles/) [#5654](https://github.com/wellcomecollection/platform/issues/5654) * Update catalogue-api to use new contributor & subject concept filters [#5821](https://github.com/wellcomecollection/platform/issues/5821) * Index concept source IDs in works index for filtering [#5820](https://github.com/wellcomecollection/platform/issues/5820) * Plan concept page user research [#5813](https://github.com/wellcomecollection/platform/issues/5813) * Review graph model [#5801](https://github.com/wellcomecollection/platform/issues/5801) #### Support the goals of the Collection with a healthy, cost effective and secure digital platform * Inspect batcher\_lambda\_output to compare lambda / ECS output [#2747](https://github.com/wellcomecollection/catalogue-pipeline/issues/2747) * Resolve issues arising from reindex for batcher lambda [#5824](https://github.com/wellcomecollection/platform/issues/5824) * Wire batcher lambda into new pipeline [#2769](https://github.com/wellcomecollection/catalogue-pipeline/issues/2769) * Investigate vector indexing in catalogue images index [#5822](https://github.com/wellcomecollection/platform/issues/5822) #### Other * Add WAF watchlist for pentest IP addresses [#11419](https://github.com/wellcomecollection/wellcomecollection.org/pull/11419) ## Focusing on next ### Digital Experience #### Improve the user experience of finding information on wellcomecollection.org * Index addressable content types, create addressable endpoint in the Content API #### Deepen engagement with stories * Create design props for onward journeys from stories #11360 * Build designs * Set up a GA event #### Other * Verify the behaviour of opening times in advance of the Christmas/New Year closure [#11410](https://github.com/wellcomecollection/wellcomecollection.org/issues/11410) * Stop the cache varying on \_ga cookie [#11391](https://github.com/wellcomecollection/wellcomecollection.org/issues/11391) ### Digital Platform #### Expand and reinforce our digital preservation capabilities * Artefactual onboarding [#5839](https://github.com/wellcomecollection/platform/issues/5839) #### Improve access to our collections for staff and users * Run ideation workshops with subject matter experts * Updating links to works search on concepts pages to use label search [#5834](https://github.com/wellcomecollection/platform/issues/5834) * Graph database in AWS spike [#5836](https://github.com/wellcomecollection/platform/issues/5836) * Reindex after relation embedder to lambda implementation and infra complete [#5838](https://github.com/wellcomecollection/platform/issues/5838) #### Support the goals of the Collection with a healthy, cost effective and secure digital platform * Inspect batcher\_lambda\_output to compare lambda / ECS output [#2747](https://github.com/wellcomecollection/catalogue-pipeline/issues/2747) * Resolve issues arising from reindex for batcher lambda [#5824](https://github.com/wellcomecollection/platform/issues/5824) * Wire batcher lambda into new pipeline [#2769](https://github.com/wellcomecollection/catalogue-pipeline/issues/2769) * Investigate vector indexing in catalogue images index [#5822](https://github.com/wellcomecollection/platform/issues/5822) #### Other * Deepstore requesting over the closure period --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.wellcomecollection.org/fortnotes/20241127.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.