Skip to content

Latest commit

 

History

History
60 lines (33 loc) · 6.49 KB

L1000.md

File metadata and controls

60 lines (33 loc) · 6.49 KB
Raw

Retreived from http://www.lincscloud.org/license/ on 2015-10-16.

License

Update - October 14, 2015

All LINCS Production Phase L1000 data generated by the Broad Institute is posted at the NCBIs Gene Expression Omnibus (GEO). Standard NIH data access rules apply - data is freely accessible by anyone (GEO BioProject ID PRJNA290347)

The website lincscloud.org, a Broad Institute developed resource for analysis of LINCS Phase 1 (2011-2014) data, will be deprecated in 2015 as the NIH has recently funded a separate LINCS Data Coordination and Integration Center (DCIC).

Our historic license is given below for reference, but the official information on access to all LINCS resources via the DCIC is available at lincsproject.org.

Access Keys, Code, and Data Files are provided on the following terms:

  1. Access Keys, Code, and Data Files are single user and assigned to the particular named individual during registration. If anyone else in your group seeks access, please have them fill out the request and we will be glad to provide another personalized key.

  2. You agree to not redistribute Access Keys, Code, and Data Files Access to these resources is restricted to use by you within your research group. Please do not redistribute them. If you have a derivative work that is significantly different from what we provide and you would like to distribute it, please contact us with the details. Our goal is to encourage significant improvements while maintaining provenance and reproducible research standards.

  3. Any discoveries you make in the data are yours We encourage you to publish results from analysis of these data. Please see "Publication Policy" below. Access Keys, Code, and Data Files are for research use only

  4. Usage of Access Keys, Code, and Data Files are restricted to academic use within not-for-profit institutions.

PUBLICATION POLICY

A LINCS-wide publication policy is in development. Until then, these are our (Broad Institute) policies.

The L1000 assay, dataset, and methods are in preparation for publication.

However, we are glad if you have found the data to be useful and would like to incorporate it into your paper. You do not need to wait for the Broad CMap group to first publish a paper. The only exception to this is a paper describing the overall contours of the LINCS dataset (i.e., the manuscript that we at the Broad are working on in collaboration with LINCS). This approach is similar to how The Cancer Genome Atlas (TCGA) policy works - a user can incorporate TCGA findings with respect to a gene of interest prior to the TCGA official paper, but he/she can't publish on the entire landscape of the TCGA breast cancer dataset (until the lead centers publish).

If your paper needs a citation to our work on L1000 or LINCS, please contact us at [email protected].

Examples of groups that have published their work on this basis include:

  1. Santagata S, Mendillo ML, Tang YC, Subramanian A, Perley CC, Roche SP, Wong B, Narayan R, Kwon H, Koeva M, Amon A, Golub TR, Porco JA Jr., Whitesell L, Lindquist S. Tight coordination of protein translation and HSF1 activation supports the anabolic malignant state. Science. 2013/7/19. 341(6143), (2013). Download paper.

  2. Johannessen CM, Johnson LA, Piccioni F, Townes A, Frederick DT, Donahue MK, Narayan R, Flaherty KT, Wargo JA, Root DE, Garraway LA. A melanocyte lineage program confers resistance to MAP kinase pathway inhibition. Nature. 2013/12/5. 504(7478):138-42, (2013). Download paper.

  3. Gustafsdottir SM, Ljosa V, Sokolnicki KL, Wilson JA, Walpita D, Kemp MM, Seiler KP, Carrel HA, Golub TR, Schreiber SL, Clemons PA, Carpenter AE, Shamji AF. Multiplex cytological profiling assay to measure diverse cellular states. PLoS One. 2013/12/2;8(12):e80999, (2013). Download paper.

  4. Wawer, MJ, Jaramillo DE, Dancik V, Fass DM, Haggarty SJ, Shamji AF, Wagner BK, Schreiber SL, Clemons PA, et al. Automated Structure-Activity Relationship Mining: Connecting chemical structure to biological profiles. J. Biomol. Screen. 2014/4/7, (2014). Download paper.

Please note that as the L1000 and LINCS datasets mature we will revisit these terms. For now, given the evolving nature of the project, we request you contact us (or the LINCS program at NIH) directly if you have any questions on data access.

Because we make these fundamental research results available for free, we cannot bear any risk associated with your use of the data or its results. Further, in order to achieve some protection from unexpected and unforeseeable circumstances, MIT must disclaim its liabilities and damages in accordance with the laws governing software licensing. Please do not allow this legal requirement to discourage your use of the Connectivity Map website.

MIT MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE DATABASE, EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES OF MERCHANTABILITY, AS TO CONFORMITY WITH WHATEVER LITERATURE MAY BE ISSUED FROM TIME TO TIME, OR ABSENCE OF LATENT OR OTHER DEFECTS, WHETHER OR NOT DISCOVERABLE. MIT EXTENDS NO WARRANTIES OF ANY KIND AS TO THE ACCURACY OF THE DATABASE OR ITS COMPLETENESS OR FITNESS FOR ANY PURPOSE. NOTHING IN THIS AGREEMENT SHALL BE CONSTRUED AS A REPRESENTATION MADE OR WARRANTY GIVEN BY MIT THAT THE PRACTICE BY YOU OF THE LICENSE GRANTED HEREUNDER SHALL NOT INFRINGE THE PATENT RIGHTS, COPYRIGHTS, OR OTHER INTELLECTUAL PROPERTY RIGHTS OF MIT OR ANY THIRD PARTY.

IN NO EVENT SHALL MIT, OR ITS TRUSTEES, DIRECTORS, OFFICERS, EMPLOYEES, AND AFFILIATES BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY KIND, INCLUDING, WITHOUT LIMITATION, LOSS OF GOODWILL, ECONOMIC DAMAGES, OR INJURY TO PROPERTY AND LOST PROFITS, REGARDLESS OF WHETHER MIT SHALL BE ADVISED, SHALL HAVE OTHER REASON TO KNOW, OR IN FACT SHALL KNOW OF THE POSSIBILITY OF THE FOREGOING.

If, by operation of law or otherwise, any of the aforementioned warranty disclaimers are determined inapplicable, your sole remedy against MIT, regardless of the form of action, including, but not limited to, negligence and strict liability, shall be replacement of the Database with an updated version if one exists.