ArrayExpress - arrayexpress

The grade for the resource as automatically determined by the criteria violations.
A full description of the resource from the resource itself, if possible.
ArrayExpress Archive of Functional Genomics Data stores data from high-throughput functional genomics experiments, and provides these data for reuse to the research community.
Last curated
(Optional) The ISO 8601 date of when the resource was last curated.
URL for the resource.
Source type
(Optional) How the resource relates to the data it contains. Current allowable entries are: "unknown", "repository", "source", "integrator", and "warehouse".
Curation status
Whether or not annotation is complete on this resource. Current allowable entries are: "complete", "incomplete", and "nonpublic".
The area of research for the resource.
The type of data the resource contains.
microarray experiments
(Optional) Tags to describe the resource and its data.
functional genomics
(Optional) Links to the resource's data.
The license that is used by the resource. We use SPDX where we can or: "inconsistent", "public domain", "unlicensed", "all rights reserved", or "custom".
License type
The type of license that is being used. This will be to define compatible data pools in the future; we only use the grossest terms now. If it is not known "unknown" is used. Current possible values are: "unknown", "unlicensed", "copyleft", "permissive", "public domain", "copyright", "restrictive", or "private pool".
License location
(Optional) The link to the resource license.
Focused curation
(Optional) Setting this flag to true indicates that the licensing was combinatorially complicated enough (as is the case in some commercial licenses) that the curator chose to wear a single "hat" during the process. From the site text: "While we try to cover as much of the licensing possibilities of a data resource that we can, in a few cases we may choose a particular "hat" to wear while evaluating to prevent a combinatorial explosion, which may also reduce the clarity of our curations for the community. In these cases, we may take on the role of a (1) non-commercial (2) academic (3) group that is (4) based in the US and trying to (5) create an aggregating resource, noting that other entities may have different results in the license commentary."
(Optional) Structured issues with the license. For every issue discovered with a resource, there should be a corresponding item in the license-issues field that marks the /exact/ violation, along with any comments. This field can be used by resources as the first step to improvement, as well as clarify any surrounding circumstances. Any issues or thoughts about a resource that do not slot into one of the criteria violations can go into the license-commentary field.
Criteria A.2.2: Minimal custom permissive terms.
(Optional) Further commentary on the license, possibly including the though process of the curations and things like locations of additional licenses.
• The entirety of the license appears to be: "No restrictions, all public data from ArrayExpress can be used by anyone and our services are completely free of charge."
• Otherwise, ArrayExpress seems to defer its licensing and ToS to the EBI terms; e.g.:; while these are similarly permissive, we take the ArrayExpress terms at face value.
• While there are distinctions occasionally made between "private" and "public" data, it seems that "private" is just staging data before publication and does not affect evaluation.
• There is an interesting section ( that describes situations where data needs to be retracted. This section, while alarmingly titled, is has no effect on the license determination.
(Optional) Marker noting that there was some extended internal discussion or controversy about the evaluation of the licensing terms. If this is marked at "true", the controversy, or a link to a permanent archive of the controversy, must be sufficiently contained in the "license-commentary" to reconstruct the issues.
(Optional) Resource contact information, link, email, or whatever is public.
(Optional) Semi-structured list of supporting grants.
ArrayExpress and related activities are supported by member states of the European Molecular Biology Laboratory; European Commission: ENGAGE [201413], EurocanPlatform [260791], GEUVADIS [261123], SLING [226073], SYBARIS [242220], EUROCANPLATFORM [260791], CAGEKID [241669], BioMedBridges [284209] and Gen2Phen [200754]; US National Institutes of Health (the National Human Genome Research Institute, National Institute of Biomedical Imaging and Bioengineering and the National Cancer Institute) [P41 HG003619]; National Center for Biomedical Ontology (one of the National Centers for Biomedical Computing supported by the National Human Genome Research Institute, the National Heart, Lung, and Blood Institute, and National Institutes of Health Common Fund [U54-HG004028]); National Science Foundation Award Number [1127112].

All copyrightable materials on this site are © 2017 the (Re)usable Data Project under the CC-BY 4.0 license. is funded by the National Center for Advancing Translational Sciences (NCATS) OT3 TR002019 as part of the Biomedical Data Translator project.
The (Re)usable Data Project would like to acknowledge the assistance of many more people than can be listed here. Please visit the about page for the full list.