I thought the cff file wouldnt hold info for a pap...
# pipeline-maintainers
d
I thought the cff file wouldnt hold info for a paper but for the actual code, i.e. zenodo entry. See for example https://zenodo.org/records/14409147 (these are the colleagues that brought my attention to it). But I am really not an expert in that 😉
r
It's been a while, but if I look back I think the issue was, that it only puts the authors of that particular PR (i.e. https://zenodo.org/records/7507478) instead of all contributors: https://zenodo.org/records/8005492
d
allegedly the title and author list of https://zenodo.org/records/14332397 was improved to https://zenodo.org/records/14409147 by the addition of the cff file. That seems a considerable improvement to me. And might also benefit the sarek entry, as I see it (e.g. there is SusiJo as entry instead of a nice name...).
r
I am not sure how the name resolution works, most names are proper and not the GitHub handles. 🤨 @James Fellows Yates wasn't in some cases also just the authors of the nf-core paper credited instead of the pipeline authors?
maybe people need to have their GitHub account connected to Zenodo?
j
Yes, the default citations.cff we added was the nf-core paper, and then suddenyl all Zenodo records of nf-core pipelines were attributed to the original nf-core paper 😬
I guess theortically we could add tooling to modify
citation.cff
to keep in sync with our manifest stuff etc
But IIRC also the abstract in teh ctaiation.cff (I think there was one), replaces our changelog ETC
It depends what we put into it to be fair
d
I think if the cff is considered then it should cite the code, i.e. a software citation, not an article. afaik the cff makes it easier to cite the software by providing a proper format (author names, orcid, title, etc.). Additionally it makes the zenodo entry look beautiful. And allegedly it lists an entry in google scholar.
j
I guess then we should have some tooling then, that merge to master the cff updates to include all the contributos and the abstract bit
Maybe make a issue on #tools ?
m
Hi. To chime on that, I also got tired of Zenodo using GitHub handles, not knowing how to separate first name from last name, etc, and then having to log in to Zenodo add all the ORCIDs again and again. I’ve ended up manually curating
citation.cff
before the release so that the Zenodo is naturally beautiful. I guess it only works for us because we have very few external collaborations.
d
in what pipeline do you use the .cff? maybe I just add it myself indepent of the template
m
There, for instance (you can see the history).
d
thanks!
j
I wonder if these can be converted/generated from the new nextflow manifest... so maybe it would be quite easy? @Daniel Straub did you make the issue on #tools? This might be worth it
d
sorry, total chaos on my todo list
j
No rush!
d