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 - Sea surface temperature data along the British Columbia Coast #110

Closed
21 of 27 tasks
hakai-it opened this issue Aug 22, 2024 · 14 comments
Closed
21 of 27 tasks
Assignees

Comments

@hakai-it
Copy link

hakai-it commented Aug 22, 2024

Sea surface temperature data along the British Columbia Coast

https://hakaiinstitute.github.io/hakai-metadata-entry-form/#/en/hakai/57FPdLIBPcb9BOLfIOW44RJVywN2/-NH0r8ddHNhVJ5bXkyqR

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 [email protected] 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 30, 2024

Hey @heather-earle Thanks for submitting this record! A few comments and suggestions:

  • I have minted a draft DOI for this record: https://doi.org/10.21966/4kr2-jc55 -- once the metadata record is complete and published, I'll make sure the DOI is 'Findable' (i.e. 'live'), and you can reference it in any derived data products.
  • I would recommend adding perhaps a few more keywords (5 - 10 is ideal). It's OK if it's a keyword that doesn't have a French translation/is not included in the dropdown list.
  • Given that the dataset is 'Ongoing', I have removed the date (2023-09-01) associated with 'end data when data was collected'.
  • The version is 1.1; to me this implies there's a version 1.0 published somewhere, is that right? Or would it be better to have the version be 1.0?
  • Is there a particular reason the dataset is licensed with CC-BY-4-NC? The DMP indicates that the data will be licensed CC-BY-4.
  • I've included your, Matt's and Lauren's ORCID, and added the ROR for Lauren.
  • I've added Tula Foundation as a Funder (not included in citation).
  • edit: Given that the ERDDAP dataset is Identical To the data in the data package, we can make the Primary Resource link to the ERDDAP dataset, and linking to the GitHub repository in the 'Related Works'. I will switch this around.
  • Recommended to include a link to the Data Management Plan in the Related Works, consider relation type: Is Documented By or Is Described By
  • Recommended to include a link to the DOI associated with the Larval Dungeness crab arrival timing dataset, perhaps with relation type: Is Supplement To
  • Similarly, I wouldn't consider the HOBO Tidbit Logger Description to be a 'Primary Resource', rather, it's supporting information that helps describe how data was collected. My recommendation would be to include it in the 'Lineage' section (as I've now done) -- let me know if that makes sense.
  • Could you include a data-dictionary.csv file in the GitHub repo that provides a definition of the columns in the data.csv files?

@JessyBarrette
Copy link
Contributor

@JessyBarrette
Copy link
Contributor

One point maybe regarding the metadata record. I think the title is maybe too broad, it would be good add in there that it refers to the Hakai Sentinels of Change project.

@timvdstap
Copy link
Collaborator

If collection is ongoing it would be good to include Time Series as well. So maybe as suggestion:

Sentinels of Change Sea surface temperature time series data along the British Columbia Coast

@timvdstap
Copy link
Collaborator

Hi @heather-earle I've noticed that the ERDDAP link in the metadata record isn't active: https://catalogue.hakai.org/erddap/tabledap/HakaiSentinelTemperature.html. Is this still the correct link for this record?

I'll tag @fostermh as well just in case he might know more?

@heather-earle
Copy link

Hi Tim, sorry I don't actually know where the right link would be found!

@heather-earle
Copy link

Some updates from today:
-I have updated the title as you suggested
-have added a couple more keywords so we have 5 now
-version is now 1.0
-same issue as the other repo, the CC-BY-4 is not one of the options in the dropdown and I can't seem to enter it
-have updated the related work with the larval arrival dataset to link to the DOI rather than github repo, and have changed it to "is supplement to"
-working on a data dictionary!

@heather-earle
Copy link

okay data dictionary added!

@fostermh
Copy link
Collaborator

it would appear the erddap dataset was never pushed to production. it is now live at https://catalogue.hakai.org/erddap/tabledap/HakaiSentinelTemperature.html

@timvdstap
Copy link
Collaborator

timvdstap commented Nov 22, 2024

Thanks @fostermh I will update the link in the metadata record - edit: nvm, seems like someone beat me to it!

@timvdstap
Copy link
Collaborator

timvdstap commented Nov 22, 2024

Some updates from today: -I have updated the title as you suggested -have added a couple more keywords so we have 5 now -version is now 1.0 -same issue as the other repo, the CC-BY-4 is not one of the options in the dropdown and I can't seem to enter it -have updated the related work with the larval arrival dataset to link to the DOI rather than github repo, and have changed it to "is supplement to" -working on a data dictionary!

Excellent, thanks for doing this @heather-earle! I'm sure not sure why you can't see the CC-BY-4 option in the dropdown but I've included it now. Will the sensor data repository be made public? I assumed it would be, and I've added a link to the GitHub repo as a related work as well.

One thing I would also consider doing is updating the text in the LICENSE file - you can copy the CC-BY-4 text into it.

Let me know once you're happy with the contents of the repository- I think once you're happy with it we can set the visibility to public and create a GitHub release.

@heather-earle
Copy link

heather-earle commented Nov 25, 2024

Ooh just seeing this - yes the sensor data repo is intended to be public.

Just added that text from CC-BY-4 into the license file. I left the original text above. Does that seem right? Happy to delete if not.

I am totally happy with the contents of the repositories :) ready to get this released!

@timvdstap
Copy link
Collaborator

I think it makes more sense to delete the MIT Licensing - that way the licensing is consistent across everything (DMP, OBIS record, catalogue record(s)).

@timvdstap
Copy link
Collaborator

Published to the Hakai 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

6 participants