> For the complete documentation index, see [llms.txt](https://docs.wellcomecollection.org/fortnotes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wellcomecollection.org/fortnotes/20241017.md). # 20241017 ## Progress against our quarterly objectives ### Digital Experience #### Improve experience for users with access needs pre and during visit \ Descriptive URLS: * Complete UID work (Content API): Update the linkResolver function to use the UID [#11074](https://github.com/wellcomecollection/wellcomecollection.org/issues/11074), Add uid to Content API response [#140](https://github.com/wellcomecollection/content-api/issues/140) * Investigate Prismic solutions for restructuring Pages urls [#11206](https://github.com/wellcomecollection/wellcomecollection.org/issues/11206) #### Deepen engagement with stories * Agreed UX project brief * Undertook competitor review #### Maintenance * Move Content-Api to Node20 [#137](https://github.com/wellcomecollection/content-api/issues/137) #### Other * Set up and test tracking for Hard Graft guides [#11142](https://github.com/wellcomecollection/wellcomecollection.org/issues/11142) ### Digital Platform #### Ensure that metadata included on the works page meets staff and user needs * Meeting held with Collections Information #### Expand and reinforce our digital preservation capabilities * Ingest corporate archive images [#1126](https://github.com/wellcomecollection/storage-service/issues/1126) * Make ingestor-images tests in Catalogue Pipeline more reliable [#5793](https://github.com/wellcomecollection/platform/issues/5793) #### Improve access to our collections for staff and users * Improve Concepts Pipeline documentation (overview, README for all service, and developer HOWTOs) [#5792](https:/github.com/wellcomecollection/platform/issues/5792) * Concepts kick-off meeting held #### Support the goals of the Collection with a healthy, cost effective and secure digital platform * Re-architect the batcher service so that it works as a Lambda [#2721](https://github.com/wellcomecollection/catalogue-pipeline/issues/2721) * Batcher Lambda, infrastructure and build [#2728](https://github.com/wellcomecollection/catalogue-pipeline/pull/2728) #### Maintenance * Make ingestor-images tests in Catalogue Pipeline more reliable [#5793](https://github.com/wellcomecollection/platform/issues/5793) * Update the ID Minter databases following AWS warning [#5785](https://github.com/wellcomecollection/platform/issues/5785) Other * Always provide link to item page from work page for logged in staff [#5762](https://github.com/wellcomecollection/platform/issues/5762) * Item is restricted but page is still showing available to download [#11014](https://github.com/wellcomecollection/wellcomecollection.org/issues/11014) ## Focusing on next ### Digital Experience #### Improve the user experience of finding information on wellcomecollection.org * Complete transition to new url structure for pages #### Deepen engagement with stories * Run research study * Formulate design hypotheses based on qual and quant insights #### Undertake a discovery phase for a collection browse experience * Competitive analysis * Gather relevant insights from research with internal users (concept pages) * Data analysis of existing concept pages, visually similar images & search behaviour * Plan and run discovery/assumption mapping workshop with platform team * Create research plan (inc. hotjar survey on concept pages) #### Other * Use Content API to populate stories listings [#11226](https://github.com/wellcomecollection/wellcomecollection.org/issues/11226) ### Digital Platform #### Expand and reinforce our digital preservation capabilities * • Complete ingesting corporate photography #5790 #### Improve access to our collections for staff and users \ Concepts: * Review “Use Identifiers to populate concepts pages” to determine next steps re. ‘no dead ends’ for concepts [#5654](https://github.com/wellcomecollection/platform/issues/5654) * Review and discussion of graph model \[following Knowledge Graph RFC] [#5801](https://github.com/wellcomecollection/platform/issues/5801) #### Support the goals of the Collection with a healthy, cost effective and secure digital platform * Move Catalogue Pipeline services from ECS to Lambda [#5784](https://github.com/wellcomecollection/platform/issues/5784) * Hold kick-off meeting for Systems Transformation Readiness [#5786](https://github.com/wellcomecollection/platform/issues/5786) * All active projects need a CODEOWNERS, add platform & experience Github Teams [#5807](https://github.com/wellcomecollection/platform/issues/5807) * Increase default message retention for scaling services [#2737](https://github.com/wellcomecollection/catalogue-pipeline/pull/2737) #### Maintenance * Run a reindex to pick up changes from Mon 7 afternoon * Answer Christy’s email (10/11/24) re number of books query #### Other * Update monitoring: surface date of oldest message, show the status of deployment service * Knowledge Graph Infrastructure Discovery [#5803](https://github.com/wellcomecollection/platform/issues/5803) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.wellcomecollection.org/fortnotes/20241017.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.