Sound Data Management Training

h1. Publishing research data

Research data publication allows your data to be reused by other researchers e.g. to validate your research or to carry out follow-on research. To that end, a suitable data publication host will allow your data to be discovered (e.g. by publishing metadata) and will be publicly accessible (i.e. on the internet).

Research data can be published on the internet through:

* project web sites

* research group web-sites

* generic web archives (e.g. "archive.org":http://archive.org)

* research data sites (e.g. "figshare":http://figshare.com/)

* more general open access research hosts (e.g. "f1000 Research":http://f1000research.com/about/)

* thematic repositories dedicated to a specific discipline / subject area - sadly there is no sign of an appropriate repository for digital music and audio research

* institutional repositories dedicated to research from a specific organisation (e.g. QMUL have "a repository":https://qmro.qmul.ac.uk/jspui/ through which "Green open access":http://en.wikipedia.org/wiki/Open_access copies of papers by QM research staff can be published).

* supplementary materials [[Publishing Data Through Journals|attached to journal articles]]

Within the Centre for Digital Music, we now have a "research data repository":http://c4dm.eecs.qmul.ac.uk/rdr/ for publishing research data outputs from the group.

If the publication web-site is also to be the long-term archive for you data, you should check that the meets the criteria for an archival storage system. However, although data will be written to the host irregularly, it is expected that the data will be accessed more frequently than archived data. Offline storage is therefore not suitable.

If an external publisher is used for your research data, you should check the T&Cs e.g. to see whether copyright on the data is transferred to the publisher and to check how long they will publish your data for.

If data is published through a publisher / repository, then it can also be held on institutional storage so long as the license is followed. Publishing under a Creative Commons license makes this easy. However, if data is available in multiple places, different versions of the data may occur (e.g. changes between dates uploaded, data corruption). You should therefore make it easy to identify which specific version of the data is correct by publishing a "digital fingerprint":http://en.wikipedia.org/wiki/Cryptographic_hash_function (e.g. a "MD5 hash":http://en.wikipedia.org/wiki/MD5). MD5 fingerprints can be generated in Windows using "MD5summer":http://www.md5summer.org/, in Linux with the Gnu "md5sum":http://www.gnu.org/software/coreutils/manual/html_node/md5sum-invocation.html utility and on Max OS X using "md5 or openssl":http://osxdaily.com/2009/10/13/check-md5-hash-on-your-mac/

h2. Persistent IDs for data

In order to ensure ongoing access to your data, should look to acquire a persistent ID for your dataset. However, persistence is a continuum with some IDs more persistent than others. DOIs and handles are designed to be persistent in the long term, allowing a unique identifier to be redirected to the current location of your dataset - if the dataset moves, the DOI/handle can be pointed at the new location. Repositories and research data sites may provide DOIs for data submitted to them. Institutional URLs may be persistent if the institution makes a policy decision to make them so. Other URLs may change when web-sites are revamped making the published URL for your data return a "404 Not Found" message.

Persistent IDs are useful for referencing datasets, and are particularly handy if they are short - long / ugly DOIs can be shortened using the "ShortDOI":http://shortdoi.org service.

And [[And more repositories|more repositories]]