Short term action: As an author give others the citable version of your software

[orchid00]

We would like to collect resources that would serve as examples of citable software in different domains.
A discussion on this topic is encouraged.

[georgiesamaha]

Hi Paula,
I work at the Sydney Informatics Hub which is a core research facility at the University of Sydney. We have made many of our optimised, reproducible bioinformatics pipelines citable for researchers. We used WorkflowHub to generate DOIs for the pipelines and have included these in our citation files on each GitHub repo.

Here are a few examples:
10.48546/workflowhub.workflow.145.1
10.48546/workflowhub.workflow.152.1
10.48546/workflowhub.workflow.146.1

[supernord]

This is a great example of a WorkflowHub DOI appearing in a research article: https://doi.org/10.1111/mec.16446
😃

[orchid00]

Hi @georgiesamaha thanks for sharing those! and describing that WorkflowHub can be used to generate DOIs. I wonder if you not only follow this process for the pipelines that the Sydney Informatics Hub supports, but maybe also encourage others to do the same. For example users of collaborators. It will be great to get to more of this kind of examples.

A side note, do you consider yourself a Research Software Engineer? If you haven't join please have a look if this is of your interest. http://rse-aunz.org/

[georgiesamaha]

Hi @orchid00, we're work closely with @supernord as Aus BioCommons partners to develop guidelines and recommendations for how bio workflow developers can develop reproducible workflows. This includes things like making your pipelines citable with DOIs and .CFF files.

Thanks for the RSE link, will take a look :)

[orchid00]

Thank you also for mentioning the Citation File Format (CFF) https://citation-file-format.github.io/
Are there any others who are using it and encouraging its use?

[tracychew]

We should encourage and use the .CIFF files, if there aren't others doing so. A good avenue for doing this is to include adding these files in Github documentation guidelines such as those provided by the BioCommons @supernord

I have found myself googling how to cite Github repositories when there is no associated peer reviewed article (often not the case for workflows)

[supernord]

*.cff files are in BioCommons documentation guidelines v1.4

Thanks to @tracychew & @georgiesamaha for the idea 😃

I also need to update the How-to-Guide to reflect use of .cffs

[orchid00]

Hi @tracychew the Software Citation Principles are a good read to find motivation https://force11.org/info/software-citation-principles-published-2016/
using .CFF files and a software licence to your repositories has good implications for reuse!

[AyeshaSadiq7]

Hi everyone,

This is Ayesha from Monash eResearch Center which is a Monash University commitment to accelerating research by applying advanced computing and information technology to important research problems. The centre partners with individual researchers, Australian research institutions and facilities global research communities to disseminate and promote research data and outcomes.

I am co-designing/co-developing a digital research infrastructure and data platform (under Monash NetZero Initiative) that will generate research-ready data sets for researchers to innovate smart energy solutions.

The idea is to choose an appropriate CC-BY license for software dissemination as an open-source project and create citable DOIs for the same using Monash Bridges as a data repository for research data, collections, and research artefacts.

Thank you.
Ayesha

[orchid00]

hi @AyeshaSadiq7 welcome to the group and thanks for your introduction.

Thanks for sharing about your work, I would definitely like to understand better what is the use of Monash NetZero, it is the first time I hear about it.

As guides for researchers you might want to have a look at:

• Liffers, Matthias, & Honeyman, Tom. (2021). ARDC Guide to making software citable. Zenodo. https://doi.org/10.5281/zenodo.5003989
• A guide about Software licensing. Australian Research Data Commons. (2021, June 21). ARDC Research Software Rights Management Guide. Zenodo. http://doi.org/10.5281/zenodo.5003962

Ayesha, I would also encourage you to check in with your copyright officer at Monash to discuss software dissemination. CC-By licences are mainly used for data and not for software. https://choosealicense.com/ is a great resource to learn more about software licences.

Also, I haven't share this page before, because we are going to transition to a new website, but in the mean time, a lot of resources are also available through this page: https://ardc.edu.au/resources/working-with-research-software/software-citation/

I also like to invite others to comment. I will be away for 4 weeks, and you might want to continue this important conversation.
@tom-h @supernord @tracychew @georgiesamaha @GraceAHall

[AyeshaSadiq7]

Thanks Paula, my bad I think I missed something in writing. It should be an open-source license (https://opensource.org/licenses) for the software and CC-BY for the generated data sets.

Thanks for correcting me. Hope to continue a good discussion on the same and will chase the shared links for more information.

[orchid00]

Cool, this other discussion topic seems relevant for the people in this thread too about CREDIT #13

[tom-h]

Another guide you might be interested in is our recently produced explainer for SPDX licence identifiers. This mechanism is particularly useful for clarifying licensing on a mix of data and software with different licences.