Dataset - Seton and Anderson Lake Multibeam Survey - 2024 - British Columbia

[hakai-it]

Seton and Anderson Lake Multibeam Survey - 2024 - British Columbia

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

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]

Thanks for the submission @hakaiholmes! Some questions:

• EPSG code 6646 seems to be for Karbala/Iraq? Am I looking at it wrong?
• I've removed the position / email associated with Hakai Institute (Publisher) - email is already included with the affiliation and the position would be only applicable to individual information.
• I've added ROR for the Hakai Institute
• Could Nick create an ORCID? Looking at Dataset - Knight Inlet Remotely Operated Vehicle Marine Habitat Survey #124, I see that Nick does have an ORCID
• If Nick's listed as Point of Contact, we should include his email
• I've moved 'Hakai Geospatial' to the individual information section. That way we can still add Hakai Institute as affiliation
• For the related work, I'm a bit on the fence -- usually for a Metadata Report I would default to the relation type 'Has Metadata', but this perhaps appears to be more of a Technical Report (as indicated by report title)? If so, I would perhaps just change the title of the related resource to 'Seton and Anderson Lake Multibeam Survey Technical Report', in which case the relation type can stay 'Is Documented By'. Happy to be convinced otherwise though.

I love how descriptive you've been with the platform/instrument(s)!

[hakaiholmes]

All done here. I have made those changes. No clue how that EPSG number got there?! Some confusion on the pre-saved contacts which I will ask you about in slack. Working on the knight ROV record fixes now.

[timvdstap]

Excellent, thanks for making those changes Keith! I've published the record and finalized the record in DataCite.