Data management plan (Draft)

D9.3 – Data Management Plan (1st version) March 2022 Authors: Carlos Serra Castells (UVEG); Alfonso Gallego Valadés (UVEG) Ref. Ares(2022)2406772 - 31/03/2022 A2C – Deliverable D9.3V1.0 Page 2 of 35 Technical references Project Acronym Agro2Circular Project Title TERRITORIAL CIRCULAR SYSTEMIC SOLUTION FOR THE UPCYCLING OF RESIDUES FROM THE AGRIFOOD SECTOR Project Coordinator Fuensanta Monzó CETEC [email protected] Project Duration October 2021 – September 2024 (36 months) Deliverable No. D9.3 Dissemination level* PU Work Package WP 9 - Project management and coordination activities Task T9.3 - Ethical issues management and Data Protection issues Lead beneficiary 22 (UVEG) Contributing beneficiary/ies All partners Due date of deliverable 31 March 2022 Actual submission date 31 March 2022 * PU = Public PP = Restricted to other programme participants (including the Commission Services) A2C – Deliverable D9.3V1.0 Page 3 of 35 RE = Restricted to a group specified by the consortium (including the Commission Services) CO = Confidential, only for members of the consortium (including the Commission Services) Document history V Date Comments v0.1 First draft of document v0.2 Revised version based on the comments of Fuensanta Monzó ) - CETEC v1.0 First final version, approved by the WP leader and the project coordinator, (will be) submitted to EC. v1.1 First draft based upon first final version v2.0 Second final version, approved by the WP leader and the project coordinator, (will be) submitted to EC. Document Distribution Log Version Date Distributed to v0.1 28/03/2022 Fuensanta Monzó-Project coordinator V0.2 30/03/2022 WP leader with corrections made by the project coordinator Verification and approval Name Date Verification Final Draft by WP leader Alfonso Gallego 31/03/2022 Approval Final Deliverable by coordinator Fuensanta Monzó 31/03/2022 A2C – Deliverable D9.3V1.0 Page 4 of 35 Disclaimer and acknowledgement This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 101036838 Disclaimer This document reflects only the views of the author(s) the European Research Executive Agency (REA) is not responsible for any use that may be made of the information it contains. Whilst efforts have been made to ensure the accuracy and completeness of this document, the A2C consortium shall not be liable for any errors or omissions, however caused. A2C – Deliverable D9.3V1.0 Page 5 of 35 Table of contents 1 List of abbreviations 7 2 Executive summary ..................................................................... 8 3 Data summary ............................................................................. 9 3.1 A2C project .......................................................................................................... 9 3.2 Data generation and collection ........................................................................ 16 4 FAIR Data .................................................................................. 17 4.1 Making data findable ......................................................................................... 17 4.1.1 Metadata ...................................................................................................... 17 4.1.2 File naming ................................................................................................... 18 4.2 Making data openly accessible ........................................................................ 19 4.2.1 Storage ......................................................................................................... 23 4.2.2 Data access .................................................................................................. 23 4.3 Making data interoperable ................................................................................ 24 4.3.1 File formats ................................................................................................... 25 4.4 Increase data re-use .......................................................................................... 28 4.4.1 Long-term use of the data ............................................................................ 28 4.4.2 Data quality control ....................................................................................... 29 5 Allocation of resources .............................................................. 31 A2C – Deliverable D9.3V1.0 Page 6 of 35 5.1 Costs for making data FAIR .............................................................................. 31 5.2 Responsibilities ................................................................................................. 31 6 Data security .............................................................................. 33 7 Ethical aspects ........................................................................... 35 A2C – Deliverable D9.3V1.0 Page 7 of 35 1 List of abbreviations APC Article Publishing Charges DAC Data Access Committee DIS Data Integration System DMP Data Management Plan DPO Data Protection Officer EC European Commission EG Ethylene Glycol FAIR Findable, Accessible, Interoperable and Re-usable FNC File Naming Convention F&V Fruits & Vegetables GA General Assembly GDPR General Data Protection Regulation LCA Life Cycle Assessment PE/PET Polyethylene/Polyethylene Terephthalate RA Research Action TPA Terephthalic Acid WP Work Package A2C – Deliverable D9.3V1.0 Page 8 of 35 2 Executive summary This is the first version of the Data Management Plan (DMP) of the Agro2Circular (A2C) project, prepared for the 6-month point in the project. The DMP describes the data management lifecycle, indicating how research data collected, processed or generated by the A2C project will be handled during and after the completion of the study. Thus, this deliverable aims to inform A2C partners about the main guidelines and good practices that will be applied to the data processed and generated in the project. This DMP defines the methodologies and standards that will be applied in A2C to make the data FAIR: findable, accessible, interoperable and reusable. The DMP has been drafted following the guidelines on FAIR data management in Horizon 2020 and the general template annexed to the document 1 . The DMP is intended to be a living document in which information will be available at a more detailed and specific level through regular updating as the project implementation progresses and when significant changes or milestones occur. The final version of the DMP will be delivered at month 34. 1 European Commission (2016). Guidelines on FAIR Data Management in Horizon 2020. Available at https://ec.europa.eu/research/participants/data/ref/h2020/grants_manual/hi/oa_pilot/h2020-hioa-data-mgt_en.pdf A2C – Deliverable D9.3V1.0 Page 9 of 35 3 Data summary 3.1 A2C project Agro2Circular (A2C) is a 36-months EU-funded project aiming at the implementation of a territorial systemic solution for the upcycling of most relevant residues in the agrifood sector (Fruits & Vegetables and multilayers) into high added value products, powered by a digital tool and constructed upon a systemic approach with high replicable/scalable potential. A2C systemic solution is based in following strategies: 1. lnnovative green hybrid extraction, purification and stabilisation routes to obtain bioactives from F&V wastes. 2. First recycling value chain for post-industrial multilayer films by combining innovative sorting, physical delamination, enzymatic depolymerisation, decontamination and mechanical recycling. 3. Digital platform for the agrifood sector, traceability in real time and decision support tool for optimal valorisation routes. 4. A2.C multidimensional model and tools fostering the territorial development of circular economy and enabling its replication/scalability, constructed through public engagement and co-creation processes. A2C has the following objectives: Objective 1: Demonstrating the first value chain for the upcycling of most representative agrifood sector wastes. Aims to demonstrate the technical viability of specific routes for the valorisation of agrifood wastes (F&V and multilayer plastics). Objective 2: Providing to the A2C technological solution the circular systemic approach by building a multidimensional model enabling the solution territorial deployment and its replication and scalability. A2C – Deliverable D9.3V1.0 Page 16 of 35 3.2 Data generation and collection Data collection under the A2C project will be as diverse as the topics covered and methodologies used at the seven RAs. An overview of the data to be collected is presented at Table 1. Some data to be collected at the different RAs are not completely specified yet, but main general guidelines on how they will be collected and processed are already defined, which are described below. Additionally, it is important to highlight that A2C consortium claims that data to be collected under the different RAs are adequate, relevant and limited to what is necessary for the research purpose fulfilling the Data Minimization Principle of the GDPR. Thus, as tasks and methodologies are clarified in the future months, A2C researchers will establish the norms to be used in data collection and data sets to be collected. Depending on their origin, two main types of data will be used during the A2C lifetime: • Data purposely generated by project partners under different activities through several means, such as surveys, individual interviews, etc. • Background data gathered by partners before the start of the project that is relevant in order to perform the project tasks and achieve its objectives. Personal data will be subject to de-identification and site control, unless written informed consent for very clearly defined research activities is specifically obtained. Data formats and data types produced under the project depend on how data will be gathered and the software used for their analysis. Clearly, several data types require different file types. As general guidelines, A2C recommends: • avoiding the use of property software format when possible; • in case of data files in different formats, converting the data to the most common data format. A2C – Deliverable D9.3V1.0 Page 17 of 35 4 FAIR Data 4.1 Making data findable In order to ensure that research data can be used, shared and re-used it is crucial to take care that those data are accessible, understandable and usable. This requires clear data description, annotation, contextual information and documentation explaining how data were created or digitized, what data mean or what their content and structure are. A2C will encourage establishing strong links between data collected and stored and the associated documentation, following recommendations such as the following: • Including information within the data or document itself, e.g., in the document properties function of a file or the file header. • Keeping a database of metadata with links to files. • Storing a readme.txt file alongside the data which provides basic explanatory details. Txt. Files will be acceptable to explain very simple stuff like how to connect to a database, not the database explanation itself • Recording relevant context in lab notebooks or associated papers and reports. • Including link to websites or web pages which explain the context of the research. 4.1.1 Metadata The use of common data and metadata standards are a key aspect for semantic and technological data operability. Metadata can describe the content, context and provenance of datasets in a standardized and structured manner, typically describing the purpose, origin, temporal characteristics, geographic location, authorship, access conditions and terms of use of a dataset. This provides structured searchable information that helps users to find existing data resources, judge whether a particular dataset is suitable for their research purpose and provides a bibliographic record for citing data. Standard dictionaries of metadata will be used for all data types produced by the data creators. A2C metadata will include different types of metadata: A2C – Deliverable D9.3V1.0 Page 18 of 35 • Descriptive metadata: describe a resource for the purpose of retrieval and identification. They may contain elements such as title, abstract, author or keywords, etc. • Structural metadata: relationships between different sets of associated data in the context of databases, such as schema describing associations between tables. • Administrative metadata: provides the information necessary to help process a resource. An example might be the date of creation or how a resource was created. It may contain several subgroups of administrative information. Among the most common are metadata on rights and metadata for long-term preservation. The latter is one of the primary purposes of repositories. A2C encourages the use of the Dublin Core metadata schema, characterised by the specification of fifteen "core" elements (properties) to describe resources. These elements have been formally endorsed in the standards ISO 15836 2 , ANSI/NISO Z39.85-2012 3 and IETF RFC 5013 4 , and consist of: 1. Contributor, 2. Coverage, 3. Creator, 4. Date, 5. Description, 6. Format, 7. Identifier, 8. Language, 9. Publisher, 10. Relation, 11. Rights, 12. Source, 13. Subject, 14. Title, and 15. Type. 4.1.2 File naming Structured data storage is essential for a proper and secure storage of data files and records. For any file-based storage this includes clear and unambiguous file naming, the use of proper versioning as well as clear and intuitive folder structure. In this sense, a file naming convention (FNC) helps the project files stay organized by making it easy to identify the file(s) that contain the information from its title and by grouping files that contain similar information close together. A good FNC also helps the consortium members to better understand and navigate through the work performed by other partners. 2 ISO (2017). 15836-1:2017 Information and documentation — The Dublin Core metadata element set — Part 1: Core elements. Available at https://www.iso.org/standard/71339.html 3 ANSI/NISO (2013). Z39.85-2012 The Dublin Core Metadata Element Set. Available at http://www.niso.org/publications/ansiniso-z3985-2012-dublin-core-metadata-element-set 4 IETF (2007). RFC 5013. Dublin Core Metadata. Available at https://datatracker.ietf.org/doc/html/rfc5013 A2C – Deliverable D9.3V1.0 Page 19 of 35 A2C will encourage the use of a standard FNC per data type and a clear versioning strategy. Below are some basic rules for the development of A2C FNCs, based on 5 , 6 : • Find the right balance of components. Too few components create ambiguity; too many limits discovery & understanding. • Avoid extra-long folder names and complex hierarchical structures but use information‐rich filenames instead. • Abbreviate the content of elements whenever possible and use meaningful abbreviations. File names that contain too many characters can be unwieldy and cause problems in transferring files. • Use the underscore (_) as element delimiter. Do not use spaces or other characters such as: ! # $ % &. • Use the hyphen (‐) to delimit words within an element or capitalize the first letter of each word within an element. • Document your decisions including what components you will use (the "project name" for example), what are the appropriate entries, what acronyms mean, etc. • Files will be grouped together based on the first few components so start the FNC with the more general components and move to the more specific ones later on. Dates should always be yyyy-mm-dd to organize files chronologically. • FNC will be shared among all partners of the project in order all individuals who needs to use the FNC are aware of it and knows how to apply it. A file naming convention breaks down if not followed consistently. 4.2 Making data openly accessible Accessibility means that metadata and data are understandable to humans and machines, and may be retrievable by their identifier via a standardised communication protocol. As stated in Article 29.2 Grant Agreement, each beneficiary must ensure open access (free of 5 Purdue University, Libraries and School of Information Studies: http://guides.lib.purdue.edu/c.php?g=353013&p=2378293 6 Santaguida, V. (2010). Folder and file naming convention – 10 rules for best practices. Available at: http://www.exadox.com/files/pdf/en/Folder-File-Naming-Convention-10Rules-Best-Practice.pdf A2C – Deliverable D9.3V1.0 Page 20 of 35 charge online access for any user) to all peer-reviewed scientific publications relating to its results. In particular, beneficiaries must: • Deposit a machine-readable electronic copy of the published version or final peerreviewed manuscript accepted for publication in a repository for scientific publications, as soon as possible and at the latest on publication. • Ensure open access to the deposited publication — via the repository — at the latest on publication, if an electronic version is available for free via the publisher; or within six months of publication (twelve months for publications in the social sciences and humanities) in any other case. • Ensure open access — via the repository — to the bibliographic metadata that identify the deposited publication. The bibliographic metadata must be in a standard format and must include all of the following: • the terms “European Union (EU)” and “Horizon 2020”; • the name of the action, acronym and grant number; • the publication date, and length of embargo period if applicable, and • a persistent identifier. Moreover, the beneficiary must aim to deposit at the same time the research data needed to validate the results presented in the deposited scientific publications. In this regard, as stated in Article 29.3 Grant Agreement, beneficiaries must also • Deposit in a research data repository and take measures to make it possible for third parties to access, mine, exploit, reproduce and disseminate — free of charge for any user — the data, including associated metadata, needed to validate the results presented in scientific publications, as soon as possible; and other data, including associated metadata. • Provide information — via the repository — about tools and instruments at the disposal of the beneficiaries and necessary for validating the results (and, where possible, provide the tools and instruments themselves). A2C – Deliverable D9.3V1.0 Page 21 of 35 This does not change the obligation to protect results, the confidentiality obligations, the security obligations or the obligations to protect personal data. Article 29.3 also provides that, as an exception, beneficiaries do not have to ensure open access to specific parts of their research data, both for data linked to scientific publications and other data, if the achievement of the main objective of the action is jeopardised by making those specific parts of the research data accessible to the public. As a general guideline, A2C will encourage the whole consortium to publish research papers at peerreviewed open access journals. The following shows some of the data that could be made available in open access via scientific publications, repository hosting or both. Datasets likely to contain personal information will be properly pseudonymised before being made available, respecting the confidentiality and security of the data subjects. ● Task 1.1 A2C Requirements. The results of this task will be reported in a public deliverable (A2C requirements). ● Task 1.2 A2C methodologies. A pre-dossier EFSA will be reported (EFSA plastics pre-dossier and compliance with agricultural standards D1.5, EFSA agrifood predossier and compliance with food/cosmetic standards D1.6). ● Task 1.4 A2C residues management and preliminary characterization. A residues management plan will be generated and it will be reported in three deliverables (D1.2, D1.3 and D1.4) ● Task 2.2 Extraction of high value-added substances at laboratory scale. Presentations, posters or technical and scientific papers will be generated. ● Task 2.3 Purification and stabilisation of extracts. Presentations, posters or technical and scientific papers will be generated. ● Sub-Task 3.1.1 Pre-treatments and preliminary decontamination. Presentation or technical paper will be generated. ● Task 3.2 Optical sorting of the multilayer materials. Presentations, posters or technical and scientific papers will be generated, including 2 deliverables (D3.3 and D3.4) ● Task 3.3 Physical recycling of complex multilayers containing aluminium. Presentations, posters, or technical and scientific papers could be created describing the separation of aluminium from multilayer structures. A2C – Deliverable D9.3V1.0 Page 22 of 35 ● Task 3.5 Mechanical recycling of simple multilayer structures and products from physical recycling. Presentations, posters or technical and scientific papers will be generated. ● Task 4.1 Formulations of the extracts at small scale. Presentations and technical information will be generated, including 1 deliverable (D4.1). ● Task 4.2 Pilot scale up of the optimal extraction routes. Presentations and technical information will be generated, including 3 deliverables (D4.2, D4.3 & D4.4) ● Sub-Task 5.1.2, 5.1.3 and 5.1.4: report on PHBV and carotenoids production, recovery and by-product valorization. Presentations, posters or scientific papers will be generated. ● Task 5.2 High barrier recycled and recyclable compounds. Presentations, posters or technical and scientific papers will be generated. ● Task 5.3 Biodegradable compounds. Presentations, posters or technical and scientific papers will be generated. ● Sub task 5.4.1 Compounds transformation. Presentations, posters or technical and scientific papers will be generated. ● Sub-task 5.4.2 Validation at small scale. Presentations, posters or technical papers will be generated. ● Sub-task 5.4.3 Plastics end life scenarios. A public deliverable D5.8 Plastic endlife scenarios will be generated. ● Task 6.1 and 6.2 Integrations and A2C demonstrators. A deliverable with the integration description and videos from the A2C demonstrators will be generated. Presentations, posters or technical papers will be generated. ● Task 6.3 Setting the basis for the future industrial implementation. A public A2C process protocol paper will be generated (D6.4) ● Task 7.1 Public engagement and community-based schemes. Public deliverables (D7.1-4) will be generated including the main features of the public engagement strategy and the community-based schemes, its implementation and main results; specific aspects will be included in the policy briefs deliverables (D7.1213), if relevant. Besides, presentations, posters or scientific papers will be generated including the main results of the public engagement strategy (Sub-task 7.1.1.) A2C – Deliverable D9.3V1.0 Page 23 of 35 Moreover, the results of the pilot community-based innovation action (Sub-task 7.1.2.) will be reported for publication in a peer-reviewed open access journal. ● Task 7.4 Social and economic analysis. The results of this task will be reported for publication in a peer-reviewed open access journal. ● Task 7.7 Validation of the A2C multidimensional model. The main results will be included in the associated public deliverable (D7.16) and presentations, posters or scientific papers will be generated. ● Task 8.8 Standardization activities. Depending on the A2C standardization strategy (to be developed and implemented), the contribution to the standardization could imply the proposal of revision of existing standards (publicly available) or the development of CEN Workshop agreements (publicly available, free of charge). 4.2.1 Storage The storage of the data collected and generated under the RAs carried out at A2C will primarily be the responsibility of the joint data controllers. However, A2C will select a data repository where all partners will be encouraged to store research data generated. It is particularly encouraged to store the research data in the Mendeley Data repository (https://data.mendeley.com/ ), as it allows to easily make the data FAIR 7 . 4.2.2 Data access The documentation describing how to find, get and access data will be described and stored in the selected data repository or software documentation. Thus, no additional documentation will be provided by the A2C project. For the cases where access to the data needs to be restricted this can be identified at the time the data is submitted to the data repository. Registration to the selected repository will 7 Elsevier. Making your data FAIR with Mendeley Data. Available at https://www.elsevier.com/__data/assets/pdf_file/0013/1012036/ACAD_RES_MDD_INFO_Fair-data-withMendeley-Data_WEB.pdf A2C – Deliverable D9.3V1.0 Page 24 of 35 be necessary as well as access via password in order to obtain A2C data. For restricted data there will be a contact point for requests for data access. Formats of data to be produced by the A2C consortium at the RAs can be handled by commonly used commercial or open software. Thus, data will be accessible using the same community-standard software. 4.3 Making data interoperable “Interoperability is the ability to access and process machine-readable data from multiple sources, sometimes automatically, without that data losing meaning or integrity” 8 . In order to achieve this goal, data requires: • Syntactic interoperability: widespread adoption of standard data formats, and the implementation of application programming interfaces and connectors that allow data from multiple sources to be accessed and integrated; • Semantic interoperability: data and information must be exchanged across systems without its context and meaning being lost; and • Search interoperability: it enables a user to conduct queries across two or more collections of data. Thus, interoperability enables improved data usability and use. For this reason, putting in practice interoperability will be a priority for A2C in order to have the following benefits (among others): • reducing time, effort and expense spent on data collection; • eliminating frustration and risks associated with finding inconsistent and incomplete data; • making available sustainable, disaggregated data for effective decision-making. 8 Steele, L., & Orrell, T. (2017). The frontiers of data interoperability for sustainable development. Development Initiatives (p. 5). Available at: https://www.publishwhatyoufund.org/wpcontent/uploads/2017/11/JUDS_Report_Web_061117.pdf A2C – Deliverable D9.3V1.0 Page 25 of 35 The following is a set of guiding principles for interoperability, based on Open Data Watch 9 , to be applied within the A2C framework: • Use and re-use existing standards: no new standards should be created in areas they already exist unless absolutely necessary. When new standards are created, they must be compatible with existing standards. • Do not overlook metadata: metadata is crucial for discoverability, accessibility and fostering trust and understanding of the context in which the data was produced. • Use common classifications wherever possible: it is important to ensure that to the extent possible, the language used to define and classify that data is the same. • Publish data in machine-readable formats: it enables a computer to access, identify and filter data in an automated way. • Ensure that standards are user driven: for data to be usable, it has to be driven by the needs of users themselves. It is crucial to long-term success and impact. 4.3.1 File formats Table 2 provides an overview of possible formats for data sharing, reuse and preservation to be used in the A2C project. 9 Open Data Watch. What are the principles of joined-up data? Available at https://opendatawatch.com/blog/what-are-the-principles-of-joined-up-data/ A2C – Deliverable D9.3V1.0 Page 32 of 35 • DPO provides expert professional knowledge in data protection law and IT security. The duties of the DPO includes: to inform and advise the controller or the processor and the employees who carry out processing of their obligations pursuant to the GDPR; to monitor compliance with personal data protection regulation; to provide advice where requested as regards the data protection impact assessment and monitor its performance; to cooperate with the supervisory authority; to act as the contact point for the supervisory authority on issues relating to processing, and to consult with regard to any other matter (art. 39.1 GDPR). Also, a DAC will be established specifically to address issues related to data release to external requestors. A2C – Deliverable D9.3V1.0 Page 33 of 35 6 Data security Data security refers to the process of protecting data from unauthorized access and data corruption throughout its lifecycle. Physical security, network security and security of computer systems and files will be considered and encouraged among the A2C consortium in order to guarantee security of data as well as to prevent unauthorized access, changes to data, disclosure or destruction of data (see Table 3). Table 3. Security measures Description Physical data security • Controlling access to buildings, rooms, cabinets where data, computers, media or hardcopy materials are held. • Logging the removal of, and access to, media or hardcopy material in store rooms. • Transporting sensitive data only under exceptional circumstances, even for repair purposes; for example, giving a failed hard drive containing sensitive data to a computer manufacturer may cause a breach of security. Network security • Not storing sensitive data such as those containing personal information on servers or computers connected to an external network, particularly servers that host internet services. • Firewall protection and security-related upgrades and patches to operating systems to avoid viruses and malicious code. Security of computer systems and files • Locking computer systems with a password. • Ensuring computer software is up-to-date. A2C – Deliverable D9.3V1.0 Page 34 of 35 • Protecting servers by power surge protection systems through line-interactive uninterruptible power supply (UPS) systems. • Implementing password protection and controlled access to data files, for example ‘no access’, ‘read only’, ‘read and write’ or ‘administrator-only’ permission. • Controlling access to files, folders or entire hard drives encryption. • Not sending personal or confidential data via email or other file transfer means without first encrypting them. • Destroying data in a consistent manner when needed: deleting files and reformatting a hard drive will not prevent the possible recovery of data; consult our guidance on data disposal. • Imposing non-disclosure agreements for managers or users of confidential data. Content extracted from UK Data Service 17 Cloud-based storage – specifically Google Drive – will be used by the project consortium in order to store and share relevant documents at management, administrative and technical level, such as meeting agendas, draft and final versions of deliverables or dissemination activities. Nevertheless, A2C is aware that this type of cloud storages is not necessarily permanent or secure. For this reason, data collected from the different tasks that include high-risk information – such as files containing personal or sensitive information or that have a very high intellectual property or commercial value – will not be stored on them. 17 UK Data Service. Data security. Available at: https://www.ukdataservice.ac.uk/manage-data/store/security A2C – Deliverable D9.3V1.0 Page 35 of 35 7 Ethical aspects A2C will be compliant with ethical guidelines as well as with the EU regulations regarding the protection of personal data. Thus, in order to adapt those guidelines and materialise in accordance with A2C objectives and characteristics, several deliverables have been or will be released facilitating that the whole consortium are aware and compliant with them. These deliverables are the following: ● D9.2 – Ethics Handbook ● D10.2 – POPD – Requirement No. 2. Specifically, D.9.2 presents the ethical guidelines and regulations of the project. The purpose of this document is to ensure that relevant legal and ethical issues are considered. All partners are responsible for ensuring that research is conducted in compliance with the guidelines described in D.9.2, which establishes set of fundamental principles to ensure Good Scientific Practise, the integrity of research involving human participants, and general principles of data privacy, confidentiality and security, including also a sample confidentiality agreement and consent form that will be the basis for the participation of the users to all the research activities carried-out in the framework of the Agro2Circular project