GISAID - gisaid

Grade
The grade for the resource as automatically determined by the criteria violations.
1
Description
A full description of the resource from the resource itself, if possible.
The GISAID Initiative promotes the international sharing of all influenza virus sequences, related clinical and epidemiological data associated with human viruses, and geographical as well as species-specific data associated with avian and other animal viruses, to help researchers understand how the viruses evolve, spread and potentially become pandemics.
Last curated
(Optional) The ISO 8601 date of when the resource was last curated.
2020-03-09
Location
URL for the resource.
https://www.gisaid.org
Source type
(Optional) How the resource relates to the data it contains. Current allowable entries are: "unknown", "repository", "source", "integrator", and "warehouse".
unknown
Curation status
Whether or not annotation is complete on this resource. Current allowable entries are: "complete", "incomplete", and "nonpublic".
complete
Field
The area of research for the resource.
biology
Type
The type of data the resource contains.
viral
Categories
(Optional) Tags to describe the resource and its data.
gene
clinical
epidemiology
influenza virus sequence
aves
evolution
demographic
geo-spatial
gis
Access
(Optional) Links to the resource's data.
None
License
The license that is used by the resource. We use SPDX where we can or: "inconsistent", "public domain", "unlicensed", "all rights reserved", or "custom".
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".
private pool
License location
(Optional) The link to the resource license.
https://www.gisaid.org/registration/terms-of-use/
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."
false
Issues
(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: The resource uses an extensive custom license.
Criteria B.1: There are terms (e.g. 2b) that would make it seem that GISAID would need to be negotiated with for any further reuse beyond.
Criteria C.1: The webapp-style interface is not suitable for scripting or batch operations; bulk access options were not apparent.
Criteria C.2: I believe it would take a bit of knowledge to probe out the correct calls and get through the authorization, assuming scripting was feasible.
Criteria D.1.2: No pass-through of data seems possible except through the license agreement; no academic exception seems to exist.
Criteria E.1.2: No pass-through of data seems possible except through the license agreement; no academic exception seems to exist.
Commentary
(Optional) Further commentary on the license, possibly including the though process of the curations and things like locations of additional licenses.
• The terms found at https://www.gisaid.org/registration/terms-of-use/ appear to be the same as the final version agreed to during registration.
• Additional terms for registry at https://www.gisaid.org/registration/register/ .
• Additional terms for registry at https://platform.gisaid.org/epi3/frontend#360c7c .
• The fact that the license agreement itself has terms makes conversation possibly difficult.
• While the license is quite readable, it has many interesting terms trying to control the behavior (e.g. 2b) of those under the agreement that may be best understood by law professionals.
• While not a current criteria violation, I feel it is worth noting that there was a 26 day waiting period between request and account creation.
Controversial
(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.
false
Contacts
(Optional) Resource contact information, link, email, or whatever is public.
https://www.gisaid.org/help/contact/
Grants
(Optional) Semi-structured list of supporting grants.
https://www.gisaid.org/about-us/grants/ , no current listing

All copyrightable materials on this site are © 2019 the (Re)usable Data Project under the CC-BY 4.0 license.
The (Re)usable Data Project is funded by the National Center for Advancing Translational Sciences (NCATS) OT3 TR002019 as part of the Biomedical Data Translator project and U24TR002306 as part of the CTSA Program National Center for Data to Health (CD2H).
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.