Page MenuHomeSoftware Heritage

Update publication page
Closed, MigratedEdits Locked

Description

The following entries should be added to https://www.softwareheritage.org/publications/:

  1. https://hal.archives-ouvertes.fr/hal-02446202

bibtex:

@article{dicosmo:hal-02446202,
  TITLE = {{Referencing Source Code Artifacts: a Separate Concern in Software Citation}},
  AUTHOR = {Di Cosmo, Roberto and Gruenpeter, Morane and Zacchiroli, Stefano},
  URL = {https://hal.archives-ouvertes.fr/hal-02446202},
  JOURNAL = {{Computing in Science \& Engineering}},
  PUBLISHER = {{IEEE}},
  PAGES = {1-9},
  YEAR = {2019},
  MONTH = Dec,
  DOI = {10.1109/MCSE.2019.2963148},
  KEYWORDS = {open science ; digital object identifier ; digital preservation ; Persistent identifiers ; Software citation ; Reproducibility ; Reference ; Software reference},
  PDF = {https://hal.archives-ouvertes.fr/hal-02446202/file/software_identifiers.pdf},
  HAL_ID = {hal-02446202},
  HAL_VERSION = {v1},
Abstract = { Among the entities involved in software citation, software source code requires special attention, due to the role it plays in ensuring scientific reproducibility. To reference source code we need identifiers that are not only unique and persistent, but also support \emph{integrity} checking intrinsically. Suitable identifiers must guarantee that denoted objects will always stay the same, without relying on external third parties and administrative processes. We analyze the role of identifiers for digital objects (IDOs), whose properties are different from, and complementary to, those of the various digital identifiers of objects (DIOs) that are today popular building blocks of software and data citation toolchains. We argue that both kinds of identifiers are needed and detail the syntax, semantics, and practical implementation of the persistent identifiers (PIDs) adopted by the Software Heritage project to reference billions of software source code artifacts such as source code files, directories, and commits. },
}
  1. https://hal.archives-ouvertes.fr/hal-02135891

bibtex:

@Article{         2020GtCitation,
  author={Pierre {Alliez} and Di Cosmo, Roberto and Benjamin {Guedj} and Alain {Girault} and Mohand-Said {Hacid} and Arnaud {Legrand} and Nicolas {Rougier}},
  journal={Computing in Science Engineering},
  title={Attributing and Referencing (Research) Software: Best Practices and Outlook From Inria},
  year=2020,
  volume=22,
  number=1,
  pages={39-52},
  abstract={Software is a fundamental pillar of modern scientific research, across all fields and disciplines. However, there is a lack of adequate means to cite and reference software due to the complexity of the problem in terms of authorship, roles, and credits. This complexity is further increased when it is considered over the lifetime of a software that can span up to several decades. Building upon the internal experience of Inria, the French research institute for digital sciences, we provide in this article a contribution to the ongoing efforts in order to develop proper guidelines and recommendations for software citation and reference. Namely, we recommend: first, a richer taxonomy for software contributions with a qualitative scale; second, to put humans at the heart of the evaluation; and third, to distinguish citation from reference.},
  keywords={Software packages;Complexity theory;Research and development;Libraries;Metadata;Best practices;Guidelines;Software citation;software reference;authorship;development process},
  doi={10.1109/MCSE.2019.2949413},
  ISSN={1558-366X},
  month={Jan},
  note = {Available from \url{https://hal.archives-ouvertes.fr/hal-02135891}}
}
  1. https://dl.acm.org/doi/10.1145/3183558 Building the Universal Archive of Source Code

bibtex:

  @article{10.1145/3183558,
 author = {Abramatic, Jean-Fran\c{c}ois and Di Cosmo, Roberto and Zacchiroli, Stefano},
 title = {Building the Universal Archive of Source Code},
 year = {2018},
 issue_date = {September 2018},
 publisher = {Association for Computing Machinery},
 address = {New York, NY, USA},
 volume = {61},
 number = {10},
 issn = {0001-0782},
 url = {https://doi.org/10.1145/3183558},
 doi = {10.1145/3183558},
 journal = {Commun. ACM},
 month = sep,
 pages = {29–31},
 numpages = {3}
}

Event Timeline

moranegg triaged this task as Normal priority.Jan 26 2020, 2:05 AM
moranegg created this task.

thanks Morane!

While we are at it, we should also make sure that we self-host all PDF preprints of our articles. It is OK to also point to preprint hosted elsewhere, but given it is the project website and these are our articles, it's kinda weird to depend on the availability of some external website to allow readers of our website to download the article. (I'm not saying to not link to the external article version, but that we should also link to a locally hosted copy.)

I missed that one and just saw that the new publications have already been added to our website.

Closing that task as resolved.

I have created T2261 to track the work related to the self hosting of PDF preprints of our articles.

@anlambert: Can you also update this page as well- https://docs.softwareheritage.org/devel/swh-model/persistent-identifiers.html
Adding the first item (hal-02446202) to the references?

It will be very helpful :-)

Should I reopen the task for that? or create a new task maybe?
Because the data is here...