CINXE.COM

<!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <meta name="ROBOTS" content="NOODP" /> <title>Researchers :: Lumen</title> <link rel="stylesheet" href="/assets/application-edf3ba94297288ba21dcd7d7f08d7b53fed070a91204df553802ab78eb5b7a75.css" media="all" /> <meta name="csrf-param" content="authenticity_token" /> <meta name="csrf-token" content="hicA7t4nbQq0DFJpHbwQ6DhiO1-R0BPQt24lXSDfnr5Ju0U21RPIhjJFIKEPRuNhwSZ9mbzoEr0gUX78Mr4Vgw" /> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <link rel="shortcut icon" href="/favicon.ico">  </head> <body class="comfy-cms-content comfy-cms-content-show"> <div id="flash"> </div> <header class="app"> <div class="nav-wrapper"> <div> <a id="root" href="/"> <img src="/assets/logo_2x-4827576148b1dd2ca23c3cd316e93121ad0364ce6722fe7e70cd2927b200249a.png" width="265" height="64" /> </a> </div> <div class="flex-end"> <nav class="main-nav"> <div class="nav-item search"><a href="/">Search</a></div> <div class="nav-item topics dropdown"> <a href="#" class="dropdown-toggle" data-toggle="dropdown">Topics</a> <div id="dropdown-topics" class="dropdown-menu" role="menu"> <ol> <li class="dropdown-submenu"> <a href="/topics/5">Copyright</a> <ol class="dropdown-menu"> <li class="title">Subtopics</li> <li class=""> <a href="/topics/12">Anticircumvention (DMCA)</a> </li> <li class=""> <a href="/topics/22">Copyright and Fair Use</a> </li> <li class=""> <a href="/topics/16">Derivative Works</a> </li> <li class=""> <a href="/topics/29">DMCA Notices</a> </li> <li class=""> <a href="/topics/14">DMCA Safe Harbor</a> </li> <li class=""> <a href="/topics/25">DMCA Subpoenas</a> </li> <li class=""> <a href="/topics/11">Piracy or Copyright Infringement</a> </li> <li class=""> <a href="/topics/15">Reverse Engineering</a> </li> </ol> </li> <li class=""> <a href="/topics/40">Counterfeit</a> </li> <li class=""> <a href="/topics/28">Court Orders</a> </li> <li class=""> <a href="/topics/8">Defamation</a> </li> <li class="dropdown-submenu"> <a href="/topics/34">EU - Right to Be Forgotten</a> <ol class="dropdown-menu"> <li class="title">Subtopics</li> <li class=""> <a href="/topics/36"> El Derecho Al Olvido</a> </li> <li class=""> <a href="/topics/37">O Pravu Osobe Da Bude Zaboravljena?</a> </li> <li class=""> <a href="/topics/35">"Recht auf Vergessen" </a> </li> <li class=""> <a href="/topics/38">Recht Om Vergeten Te Worden</a> </li> <li class=""> <a href="/topics/39">правото да бъдеш забравен</a> </li> </ol> </li> <li class=""> <a href="/topics/3">Fan Fiction</a> </li> <li class=""> <a href="/topics/33">Government Requests</a> </li> <li class=""> <a href="/topics/26">International</a> </li> <li class=""> <a href="/topics/13">John Doe Anonymity</a> </li> <li class=""> <a href="/topics/32">Law Enforcement Requests</a> </li> <li class=""> <a href="/topics/18">Linking</a> </li> <li class=""> <a href="/topics/1">Lumen</a> </li> <li class=""> <a href="/topics/30">No Action</a> </li> <li class="dropdown-submenu"> <a href="/topics/20">Patent</a> <ol class="dropdown-menu"> <li class="title">Subtopics</li> <li class=""> <a href="/topics/24">E-Commerce Patents</a> </li> </ol> </li> <li class=""> <a href="/topics/21">Responses</a> </li> <li class=""> <a href="/topics/31">Right of Publicity</a> </li> <li class="dropdown-submenu"> <a href="/topics/6">Trademark</a> <ol class="dropdown-menu"> <li class="title">Subtopics</li> <li class="dropdown-submenu"> <a href="/topics/2">Domain Names and Trademarks</a> <ol class="dropdown-menu"> <li class="title">Subtopics</li> <li class=""> <a href="/topics/10">ACPA</a> </li> <li class=""> <a href="/topics/19">Documenting Your Domain Defense</a> </li> <li class=""> <a href="/topics/9">UDRP</a> </li> </ol> </li> <li class=""> <a href="/topics/17">Protest, Parody and Criticism Sites</a> </li> </ol> </li> <li class=""> <a href="/topics/23">Trade Secret</a> </li> <li class=""> <a href="/topics/27">Uncategorized</a> </li> </ol> </div> </div> <div class="nav-item"> <a href="/media_mentions/search">Research and Media Mentions</a> </div> <div class="nav-item"> <a href="/pages/about">About</a> </div> </nav> </div> </div> <div class="container header-bar"> <h2>Researchers</h2> </div> </header> <section class="main app"> <div class="main-inner"> <div class="static-pages"> <header> <h1>Lumen Tools for Researchers</h1> </header> <h2>An Introduction to the Lumen Project</h2> <h3>FAQ Contents:</h3> <ul class="contents"> <a href="#whatis"> <li>What is Lumen?</li></a> <a href="#database"> <li>What is in the database?</li></a> <a href="#missing"> <li>What is missing?</li></a> <a href="#clearinghouse"> <li>Who is Lumen for?</li> <li>Viewing a Notice</li></a> <a href="#documentation"> <li>How does it work?</li></a> <a href="#api_terms"> <li>API Terms of Use</li></a> <ul></ul><li><a href="https://lumendatabase.org/pages/researcher-interview-series">Researcher Interview Series</a></li></ul><section> <a id="whatis"> <h2>What is Lumen?</h2></a> <p>Lumen is an independent research project studying cease and desist letters concerning online content. We collect and analyze requests to remove material from the web. Our goals are to educate the public, to facilitate research about the different kinds of complaints and requests for removal--both legitimate and questionable--that are being sent to Internet publishers and service providers, and to provide as much transparency as possible about the “ecology” of such notices, in terms of who is sending them and why, and to what effect. </p> <p>Our database contains millions of notices, some of them with valid legal basis, some of them without, and some difficult to determine. The fact that Lumen has a notice in its database does <u>not</u> mean that Lumen is authenticating the provenance of that notice or making any judgment on the validity of the claims it raises. </p> <p> Conceived, developed, and founded in 2002 by then-Berkman Klein Center Fellow Wendy Seltzer, the project, then called "Chilling Effects", was initially focused on requests submitted under the United States' Digital Millennium Copyright Act. As the Internet and its usage has evolved, so has Lumen, and the database now includes complaints of all varieties, including trademark, defamation, and privacy, domestic and international, and court orders. The Lumen database grows by more than 40,000 notices per week, with voluntary submissions provided by companies such as Google, Twitter, YouTube, Wikipedia, Meta, Counterfeit Technology, Medium, Stack Exchange, Vimeo, DuckDuckGo, aspects of the University of California system, and Wordpress. As of the summer of 2019, the project hosts approximately twelve million notices, referencing close to four billion URLs. In 2018, the project website was visited over ten million times by users from virtually every country in the world. </p> <p><br></p> <p><br> </p><a id="database"> <h2>What content can I find in the database, and where does it come from?</h2> </a> <p><a id="database"></a><a id="what is">See </a><a href="https://www.lumendatabase.org/pages/lumen-notice-basics"></a><a href="https://www.lumendatabase.org/pages/lumen-notice-basics">here for comprehensive and up-to-date details</a> of who sends Lumen notices, what notices they send, and what details are part of each notice. Aggregating all of these different requests to remove material facilitates the research, study and mapping of the Internet's removal request landscape by journalists, NGOs, policy-makers, and academics. </p><a id="missing"> <h2>A notice or work contains "[redacted]" – what is missing?</h2></a> <p>Lumen makes a good faith effort to redact out all personally identifying information (“PII”) contained within notices other than the name of the sender or rightsholder, and the country of origin of the notice. Our automatic redaction processes seek to identify and remove the following:</p><ul><li>Email addresses</li><li>Phone numbers</li><li>Other forms of ID number (e.g. Social Security #s, national ID #s)</li></ul><p> Further, an individual or company submitting a notice directly to the Lumen database may have decided not to share with Lumen, or to keep private, certain pieces of information in the notice. </p> <p>Please note that for DMCA notices, Lumen does <strong>not</strong> typically redact the name of the rightsholder making the request or the URL(s) of the material complained of. Without the location of the complained-of material and the complainant, the notices are meaningless from a transparency or research perspective, to say nothing of offering no insight as to possible misuse of takedown notices as a vehicle for censorship. </p> <p> When a company shares copies of court orders it has received with us, Lumen typically displays those orders in the form in which they have been shared with Lumen and further, makes a good faith effort to do so in accordance with the applicable law of the jurisdiction from which the order emerged. United States court orders, unless sealed, are public documents. </p> <p>See <a href="https://www.lumendatabase.org/pages/lumen-notice-basics">here</a> for more details on what gets redacted from what notices.<br> </p> <a id="clearinghouse"> <h2>Who is Lumen for?</h2></a> <p>Lumen is designed for casual use both by lay Internet users curious about a notice they may have encountered, perhaps in the news or because of personal interest. (see below for more details about viewing notices) as well as for more powerful and potentially expansive use by journalists, NGOs, policy-makers, academics, and other legal researchers conducting more in-depth and focused research or studying larger trends about content removal online. <br></p><p>Lumen is not intended to be, is not set up to to be, and should not be used as, part of the work-flow of any particular business model. Companies interested in takedown notices regarding them or their clients that have been sent to other platforms would be best served contacting those platforms directly for more information. If you or your organization are interested in conducting journalistic, academic, legal, or policy-focused research on Lumen data -- research you will then publish, or have further ideas about we might improve the database and its interfaces, email us at team@lumendatabase.org. <br>At this time, Lumen generally issues researcher credentials only to people or non-profit organizations planning journalistic, academic, or legislative policy-focused public written research outputs.<br></p> <h2><a id="viewing">Viewing a Notice</a></h2> <p>For non-researchers, Lumen currently offers access to one full notice per email address every twenty-four (24) hours. Submitting an email address through the request form will provide a 1-time use URL for that particular notice that will display the full contents of the notice. Access through this URL will last for 24 hours. See <a href="https://lumendatabase.org/blog_entries/803">here</a> for more details. </p> <a id="documentation"> <h2>How does it work?</h2></a> <p>Most users will find that the web interface will suffice for browsing and discovery within the database. However, for those that need to access larger swaths of data for their research, or for those interested in submitting copies of takedown notices to Lumen, we offer our API. Read on for further information. </p></section><section> <h2>BASIC FACTS ABOUT THE API AND DATABASE</h2> <h3>Contents</h3> <ul class="contents"> <a href="#apidocs"> <li>API Documentation</li></a> <a href="#formatting"> <li>Formatting</li></a> <a href="#timestamps"> <li>Understanding dates - Unix Timestamps</li></a> <a href="#searching"> <li>Searching the database</li></a> </ul> <a id="apidocs"> <h2>API Documentation</h2></a> <p>The documentation for the Lumen API can be found <a href="https://github.com/berkmancenter/lumendatabase/blob/master/doc/api_documentation.mkd">here</a>. </p> <a id="formatting"> <h2>Formatting</h2></a> <p>When a query or request is submitted to the database, the system will return a response with a list of JSON-encoded attributes. Learn more about JSON (JavaScript Object/Open Notation) <a href="https://www.json.org/">here</a>. This format is designed to be “machine readable,” and not necessarily useful to a human reader in its raw form. However, there are many tools for rendering JSON output into a friendlier form, and we recommend finding one that works for you. </p> Example JSON Request: <pre><code> curl https://lumendatabase.org/notices/1.json </code> </pre> Example Successful JSON Output: <pre><code> { "dmca":{ "id":1, "title":"Lion King on YouTube", "body":null, "date_sent":"2013-06-04T19:23:12Z", "date_received":"2013-06-05T20:31:44Z", "topics":[ "Anticircumvention (DMCA)", "Bookmarks", "Lumen" ], "tags": [ "tag_1", "tag_2" ], "jurisdictions": [ "US", "CA" ], "action_taken": "Partial", "sender_name": "Joe Lawyer", "recipient_name": "Google, Inc.", "works": [ { "description": "Lion King Video", "copyrighted_urls": [ { "url": "https://www.example.com/lion_king.mp4" }, { "url": "https://www.example.com/lion_king.mov" } ], "infringing_urls": [ { "url": "https://www.example.com/infringing1" }, { "url": "https://www.example.com/infringing2" }, { "url": "https://www.example.com/infringing3" } ] } ] } } </code> </pre> <a id="timestamps"> <h2>Understanding dates - Unix Timestamps</h2></a> <p>The Lumen database accepts dates in a variety of formats but always outputs dates in Unix Time, which is the number of seconds elapsed since the beginning of the Unix epoch. This can be quite confusing at first, and we recommend using a Unix Timestamp conversion tool (like this one <a href="https://www.unixtimestamp.com/">here</a>) to transform these raw date outputs into something a human can understand. </p> <a id="searching"> <h2>Searching the Database</h2></a> <p>Most users will find that the web interface will suffice for browsing and discovery within the database. However, for those that need to access larger swaths of data or create automated processes to digest data trends, we offer our new API. </p> <p>Searching the database, whether through the web interface or with the API, is done via full-text search. The default search is to search all possible notice fields and facets. Searches can also refined based on specific slices of the database or on specific facets of the data. See the <a href="https://github.com/berkmancenter/lumendatabase/blob/master/doc/api_documentation.mkd#request">documentation</a> for the applicable notice parameters and metadata. </p> <hr> <h2>QUERYING THE DATABASE WITH THE API</h2> <h3>Contents</h3> <ul class="contents"> <a href="#key"> <li>Getting an API Key</li></a> <a href="#commandline"> <li>Basic search from the command line</li></a> <a href="#topics"> <li>Requesting a list of topics</li></a> <a href="#api_notice_search"> <li>Searching notices</li></a> <a href="#bulk_download"> <li>Downloading results in bulk</li></a> </ul> <a id="key"> <h2>Getting an API Key</h2></a> An authentication key is needed in order to query the database at will via the API. Researchers interested in using Lumen's API should contact the Lumen staff at team@lumendatabase.org to be provided with one. API queries to the database submitted without a token will return an error.<br>At this time we generally issue Lumen researcher credentials only to people or non-profit organizations planning journalistic, academic, or legislative policy-focused public written research outputs.<br><br><a id="commandline"> <h2>Basic search from the command line</h2></a> <p>To query the database, use your preferred tools for HTTP "get" requests. There are a number of options available, so pick one depending on your research needs.<br>Examples include: </p> <ul class="tools"> <li>Curl - a command line program for Mac, iOS and BSD operating system computers, but not for Windows. In order to use curl commands on Windows, a separate tool such as CygWin or Putty is needed.</li> <li>wget - dumps the results of the "get" request to a file.</li> </ul> <p>Example search query for <code>Batman</code> where <code><parameter></code> is the database field or facet that is the object of the search. </p> <pre><code> curl -H "Accept: application/json" -H "Content-type: application/json" 'https://www.lumendatabase.org/notices/search?<b><parameter>=batman</b>' </code> </pre> <p>Here’s a search query for <code>star</code> where <code>term</code> is the parameter. </p> <pre><code> curl -H "Accept: application/json" -H "Content-type: application/json" 'https://www.lumendatabase.org/notices/search?<b>term=star</b>' </code> </pre> <p>Searches can also combine multiple parameters when linked with an ampersand. Below, the query combines a search for <code>star</code> where <code>term</code> is the parameter, where <code>batman</code> is the <code>sender_name</code>, and <code>date_received</code> falls between <code>RANGE1..RANGE2</code> </p> <pre><code> curl -H "Accept: application/json" -H "Content-type: application/json" 'https://www.lumendatabase.org/notices/search?<b>term=star&sender_name=batman&date_received=_facet=RANGE1..RANGE2</b>' </code> </pre> <p>Running these search queries through the API will allow you to search for some period of time, as well as download search results for use and reuse in applications. A complete list of searchable parameters can be found <a href="https://github.com/berkmancenter/lumendatabase/blob/master/doc/api_documentation.mkd#search-notices-via-fulltext">here</a>. </p> <a id="topics"> <h2>Requesting a List of Topics</h2></a> <p>The database classifies notices into one or more topics, more of which may be added over time. Certain topics are categorized as subtopics of a larger, comprehensive root topic. For example, like “DMCA,” “fair use,” and “anti-circumvention” all fall under “Copyright.” Each topic has a unique numerical ID in the database. To request a list of topics, use the following command. </p> <pre><code> curl https://www.lumendatabase.org/topics.json </code> </pre> <p>This command will return results with three pieces of information: 1) the topic's unique ID number, 2) the name of the topic, and 3) either the ID number of the parent topic or null if the topic is a root topic. </p> <table class="codetable"> <tbody> <tr> <td>id </td> <td>integer </td> <td>The unique ID used for the topic_ids array during notice creation </td> </tr> <tr> <td>name </td> <td>string </td> <td>The topic name </td> </tr> <tr> <td>parent_id </td> <td>integer </td> <td>The parent topic_id of this topic, or "null" if this is a root topic. </td> </tr> </tbody> </table> <a id="api_notice_search"> <h2>Searching the notices</h2></a> <p>On the web interface, above a certain number of hits your search results will be paginated. By default, results are sorted by descending relevance. Full-text search results contain the same data as an individually-requested notices, with the addition of a score field that articulates the result relevance to the query term; higher numbers are more relevant. Terms are joined with an 'OR' by default. </p> <a id="bulk_download"> <h2>Downloading Results in Bulk</h2></a> In order to better manage its resources, Lumen limits requests to its API as well as use of the web-based user interface. For those interested in less restricted access to the database through the API, please see <a href="#key">"Getting an API key."</a> <a id="api_terms"> <h2>API Terms of Use</h2></a> The terms of use for the API are available by clicking <a href="/pages/api_terms">here</a>.</section> </div> </div> </section> <footer class="main"> <div class="nav-wrapper"> <div class="nav-item"> <span><img height="16" style="vertical-align: middle;" src="/assets/Cc.logo.circle-e5300412c8b02cb8ba4db0b20bafbc078b7661cb21b155c36253170b61b7f736.svg" /> 2017 Lumen</span> </div> <div class="flex-end"> <nav> <span class="nav-item"><a href="/pages/legal">Legal</a></span> <span class="nav-item"><a href="/pages/license">Licenses</a></span> <span class="nav-item"><a href="/pages/privacy">Privacy</a></span> <span class="nav-item"><a href="/pages/researchers">Researchers</a></span> <span class="nav-item"><a href="/pages/blog-archive">Blog Archive</a></span> <span class="nav-item"><a href="/pages/lumen-research-sprint">Spring '22 Research Sprint</a></span> <span class="nav-item"><a href="/users/sign_in">Sign In</a></span> </nav> </div> </div> </footer> <script src="/assets/application-8680dd11e43ce5255b4a75a3635a812dd463a91fb238b70e600fa9b3f5fbe5ea.js"></script>  <script type="text/javascript"> var _paq = _paq || []; /* tracker methods like "setCustomDimension" should be called before "trackPageView" */ _paq.push(["setDomains", ["flutie.law.harvard.edu","*.www.chillingeffects.org","*.chillingeffects.org","*.lumendatabase.org","*.www.lumendatabase.org"]]); _paq.push(['trackPageView']); _paq.push(['enableLinkTracking']); (function() { var u="//stats.berkman.harvard.edu/"; _paq.push(['setTrackerUrl', u+'piwik.php']); _paq.push(['setSiteId', '3']); })(); </script> <script src="/assets/piwik-3baf1baf98198bf4189c7074b479642a1f7078e67dabdc9b045b463a4e655f59.js" defer="defer" async="async"></script>  </body> </html>