> For the complete documentation index, see [llms.txt](https://docs.wellcomecollection.org/sensitivity-and-access-procedures/MlCudwyUwusoQqpgXspq/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/sensitivity-and-access-procedures/MlCudwyUwusoQqpgXspq/collections-access-diversity-and-inclusion-forum-cadi/topics/content-advisories.md).

# Content Advisories

The team discussed using content advisories to flag offensive, out-dated or sensitive content and metadata.

We currently use a fairly broad access statement 'Open with advisory' for sensitive content, without expanding on the reason for this status.

We’ve explored supplementing open with advisory with a content advisory statement, and where this would go in CALM and Sierra. There is also work in progress on Safeguarded Access statement for Child Sexual Abuse material. 

So far this work has focused on the content of material, not about language used in catalogue or a sort of higher level statement when people first encounter the catalogue.  Ultimately we would want something that works at both a general and a granular level.

Before we get to this stage we want to think more openly about  the end goal: why do we want content advisories, what is the purpose, what they are not. 

Documentation:

[Content Advisory powerpoint ](https://wellcomecloud.sharepoint.com/:p:/r/sites/wc2/cr/tpd/Strategy%20%20LongTerm%20Planning/CIT%20development/Access%20and%20Sensitivity%20Forum/2023-06-27.pptx?d=wbecc5d800069408abf0c83220e830531\&csf=1\&web=1\&e=OV9l0f)

[Notes on discussion](https://wellcomecloud.sharepoint.com/:w:/r/sites/wc2/cr/tpd/Strategy%20%20LongTerm%20Planning/CIT%20development/Access%20and%20Sensitivity%20Forum/2023-06-27%20meeting%20notes.docx?d=w66ff2afb375e426c954e1a91f08ebe43\&csf=1\&web=1\&e=wDGHdd)