Data Access Committees (DACs)

All submissions made to the EGA must be affiliated to a Data Access Committee (DAC)

 

What is a DAC?

The Data Access Committee (DAC) usually consists of one or more named individuals whom are responsible for making the data access decisions for the datasets that fall under the responsibilty of the DAC.

A DAC is typically formed from the same organization that monitored the collection of samples and analyses of the derived data or a designate of this organization.

Mutiple datasets may be affiliated to a single DAC.

 

How is a DAC formed?

To establish a DAC you must register the details of your DAC during the submission process to the EGA.  You will be required to provide a DAC name, name of the individual/s that make up your DAC and contact details for your DAC, together with the datasets affiliated to the DAC.

All the necessary information you need to provide will be collected during the submission procedure.

 

How should a DAC be named?

The chosen name must be informative to the applicant.  For example, internal identifiers, such as grant numbers, should not be used.  Individual names, such as the name of the Principal Investigator should also not be used.  

DAC's are often named after the organisation or department of the data source.  Browse the full list of DAC names currently in the EGA.

 

What documentation does the DAC need to provide?

1. Data access application form

The Data access application form is used by the DAC to collect the necessary information from the applicant/s to enable the DAC to make its data access decisions.  It is the DAC's responsibility to provide the applicant with the Data Access application form.  The EGA does NOT need to receive a copy of the Data access application form.

Examples of a Data access application form

 

2. Data Access Agreement (DAA) 

Each dataset that is submitted to the EGA must be linked to a Data Access Agreement (DAA), which defines the terms and conditions of using the dataset, such as how the data files should be stored once downloaded or details of publication embargoes that should be observed by the approved user.  The DAA is collected when datasets are registered during the submission process.

Examples of a DAA

 

3. EGA DAC access policy document 


The document provides contact details of the authorised DAC user who will be provided access to the EGA DAC admin tools, which enable accounts to be created and managed with access permissions set for the dataset/s that fall under the DAC.  The document should be sent to the ega-helpdesk

Further information on the DAC access policy document

 

How does the DAC pass data access decisions to the EGA?

Authorised DAC users (named on the EGA DAC access policy document) are provided access to the EGA DAC admin tools.  The tools facilitate creation and management of new and existing EGA accounts with access permissions for the datasets that fall under the DAC's responsibilty. 

Upon receipt of the EGA DAC access policy document, the authorised DAC users are be sent further details, by email, on how to use the EGA DAC Admin tools.

The DAC contact/s named on the Data Access Policy document may also email the ega-helpdesk with full institutional contact details (including an institutional email address) of the successful applicants.  Please note: personal email addresses (e.g. Hotmai, Google, etc) are not accepted for creating EGA accounts.

**THE EGA WILL NOT CREATE EGA ACCOUNTS FROM APPLICATION FORMS FORWARDED BY THE DAC**