Page tree
Skip to end of metadata
Go to start of metadata


Currently how to cite software is not clear or technically resolved, and secondly the documentation of basic information (metadata) that a software maker should provide is also not clearly defined so that researchers looking to use published works do not have enough information to act on.

Guidance is needed on both issues and we can engage with key players working on these problems.

Editorial evaluation

Editorial criterion

#Questions 1. needs 3. improving systems  

#Editorial 1. empowering 2. discourse 3. bottom-up 5. replicable models 

#Brand 3. gender equality 4. co-creation 

#Strategy 1. three channel  

#Audience 1. career 2. engaged

Note: Blog comparators are not carrying stories on this topic (3.18 SW)

How to break the topic down

  • How to record information to describe a software project and its contributors
  • Projects going on to create systems for software citation: to record, to read, to collect, etc. Get input from different projects. What are their research questions/interim findings. We have CodeMeta, CFF, CiteAs.
  • What information do journals and repositories want when submitting software
  • How can citing be more useful for researchers. Is there enough information to be useful for research publication/software readers/users
  • The Future: Can software cited be fully available in a – validated, CI, packet managed, dependency managed, virtualised way – so that it can be retrieved or run live. e.g, Jupyter and Binder to republish
  • Note: we need clear guidelines or pointers to this info, for: software makers, journal submissions of software, and academic writers of scholarly literature wanting to cite software.
  • Top three info sources in each area: journals, papers, software citation software project, working groups and organisations

Community: to engage 

Literature and projects (Zotero)

Key resources

2016 Force11 working group running through Dec' 18. Group Article

2018 Nature Software Submission Guidelines’, 2018. 


Blog post in and running order:


  • Project: CFF Citation File Format Stephan Druskat, CFF lead, HU (see attached draft)
    OR, if it comes in
  • Force11 group report. Neil Chue Hong, Director Software Sustainability Group, Edinburgh Uni, FORCE11 Software Citation WG co-leader (due 10 May, now in 22 may)

Followed by 

No, or no signs of life

  • Project: CiteAs

Possible and being worked on

  • Re-use and journals. Blog. How software is described and documented so that its citation can be of use to future practitioners and readers of research publications. e.g. 2018 Nature Software Submission Guidelines’, 2018.
  • Project: CodeMeta
  • See list possible articles
  • Get more articles 0.5 day
    • FORCE11
    • Juyptr
    • DHd – Digital Humanities im deutschsprachigen Raum e.V. (DHd)/ Association Digital Humanities in German Speaking Countries, DHd Working Group Software Engineering in den Digital Humanities
    • Digital Preservation Coalition & Software Preservation Network, Jessica Meyerson and Sarah Middleton,
    • Anna Novesky, "Authorship of Data and # Research Software - Possibilities of Visualization and Establishment in History", 

    • Emily Sena, research replication, Uni of Edinburgh
    • Harvard Astrophysics

Editorial posts (to do)

  • Theme announce SW
  • Theme - key issue breakdown (notebook)

Notebook (June to August)

  • How to: The Software Citation community - get them onto the forum to help move things forward. I now have the contacts and literature from #OSBarcamp 
  • Blog/ resource: someone could give the top 3 lit, journals, projects, citation managers to use: Literature and projects (provisional)
  • DataCite - how to join ORCID, posts and software use
  • Learning resources:
    • Open Science MOOC
    • FORCE11 summer course
  • Hold a video-conf workshop

In the notebook - but outside of the theme:

  • Announce next theme
  • Hold consultation - ongoing
  • Upload Open Science taxonomy
  • Map whats happening in LG with Open Science
  • Integrate Zotero library

Issues and questions:

Lobby OpenAIRE to include software. Currently OpenAIRE policy is not to include it – forum issue

The Future?

Discover and run scientific code, Code Ocean

Simulations in the browser, Jupyter and Binder to republish

Continuos Integration and validation, with dependencies and full contributor audit 

Create a grid for the theme

To include: timeline, issues, keywords, who to name check, questions to ask.


See software cite theme contacts

How To

Practical guide for GitHub using Zenoda to store a version and get a PID DOI

How CiteAs searches for sources