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 - iTrack Oysters February 2023 Experiment - Environmental and Oyster Health Data #112

Open
20 of 27 tasks
hakai-it opened this issue Sep 25, 2024 · 7 comments
Open
20 of 27 tasks
Assignees

Comments

@hakai-it
Copy link

hakai-it commented Sep 25, 2024

iTrack Oysters February 2023 Experiment - Environmental and Oyster Health Data

https://hakaiinstitute.github.io/hakai-metadata-entry-form/#/en/hakai/KstJ1LGR2ZbovZiE2SeSKVz4y4E2/-O0G3gSlISPfB-f0u3Zz

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

Chatted with @bcollicutt today, I will review this record next week. Brenna will connect with data collaborators to verify authorship.

@timvdstap
Copy link
Collaborator

timvdstap commented Oct 1, 2024

Hi @bcollicutt hope you had a great long weekend! Your metadata record looks great! Few minor comments:

  • I included UVic's ROR for Mark Loui and Caren.
  • Given that the record is published in our catalogue, I've included 'Hakai Institute' as 'Publisher'. You'll also see this reflected in the recommended citation (behind the version).
  • I've added Tula Foundation as a Funder, not including it in the citation.
  • Mesocosm tank has recently been added as controlled vocab by NERC in their L06 Vocabulary. It doesn't (yet?) show up as an option to include under 'Platform' in the metadata record (@fostermh do you know if this would happen automatically). I don't think this should be a factor preventing you from publishing the record, we can always add it later if need be. Hopefully for future records it becomes an option to select.

I think the remaining things to do are: 1) confirm with co-authors that the citation is OK. 2) confirm you are happy with the contents of the repository - if there have been any changes to the recommended citation, make sure these are reflected in the README as well. Once this is done, we can create a release for this data package, update the metadata (form & DataCite) and publish to the catalogue 🥇

@fostermh
Copy link
Collaborator

fostermh commented Oct 1, 2024

the platforms list is not updated automatically. 'Mesocosm tank' has been added to the list and should be live momentarily.

@timvdstap
Copy link
Collaborator

Hi @bcollicutt I'm just checking on the status of this metadata record, were you able to confirm the author list? :)

@bcollicutt
Copy link

bcollicutt commented Oct 17, 2024 via email

@timvdstap
Copy link
Collaborator

@bcollicutt It's definitely possible to publish the metadata record while having the GitHub repository private. We'll just want to make sure that we include a statement (e.g., in the resource description) so that people know how they can request the data if they'd like, and it would be good to have a timeframe as to when the repository can be made publicly available.

@timvdstap
Copy link
Collaborator

@bcollicutt would you happen to have an update on this metadata record? Is it OK with collaborators to publish a metadata-only record? :)

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

5 participants