Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dataset - Fraser River Airborne Surveys - 2021 - Hakai Airborne Coastal Observatory #86

Open
18 of 27 tasks
hakai-it opened this issue Feb 5, 2024 · 1 comment
Open
18 of 27 tasks
Assignees

Comments

@hakai-it
Copy link

hakai-it commented Feb 5, 2024

Fraser River Airborne Surveys - 2021 - Hakai Airborne Coastal Observatory

https://cioos-siooc.github.io/metadata-entry-form/#/en/hakai/RvRPlFMSsIaBwoGdQIq5BVYfBBa2/-NHfqx-d8tuAroY8BWc7

Best Practices Checklist

In General

  • No previous versions of this metadata record exist (eg for earlier versions of the data, if so update that record rather than creating a new one)

Data Identification

Dataset title:

  • No version information in the title
  • Frontloaded (with the most important information first)
  • Include the geographical region the data apply to
  • Short – aim for 60 characters including spaces
  • Does not include acronyms – put these in the keywords
  • Does not include the word “dataset”
  • Time series datasets should include “time series” at the end of the title

Abstract

  • Abbreviations have been expanded upon at first mention
  • Abstract describes how, when, what, where, why of data collection and is limited to no more than 500 words

DOI

  • A DOI has been drafted for this record
  • DOI has been updated via the form after review and changes to record
  • DOI has been manually edited on datacite fabrica
  • DOI status has been changed from Draft to Findable

Spatial

  • Ensure that Depth or Height Positive is correctly selected

Contact

  • ROR and ORCID(s) are included and linked properly where applicable
  • For datasets where DFO is a partner, ensure 'parent' ROR is added (https://ror.org/02qa1x782). DFO 'child' organizations (i.e. CHS) and their ROR are optional.
  • Include Hakai Institute as Publisher and include data@hakai.org as email
  • Make sure email address is provided if the role is 'Metadata Custodian' or 'Point of Contact'
  • Add contact affiliation where known including ROR
  • If resource is (partially) generated by Hakai researchers, include 'Tula Foundation' (with associated ROR) with 'Funder' role. Be sure to uncheck 'include in citation' for Tula Foundation.

Resources

  • Resource links go to specific dataset download (not generic platform like waterproperties.ca)
  • Readme, changelog, data dictionary, protocols included in data-package (for tabular text based data)
  • An archive folder, or other means, for older data versions is included in the data package if the version is not 1.0
  • Links work
  • All files in the data package can be opened and are not corrupt
  • No executable files in the data package. Files should be open formats and standards (.csv, .txt for example)
@timvdstap
Copy link
Collaborator

timvdstap commented Aug 1, 2024

Hey @hakaiholmes - I'm sorry I'm only getting to this record now! Some thoughts, comments and suggestions:

General

Resource Identification

  • I think I would remove the information related to the data files from the abstract, I think it distracts a little bit from the what, when, where and why that should be covered.
  • I would remove the sensor and instrument breakdown currently included in the abstract and include it under 'Platform'. There seems to be a bit of duplication in the second paragraph as well

Contacts

  • If 'Hakai Institute' as a contact is OK (vs. e.g. Hakai Geospatial, or individual authors), then I have included 'Publisher' as a role.

Data and Documentation

  • Is it possible that the link to the webmap is specific to the area surveyed that is described in this metadata record?
  • I would include the metadata report link under 'Related Works' with the relation type being 'Has Metadata' as the related work will have the metadata for the primary resource.
  • Just confirming that there's no specific DMP for this project that you could include under Related Works, correct?
  • If this is indeed a new version of the 2020 Fraser River Airborne Survey then you can include that as a related work as well (I would do relation type = 'Continues', rather than 'Is New Version Of')

Platform

  • I have changed the type of platform from aeroplane -> research aeroplane
  • Seems like you could perhaps include additional instruments/sensors from the abstract in this section?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants