Protein ANalysis THrough Evolutionary Relationships Classification System (PANTHER) - panther

Grade
The grade for the resource as automatically determined by the criteria violations.
3
Description
A full description of the resource from the resource itself, if possible.
The PANTHER (Protein ANalysis THrough Evolutionary Relationships) Classification System was designed to classify proteins (and their genes) according to evolutionary family/subfamily, molecular function, biological process, and pathway. The PANTHER Classifications are the result of human curation as well as sophisticated bioinformatics algorithms.
Last curated
(Optional) The ISO 8601 date of when the resource was last curated.
Unknown
Location
URL for the resource.
http://pantherdb.org/
Source type
(Optional) How the resource relates to the data it contains. Current allowable entries are: "unknown", "repository", and "source", and "integrator".
TBD
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.
genomic resource
Categories
(Optional) Tags to describe the resource and its data.
orthology
Access
(Optional) Links to the resource's data.
download
License
The license that is used by the resource. We use SPDX where we can (https://spdx.org/licenses/) or: "unknown", "public domain", "all rights reserved", or "custom".
all rights reserved
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 "TODO" is used. Current possible values are: "unknown", "copyleft", "permissive", "public domain", "copyright", "restrictive", or "closed pool".
copyright
License location
(Optional) The link to the resource license.
TBD
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 D.1.2: Given the all rights reserved copyright statement, any downstream reuse would require negotiation.
Criteria E.1.2: Given the all rights reserved copyright statement, all user/agent types would need to negotiate downstream reuse.
Commentary
(Optional) Further commentary on the license, possibly including the though process of the curations and things like locations of additional licenses.
• There is an alternate curation for this resource that bases itself off of 'http://www.pantherdb.org/tou.jsp', which was found using a narrow Google search and not given consideration due to the difficulties in finding it--we have found no access to this document yet except for the Google search.
• Considering the alternate license, downloads are under a permissive minimal license that states '...as long as the following copyright statement is placed at the top of each file: Copyright © 2005 SRI International', which besides being likely out of data, is custom and does not cover APIs, remixing, and the like. It is hard to interpret the consequences of this license.
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.
feedback@pantherdb.org
pdthomas@usc.edu
Grants
(Optional) Semi-structured list of supporting grants.
TBD

All copyrightable materials on this site are © 2017 the (Re)usable Data Project under the CC-BY 4.0 license.
ReusableData.org 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.