You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Resource License Information: The following information was taken directly from the LINCS Release-Policy:
All investigators are encouraged, to publish results based on LINCS data. These results may include, but would not be limited to, integrating LINCS data with data from other sources. LINCS data are released with the sole restriction that they must be correctly cited so that others can establish provenance and access the original data; the correct citation will be released with each data set and will comprise either a PMID/PMCID reference or a unique LINCS identifier. Investigators are encouraged to inform the LINCS Consortium of ongoing integrative analyses in order to minimize duplicative and competitive analyses groups. This information will also be available on the Community pages of the LINCS website.
Is Identifier Mapping Required? Only minor annotation work may be needed given that all of the data follow FAIR and use many of the OBO ontologies. See here for link to information on mapping and the use of standard terminologies.
Rationale for New Resource Request: To enrich the current coverage of experimental and assay-based results that are represented in the KG.
Resource Name: LINCS Consortium Data
Resource URL:
Resource License Information: The following information was taken directly from the LINCS Release-Policy:
Data Source Identifier Type:
Is Identifier Mapping Required? Only minor annotation work may be needed given that all of the data follow FAIR and use many of the OBO ontologies. See here for link to information on mapping and the use of standard terminologies.
Rationale for New Resource Request: To enrich the current coverage of experimental and assay-based results that are represented in the KG.
@bill-baumgartner - Do you agree?
The text was updated successfully, but these errors were encountered: