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 - Denali Fault - 2024 - Airborne LiDAR Survey #117

Closed
16 of 27 tasks
hakai-it opened this issue Nov 26, 2024 · 6 comments
Closed
16 of 27 tasks

Dataset - Denali Fault - 2024 - Airborne LiDAR Survey #117

hakai-it opened this issue Nov 26, 2024 · 6 comments
Assignees

Comments

@hakai-it
Copy link

hakai-it commented Nov 26, 2024

Denali Fault - 2024 - Airborne LiDAR Survey

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

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 Nov 26, 2024

Nice work @hakaiholmes ! Few things I've changed, let me know if you agree with them:

  • I changed the affiliation for Hakai Geospatial to be Hakai Institute. It still shows Hakai Geospatial in the citation as per the latest changes that Matt made.
  • I put Hakai Institute as Data Owner, rather than Tula being the data owner. Perhaps an interesting consideration as to whether Hakai or Tula is the data owner, but I've made the change merely out of consistency with other records.
  • I changed the resource type for the metadata report to be 'Has Metadata' as opposed to 'Documents', seemed more fitting for a metadata report. If you disagree please let me know!
  • Wondering if you're OK with me changing the platform type to 'research aeroplane' vs 'aeroplane'?

@hakaiholmes
Copy link

Agree
Agree
Agree
I just updated it to research aeroplane and saved it as the default for future records. Thanks!

@hakaiholmes
Copy link

Kisik was added as a contact and in the citation - just checking with Derek on that update now.

@timvdstap
Copy link
Collaborator

Kisik was added as a contact and in the citation - just checking with Derek on that update now.

Sounds good, just make sure to give them a role ;-)

@hakaiholmes
Copy link

yes, I saw that and updated it. At lease I am pretty sure... yes - we are good on Denali.

@timvdstap
Copy link
Collaborator

Looks great to me, will publish to the catalogue!

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