Audit addressable content types for descriptions

[rcantin-w]

• Promo captions
• Standfirst
• Intro text
• Metadata description
• "Featured" Text

Audit out which content type uses what in reality, and which should be:

1. Displayed on the UI
2. Query-able. The thing to consider here would be that they shouldn't necessarily all be appended as it might skew the relevance.

[davidpmccormick]

I think metadata description was primarily used to improve SEO. My instinct is that this would then be less appropriate as human-friendly search content?

[davidpmccormick]

Having looked through a sample of the content types and the fields mentioned above for each, I propose the following.

The metadata description is not consistently populated anywhere and I think it should be ignored for this piece of work altogether.

Exhibition

• promoText appears to be the same as what was (pre-migration) a text block with the featured flag
• Doesn’t use standfirst
• Recommend using promo text for query and display

Event

• Doesn’t use featured text or standfirst
• Recommend using promo text for query and display

Story

• Standfirst is (usually?) different/longer from promoText
• Recommend concatenating promoText and stand first for query, and promoText alone for display

Page

• We recently added introText (only appears on c. 3 at present).
• Recommend concatenating promoText and introText for query, and promoText alone for display

Visual Story

• promoText and standfirst can be very similar
• Recommend using promoText alone for query and display

Exhibition text

• Doesn’t have promoText or standfirst
• Use intro_text || the exhibition’s promoText if it isn’t filled, for query and display

Exhibition highlight tour

• Doesn’t have promoText or standfirst
• Use intro_text || the exhibition’s promoText if it isn’t filled, for query and display

Book

• Use promoText for query and display

Project

• Use promoText for query and display

Season

• Use standfirst concatenated with promoText for query, and promoText alone for display

[rcantin-w]

Could you update the table with your findings 🙏 ? https://www.notion.so/wellcometrust/All-search-definition-acceptance-criteria-1366687658a180f28254d4429bf764ce

[rcantin-w]

How is this affected by the standfirst changes ticket and do we think it's something we should consider doing before doing this work?

[davidpmccormick]

It would be affected if/when we do it, yes. My instinct is to carry on with this work before making changes to the standfirst – we already have queries using the current standfirst-as-a-slice implementation and they will need to be updated as well. Then they can all be updated at once.

[rcantin-w]

Sounds good. We'll need to make sure the Content API supports both until it gets fully removed, but I think after this piece of work, we'll always have to think "How does my change affect the Content API" anyway.

[LaurenFBaily]

Reviewed and this all makes sense to me, minus the event question which is captured on a separate ticket anyway.