Ability to stop the publication of quoted sections

[RichardTaylor]

Often censor-rule challenges relate to material under "show quoted sections".

If the display of such material could be turned off for a message, or thread, this could greatly speed up the removal of problematic material from a thread.

[FOIMonkey]

+1 This would be really helpful.

[garethrees]

Context

Often censor-rule challenges relate to material under "show quoted sections", which are usually of less value than the main body text of a message. If the display of such material could be turned off, we could greatly speed up the removal of problematic material from a thread.

Scope

We'll tackle this on a per-message basis.

We can add a simple Boolean field to IncomingMessage so that it can be toggled by admins. This should be set to true by default, and then unchecked if we want to disable them.

When unchecked, we:

1. Shouldn't render the link to "show quoted sections" for that message
2. Shouldn't render the quoted sections for that message if the ?unfold=1 parameter is present (i.e. if a user has clicked on "show quoted sections" for a different incoming message)

Technical Considerations

We'll want to check that this value is adhered to in at least:

• The PDF export / Zip download of requests
• The text for search indexing

Out of Scope

As described above, we won't tackle this on a whole request basis.

It will be easy to set multiple messages on a request through the console, and not that annoying to do via the admin interface in all but the longest threads.

The one benefit of tackling on a whole-request basis would be that we can guard against future responses that may contain problematic material in the quoted sections. We can come back to that in a future issue, once we've got the basic mechanics in place (and once some of the related code gets a little tidier through this initial scope!).

[HelenWDTK]

This issue has been automatically closed due to a lack of discussion or resolution for over 12 months.
Should we decide to revisit this issue in the future, it can be reopened.