#+INCLUDE: "../../common/modules/rdc-bio.org::#main" :only-contents t :minlevel 2
* Software and Open Science
** Why Open Science? :noexport:
#+BEAMER: \vspace{-.5em}
*** Open Science ([[https://www.ouvrirlascience.fr/wp-content/uploads/2021/10/Second_French_Plan-for-Open-Science_web.pdf][Second National Plan for Open Science]], France, 2021)
/Unhindered/ dissemination of results, methods and products from scientific
research.\\
It draws on /the opportunity provided by recent digital progress/
to develop /open access/ to /publications/ and – as much as possible – /data/,
/source code/ and /research methods/.
#+BEAMER: \pause
#+BEAMER: \vspace{-.3em}
*** Jean-Eric Paquet (EU DGRI, [[https://www.eosc.eu/sites/default/files/EOSC-SRIA-V1.0_15Feb2021.pdf][on the objective of Open Science]])
# Preface of EOSC SRIA https://www.eosc.eu/sites/default/files/EOSC-SRIA-V1.0_15Feb2021.pdf
“Increase /scientific quality/, the /pace of discovery and technological
development/, as well as /societal trust in science/.”
#+BEAMER: \pause
#+BEAMER: \vspace{-.1em}
*** Mariya Gabriel ([[https://www.s4d4c.eu/insights-from-commissioner-mariya-gabriel-towards-the-european-union-science-diplomacy/][EU Commissionneer]] for Research)
# From the article: https://www.s4d4c.eu/insights-from-commissioner-mariya-gabriel-towards-the-european-union-science-diplomacy/
The COVID-19 crisis has also shown that cooperation at international level
in research and innovation is more important than ever, including through
/open access to data and results/. /No nation, no country can tackle any of
these global challenges alone/.
#+BEAMER: \pause
#+BEAMER: \vspace{-.3em}
*** Yuval Noah Harari (on COVID 19)
\hfill /“The real antidote [to epidemic] is/ scientific knowledge /and/ global cooperation.”
** Software is a pillar of Open Science
#+INCLUDE: "../../common/modules/swh-ardc.org::#pillaropenscience" :only-contents t :minlevel 3
#+BEAMER: \pause
***
\hfill Preserving (the history of) source code is necessary for /reproducibility/
** Software /Source Code/ is Precious Knowledge
#+INCLUDE: "../../common/modules/source-code-different-short.org::#softwareisdifferent" :only-contents t :minlevel 3
* Policy framework and growing needs
** The Paris Call on Software Source code (2019, UNESCO)
#+INCLUDE: "../../common/modules/policyactions.org::#pariscall2019science" :only-contents t :minlevel 3
** Second French National plan for Open Science (2021, MESRI)
#+INCLUDE: "../../common/modules/policyactions.org::#pnso2" :only-contents t :minlevel 3
** Research Software is getting recognized
#+INCLUDE: "../../common/modules/policyactions.org::#awards2022" :only-contents t :minlevel 3
** A plurality of needs that we must address
#+INCLUDE: "../../common/modules/swh-ardc.org::#userneeds" :only-contents t :minlevel 3
** Archive, Reference, Describe, Cite and Credit
#+INCLUDE: "../../common/modules/swh-ardc.org::#ardc" :only-contents t :minlevel 3
* Can you address these needs?
** A word of warning: forges are /not/ archives!
*** 2015: the first big bad news
Google Code and Gitorious.org shutdown: ~1M endangered repositories
- broken links in the web of knowledge (my papers too)
** Addressing the four needs... \hfill (see [[https://dx.doi.org/10.1007/978-3-030-52200-1_36][ICMS 2020]] for details)
#+INCLUDE: "../../common/modules/swh-ardc.org::#swh-ardc-short" :only-contents t :minlevel 3
** HAL and Software Heritage: building a curated software catalog
#+INCLUDE: "../../common/modules/swh-ardc.org::#halswhoverview" :only-contents t :minlevel 3
* Yes you can!
** An example is worth a thousand words
#+INCLUDE: "../../common/modules/swh-ardc.org::#demoswhhal" :only-contents t :minlevel 3
* Call to action
** Best practices for ARDC actionable today ...
#+INCLUDE: "../../common/modules/swh-ardc.org::#ardc-best-france" :only-contents t :minlevel 3
** Bottomline
*** HAl+SWH let you address all the needs at once...
- /researcher, engineer/: archival, reference, credit, CV etc. /with a little effort from them/
- /labs, organizations/: track and report software production in a simple way
- /technology transfer offices/: view the software production
- /national level/: a /curated/ catalog of the software production
#+BEAMER: \pause
*** ... with a little effort from your side
- Update the Open Science policy to include software
- Train on the use of SWH and HAL for software
- Join the network of HAL moderators for software
#+BEAMER: \pause
***
#+LATEX: \centering{\large it's a long road, but together we can make it}\\[1em]
#+latex: \centering{\huge\bf Questions?}
-* END
- \end{document}
* Appendix :B_appendix:
:PROPERTIES:
:BEAMER_env: appendix
:END:
**
\vfill
\centerline{\Huge Appendix}
\vfill
-* Policy news
-** The Paris Call on Software Source code (2019, UNESCO)
-#+BEAMER: \vspace{-.8em}
-*** :B_column:BMCOL:
- :PROPERTIES:
- :BEAMER_col: .53
- :BEAMER_env: column
- :END:
- #+ATTR_LATEX: :width .65\linewidth
- file:UNESCOParisCallMeeting.png
- UNESCO, Inria, Software Heritage invite\\
- [[https://en.unesco.org/news/experts-call-greater-recognition-software-source-code-heritage-sustainable-development][40 international experts to meet in Paris]]
- #+BEAMER: \pause
-*** :B_column:BMCOL:
- :PROPERTIES:
- :BEAMER_col: .5
- :BEAMER_env: column
- :END:
- #+ATTR_LATEX: :width .6\linewidth
- file:paris_call_ssc_cover.jpg
- [[https://en.unesco.org/foss/paris-call-software-source-code][The call is published on Feb 2019]]\pause
-*** :B_ignoreheading:
- :PROPERTIES:
- :BEAMER_env: ignoreheading
- :END:
-# #+BEAMER: \vspace{-.3em}
-***
- :PROPERTIES:
- :BEAMER_COL: 1.06
- :BEAMER_env: block
- :END:
- #+LATEX: {\it
- “[We call to] promote software development as a valuable research activity,
- and research software as a key enabler for Open Science/Open Research,
- sharing good practices and recognising in the careers of academics their
- contributions to high quality software development, in all their forms”
-** The UNESCO recommendations for Open Science, 2018-2021
- #+INCLUDE: "../../common/modules/policyactions.org::#unesco2021" :only-contents t :minlevel 3
-** The EOSC SIRS report: Software Source Code and Open Science, 2020
- #+INCLUDE: "../../common/modules/policyactions.org::#eoscsirs2020-expanded" :only-contents t :minlevel 3
-** French National plan for Open Science, 2021-2024
- #+LATEX: \vspace{-.3em}
- #+INCLUDE: "../../common/modules/policyactions.org::#PNSO2" :only-contents t :minlevel 3
- #+BEAMER: \pause
-***
- \hfill The "Collège Logiciel" of the National Committee on Open Science (CoSO) is now live!
-** Software in the EOSC
- #+INCLUDE: "../../common/modules/policyactions.org::#eoscswtf2021" :only-contents t :minlevel 3
-** Call to action: let's engage with policy makers (it may be us!) :noexport:
-#+BEAMER: \vspace{-.5em}
-*** Institutional representation :B_block:
- :PROPERTIES:
- :BEAMER_COL: .5
- :BEAMER_env: block
- :END:
- we need an (open source) software VP in
- - universities
- - ministries
- - governments
-#+BEAMER: \pause
-*** Funding for infrastructures :B_block:
- :PROPERTIES:
- :BEAMER_env: block
- :BEAMER_COL: .5
- :END:
- push for funding instruments adapted to digital infrastructures (e.g. ESFRI):
- + cost of human resources is /predominant/
- + /much shorter/ time frame
-#+BEAMER: \pause
-*** :B_ignoreheading:
- :PROPERTIES:
- :BEAMER_env: ignoreheading
- :END:
-*** Set the default to open: pass the message
- /publicly funded research software should be open source/ \\
- \hfill exceptions must be justified
-#+BEAMER: \pause
-*** Career evaluation and incentives
- - recognize /quality/ software development
- + see e.g. [[https://hal-lara.archives-ouvertes.fr/hal-03110723][the 2021 Inria guidelines]] (in french)
- and [[https://hal.archives-ouvertes.fr/hal-02135891][this CiSE 2020 article]] (in english)
- - keep the human in the loop, avoid number games
-** The floor is yours
-***
-#+LATEX: \centering{\large it's a long road, but together we can make it}\\[1em]
-
- #+latex: \centering{\huge\bf Questions?}
-*** References
- #+BEGIN_EXPORT latex
- \begin{thebibliography}{Foo Bar, 1969}
- \footnotesize
-% \bibitem{SwForumEu2021} R. Di Cosmo, \emph{A revolutionary infrastructure for Open Source}, 2021, EU Software Forum \href{https://annex.softwareheritage.org/public/talks/2021/2021-03-24-SwForum.pdf}{(slides)} \href{https://youtu.be/AwY527kDMfM?t=178}{(video)}
- \bibitem{UNESCOOS} UNESCO, \emph{Draft recommendations on Open Science}
- \bibitem{EOSCSirs2020} EOSC SIRS Task Force, \emph{Scholarly Infrastructures for Research Software}
- \newblock 2020, Publications office of the European Commission, \href{https://doi.org/10.2777/28598}{(10.2777/28598)}
- \bibitem{DiCosmo2020d} R. Di Cosmo, \emph{Archiving and Referencing Source Code with Software Heritage}
- \newblock International Conference on Mathematical Software 2020 \href{https://dx.doi.org/10.1007/978-3-030-52200-1_36}{(10.1007/978-3-030-52200-1\_36)}
-% \bibitem{DiCosmo2019} R. Di Cosmo, M. Gruenpeter, S. Zacchiroli\newblock
-% \emph{Referencing Source Code Artifacts: a Separate Concern in Software Citation},\newblock
- example: [[https://archive.softwareheritage.org/swh:1:dir:92a6d0b9953aa3645ffac6bb4fb30a02932872eb;origin=https://gitlab.inria.fr/gt-sw-citation/bibtex-sw-entry;visit=swh:1:snp:05753fe748b7b85cbd0a9e2bea89aac5268b06c6;anchor=swh:1:rev:7c621448de21b0950cdff2dda37834cd4b389bfa][archived version of biblatex-software]]
-* Adoption
-** Growing adoption of SWH in Academia (selection)
- #+INCLUDE: "../../common/modules/swh-adoption-academic.org::#adoption" :only-contents t :minlevel 3
-* Demo time!
-** Overview of the Software Heritage / HAL synergy
- #+ATTR_LATEX: :width \linewidth
- file:hal-swh-overview.png
-** A walkthrough
- #+INCLUDE: "../../common/modules/swh-ardc.org::#demoswhhal" :only-contents t :minlevel 3
-** Growing adoption of SWH in Academia (selection)
- #+INCLUDE: "../../common/modules/swh-adoption-academic.org::#adoption" :only-contents t :minlevel 3
-** An international, non profit initiative\hfill built for the long term
-** Call to action on ARDC: let's foster adoption!
-*** Train students and colleagues to [[https://www.softwareheritage.org/save-and-reference-research-software/][archive and reference relevant source code]]
-#+BEAMER: \vspace{-.5em}
-***** :B_column:BMCOL:
- :PROPERTIES:
- :BEAMER_col: .05
- :BEAMER_env: column
- :END:
-***** :B_column:BMCOL:
- :PROPERTIES:
- :BEAMER_col: .45
- :BEAMER_env: column
- :END:
- + full details in the [[https://dx.doi.org/10.1007/978-3-030-52200-1_36][ICMS 2020]] article
-***** :B_column:BMCOL:
- :PROPERTIES:
- :BEAMER_col: .5
- :BEAMER_env: column
- :END:
- + short operational [[https://www.softwareheritage.org/save-and-reference-research-software/][HOWTO online]]\pause
-***** :B_ignoreheading:
- :PROPERTIES:
- :BEAMER_env: ignoreheading
- :END:
-*** Engage conferences, journals, learned societies to use Software Heritage and SWHIDs
- APIs for [[https://save.softwareheritage.org][save code now]] and [[https://hal.inria.fr/hal-01872189][deposit]] are available to integrate with
-#+BEAMER: \vspace{-.5em}
-***** :B_column:BMCOL:
- :PROPERTIES:
- :BEAMER_col: .25
- :BEAMER_env: column
- :END:
- + Research Articles
-***** :B_column:BMCOL:
- :PROPERTIES:
- :BEAMER_col: .42
- :BEAMER_env: column
- :END:
- + Artifact Evaluation Committees
-***** :B_column:BMCOL:
- :PROPERTIES:
- :BEAMER_col: .3
- :BEAMER_env: column
- :END:
- + Badging initiatives
-***** :B_ignoreheading:
- :PROPERTIES:
- :BEAMER_env: ignoreheading
- :END:
- #+BEAMER: \pause
-*** Help grow and structure the community
- - Promote the [[https://www.softwareheritage.org/ambassadors/][ambassador program]]
- - Encourage our institutions to
- + include Software Heritage in their Open Science policy
- + become [[https://www.softwareheritage.org/support/sponsors/][member/sponsor]]
- + build a Software Heritage mirror (see ENEA)
-* What is at stake before and beyond ARDC
-** What is at stake: before ARDC
- #+INCLUDE: "../../common/modules/swh-ardc.org::#beforeardc" :only-contents t :minlevel 3
-** What is at stake: beyond ARDC
- #+INCLUDE: "../../common/modules/swh-ardc.org::#beyondardc-evaluation" :only-contents t :minlevel 3
-* State of affairs in CS
-** The state of the art (in CS!) is far from ideal
-*** Main reasons: source code (/or the right version of it/) cannot be found
- - *policy issue*: opening up the code of research software
- - *infrastructures*: archive and reference it\hfill *let's start here*
-
-* Detailed addressing ARDC
-** Addressing the A(rchive)
- #+INCLUDE: "../../common/modules/swh-ardc.org::#swh-a" :only-contents t :minlevel 3
-** Recent preservation news
-*** Saving 250.000 endangered repositories...
- - summer 2019: BitBucket announce Mercurial VCS phase out
- - fall 2019: Software Heritage teams up with Octobus (funded by NLNet, thanks!)
- - july 2020: BitBucket erases /250.000/ repositories
- - august 2020: [[https://bitbucket-archive.softwareheritage.org][bitbucket-archive.softwareheritage.org]] is live
-#+BEAMER: \pause
-*** ... preserving the web of knowledge \hfill (original tweet [[https://twitter.com/gabrielaltay/status/1300218789762662401][is here]] ) :B_picblock:
** What about FAIR? (Findable, Accessible, Interoperable, Reusable)
*** FAIR data principles /for data/
*in a nutshell:* metadata, metadata, metadata all over the place (makes sense for data)\pause
*** But software is /not data/ ...
the terms /interoperability/ and /reusability/ have precise technical meaning for software,
and /differ significantly/ from what is intended by the I and R of FAIR;
- see the entries for [[https://en.wikipedia.org/wiki/Interoperability#Software][software interoperability]] and [[https://en.wikipedia.org/wiki/Reusability][software reusability]]
- it is /very difficult/ to achieve these properties even for commercial software developed by multi billion dollars corporations\pause
*** FAIR for software is a distraction
\hfill let's focus on the real issues at stake: ARDC a good starting point
-* SWHIDs
-** R(eference): granularity and identifiers \hfill [[http://doi.org/10.15497/RDA00053][10.15497/RDA00053]]
- #+LATEX: \only<1>{\begin{block}{}\centering Top concept layers vs. bottom artifact layers\end{block}}
- #+LATEX: \only<2>{\begin{block}{}\centering Extrinsic identifiers are key for the concept layers\end{block}}
- #+LATEX: \only<3>{\begin{block}{}\centering Intrinsic identifiers are key for the artifact layers\end{block}}
- #+LATEX: \only<4>{\begin{block}{}\centering In some cases, extrinsic identifiers can be added too\end{block}}
-
-** Extrinsic and Intrinsic identifiers in a nutshell
-*** Extrinsic identifiers: no /per se/ relation with the designated Object
- A /register/ keeps the correspondence between the identifier and the object
- - pre-internet era :: passport number, social security number, ISBN, ISSN, etc.
- - internet era :: DOI, Handle, Ark, PURLs, RRID, etc.\pause
-*** Intrinsic identifiers: derived from the designated Object
- /No register/ needed to keep the correspondence between the identifier and the object
- - pre-internet era :: musical notation, chemical notation (/NaCl/ is table salt)\pause
- - internet era :: cryptographic hashes for distributed software development, Bitcoin\pause
-***
- \hfill more in [[https://www.softwareheritage.org/2020/07/09/intrinsic-vs-extrinsic-identifiers/][this dedicated blog post]] (with pointers to literature)
+ #+LATEX: \only<1>{\begin{block}{}\centering Top concept layers vs. bottom artifact layers\end{block}}
+ #+LATEX: \only<2>{\begin{block}{}\centering Extrinsic identifiers are key for the concept layers\end{block}}
+ #+LATEX: \only<3>{\begin{block}{}\centering Intrinsic identifiers are key for the artifact layers\end{block}}
+ #+LATEX: \only<4>{\begin{block}{}\centering In some cases, extrinsic identifiers can be added too\end{block}}
+
+** Extrinsic and Intrinsic identifiers in a nutshell
+*** Extrinsic identifiers: no /per se/ relation with the designated Object
+ A /register/ keeps the correspondence between the identifier and the object
+ - pre-internet era :: passport number, social security number, ISBN, ISSN, etc.
+ - internet era :: DOI, Handle, Ark, PURLs, RRID, etc.\pause
+*** Intrinsic identifiers: derived from the designated Object
+ /No register/ needed to keep the correspondence between the identifier and the object
+ - pre-internet era :: musical notation, chemical notation (/NaCl/ is table salt)\pause
+ - internet era :: cryptographic hashes for distributed software development, Bitcoin\pause
+***
+ \hfill more in [[https://www.softwareheritage.org/2020/07/09/intrinsic-vs-extrinsic-identifiers/][this dedicated blog post]] (with pointers to literature)