Skip to content

Open Science at LIMOS✯

UCA, like at the national level, is pushing for French research labs to follow an open science policy, meaning that data sharing is the rule and non-sharing is the exception that must be justified.

This policy is based on data sharing that must be FAIR:

  • **F**indable: rich metadata, indexed and identified by DOI
  • **A**ccessible: defined access protocol
  • **I**nteroperable: standardized open formats, specific vocabularies (Thesaurus)
  • **R**eusable: clear license, complete documentation

An Open Science cell has been created at UCA and offers various resources: https://science-ouverte.uca.fr/

At LIMOS, the "Open Science" policy is based on:

  • publications linked to a project, primarily using HAL as the main tool
  • code linked to a project, with code archiving on Software Heritage
  • data linked to the project, with referencing of the repository storing the data on Recherche Data Gouv
  • drafting a DMP (Data Management Plan) on Opidor for all ANR and European projects (CNRS requirement)

Note: An algorithm will be considered as research data

Publications - Open Science✯

Tenured academic staff (not PhD students) are required to have an account on HAL and to provide certain information:

  • an idHal (to be defined) to merge different author forms
  • an ORCID
  • the research field(s) associated with the research theme
  • the affiliated lab
  • deposit preferences

Publication deposit must be accompanied by the PDF for the publication to be considered as open science

See the HAL chapter

Code and Open Science✯

The code you produce for a project must be saved on Software Heritage

If it is deposited on GitLab LIMOS in a public repository, it will be harvested automatically by Software Heritage (quarterly or annual harvesting)

To comply with open science principles, the repository must therefore be public and must contain information about the project context with a Readme file, license information, and contact information related to the project and code. Ideally, there should be three files for this:

  • Readme
  • license
  • contact

You can save a new GitLab repository on Software Heritage from their archive page using the Save code now button, then entering your repository URL.

Add repository to SH

If the repository already exists on Software Heritage and you want to update it, click on the project and then on the Save again button

Update repository on SH

Readme✯

In text or markdown format, must contain:

  • A quick presentation of the project and the need it addresses
  • Main features and operating principle
  • Deployment information if needed

License✯

The ministry recommends two Creative Commons-type licenses for code to be included in the license file

Both licenses must be indicated in parallel: Etalab for the French side and CC By for international use

In short, the code can be freely used, provided that the author is credited by mentioning their name. This does not mean that the author agrees with how their work is used

Contact✯

This file must include the identity of the depositor (name, first name, email) and especially the identity of a person who can respond over time to various information requests that may arise

Repositories and Referencing✯

In an open science approach, your datasets should be accessible and referenced, unless they contain sensitive data.

Ultimately, your dataset must at least have a reference on recherche.data.gouv

Archiving✯

To archive your dataset, see /recherche/projets/#archivage

Referencing✯

Under development: UCA has a collection on recherche.data.gouv and LIMOS has a sub-collection

To create a reference, you must send the following information to the UCA Open Science service:

  • a title
  • a description
  • the authors (+ their ORCID)
  • contributors
  • keywords from standardized thesauri such as GEMET or INSPIRE

Data Management Plans✯

DMPs must be drafted on the Opidor platform; they serve to comprehensively present the data of your project. This document is almost mandatory for ANR projects and increasingly required for ERC projects

This document is very important in the open science policy as it will comprehensively present the data and metadata

See the DMP documentation