Ticket #495 (new task)
process for dealing with content take-down requests
| Reported by: | https://id.mayfirst.org/malloryk | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 5 |
| Keywords: | Cc: | ||
| Project Area: | Other | Project: | policy |
| Skill Set Required: | Training or Documentation |
Description
There have been a few requests for content to be removed from our sites and open archives of list serves.
The first question is should we always and fully comply with these requests or are there exceptions?
The second question is how we deal with take-downs?
I can offer my perspective just to start:
- MF/PL, the server host, won't comply with a request to take down information that infringes on free speech, even when the notice cites a violation of fair use. However, what if the request for take down is for information of a personal, sensitive nature? What if the request is coming from the person that created the content (like in the most recent case of an individual that had a film in 2007 and wants the submitted application's node removed)?
- If we decide to take down information, we should replace it with a standard node that preserves the title of the node (in case something linked here previously or a search engine found a cached copy of the old page) and replaces the body with text that indicates that it has been removed at ###'s request. Then, we can cite our policy on content creation and take-down requests here, too.
Change History
Note: See
TracTickets for help on using
tickets.
