The Support and Safety team requests some improvements to some self-written tools to help them complete important tasks as part of their workflows. This ticket will be an investigation into the DMCA Takedown Form, while T159467 covers the child protection tool.
The tools are currently found at http://lcatools.corp.wikimedia.org — @Jalexander will be able to provide login credentials to pertinent developers on request for investigation and/or development. Existing code is here: https://github.com/jamesryanalexander/lca-tools
**What the tool does:**
This tools is found either from the main page or left rail of the Trust and Safety tools wiki as "DMCA Takedown Form"
This is a form to fill out information about a DMCA takedown (both data about the takedown itself, as well as the file or page that is being taken down), and attach a file with additional information as needed. The form sends data (and the file) to [[ https://lumendatabase.org/ | Lumen Database ]] (formerly Chilling Effects) via their API, and receives (for log and sugar case) the Lumen ID/URL.
The tool formats posts for:
* WMFwiki -- provides link to post on WMFWiki and allows copy and paste of the main post
* the User Talk page of the uploader -- also allows you to make the edit directly via MW OAuth in addition to copy/paste
* When the takedown is on Commons, it formats posts for Commons Village pump and the Commons DMCA noticeboard. (It also allows one click posting of those via OAuth in addition to copy/paste).
* The tool also creates a SugarCRM case with basic info about the takedown.
There is a separate sub-tool that only reports to Lumen without formatting the posts/creating sugar case. This is mostly used for when the API was down or issues happened.
* Right now, the tool only tracks the files that are taken down. We also want to track the requests that don't lead to a takedown, so there should be a full log. Some of the fields should not be mandatory, and there should likely be an option added for request granted (image removed) or denied (image kept.)
* We may need this to write to SalesForce instead of Sugar. I need to check with @Jalexander
* Will these requested changes require a complete rewrite, or small-scale fixes?
* Where should these tools live — on the existing private server, or ToolLabs?
* Should we merge the sub-tool with the main tool, or keep them separate?
* Written answers to open questions in this ticket
* Written proposal for how to implement requested changes to the two tools
* Documented knowledge learned to help with further development of this project
* Any needed additional cards created
In an CommTech estimation meeting on March 7, 2017 this card was sized as a '5'.