When metadata records are submitted for publication to the Hakai Metadata Catalogue they should include a version number that includes a major and minor version, ie. v2.1, where 2 is the major version and .1 is the minor version. Versioning is specific to the data product, not the metadata. Minor changes to the metadata do not require an update on the version.

For every data product, data providers need to determine what constitutes a major vs. minor version increment in a data management plan. As a suggested practice, something that affects the whole dataset or product, such as reprocessing or a change in author list, would constitute a major version change while annual additions of data (i.e. time series datasets) or minor error updates constitute minor version changes. When versions are incremented, it is critical that previous versions of the dataset remain available.

If your data record links users to data that is only available upon request, it is still good practice to include a version element. To avoid confusion, ensure that the version number in your metadata record matches the most up to date version number found in your data product. Versioning should also be included when no incremental changes are expected.

For changes in major and minor versions, it is important to include a log of what changes were made using something like a Changelog.txt file. This Changelog file should be stored within your data package.

When the data product is hosted on GitHub (Hosting Data) the version associated with the data record in the Hakai Metadata Catalogue should match the version of the GitHub Release. For data products not stored on the Hakai GitHub repository, ensure that your data product has an associated Changelog that indicates what the most recent version is, in addition to a folder containing archived versions.

For larger, continuous data records such as the CTD Research Grade Data that are published to ERDDAP, we want to ensure that we retain old versions of the datasets for reproducibility purposes. The suggested practice is to export .csv files annually into a data package and host this on a GitHub repository. A release of a data package would reflect annual increments of the data (i.e. one release for the 2015 - 2021 data, another release for 2015 - 2022 data, etc.). These releases would all be included in the same GitHub repository and added as downloadable resources (.zip file) to a single metadata record. The DOI associated with the data record would remain the same, but the version element of the data record in the Hakai Catalogue would reflect the latest version, with older versions archived and downloadable as unique releases via the Download and Resources section of the metadata record. These older versions should contain a readme file with the recommended citation specific to that version. The recommended citation in the Hakai Data Catalogue can be updated and should always reflect the recommended citation for the latest version.

Currently, no fields exist in the Metadata Entry Tool to link data records or DOIs to existing records in the Hakai Data Catalogue or other external catalogs. Until this feature is implemented, please include any related data products that you want to reference in the abstract, along with the relation type (i.e. "subset of", "is newer version of", etc). A list of the most commonly used relations can be found here.