Improve prominence of uploaded files

[FOIMonkey]

When authorities release information offsite, such as via SharePoint, we will upload a copy of the data and link to it in an annotation.

Often, users will not see the upload, and will request a code to access the SharePoint, which is sent to the request thread. When this happens multiple times, it makes the threads look cluttered, generates unneeded emails to the original requester and resets the classification status.

It would be helpful if we had some way of making files that we upload more visible.

[RichardTaylor]

This could be via a special annotation which was given extra prominence. We have a ticket for special annotations: #34

a code to access the SharePoint, which is sent to the request thread. When this happens multiple times, it makes the threads look cluttered

We could deal with this by fixing older such messages in their collapsed state, perhaps automatically, or at least when permanently collapsed by the requester or an admin. I think the best ticket for this is #1749

[RichardTaylor]

Perhaps ideally we'd have something more structured than an annotation to record the link between a thread/message and the file. We do already manually upload files into a directory structure which connects them with a specific request thread.

We do usually want an annotation though to explain what's happened and what we've done.

An ideal system would involve:

• An ability for admins to upload files Add function to upload files via admin interface #1155
• For a file to be associated with the relevant request, message, and attachment. (Typically an uploaded file will replace a specific attachment).
• For the new file to be presented to users in context, with appropriate prominence, with an explanation as to how and why it has been uploaded manually.
  • Consider a faded out icon for the original attachment, with a link to the new file displayed next to it.
• We could have canned responses for the explanations.

[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.