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 Landslide Project - 2022-2024 - Drone Data - Hakai Institute #116

Closed
19 of 27 tasks
hakai-it opened this issue Oct 31, 2024 · 8 comments
Closed
19 of 27 tasks
Assignees

Comments

@hakai-it
Copy link

hakai-it commented Oct 31, 2024

Fraser River Landslide Project - 2022-2024 - Drone Data - Hakai Institute

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

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

Hey @hakaiholmes some thoughts / recommendations:

  • Is this record a continuation of https://doi.org/10.21966/zjc2-b004 ?
  • Personally, I would remove 'Hakai Institute' from the title, but instead include it as the publishing institute so that it still appears in the recommended citation (see next item).
  • Have the 'Hakai Institute' with role: Publisher appear in the citation (checking the box)
  • Jeremy Venditti and Brian Menounos are currently not included as contacts - should they be, if they are large partners on this project? Looking at the mapping report, I also see the names Julia Carr, Aaron Steelquist and Erin Seagren - should they be given attribution as well?
  • I don't think the data@hakai.org will show up in the metadata record if no additional individual information is provided (first + last name etc).
  • I know I'm starting to sound like a broken record, but I would consider being more explicit in the author list, especially if this is spelled out in greater detail in the metadata report. In the current format the people included in the metadata report don't receive any attribution.
  • I've added Will's email address to his individual information as he's listed as the metadata custodian
  • Should the DJI Mavic 3 drone also be included as a platform?
  • Can the data be requested? If so, how (is there an online request form that users can fill out, or do they need to email someone)? I ask mainly because it's flagged as a 'dataset' resource type, rather than as Report.

@hakaiholmes
Copy link

Thank you for those edits. Most have been made. I stuck with the drone side of things for the contacts on this record. The larger report will have Jeremy et al included.
Almost ready to publish again here.

@timvdstap
Copy link
Collaborator

Sounds good, thanks Keith, let me know when you'd like to do another quick review!

@timvdstap
Copy link
Collaborator

Few comments:

  • Title says 2022-2024 Drone data, but in the abstract it reads that drone imagery data was collected in 2022 and 2023.
  • As a suggestion: given that this record is for the drone data, I would consider making the link to the metadata report a Related Work, e.g. with relation type 'Has Metadata'. The Primary Resource could then only be a link to the Data Request Form.
  • I would change the description of the Data Request Form.
  • Just checking whether Fraser River - BCSRIF Landslide Mapping - 2022 - Hakai Airborne Coastal Observatory](https://doi.org/10.21966/zjc2-b004) is connected to this record? Is this record a continuation of that dataset?

@hakaiholmes
Copy link

1 - let me check on those dates.
2 - I think I got turned around on the relates and primary resource - I will sort that out now
3 - data request - yup - agreed
4 - related project - but different data and methods - could be linked for sure .

I will update when these are done. Thanks again!

@hakaiholmes
Copy link

I have updated all these items and added some related links. Have a look and ping me if you see any other issues.

Note - I decided to go with all authors listed because of our partnership role with SFU and multiple publications may be sourced so it is actually easier this way.

@timvdstap
Copy link
Collaborator

timvdstap commented Nov 21, 2024

I think it looks great @hakaiholmes! I've published the record to the catalogue again - please let me know if you have any concerns around that!

@hakaiholmes
Copy link

Great thank you!

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

4 participants