How to properly cite Hyrax and related OPeNDAP software

Community
, , , ,
1

This post refers to Hyrax, Olfs, bes and libdap4, which are actively developed and maintained by the OPeNDAP, Inc team.

I want to know if there is a standard way to properly cite OPeNDAP software on a research or white paper, and potentially a presentations, that makes use of hyrax.

What I know

Each release of hyrax produces 3 tags, one per bes, olfs and libdap. So for example, the newest release Hyrax 1.17.0 requires:

  • OLFS1.18.14 , with DOI: 10.5281/zenodo.10565216. In text (Harvard style) this is:
Nathan Potter (2024) “OPENDAP/olfs: OLFS version 1.18.14 for Hyrax-1.17.0”. Zenodo. doi: 10.5281/zenodo.10565216.

James Gallagher (2024) “OPENDAP/bes: BES-3.21.0-46 for Hyrax-1.17.0”. Zenodo. doi: 10.5281/zenodo.10564745.

James Gallagher (2024) “OPENDAP/libdap4: Hyrax-1.17.0”. Zenodo. doi: 10.5281/zenodo.10564122.

My question is:

  • should there be a single bundled DOI?

And if so

  • what is the best way to do so?

Having a standard way for users/publishers/etc to reference all Hyrax together would make it easier for us to track the a “measure” of the impact it has. A potential useful statistic.