the zipped csv format with txt metadata from figshare

[pvgenuchten]

figshare is a popular data repository for scientific publications, endorsed by various journals

within the figshare community, there is a convention to package a set of csv's with a textual metadata file into a zipfile

the textfile often holds important metadata which is often not included in the Datacite metadata

for every column in the dataset it may indicate the meaning of the column, the unit of measure and the procedures used to measure the value

It seems that there is no convention for a metadata format, to make this file machine readable

Some questions that are relevant:

• is figshare the only platform with this convention, or is it used more widely
• can we discuss with a group of researchers if we can adopt this approach in soil mission, slightly altered so the file is machine readable

Some samples of the metadata below

We have provided an accurate dataset describing a complete year (from 01/07/2013 to 30/06/2014) of the trajectories for all the 442 taxis running in the city of Porto, in Portugal (i.e. one CSV file named "train.csv"). These taxis operate through a taxi dispatch central, using mobile data terminals installed in the vehicles. We categorize each ride into three categories: A) taxi central based, B) stand-based or C) non-taxi central based. For the first, we provide an anonymized id, when such information is available from the telephone call. The last two categories refer to services that were demanded directly to the taxi drivers on a B) taxi stand or on a C) random street.

Each data sample corresponds to one completed trip. It contains a total of
9 (nine) features, described as follows:

- TRIP_ID: (String) It contains an unique identifier for each trip;
- CALL_TYPE: (char) It identifies the way used to demand this service. It may contain one of three possible values:
‘A’ if this trip was dispatched from the central;
‘B’ if this trip was demanded directly to a taxi driver on a specific stand;
‘C’ otherwise (i.e. a trip demanded on a random street).
- ORIGIN_CALL: (integer) It contains an unique identifier for each phone number which was used to demand, at least, one service. It identifies the trip’s customer if CALL_TYPE=’A’. Otherwise, it assumes a NULL value;
- ORIGIN_STAND: (integer): It contains an unique identifier for the taxi stand. It identifies the starting point of the trip if CALL_TYPE=’B’. Otherwise, it assumes a NULL value;
- TAXI_ID: (integer): It contains an unique identifier for the taxi driver that performed each trip;
- TIMESTAMP: (integer) Unix Timestamp (in seconds). It identifies the trip’s start;
- DAYTYPE: (char) It identifies the daytype of the trip’s start. It assumes one of three possible values:
‘B’ if this trip started on a holiday or any other special day (i.e. extending holidays, floating holidays, etc.);
‘C’ if the trip started on a day before a type-B day;
‘A’ otherwise (i.e. a normal day, workday or weekend).
- MISSING_DATA: (Boolean) It is FALSE when the GPS data stream is complete and TRUE whenever one (or more) locations are missing
- POLYLINE: (String): It contains a list of GPS coordinates (i.e. WGS84 format) mapped as a string. The beginning and the end of the string are identified with brackets (i.e. [ and ], respectively). Each pair of coordinates is also identified by the same brackets as [LONGITUDE, LATITUDE]. This list contains one pair of coordinates for each 15 seconds of trip. The last list item corresponds to the trip’s destination while the first one represents its start;

The total travel time of the trip (the prediction target of this competition) is defined as the (number of points-1) x 15 seconds. For example, a trip with 101 data points in POLYLINE has a length of (101-1) * 15 = 1500 seconds. Some trips have missing data points in POLYLINE, indicated by MISSING_DATA column, and it is part of the challenge how you utilize this knowledge.

Acknowledgements
Data from ECML/PKDD 15: Taxi Trip Time Prediction (II) Competition

Inspiration
Added this dataset because competition datasets do not appear in the dataset search and this dataset could help learn basic
methods in the area of geo-spatial analysis and trajectory handling

This dataset contains all the citation data (in CSV format) included in COCI, released on 23 January 2023. In particular, each line of the CSV file defines a citation, and includes the following information:

[field "oci"] the Open Citation Identifier (OCI) for the citation;
[field "citing"] the DOI of the citing entity;
[field "cited"] the DOI of the cited entity;
[field "creation"] the creation date of the citation (i.e. the publication date of the citing entity);
[field "timespan"] the time span of the citation (i.e. the interval between the publication date of the cited entity and the publication date of the citing entity);
[field "journal_sc"] it records whether the citation is a journal self-citations (i.e. the citing and the cited entities are published in the same journal);
[field "author_sc"] it records whether the citation is an author self-citation (i.e. the citing and the cited entities have at least one author in common).
This version of the dataset contains:

