{'fraction_non_alphanumeric': 0.03298471440064361, 'fraction_numerical': 0.015285599356395816, 'mean_word_length': 5.5473684210526315, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Git-RDM: A research data management plugin for the Git version control system

Many research funding agencies (Research Council UK 2015) and research societies (Royal Society 2012) are increasingly requiring that data from at least publicly funded research be made openly available, and with clear citations that describe provenance. These requirements have led to the proliferation of institutional repositories with universities maintaining a handful of data services, but also repository services capable of minting a persistent and citable Digital Object Identifier (DOI) (Technical Committee ISO/TC 46 (Information and documentation), Subcommittee SC 9 (Identification and description) 2012) for every published item. Figshare (figshare.com) and Zenodo (zenodo.org) are examples of the latter. Alongside data, software is also increasingly seen as a research output. This viewpoint necessitates not just open-source publication of code, but also provenance and attribution. While a DOI is an identifier of static items, many research teams use version control systems and services to organise their collective efforts and publish output, be that code or data. Popular examples include Git (Chacon and Straub 2014) and GitHub (github.com).