Data request and provision process - d-fine/Dataland GitHub Wiki

Data requests

Request priorities

Each data request is given a priority based on the following criteria:

  • Urgent - Requests that should be delivered as soon as possible
  • High - Request from a member
  • Baseline - Request for core datasets
  • Low - Request from a non-member

Each dataset, aggregated over all open requests, gets a priority based on the following criteria:

  • Urgent - An Urgent request exists for this dataset
  • Very High - Multiple members have requested this dataset
  • High - One member has requested this dataset
  • Baseline - A request exists that specifies this dataset as a core dataset
  • Normal - Multiple non-members have requested this dataset
  • Low - One non-member has requested this dataset

How to mark a dataset as non-sourceable

If you could not find any data for a request matching a specific company, framework, and reporting period, you may mark it as non-sourceable. For this, you need:

  • the companyId which is the company's UUID within Dataland,
  • the dataType which corresponds to a framework like "eu-taxonomy-financials" or "sfdr", and
  • the reportingPeriod of the data to be marked as non-sourceable.

Proceed as follows

  1. Go to the metaDataController in the Dataland backend API at https://dataland.com/api/swagger-ui/index.html#/meta-data-controller.
  2. To mark data as non-sourceable, use the POST endpoint. You have to provide a request body of the form
{
  "companyId": "string",
  "dataType": "eutaxonomy-financials",
  "reportingPeriod": "string",
  "isNonSourceable": true,
  "reason": "string"
}

You may provide a reason why this data could not be found, e.g. if only data for the parent company is provided.

If you were successful, you will get a 200 response. If the provided request body is malformed, e.g. due to a typo in the dataType, you will receive a 400 response. You will also receive a 400 response if you try to mark data as non-sourceable which already exists on Dataland.