20241114

Progress against our quarterly objectives

Digital Experience

Deepen engagement with stories

Undertake a discovery phase for a collection browse experience

Maintenance

Digital Platform

Ensure that metadata included on the works page meets staff and user needs

  • Met with Collections Info

Improve access to our collections for staff and users

Support the goals of the Collection with a healthy, cost effective and secure digital platform

Maintenance

Focusing on next

Digital Experience

Improve the user experience of finding information on wellcomecollection.org

  • Work out best technical approach to All search #148arrow-up-right

  • Index all addressable content types

Deepen engagement with stories

  • Create design props for onward journeys from stories #11360arrow-up-right

  • Decide on hypotheses to test

  • Agree spec/approach for build

Undertake a discovery phase for a collection browse experience

  • Recruitment: complete external and existing web site users recruitment Explore UR recruitment options with existing WC users #11361arrow-up-right

Other

Digital Platform

Expand and reinforce our digital preservation capabilities

Improve access to our collections for staff and users

  • Run in-library user testing and begin analysis

  • Talk to internal users (staff) about concepts and themes

  • Review “Use Identifiers to populate concepts pages” to determine next steps re. ‘no dead ends’ for concepts

    • Use identifiers to populate Concepts pages #5654arrow-up-right

    • Update catalogue-api to use new contributor & subject concept filters #5821arrow-up-right

    • Update concept pages to use concept ID for subjects & contributor based concepts (behind a toggle)

    • Scope work for updating search filters to use concept ID filters for subjects & contributors

  • Complete refactoring graph model to include wikidata

  • Review model opportunities

Support the goals of the Collection with a healthy, cost effective and secure digital platform

  • Move Catalogue Pipeline services from ECS to Lambda #5784arrow-up-right

    • Inspect batcher_lambda_output to compare lambda / ECS output #2747arrow-up-right

    • Resolve issues arising from reindex for batcher lambda

    • Wire batcher lambda into new pipeline?

    • Plan relation-embedder to lambda

    • Support Collections Product Lines to write user needs for the systems project

    • Run ideation workshops with subject matter experts

    • Review Coeli

Maintenance

  • Upgrade lambdas in platform infra repo

Other

  • Move to use a features vector with 4,096 dimensions (and clean up the existing feature vectors in use)

Last updated