kmexter
commented
11 months ago Katrina's suggestion
Datasets Descriptions. Mandatory sheet (mark mandatory ones in orange and optional ones in green?)
- DatasetIdentifier: "To link the datasets in the rows of this googlesheet together". Example: VLIZdataset1
- DatasetDescriber: :"The name of the agent (filled in in the Agents tab) who filled in this dataset row". Example KExter
- DatasetTitle: "A title for the dataset"
- DatasetDescription: "A brief description of the dataset"
- DataLandingPageURL: "A dataset landing page is a dedicated web page that serves as the entry point to access comprehensive information about a specific dataset, including its contents, structure, and metadata. Ideally this is given as a DOI, in any case it must be a full URL. If the same data are published in multiple places, use "," to separate them and the first should be the one you consider to be "the most important/comprehensive. Leave blank if these data are not provided with a landing page.".
- NotAccessibleData: "If the data do exist but are not published, please explain here why they are not published and what advice WP1 could give you to help you publish these data"
- InProgressData-Date: "For data that are in progress, please fill in an approximate date (YYYY-MM) you expect them to be published"
- EOVDescription: "Where relevant, please describe the class of EOV/EBV in this dataset. WP1 will use this to chose an EOV/EBV MBO vocabulary, so please make the explanation clear and avoid the use of acronyms". See https://github.com/marco-bolo/dataset-catalogue/issues/15
- IndicatorDescription: "Where relevant, please describe the class of indicators in this dataset. WP1 will use this to chose an EOV/EBV MBO vocabulary, so please make the explanation clear and avoid the use of acronyms". See https://github.com/marco-bolo/dataset-catalogue/issues/15
- Programme: as described in the Programme tab
Agent --> I realised that if this googlesheet needs to be turned into json (even if just for our own purposes), we need the Agents sheet still. Mandatory sheet.
- everything that is on the Agent sheet now should be copied over
- everything is mandatory where relevant except: ID, URL
however, if we instead think we should just ask for the agents to be written in a formatted way into the cells in the mandatory and optional sheets, then we would need to say "enter as first name, last name, email, orcid, gh handle, organisation name" and accept the fact that 1/2 of them will do it wrong
Project --> I would change the title of this tab to "Overarching programme" or "Monitoring programme". Mandatory sheet.
- all field mandatory where relevant
Datasets Additional Description - Optional . Copy descriptions from what is currently in the googlesheet already (noting I have slightly renamed some of the column titles)
- DataProviderAgent
- DataContactAgent
- FunderAgent
- DataContributorAgents
- licence
- DatasetCitation
- Keywords
- DataTypes (will need to see https://github.com/marco-bolo/dataset-catalogue/issues/14 for what to allow to be entered here)
- DatasetVersion
- DatasetStartDate
- DatasetEndDate
- SpatialCoverage-MarineRegion
- SpatialCoverage-WKT
- CoordinateProjection
- TaxonomicCoverage (see https://github.com/marco-bolo/dataset-catalogue/issues/8)
- VariablesMeasured - specifically for where these are raw data, not EOVs or indicators
- SourceDatasetIdentifier - The DatasetIdentifier for the dataset in this googlesheet that is the source data for this particular dataset
- RelevantCitations
See meeting minutes from Dec 15: https://docs.google.com/document/d/1Fvgb3eKFwsQO8XEp51giphrZXw2M8E9x8W6SEmHrb8M/edit
For datasets that are already published and have a DOI (or other type of URL), we will harvest metadata from there (VLIZ) rather than asking the data providers to copy those over We need to ask also some extra information, so we will need 3 tabs in this new gsheet
In this issue we should all put our suggestions about which columns of the current googlesheet should go into the new one. Then someone has to create the new googlesheet as we need to push this out in the first week of Jan.