This task focuses on been able to call the DOI service to mint a DOI for a download as an additional step to the current generate file, send e-mail workflow.
There should be at least a new parameter for the download request, a flag to indicate that a DOI needs to be generated, the default value will be NO to preserve compatibility.
If not already provided, a new parameter with the source url will need to be passed in, this will covr the requirement to 'regenerate' a DOI as per AtlasOfLivingAustralia/doi-service#13
DOI Metadata:
Title: ALA Occurrence Download
Authors: Atlas Of Living Australia
ApplicationUrl: <search url>
providerMetadata:
publisher: Atlas Of Living Australia
title: ALA Occurrence Download
creator: [{name:<Dataset Provider1 name>, type:Producer} ,...]
contributor: {name: <requestor name> }
Field names to be confirmed but that should be a good functional start
To be stored in textfile
breakdown of datasets with counts to be stored (see GBIF DOI page & issue #11)
citation text to be stored
calling hub to be stored (so we can generate a new search URL)
Downloads will optionally generate a DOI
This task focuses on been able to call the DOI service to mint a DOI for a download as an additional step to the current generate file, send e-mail workflow.
There should be at least a new parameter for the download request, a flag to indicate that a DOI needs to be generated, the default value will be NO to preserve compatibility.
If not already provided, a new parameter with the source url will need to be passed in, this will covr the requirement to 'regenerate' a DOI as per AtlasOfLivingAustralia/doi-service#13
DOI Metadata:
Title: ALA Occurrence Download Authors: Atlas Of Living Australia ApplicationUrl: <search url>
providerMetadata: publisher: Atlas Of Living Australia title: ALA Occurrence Download creator: [{name:<Dataset Provider1 name>, type:Producer} ,...] contributor: {name: <requestor name> }
applicationMetadata: searchUrl: <search url> datasets: [{name: <Dataset Provider1 name>, count: <count> },...] requestorId: <userId>
Field names to be confirmed but that should be a good functional start
To be stored in textfile
breakdown of datasets with counts to be stored (see GBIF DOI page & issue #11) citation text to be stored calling hub to be stored (so we can generate a new search URL)
Maybe the DOI JSON Object?