1,463,920,523 citations;
77,045,952 bibliographic resources.
The size of the zipped archive is 37.5 GB, while the size of the unzipped CSV file is 238.5 GB.



Additional information about COCI can be found at the [official webpage](http://opencitations.net/index/coci).

Plant measurements
Measurements taken in Acacia and Banksia plants.

bio:
plants were left to dry 48 hours at 60 C, and then weighed to obtain dry biomass
genus refers to plant genus: acacia and banksia
species refers to plant species
nematode refers to nematode inoculation: CTL (no nematodes); BFN (bacterial feeding nematodes added); RLN (root feeding nematodes added)
grown refers to plant mixture: alone (plant grown with members of the same species) and both (plant grown in mixture)
Total: whole plant (root & shoot) dry mass, in grams
Above: shoot dry mass, in grams
Below: root dry mass, in grams

cn:
carbon and nitrogen content of plants, analyzed by an Elementar Vario Micro Cube elemental analyzer (Elementar Analysensysteme GmbH, Hanau, Germany) interfaced to a PDZ Europa 20-20 isotope ratio mass spectrometer (Sercon Ltd., Cheshire, UK,) analyzed at UC Davis isotopic facility (USA).
genus refers to plant genus: acacia and banksia
stage refers to successional stage: early and late
nematode refers to nematode inoculation: control (no nematodes); bacterial (bacterial feeding nematodes added); plant (root feeding nematodes added)
grown refers to plant mixture: alone (plant grown with members of the same species) and both (plant grown in mixture)
%C: carbon shoot concentration (%)
%N: nitrogen shoot concentration (%)
Cg: total grams of carbon in shoot
Ng total grams of nitrogen in shoot

iso:
isotopic signature of plants, analyzed by an Elementar Vario Micro Cube elemental analyzer (Elementar Analysensysteme GmbH, Hanau, Germany) interfaced to a PDZ Europa 20-20 isotope ratio mass spectrometer (Sercon Ltd., Cheshire, UK,) analyzed at UC Davis isotopic facility (USA).
genus refers to plant genus: acacia and banksia
stage refers to successional stage: early and late
nematode refers to nematode inoculation: control (no nematodes); bacterial (bacterial feeding nematodes added); plant (root feeding nematodes added)
grown refers to plant mixture: alone (plant grown with members of the same species) and both (plant grown in mixture)
d15N: isotopic nitrogen signature in shoot (deltha15N, at%)

nit: 
nitrogenase activity was estimated in fresh acacia nodules using the acetylene reduction essay (Hardy, Burns, & Holsten, 1973)
species refers to plant species
nematode refers to nematode inoculation: control (no nematodes); bacterial (bacterial feeding nematodes added); plant (root feeding nematodes added)
grown refers to plant mixture: alone (plant grown with members of the same species) and both (plant grown in mixture)
ppm_nod: ethylene produced per nodule (ppm)

nod:
number of nodules were counted on freshly harvested roots
species refers to plant species
nematode refers to nematode inoculation: control (no nematodes); bacterial (bacterial feeding nematodes added); plant (root feeding nematodes added)
grown refers to plant mixture: alone (plant grown with members of the same species) and both (plant grown in mixture)
Nods: number of nodules per plant

[pvgenuchten]

Seems this approach seems not common in zenodo (zenodo does not preview files which are included in zips, it does if the file is uploaded separately)

in some cases a README.md is provided (convention of github)

[pvgenuchten]

this is what 4tu writes about dataset readme's.
derived from figshare's sharing best practice

[pvgenuchten]

If i'd had to come up with a metadata convention, i'd suggest readme.yml:

identification:
  title: objects in the field
  abstract: objects were measured in the field by specialists
  dates:
    creation: 2000-09-01
contact:
  author:
    individualname: Genuchten, PPL van
    organization: ISRIC - World Soil Information
content_info:
  attributes:
    - name: height
      type: numeric
      units: m
      title: the height of the object, measured from ground
    - name: weight
      type: numeric
      units: kg
      title: the weight of the object, measured at 20 gC  

It's fully compatible with MCF and human readable