Dataset - False Creek Bioblitz, 2022

[hakai-it]

False Creek Bioblitz, 2022

https://cioos-siooc.github.io/metadata-entry-form/#/en/hakai/pX9Euv7m4yaHRKPuMtylMexACtt2/-Nd0YqVrleM4mMLlJDSU

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.

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)

[Br-Johnson]

Couple of notes:

• The Title could be descriptive to indicate that the dataset contains species occurrences.

• Is the 'status of the dataset' really ongoing? How so? Is there no end date to the data collection? Ie there's data still being collected? If it is all done, would change status to 'completed' and add a publication date (generally the date we publish the record).

• How were the oceanographic data collected? Could add that to instrument list.

• What sequencing platform was included? Could add that to the instruments section.

• I would recommend combining your 'Master specimen list' and 'Oceanographic measurements' datasets into one folder available at in one resource link, and provide a README.txt file to orient users to the contents of the data package, include a data dictionary file that describes the variables in each dataset. Ideally, this is hosted on GitHub rather than on a Google Drive. For reference, you can find a description of the required data package files here: https://data.hakai.org/mobilization/publishing/#hakai-data-package-content-recommendations

[timvdstap]

Assigning myself - will likely be working on helping standardize and mobilize species occurrence data from this bioblitz to OBIS. In light of that, this record should also be published to the Hakai Catalogue once all items are addressed.

[timvdstap]

Some additional thoughts to Brett's comments above:

• Add a description of the Geographic Extent in the 'Spatial' tab
• In the abstract you make mention of various partners/collaborators to this project - would you want them included as contributors in the metadata record (they don't necessarily need to be included in the citation)? If there's lots of contributors you can also add in an acknowledgement section in your GitHub repository readme.
• There's a new tab called "Taxonomic Classification" where you can include information about taxa included in the dataset. You likely have lots of taxa observed -- perhaps you can either add the main orders, or the species/genus most often observed?
• Pending future discussions, but I think it would make most sense for the Primary Resource to point to the overall GitHub repository. Subsets of the data published to e.g., BOLD, iNaturalist etc should be listed as Related Works.