Sven F.

I think the bibTex specification does not cover software as a native entry type: https://en.wikipedia.org/wiki/BibTeX#Entry_types If you have a look at the current CFF core specification, it is targeted for...

x-ref https://github.com/nf-core/tools/issues/361, because the CFF would need to be updated with the correct DOI before the release as well.

Started to model the release process for nf-core pipelines with BPMN, so we have some documentation of it :D (not complete yet, but feel free to hit me with the...

Current status of the process (will be modified regularly until finished): 

Hm, I was just thinking that we get this information for free over the Anaconda API, right? For example: https://api.anaconda.org/package/bioconda/samtools Although package maintainers do not always provide all fields info...

hm, i see. There is no such thing as a tool registry with DOI and publication URIs, right? Maybe we need this...

Maybe should activate this discussion again: https://github.com/nextflow-io/nextflow/issues/866 Tools and parameters that are used in Nextflow should be descripted in a structured way, so humans and machines can work with it....

Uh, this is actually very nice. Just checked the API request for fasttree: https://bio.tools/api/tool/fasttree Seems that we get the information we need from it, so no need to have an...

Just thinking wildy here: why not just providing the top-level DOI that automatically routes to the latest Zenodo DOI version of a project and avoid the hassle? People can get...

> You mean one like that: https://zenodo.org/badge/latestdoi/54024046 That's the one you can get with the first release with Zenodo. Exactly. > But there's way to reserve a DOI so it...