Dataset - Bute Inlet Geohazard - Topography Surveys - 2023 - Hakai Airborne Coastal Observatory

[hakai-it]

Bute Inlet Geohazard - Topography Surveys - 2023 - Hakai Airborne Coastal Observatory

https://hakaiinstitute.github.io/hakai-metadata-entry-form/#/en/hakai/RvRPlFMSsIaBwoGdQIq5BVYfBBa2/-NpRG7xQ84LQrgS4jhie

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]

@hakaiholmes Some thoughts and suggestions below:

Resource Identification

• I would expand on the LiDAR and ACO abbreviations upon first mention.
• I would remove 'Hakai Institute' from the keyword list but perhaps include ACO or Airborne Coastal Observatory
• Should 'Watersheds' also be added as a project?

Contacts

• The abstract makes mention of contacting either Ian or Derek -- I would include them within the contact list as well, even if they shouldn't necessarily be included in the citation.
• 'Hakai Institute' is currently listed as the main author, but I also see 'Hakai Geospatial' in the contacts. Should the main author (and associated roles) be 'Hakai Geospatial' instead?
• I have removed 'Geospatial Science' and the individual email from the 'Hakai Institute' contact
• Hakai Geospatial currently has the role 'Publisher', but the Publisher would be Hakai Institute. I now have 'Originator' listed as role under 'Hakai Geospatial', but my guess is that the roles listed under 'Hakai Institute' should be under 'Hakai Geospatial' instead?
• Good to review the contact and how you'd like Hakai Geospatial to be represented: see https://github.com/HakaiInstitute/hakai-data/issues/111. Right now Hakai Geospatial is listed as the organization, but as a result the Hakai ROR cannot be added.

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?

Platform

• I have changed platform type from aeroplane -> research aeroplane

[timvdstap]

@hakaiholmes I'm sorry this one has slipped under my radar! It seems like it's already published, I made some minor changes to the contacts and the resources (the metadata report was in there as both a primary resource and related work). Would you mind having a quick lookover and see if you agree with those changes?

If so, please let me know and I can make the DOI 'live' and close this issue :)