Skip to end of banner
Go to start of banner

Workflow - Data mobilisation - Information for data providers

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

This page is intended for site and platform coordinators who have an interest to participate in data calls distributed through eLTER. The wiki shall provide a step-by-step procedure of what is needed, how this is done and what is it used for.

What are “eLTER data calls”?

eLTER data calls are specific calls for specific data from your site that eLTER receives and forwards to either all sites or specific sites if e.g. only data from a certain habitat is required. All calls are published here and communicated regularly during Site and Platform Forum meetings and in the eLTER Newsletter.

How can you provide data for eLTER data calls?

If you as site and platform coordinators want to provide data to these calls, you will find a step-by-step procedure below of how this is done. The procedure is divided in “data is already published” (i.e. your data is already stored in a public repository and possibly even has a DOI) and “data is not published” (data is stored locally and has no DOI).

Your data is already published and has a DOI follow this workflow

 Please expand if this applies
  1. Step: Metadata File
    Create a metadata file of your data sets following a metadata file template [link]

  2. Step: Submit Metadata file
    Send the metadata file to office@elter-ri.eu. The subject should be: [Data Call ID]_[DEIMS.ID]_[Name of the file]. The “DataCall.ID” can be found in the first column of the call table. The “DEIMS.ID” can be retrieved from deims.org. The name of the file may indicate the included variables. An example subject would be:
    DataCall_2023_01_d9b8f5f4-f92f-4e95-ad23-f4951196dec2_AirTemperature

  3. Step: Cross-check
    Your metadata will then be added to eLTERs Digital Asset Register. Once this step is accomplished, you will receive a request to crosscheck all entries, before it is send to the issuer of the data request.

Your data is NOT published follow this workflow

 Please expand if this applies
  1. Step: Data compilation
    Compile the required data for the selected data call

  2. Step: Prepare datasets
    Please format your data according to the pre-defined data formats. We provide you with a template for your convenience.

  3. Step: Upload data on B2Share
    Please upload the created dataset to the B2Share repository. This document walks you through the process and provides information (like the naming convention) that we ask you to adhere to, to allow for a smooth processing.

  4. Step: Cross-check
    Metadata of your data (added during step 3) will then be listed in eLTERs Digital Asset Register. Once this step is accomplished, you will receive a request to crosscheck all entries, before it is send to the issuer of the data request.

How to get help?

In case you have questions or need help during the process of providing data, please contact the eLTER Head Office (office@elter-ri.eu).

Frequently Asked Questions

 What is B2Share and is my data safe?

B2SHARE is developed and by the EUDAT2020 project in order to provide a common data infrastructure for European research data. eLTER PLUS is using the services provided by the EUDAT2020 project in order to share and publish data files. When uploading data files to B2SHARE a PID (Persistent Identifier) and DOI (Digital Object Identifier) is created to allow an unambiguous identification of the file including a resolution service for the PID. B2SHARE supports an open data policy, allowing implementing a retention period. The data is deposited in Finland at the Finnish IT Center for Science. More precisely it is stored on servers in Kajaani, a newly-built and environmentally-friendly data centre using the most advanced and modern data centre technology. EUDAT retains the right of archiving, i.e. creating replicas at trusted centres to take care of long-term persistence.

  • No labels