Data management plan 1 (Deliverable D7.2)
Abstract
This plan outlines the workflow for data management, including the creation, curation and sharing of data. The responsibilities of the file managers are outlined, along with the guidelines for creating and curating data on the RestPoll drive.
Full text
Data management plan 1 WP7: COORDINATING, NETWORKING, AND DATA MANAGEMENT TASK 7.2: DATA MANAGEMENT AND PUBLICATION STRATEGY Deliverable D7.2 30 December 2024 Version 1 Dimitry Wintermantel, Amibeth Thompson, Felix Fornoff University of Freiburg Sara Leonhardt, Paula Prucker, TUM Zehra Basaran, Georgios Kleftodimos, CIHEAM-IAMM Georg Andersson, Maj Rundlöf, ULUND Oliver Schweiger, UFZ / Nicola Gallai, ENSFEA Martin Thorsøe, AU / Annie Ouin, INPT Remco Ploeg, WU / Lynn Dicks, UCAM Tom Breeze, UREAD RestPoll Restoring Pollinator habitats across European agricultural landscapes based on multi-actor participatory approaches
This project receives funding from the European Union’s Horizon Europe Framework Programme under project No. 101082102. 2 D7.2: Data management plan Prepared under contract from the European Commission Grant agreement No. 101082102 EU Horizon Europe Framework Programme Project acronym: RestPoll Project full title: Restoring Pollinator habitats across European agricultural landscapes based on multi-actor participatory approaches Start of the project: Oct 2023 Duration: 48 months Project coordinator: Professor Alexandra-Maria Klein University of Freiburg, Freiburg, Germany www.restpoll.eu Deliverable title: Data management plan 1 Deliverable n°: D7.2 Nature of the deliverable: Report Dissemination level: Public WP responsible: WP7 Lead beneficiary: ALU Citation: Wintermantel, D., Thompson, A., Fornoff, F. et al. (2024). Data management 1. Deliverable D7.2. EU Horizon RestPoll Project, Grant agreement No. 101082102. Due date of deliverable: Month 15 Actual submission date: Month 15 Deliverable status: Version Status Date Author(s) 1.0 Submission to EU 30 Dec 2024 Wintermantel [ALU-FR], Thompson [ALU-FR], Fornoff [ALU-FR], Leonhardt [TUM], Prucker [TUM], Basaran [CIHEAM-IAMM], Kleftodimos [CIHEAM-IAMM], Andersson [ULUND], Rundlöf [ULUND], Schweiger [UFZ], Gallai [ENSFEA], Thorsøe [AU], Ouin [INPT], Ploeg [WU], Dicks [UCAM], Breeze [UREAD] The content of this deliverable does not necessarily reflect the official opinions of the European Commission or other institutions of the European Union.
This project receives funding from the European Union’s Horizon Europe Framework Programme under project No. 101082102. 3 D7.2: Data management plan Table of contents Preface .................................................................................................................................................. 4 1. Summary ....................................................................................................................................... 4 2. General workflow........................................................................................................................ 5 3. RestPoll drive and folder structure ......................................................................................... 6 4. Naming conventions .................................................................................................................. 9 4.1. Variable Names ........................................................................................................................ 9 4.2. File names ................................................................................................................................. 9 4.3. Public Data folder names ..................................................................................................... 11 5. General metadata in README sheets/files ......................................................................... 11 6. Data dictionary ........................................................................................................................... 11 7. Data file structure ..................................................................................................................... 12 7.1. Quantitative Data Files ........................................................................................................ 12 7.2. Qualitative Data Files ........................................................................................................... 15 8. Data storage and backup ......................................................................................................... 15 8.1. Track-Changes and Version Control ................................................................................ 16 9. Repositories for publication ................................................................................................... 16 9.1. Zenodo ..................................................................................................................................... 17 9.2. GLOBI ....................................................................................................................................... 17 9.3. GBIF .......................................................................................................................................... 17 9.4. The EU Pollinator hub ........................................................................................................... 17 10. Responsible contact people ..................................................................................................... 17 10.1. Data Ownership .................................................................................................................. 17 11. FAIR data ..................................................................................................................................... 18 11.1. Making data findable, including provisions for metadata ........................................ 18 11.2. Making data accessible .................................................................................................... 18 11.3. Making data interoperable .............................................................................................. 18 11.4. Increase data re-use ........................................................................................................ 19 12. Other research outputs ........................................................................................................... 19 13. Allocation of resources ............................................................................................................ 19 14. Data security .............................................................................................................................. 19 15. Ethics .......................................................................................................................................... 20 16. Other issues .............................................................................................................................. 20 17. Accessing the RestPoll Drive ................................................................................................. 20 17.1. Data sharing ....................................................................................................................... 22 17.2. Data security ...................................................................................................................... 24
This project receives funding from the European Union’s Horizon Europe Framework Programme under project No. 101082102. 4 D7.2: Data management plan Preface This plan outlines the workflow for data management, including the creation, curation and sharing of data. The responsibilities of the file managers are outlined, along with the guidelines for creating and curating data on the RestPoll drive. 1. Summary This plan outlines a comprehensive workflow for managing research data within the RestPoll project, from collection to publication. The RestPoll drive (a Microsoft SharePoint page) is used to store and exchange data within the project. On this drive data are accessible to all RestPoll members. Sensitive personal data are not stored on the RestPoll drive but on secure institutional drives. Central to the plan is the RestPoll data dictionary, where all data files with their respective file managers are listed and all variables across all RestPoll data files as well as key concepts are defined (see ‘Data dictionary’ below). Data file managers are tasked with preparing structured files from templates for data entry, ensuring these files include relevant metadata. Common protocols for data collection will reduce risk of data not being consistent and safeguard data quality. Data collection procedures will also be calibrated before start and data files may include some features that facilitate correct data entry (see ‘Structure of spreadsheet files’ below). After data entry, a second person should check a random selection of entries to validate quality. RestPoll will generate data on pollinators, pollination success and land use metrics in and around the case-study areas. This will be mostly in form of numeric data, but also image, geospatial and text documents. In addition, RestPoll will possibly make use of existing data on the above or possible covariants. All data will be stored along with rich metadata. For reused data, the metadata documents their provenance. Data will typically be stored in excel files or GeoPackages (in the case of spatial data). Before publication, Excel files will be transformed to ODS or CSV files. Photos, in a lossless compressed format (which allow for reconstruction of compressed data without loss of information) such as compressed TIFF or PNG, will be created to document field work and possibly for identification of pollinators. Other formats include RAW, BMP, or GIF. Recordings of workshops or interviews may be retained, with consent from participants, as .WAV or .mp4 files or similar, although they may only be stored temporarily for transcription purposes and then deleted. Transcripts, protocols, surveys / questionnaires and other qualitative data will be saved as .txt or .doc files. Other data types resulting from this project include, for example, R-files (.R, .Rmd) and R-packages from the open-source software R. The expected size of the data generated or re-used by RestPoll will depend to a considerable extent on how many photos and recordings will be created, which in turn will depend on whether photos of pollinators and plants will be stored for identification. The RestPoll drive may require storage for 200 GB to 1 TB.
This project receives funding from the European Union’s Horizon Europe Framework Programme under project No. 101082102. 5 D7.2: Data management plan 2. General workflow Below is the proposed workflow for data preparation, creation, and curation, but is subject to change based on feedback during the progress of the project. Members who would like to suggest changes or feedback, please contact Dimitry Wintermantel ([email protected]) and Amibeth Thompson ([email protected]). 1. Check the RestPoll data dictionary for current terms and variables. 2. Preparation of protocols that specify what variables should be recorded, using variables already existing in the data dictionary or using new unique variables; variables typically include date of data collection (or action), site identity, observer(s) etc. 3. Update of the RestPoll data dictionary by adding the data file name (in the ‘Data_files’ sheet) and new (i.e. previously undefined) variables (in the ‘Variables’ sheet; Fig. 1). 4. Preparation of files by the respective file managers (each file has one file manager). The structure of the file and potentially also some mock data (that is clearly indicated to be mock data and that is deleted after some real data has been entered) should facilitate correct data entry. The files should contain metadata both on the entire file (see ‘General metada in README sheets/files’) as well as on individual variables (see ‘Structure of spreadsheet/qualitative files’) but no sensitive information such as personal data of land owners. 5. Data collection. 6. Data entry. Validation of random samples of data entries should be carried out by a second person to verify that data has been entered correctly. 7. Data cleaning/correction and documentation of the process. 8. Data analysis and documentation of the process (e.g. by using detailed methods descriptions or syntax-based files, where meaningful function and object names as well as comments facilitate readability). 9. Typically, at the time of publication (see publication policy in Deliverable 7.1) of peer-reviewed research, a copy of the data used for the publication shall be saved in an open-source format (excel to ODS or CSV and word to ODT or TXT). Simple text-based file formats such as CSV and TXT are likely most enduring, but ODS and ODT files allow keeping multi-sheet files easily together. Therefore, data file managers should decide between the two forms (CSV/TXT or ODS/ODT). These files shall be stored in subfolders (see ‘Naming conventions’ below for how subfolders and files should be named). 10. These shall be saved in subfolders named after the original file, the date of editing/transforming, and the person who transformed the data. These should then be uploaded to the Zenodo repository and a platform more targeted to the data (see ‘Repositories for publication’).
This project receives funding from the European Union’s Horizon Europe Framework Programme under project No. 101082102. 6 D7.2: Data management plan Figure 1. Overview of the data management workflow. On the RestPoll drive, which is accessible to all RestPoll members, a file manager creates a data file (labelled ‘Your data file’) from a template, which is linked to the data dictionary, where all variables are to be defined. Data will continuously be entered in the data file. Eventually, a copy of the data file will be transformed to an open-source format, saved with the date added to the file name in a subfolder of the folder where the main data file is stored on the RestPoll drive and published on Zenodo and one or more platforms targeted to the type of data. 3. RestPoll drive and folder structure Microsoft SharePoint will be used to store and manage data. The “RestPoll Data” SharePoint site consists of four document libraries: Deliverable & Milestones, Library, Public Data, and Data (Figure 2). The Deliverable & Milestone library will be linked to the final version of the respective document/file/folder from the WP folder (in the Data library). This folder will be assessable for all RestPoll members. The Library library will be for storing and sharing identification keys for insects and plants and relevant literature for within and across Tasks. This library will be assessable for all RestPoll members. The Public Data library will include folders that contain the final files for any public (published) data (i.e. manuscripts, reports, etc.). This will be linked from the respective “Public Data”
This project receives funding from the European Union’s Horizon Europe Framework Programme under project No. 101082102. 7 D7.2: Data management plan folder in the Data library. The Data library will store all of the raw and final data collected within RestPoll (details below). This library will only be accessible by Data File managers and other RestPoll members responsible for data creation or entry. Figure 2: Overview of the document libraries on the “RestPoll Data” Sharepoint site. The Data library will be the main data storage and management location for data collected within the realm of the RestPoll project and the Data Dictionary. Each Work Package (WP) will have its own folder for storing data. The first three levels of folders will be identical for all WPs (Figure 3). Within each WP folder (level 1) will be a folder for each Task (level 2). Within each Task folder, there will be a folder for storing Raw Data, for aggregated Data, the Deliverable & Milestones, and for the Public Data (level 3). Additional folder levels may be created by the Data file managers of the affiliated WP / Task to help organize the stored data. When possible, please abide by the Naming Conventions (see section 4), however there is flexibility for the Raw Data folder. See Figures 4 and 5 for examples for WP 1Tasks 1.1 and 1.2.
This project receives funding from the European Union’s Horizon Europe Framework Programme under project No. 101082102. 8 D7.2: Data management plan Figure 3: Overview of the folder structure for each Work Package in the Data library. Figure 4: Example of additional folder level for Task 1.1. An additional folder has been added for each case study areas in Raw Data, whereas the Data folder contains one excelsheet with all of the aggregated data.
This project receives funding from the European Union’s Horizon Europe Framework Programme under project No. 101082102. 9 D7.2: Data management plan Figure 5: Example of additional folder levels for Task 1.2. Folder level 4 contains the different types of data that will be collected (Transect walk, Photos, and Pollination services) and then level 5 are the folders for each case study area. Within the case study area folders, it is further divided for the different sites and dates when the data was collected. 4. Naming conventions Files, sheets and variable names should use underscore (_) rather than spaces or hyphens to separate words and start with letters rather than numbers to avoid potential issues in some programming languages. 4.1. VARIABLE NAMES Variable names should be simple and descriptive. They start with an uppercase letter and are followed by lowercase letters. Acronyms, used only if widely understood and accepted (e.g. DNA), are typically spelled in uppercase letters or how they are spelled in standard English (e.g. DNA or cDNA). Different words are separated by an underscore (_) e.g. “Bombus_abundance”. 4.2. FILE NAMES Relatively simple, descriptive file names will allow other RestPoll members to easily find the data files they need. Files should be named using this convention: [Data title]_RestPoll_WP[WP number. Task]_[Partner acronym] e.g. “Pollinator_survey_RestPoll_WP1.2_ALU.xlsx”. In rare instances, it may make sense to store data in a format other than the tidy data format (i.e. for overview rather than analysis). In this case, the file name should contain “_overview” after the data title e.g. “Sites_overview_RestPoll_WP1.1_ALU.xlsx”.
This project receives funding from the European Union’s Horizon Europe Framework Programme under project No. 101082102. 16 D7.2: Data management plan Backups of data will be done regularly by the file managers, on hard drives and cloud services. Backup storage shall be password-protected. Backups of data on the RestPoll drive will be done on the bi-weekly basis. Long term storage is procured by the local universities and on Zenodo. 8.1. TRACK-CHANGES AND VERSION CONTROL When working on a text document, it is suggested that track-changes be used when working with multiple partners or revisions. Otherwise, “Version History” can be used to restore deleted or changed text. When working on datasheets, mistakes can occur when entering data or rearranging data (i.e. mixing of data across rows or columns). In the case the files should be restored using “Version History”, the follow steps should be taken by the file manager: 1. Download the current version of the document to save potential new additions not in the older version. 2. Open the document. Next to the file name click the “∨” button, where a drop-down menu will appear. Click “Version History.” 3. Here you will have multiple versions based on different users and dates when data has been entered. Restore or create a copy of the version of the document before the mistake has been made. 4. Add the data or information that was added after the mistake was made. 9. Repositories for publication Data will be published in Zenodo and in repositories targeted to specific data such as GloBI, GBIF and the EU Pollinator Hub.the EU Pollinator Hub.
This project receives funding from the European Union’s Horizon Europe Framework Programme under project No. 101082102. 17 D7.2: Data management plan 9.1. ZENODO Zenodo is a general-purpose open-access repository developed under the European OpenAIRE program and operated by CERN. All data should eventually be published here. Data should be published in the “RestPoll Horizon” Community (https://zenodo.org/communities/restpoll). 9.2. GLOBI Global Biotic Interactions (GloBI) is an open-access repository focused on interaction data (e.g., predator-prey, pollinator-plant, pathogen-host, parasitehost). Please upload data here that involves two potential interactors, such as plants and pollinators. 9.3. GBIF The Global Biodiversity Information Facility (GBIF) is an international network and data infrastructure funded by the world’s governments. It provides open access to data about all types of life on Earth. 9.4. THE EU POLLINATOR HUB The EU Pollinator Hub is an open-access interactive platform that centralizes and integrates data related to pollinators, bees, beekeeping, and other relevant data for the agricultural sector. 10. Responsible contact people General data management: Dimitry Wintermantel (dimitry.winterma[email protected]nifreiburg.de) Folder structure on RestPoll drive: Amibeth Thompson ([email protected]) In addition, each data file has a data file manager with the following duties: • Create file potentially with features that facilitate correct data entry • Update data dictionary to include the file and all of its variables (make sure that only new variables are being added) • Validate that data are being entered correctly, correct and inform people entering data if needed • Ensure that file is regularly backed up and restore correct version in case of errors (see ‘Data storage and backup’) • Inform all data-owning partners about requests to use/see the data • Remind data users to put data in open-source format on Zenodo and a subfolder on the RestPoll drive when it is time to publish the data 10.1. DATA OWNERSHIP In accordance with the Grant Agreement (Article 16), results are owned by the beneficiaries that generate them. Two or more beneficiaries will own results jointly if they
This project receives funding from the European Union’s Horizon Europe Framework Programme under project No. 101082102. 18 D7.2: Data management plan have jointly generated them and it is not possible to establish the respective contribution of each beneficiary, or separate them for the purpose of applying for, obtaining or maintaining their protection. In case of joint ownership, the joint owners have the obligation to conclude a joint ownership agreement. The beneficiaries may transfer ownership of their results, provided this does not affect compliance with their obligations under the Agreement and must inform the other beneficiaries with access rights of the transfer at least 45 days in advance (or less if agreed in writing), unless agreed otherwise in writing for specifically identified third parties including affiliated entities or unless impossible under the applicable law. In each file, the partners that own the data are listed in the README sheet. The data owners shall • decide whether the data can be used for certain studies or shared with people outside of RestPoll • suggest co-authors for publications using the data This information will be used to create the results ownership list (ROL), which is a list of owners of the results generated by the action must be provided to the granting authority at the end of the action in the final reporting. When ownership of the results is not clear, all potential owners will be listed. 11. FAIR data To ensure our data is FAIR, we share our data with existing infrastructures like GloBI, GBIF, and the EU Pollinator Hub, along with the “RestPoll Horizon” community within Zenodo. 11.1. MAKING DATA FINDABLE, INCLUDING PROVISIONS FOR METADATA To enhance data findability, each dataset in the RestPoll project will be assigned a unique, persistent identifier (DOI) upon deposition in the Zenodo public repository. This ensures that data sets can be reliably located and cited. Metadata accompanying these data sets will be rich and descriptive, including but not limited to, the dataset title, creator(s), publication date, summary, keywords, and geographic location (if applicable). We will adhere to disciplinary and general metadata standards to ensure consistency and quality. This metadata will be structured to make them easily findable by search engines. Additionally, the naming convention outlined above will facilitate intuitive searching and categorization of data sets. 11.2. MAKING DATA ACCESSIBLE Once found, the person needs to know how to access the data. Both data and metadata should be retrievable by the identifier. The protocol for accessing the data is free, open and universally implementable. 11.3. MAKING DATA INTEROPERABLE
This project receives funding from the European Union’s Horizon Europe Framework Programme under project No. 101082102. 19 D7.2: Data management plan The data, metadata, and documentation adhere to disciplinary standards. Additionally, interoperability is ensured through the above described comprehensive data dictionary, which will provide clear definitions and units for each variable, promoting uniform understanding and use across different data sets. Files shall be made publicly available in open-source formats (typically ODS/ODT, CSV/TXT or geopackages). README sheets/files with metadata are provided. 11.4. INCREASE DATA RE-USE The data shall be released under the Creative Commons license (CC0) as data cannot be copyrighted (Benichou et al. 2023). It will be linked via a DOI with publications detailing the provenance of the data sets. Manuscripts will be released under the latest Creative Commons BY license (CC-BY). All data will be made publicly available at the time of publishing peer-reviewed articles or 2 years after completion of the RestPoll project. 12. Other research outputs Protocols will be publicly available on the RestPoll website. Teaching, training, and outreach materials will be publicly available on the RestPoll website. Codes for analysis (R scripts, R packages, etc.) will be uploaded, linked to, and maintained on the RestPoll GitHub. Insect specimens will be collected according to the Pollinator and Botanical Protocol (D1.2) and preserved by pinning according to the guidelines by Schauff 1986 (pg. 32). Specimens will be labeled with regional data (location, date, collector, flower visited), along with the identification (Order, Family, Species, Genus). The long-term preservation of the collections will be according to the affiliated institute's regulations or requirements, most often being preserved in a natural history museum. If an institute does not have a protocol or requirement already in place, we will provide an exemplary protocol that they can implement and adjust accordingly. Photos will be uploaded to iNaturalist. This platform provides the posted content under the Creative Commons Attribution Noncommercial license (CC BY-NC). iNaturalist will be used to help with plant or inset identification that cannot be resolved by RestPoll members and will also be used to store pictures and make them publicly available. A RestPoll project has been created to link observations together (https://www.inaturalist.org/projects/restpoll). Instructions for uploading observations can be found here. 13. Allocation of resources Individuals responsible for data management have been listed above. Costs for the RestPoll drive will be covered out of ALU’s designated budget within the RestPoll grant. 14. Data security To safeguard privacy and comply with the General Data Protection Regulation (GDPR, Regulation (EU) 2016/679), sensitive data, such as contact details of land owners, will not
This project receives funding from the European Union’s Horizon Europe Framework Programme under project No. 101082102. 20 D7.2: Data management plan be stored on the RestPoll drive. Such information will be stored in secure, restrictedaccess locations by the responsible partner organizations. For long-term accessibility, non-sensitive data will eventually be stored in the Zenodo repository and on the RestPoll website. 15. Ethics Most of the ethical considerations relate to the activities in WP3, WP4 and WP5, in which interaction with stakeholders and collection of data representing perceptions, preferences and other and other forms of personal information. However, also WP1 and WP2 will rely on e.g. contact details to farmers and other land owners. The project will collect minimal personal data from participants, such as name, gender, email, and location. This data will be used only with consent for project activities and stored locally in a restricted access, access-controlled by the LL leader in each country. RestPoll will adhere to the "do no harm principle" and "anonymization principle" when analyzing data and producing outputs such as publications, networking reports, and communication supports. Lead institutions will be responsible for gaining ethical approval for gathering specific data sets of these types, when it is required. RestPoll confirms applying the ethical guidelines of the Horizon Europe project and all relevant EU/national legislation, international conventions, and declarations. This includes the Charter of Fundamental Rights of the EU, the European Convention for the Protection of Human Rights and Fundamental Freedoms, and GDPR. In accordance with the GDPR, the cornerstone of our ethical practice is the informed consent from our informants. We will ensure that all participants clearly understand the purpose of the research and participate voluntarily, that there are clearly identified data controllers (i.e. person who is handling the raw data) and that, where possible, there are defined mechanisms for withdrawing data prior to analysis. Any publications or dissemination of project data will respect the participants' right to privacy, thus any request for deletion of data will be promptly honored. No personal data will be included in published materials without explicit, informed consent from the individuals involved. To prevent the disclosure of personal information, all data containing personal information will be anonymized before storing and sharing among partners or publication online in accordance with the GDPR. Further, sensitive data will be securely saved from other data and not be shared between partners but stored separately by each partner organization. 16. Other issues The data management procedures are as outlined above. 17. Accessing the RestPoll Drive All file managers and other relevant RestPoll members will be invited to join the RestPoll Drive via an Email invitation. Please inform Amibeth Thompson ([email protected]) for access to the drive. 1. The email invitation will be from “Nina Kranke”. Please click “Accept Invite” and follow the instructions to sign in.
This project receives funding from the European Union’s Horizon Europe Framework Programme under project No. 101082102. 21 D7.2: Data management plan 2. Once you are logged in you will see an empty App-Dashboard, i.e. without any apps. If you click on the “∨“ symbol in the upper left-hand corner, then on ‘My Groups’. 3. Afterwards, click on “Groups I am in (1)”, where you should have access to “RestPoll Drive.”
This project receives funding from the European Union’s Horizon Europe Framework Programme under project No. 101082102. 22 D7.2: Data management plan 4. Click then on “Sharepoint” and it should take you to the site. 5. This will bring you to the RestPoll Drive homepage. The different library should be visible on the lefthand side of the page (orange arrow). If not, click the arrows on the right-hand side (green arrow). 17.1. DATA SHARING Only file managers will have full access to the RestPoll Data drive. However, file managers can share data (folders, files, etc.) with other members. To share data, click either the share icon or the three dots and “share”.
This project receives funding from the European Union’s Horizon Europe Framework Programme under project No. 101082102. 23 D7.2: Data management plan The standard settings are to share the date with “view” settings, but these can be adjusted by clicking on the eye icon. An email can be sent or a link can be created and shared with anyone. A password or expiration date can be. More information can be found here: https://support.microsoft.com/en-us/office/share-sharepoint-files-or-folders1fe37332-0f9a-4719-970e-d2578da4941c
This project receives funding from the European Union’s Horizon Europe Framework Programme under project No. 101082102. 24 D7.2: Data management plan 17.2. DATA SECURITY Because all file managers have access to the RestPoll Drive, some data may need to have restricted access, such as data with sensitive information. Private folders can be created within the WP or Task folders with access only for specified members. 1. Create a folder where you would like to store your secure data. Click on the three dots (…) and click on “Manage access”.
This project receives funding from the European Union’s Horizon Europe Framework Programme under project No. 101082102. 25 D7.2: Data management plan 2. In the pop-up box, click again on the three dots (…) and then “Advanced settings”. 3. In the new window, click “Stop Inheriting Permissions”. In the pop-up window, click “OK”. 4. Select all current users and then click “Remove User Permissions”. 5. Once all users have been removed, click on “Grant Permission.” In the pop-up window, add the email address(es) of member(s) who should have access to the folder. Un-check “Require sign-in” and then click, “Share”.