Skip to content

Latest commit

 

History

History
88 lines (52 loc) · 6.75 KB

ega-8-properties-policy-descriptor.md

File metadata and controls

88 lines (52 loc) · 6.75 KB

Policy descriptor Schema

https://raw.githubusercontent.com/EbiEga/ega-metadata-schema/main/schemas/EGA.policy.json#/properties/policyDescriptor

Node containing the full description of the policy, whether it is hosted at some public resourced and referenced here; or directly written here.

Abstract Extensible Status Identifiable Custom Properties Additional Properties Access Restrictions Defined In
Can be instantiated No Unknown status No Forbidden Forbidden none EGA.policy.json*

policyDescriptor Type

object (Policy descriptor)

any of

policyDescriptor Properties

Property Type Required Nullable Defined by
policyReference string Optional cannot be null EGA policy metadata schema
policyText string Optional cannot be null EGA policy metadata schema

policyReference

A publicly accessible reference to the policy, where the updated text of the policy is hosted.

policyReference

policyReference Type

string (Reference to the policy)

policyReference Constraints

URI: the string must be a URI, according to RFC 3986

policyReference Examples

"https://github.com/EbiEga/ega-metadata-schema/blob/main/schemas/EGA.policy.json"
"https://ega-archive.org/submission/dac/documentation"

policyText

Text describing in detail the Data Access Agreement (DAA) of the policy.

policyText

policyText Type

string (Policy text)

policyText Examples

"The data is fully available upon request with the data-access committee of this study."
"Access to data generated is available by emailing application to the Data Access Committee and will be granted to qualified investigators for appropriate use.\\nThe following two documents may be required by the Data Access Committee.\\n1) DATA ACCESS AGREEMENT\\nIn signing this agreement, You are agreeing to be bound by the terms and conditions of access set out in this agreement.\\nDefinitions:\\n- Data means all and any human genetic data obtained related to the 'Study on the proliferation history of lung adenomas'.\\n- User means a researcher whose User Institution has previously completed this Data Access Agreement and has received acknowledgment of its acceptance.\\n- User Institution means the organization at which the User is employed, affiliated or enrolled.\\nYou agree to use the Data only for the advancement of medical research, according to the consent obtained from sample donors.\\n- Publications means, without limitation, articles published in print journals, electronic journals, reviews, books, posters and other written and verbal presentations of research.\\nYou agree not to use the data for the creation of products for sale or for any commercial purpose.\\nYou agree to preserve, at all times, the confidentiality of any information related to Data and to not transfer or disclose the Data.\\nYou agree to use the data for the approved purpose and project described in your Application.\\nYou agree to acknowledge in any work based in whole or part on the Data, the published paper from which the Data derives.\\nFor and on behalf of User:\\n Report the name of Applicants, Signature of Applicants and Date.\\nFor and on behalf of User Institution:\\nReport the name of Institutional Authority, his/her and Date.\\n\\n2) DATA ACCESS APPLICATION FORM:\\nApplications for access to data can be submitted at any time. The Data Access Committee will consider applications on a rolling basis and aim to provide a decision within one months of receipt. The Application must include:\\n- A full postal and email address for each Applicant. PhD student applicants must include their supervisors as a co-applicant and provide their full contact details.\\n- Title of the project.\\n- A clear description of the project and its specific aims, including specific details of what You plan to do with the data and including key references.\\n- Signature, name and date of each Applicant.\\n- Data Access Agreement dated and signed."