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 - Elliot Creek Landslide - 2023 - Hakai Airborne Coastal Observatory #83

Closed
21 of 27 tasks
hakai-it opened this issue Jan 30, 2024 · 5 comments
Closed
21 of 27 tasks
Assignees

Comments

@hakai-it
Copy link

hakai-it commented Jan 30, 2024

Elliot Creek Landslide - 2023 - Hakai Airborne Coastal Observatory

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

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 - again sorry, working my way through a list of submitted records as we speak!

General

  • Is this record a continuation of the work described in this record: https://doi.org/10.21966/r30c-a485 ? If so, would you consider the webmap to be an entirely new product or a new version of the 2022 webmap (and therefore, perhaps better to update existing record). My guess is that this would be a new product?

Resource Identification

  • I would perhaps recommend expanding the abbreviations of LiDAR and GLOF
  • I would remove the Hakai Institute as keyword, but perhaps add ACO/Airborne Coastal Observatory

Contact

  • 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.

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 2023 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 2022 Elliot Creek Landslide record then you can include that DOI (https://doi.org/10.21966/r30c-a485) as a related work as well (I would do relation type = 'Continues', rather than 'Is New Version Of'). I would remove the link to the 2022 metadata report but rather add the 2022 Elliot Creek Landslide record as a related work.

@timvdstap
Copy link
Collaborator

Hey @hakaiholmes I see this record is published but this GitHub issue is still outstanding, and the DOI is still in draft. Could you perhaps have another quick review of the metadata and my suggestions above? If all looks good please let me know, then I can make the DOI Findable and close this issue.

@hakaiholmes
Copy link

Working on edits now - I do not think we have a solution for the webmap going directly to project outlines, but that would be ideal - putting it on the list and I will look into it.
No DMP was made
I will include those related works links as suggested.
Should be done with this shortly.

@hakaiholmes
Copy link

Edits completed to the record.
Should be good to go, but ping me if you see any other issues.

@timvdstap
Copy link
Collaborator

Thanks @hakaiholmes looks good to me! Few minor things I changed:

  • Added Hakai Institute as Publisher, now included in the citation
  • Rather than linking to the URL for the 2022 metadata report, I linked to DOI for that record

I'll update the record in DataCite and close this issue -- feel free to reopen if you have any questions or concerns, or if you disagree with those changes!

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