1.2 How will the data be collected, observed or generated?

What standards, methodologies or quality assurance processes will you use?

Content to be filled in by: NL, KD, JK
In addition to the official SNSF guidance, consider also for each dataset type in your project (including data you might re-use):
Examples:

How will you organize your files and handle versioning?

Content to be filled in by: NL, JK, KD
Indicate and describe the tools you will use in the project. You may rely on the following tools depending on your needs:
Contact for assistance: researchdata@epfl.ch (EPFL), data-archive@library.ethz.ch (ETHZ)

1.3 What documentation and metadata will you provide with the data?

Content to be filled in by: JK, NL, KD, AS, ME
Indicate all the information that is required in order to be able to read and interprete the data (context of data) in future. General documentation of the data is often compiled into a plain text or markdown README file. These formats may be opened by any editor and are future proofed.
In addition, for each data type :
Additional information that are helpful in a README file:
Contact for assistance: researchdata@epfl.ch (EPFL), data-archive@library.ethz.ch (ETHZ)

2.Ethics, legal and security issues

2.1 How will ethical issues be addressed and handled?

Content to be filled in by: ReO (+VPSI), AS, ME
OK pour ReO, en cours.
Done for VPSI (see last sentence)
Methods to ensure the protection of personal and/or sensitive data are described in the following paragraph (2.2).

2.2 How will data access and security be managed?

Content to be filled in by: VPSI + ReO
OK pour ReO, en cours.
Done for VPSI (see below)
    - All personal data will be anonymized in such a way that it will be impossible to attribute data to specific persons.
     - All personal data will be pseudonymized. The correspondence table will be encrypted and access restricted to the project leader.    
    - All sensitive data will be encrypted and encryption keys will be managed only by authorized employees.
    - Sensitive data transfers will be end-to-end encrypted.
    - Sensitive data will be accessible only by authorized participants to the project. The list of authorized participants will managed by…
    - Data access rules will be detailed in before starting the project.
    - Access to laboratory and offices will be restricted to authorized persons. The list of authorized persons will managed by…
    - All data will be backuped on a regular basis and access to backup media will be managed accordingly to data access rules. Backups will be stored in another location.
    - All damaged media containing sensitive data will be physically destroyed.
    - All servers will be located in a datacentre… with restricted access.
    - No data will be stored on a public cloud / cloud hosted outside Switzerland.
    - No sensitive/personal data will be stored on a public cloud / cloud hosted outside Switzerland.
    - All computers storing or computing sensitive data will not be connected to the Internet.
    - All computers storing or computing sensitive data will have a hardened configuration (disk encryption, restricted access to privileged accounts to a small, controlled group of users, restricted or disabled remote access using privileged accounts, disabled guest or default accounts, local firewall, automatic screen lock with password protection, disabled remote out-of-band management (IPMI, Active Management Technology (AMT), etc.), disabled USB ports, removable privacy filter on screens, automatic updates via “Windows Update”, Apple’s “Software Update” or Linux “yum auto-update”, anti-virus software, Adobe’s “Flashplayer” and “Java” runtime disabled,…).