# "Mobility and migration in Neolithic societies by the prism of apprenticeship networks. Lithic productions at the cusp to the Vth millennium BC" project DMP

Plan de gestion de données créé à l'aide de DMP OPIDoR, basé sur le modèle "ANR - structured DMP template (english)" fourni par
Agence nationale de la recherche (ANR).

## Plan Details

**Plan title** "Mobility and migration in Neolithic societies by the prism of apprenticeship networks. Lithic productions at the cusp to the Vth millennium BC" project DMP

**Deliverable** 5.1

**Version** First version

**Plan purpose/scope** This initial Data Management Plan (DMP 1) for the ANR MOBILITH project is focused on identifying and describing the various datasets that will form the foundation of the project. It also aims to highlight the interconnections between these datasets. This document represents the first deliverable of Work Package 5, which is dedicated to project management. The work package focuses on ensuring effective project monitoring and developing the Open Science Roadmap.

**Fields of science and technology (from OECD classification)** 6.1 History and archaeology

**Language** eng

**Creation date** 2024-03-14

**Last modification date** 2025-05-15

**License**

**Name** Creative Commons Attribution 4.0 International

**URL** http://spdx.org/licenses/CC-BY-4.0.json

**Associated documents (publications, reports, patents, experimental plan...), website**

* MOBILITH blog_Carnet Hypotheses : https://mobilith.hypotheses.org/

## Project Details
**Project title**
Mobility and migration in Neolithic societies by the prism of apprenticeship networks. Lithic productions at the cusp to the Vth millennium BC

**Acronym**
MOBILITH

**Abstract**
The MOBILITH project is based on the study of lithic industries from the first agro-pastoral communities in continental Europe (5250 to 4750 BCE). In this spatio-temporal framework, the LBK was fragmented into a mosaic of cultural entities. Four key areas located in Belgium, the Netherlands, Germany and the Czech Republic have been selected, because they reflect distinct cultural trajectories. The analysis will focus on the reconstruction of learning networks and the circulation of raw material networks. By modelling the evolution of these networks based on a demographic approach and Social Network Analysis (SNA), the aim will be to understand the nature and impact of mobility on the cultural trajectories perceived by archaeologists. This 42-month project is structured around a combination of original study methods, the scope of which is fully in line with the objectives of the ANR's Axis D.06 (Studies of the past, heritage, cultures). In particular, the diachronic perspective adopted will shed new light on cultural evolution through the prism of an archaeology of the transmission of technical know-how.

**Funding**

* Agence Nationale de la Recherche :

* French National Research Agency : ANR-24-CE27-1795

**Start date**
2025-01-01

**End date**
2028-07-01

**Partners**

* Centre national de la recherche scientifique
  https://ror.org/02feahw73

* Technologie et Ethnologie des Mondes Préhistoriques

**Research outputs :**

1. Datasets for the lithic study in Key Area 1 (Dataset)

2. Datasets for the lithic study in Key Area 2 - Saxony (Dataset)

3. Datasets for the lithic study in Key Area 3 - Bavaria (Dataset)

4. Datasets for the lithic study in Key Area 4 (Dataset)

5. Results of the Experimentation (Dataset)

6. Social Network Analysis WP3 (Dataset)

7. Demography analysis WP3 (Dataset)

**Contributors**

<table><thead><tr><td>Name</td><td>Affiliation</td><td>Roles</td></tr></thead><tbody><tr><td>Allard Pierre -<br>https://orcid.org/0000-0001-8775-1656</td><td>CNRS, UMR<br>8068 TEMPS</td><td><ul><li>Contact Person (Expe WP1)</li><li>Data Collector (Expe WP1, Datasets KA1, Datasets KA1)</li><li>Data Curator (Expe WP1, Datasets KA3, Datasets KA2, Datasets KA4, Datasets KA1, Expe WP1)</li></ul></td></tr></tbody></table>
<table><tr><td></td><td></td><td><ul><li>Data Manager (Expe_WP1)</li><li>Researcher (Expe_WP1)</li></ul></td></tr><tr><td>Bauer Lisa -<br><a href="https://orcid.org/0009-0009-1319-4901">https://orcid.org/0009-0009-1319-4901</a></td><td>UMR8068 -<br><a href="https://orcid.org/0009-202224230W">202224230W</a></td><td><ul><li>Contact Person (Datasets KA3, Datasets KA2)</li><li>Data Collector (Datasets KA2, Datasets KA3, Expe_WP1, SNA, Datasets KA3, Datasets KA2, Datasets KA2)</li><li>Data Curator (Datasets KA2, Datasets KA2, Datasets KA3, Datasets KA3, Expe_WP1, Expe_WP1, Datasets KA4, Datasets KA1)</li><li>Data Manager (Datasets KA2, Datasets KA2, Datasets KA3, Datasets KA3, Datasets KA3, Expe_WP1)</li></ul></td></tr><tr><td>Beillard Victor</td><td>CNRS, UAR<br>3225</td><td><ul><li>Other (Datasets KA3, Datasets KA1, Expe_WP1, SNA, Demography, Datasets KA4, Datasets KA2)</li></ul></td></tr><tr><td>DENIS Solène -<br><a href="https://orcid.org/0000-0001-7986-217X">https://orcid.org/0000-0001-7986-217X</a></td><td>Technologie et<br>Ethnologie des<br>Mondes<br>PréhistoriqueS -<br><a href="https://orcid.org/0000-202224230W">202224230W</a></td><td><ul><li>(Datasets KA4)</li><li>Contact Person (Datasets KA4)</li><li>Data Collector (Datasets KA1, Expe_WP1, Datasets KA4, Datasets KA1)</li><li>Data Curator (Datasets KA1, Datasets KA4, Datasets KA3, Expe_WP1, Datasets KA2, Expe_WP1, Expe_WP1)</li><li>Data Manager (Expe_WP1)</li><li>Data contact (Datasets KA1)</li><li>Project Coordinator (Datasets KA1, Datasets KA1, Datasets KA1, Datasets KA4, Datasets KA4, Datasets KA2, Datasets KA3, Expe_WP1, SNA, SNA, Datasets KA1, Datasets KA4, Expe_WP1, SNA, Demography)</li><li>Project coordinator</li></ul></td></tr><tr><td>Hilpert Johanna</td><td>Cologne<br>University</td><td><ul><li>Contact Person (Demography)</li><li>Data Collector (SNA)</li><li>Data Manager (SNA, SNA)</li><li>Researcher (SNA, SNA, Demography, Demography)</li></ul></td></tr><tr><td>Le Tellier-Becquart<br>Nathalie - 0000-0003-0880-7194</td><td>CNRS -<br><a href="https://orcid.org/0000-202224230W">202224230W</a></td><td><ul><li>DMP Manager (Datasets KA2, Datasets KA2, Datasets KA3, Datasets KA3)</li><li>DMP manager</li><li>Data Manager (Datasets KA1, Datasets KA4, Datasets KA2)</li></ul></td></tr><tr><td>Montagne-Borras<br>Aurélie</td><td>CNRS, UAR<br>3225</td><td><ul><li>Other (SNA, Demography, Expe_WP1, Datasets KA1, Datasets KA2, Datasets KA3, Datasets KA4)</li></ul></td></tr></table>
Budget

<table><thead><tr><td>Cost type (Title)</td><td>Amount</td><td>Lifecycle stage</td></tr></thead><tbody><tr><td>Personnel cost (Post-doc position)</td><td>60000 EUR</td><td>Data collection/production associated costs - SNA</td></tr><tr><td>Personnel cost (PhD)</td><td>68998 EUR</td><td>Data collection/production associated costs - Datasets KA3</td></tr><tr><td>Personnel cost (Post-doc position)</td><td>60000 EUR</td><td>Data collection/production associated costs - Demography</td></tr><tr><td>Personnel cost (PhD)</td><td>68999 EUR</td><td>Data collection/production associated costs - Datasets KA2</td></tr></tbody></table>
"Mobility and migration in Neolithic societies by the prism of apprenticeship networks. Lithic productions at the cusp to the Vth millennium BC" project DMP

Datasets for the lithic study in Key Area 1

Data description and collection or re-use of existing data

Research output description

Name Datasets for the lithic study in Key Area 1

Description This dataset will be created to record the lithic technology characteristics of LBK and post-LBK sites from Belgium, the Netherlands, and the German Rhineland. It will consist of:

* **A spreadsheet** compiling all studied artifacts, where each row corresponds to a single piece or a batch of pieces. The columns will describe various observed variables, both quantitative and qualitative.

* **A series of photographs** taken at different scales (meso- and microscopic) to illustrate key technical scars.

* **A series of drawings** to visually represent the overall composition of the studied assemblages.

* **Textual** will potentially include reports of the recording, including a description of the assemblage, context of the site and reasoning for the assemblage being selected and R codes of the lithic analysis.

Persistent identifiers will be pursued so that the data can be reliably and efficiently located and referred
to. The dataset will be made available online on the **Nakala** platform.

As far as possible, we always favour open and standard formats to encourage data sharing and
re-use: spreadsheets in .csv or .txt format; photographs in .tif or .png formats; documents in .pdf
or .txt format.

Type Dataset

Workpackage WP2

Keywords

* lithic technology (Pactols)

* Hesbaye (Pactols lieux)

* Limbourg néerlandais (Pactols lieux)

* Rhénanie (Pactols lieux)

Keywords (free-text)

Language eng

May contain personal data? No

May contain sensible data? No

May take ethical issues into
account? Yes

Will existing data be reused?
**Justification**

The dataset will consist of two types of data:

1. **New data** from sites where no detailed technological studies have been conducted.

2. ** Reused data from research conducted during the PhD and postdoctoral projects of Solène Denis. These data may be supplemented with additional variables when necessary. The reused data have already been made available online as Supplementary Material: https://doi.org/10.1515/opar-2020-0180.**

** Reused data**

* Neolithization Processes of East Belgium: Supra-Regional Relationships Between Groups Highlighted by Technological Analysis of Lithic Industry : https://doi.org/10.1515/opar-2020-0180

**How new data will be collected or produced?**

**Name of the method**

Lithic Technology

**Description**

The method is based on a technological analysis of lithic industries, aiming to reconstruct the production process chains (*chaîne opératoire*). It incorporates various complementary types of sorting, categorised by raw material and production stage. Data recording is tailored to the quality of information provided by each piece. Finished products will undergo detailed analysis using approximately thirty criteria, while production waste will be documented in batches based on around ten criteria. The practical aspects of the study are adapted to the material's packaging (e.g., marking, storage in pits, by stratigraphic unit) and the study location (e.g., whether the material can be spread out for analysis).

The artefacts are observed with the naked eye or under the microscope if necessary for certain very specific aspects such as preparations for detachment. The pieces and specific elements are measured with an electronic calliper. They are counted and weighed. All the data are registered in an Excel spreadsheet.

Technical scars are described and interpreted through comparisons with experimental data, which are extensively available in the **Technothèque** of UMR 8068.

**Data Nature**

Observational data

**Equipments, technical platforms used**

* Technothèque of the UMR 8068 lab : https://teknotek.pretech.cnrs.fr/s/fr/page/accueil

* Microscope numérique mobile Dino-Lite AM7915MZT : https://www.dino-litefrance.fr/produits/la-gamme/microscopes/universel/am7915mzt-microscope-numerique-usb-dino-lite/

**Documentation and data quality**

**What metadata and documentation (for example way of organising data) will accompany the data?**
<table><tr><td>Description</td><td><p>The data will be recorded and stored on the professional laptop of Solène Denis and Pierre Allard.</p><p><strong>Metadata</strong> standards of Dublin Core Metadata Terms (DCMT) will be used. The following <strong>metadata</strong> will be given for this dataset, in English:</p><ul><li>a <strong>lithic data dictionary</strong> will be associated with the spreadsheets for the key areas in order to unify the lithic databases. It will include descriptions of codes and the structuring of data as well as drawings for particular features.</li><li>for assemblages with specific documentation of elements and features a <strong>spreadsheet for documentation</strong> (images and drawings) will be produced</li><li>A <strong>readme file</strong> will be produced with specific informations about the process of recording and indications of specific aspects (differences in recording etc.)</li><li>A <strong>readme file</strong> will be produced within the "documentation" folder in order to document specific aspects and problems regarding the existing data for each site</li><li>a <strong>readme file</strong> will be produced within the "GIS" folder in order to document any custom changes of the data (modifications of points and polygons, addition of columns etc.).</li></ul><p><strong>Naming conventions</strong> of files will be as follows:</p><ul><li>spreadsheets for sites: "mobilit_h KA1_sitename YYYY-MM-DD"</li><li>a metadata sheet: "mobilit_h KA1_lithicdatadictionary YYYY-MM-DD"</li><li>images of finds: "mobilit_h KA1_sitename_ID picture_1"</li><li>drawings of finds: "mobilit_h KA1_sitename_ID drawing_1"</li></ul><p>The <strong>folder structure</strong> will be organized in order to be identifiable easily for each site. Versions of data will be archived with their respective date. The hierarchy of folders will be as follows:</p><ul><li>"KAx" (here "KA1")</li><li>"KA1_sites": Contains a spreadsheet with sites for this key area.</li><li>"KA1_CODE_sitename" (e.g., "KA1_BCC_Blicqu")</li><li>"Documentation" (raw data of reports, images, drawings, georeferenced data, readme files),</li><li>"Data" (containing data spreadsheets, readme files and lithic data dictionary)</li><li>"Images"</li><li>"Drawings"</li><li>"Analysis" (containing R codes and files, figures and sketches of refitting, readme file, etc.)</li><li>"GIS" (containing modified shapefiles for each site, on the basis of the raw data, but customized to the research questions, as well as a readme file)</li></ul></td></tr><tr><td>Metadata/data standards</td><td><ul><li>Dublin Core: https://rdamsc.bath.ac.uk/api2/m15</li></ul></td></tr><tr><td>Metadata language code</td><td>eng</td></tr><tr><td>Documentation software</td><td></td></tr></table>

## What methods will be used to ensure their scientific quality?

<table><tr><td>Description</td><td><p><strong>Data cleaning:</strong> The database will be cleaned with free software, e.g., OpenRefine.</p><p><strong>Peer review of data:</strong> The data will be cross-tested by the lithic research group (Pierre Allard, Lisa Bauer, Solène Denis).</p><p><strong>Data entry validation:</strong> The validation of data will be ensured by using a customized database (in MS Access) with the pre-defined structure of data entries. This can easily be exported as various spreadsheet formats.</p><p><strong>Representation with controlled vocabularies:</strong> This will be achieved by recording in the database and the lithic dictionary file.</p></td></tr></table>

## Legal and ethical requirements, codes of conduct
## How will other legal issues, such as intellectual property rights and ownership, be managed? What legislation is applicable?

<table><tr><td>Description</td><td>The project data are public archives within the meaning of the Code du patrimoine, article L211-4. This status was reiterated by the directive issued by CNRS and Archives de France in 2007 (Instruction No. DAF/DPACI/RES/2007/002 of January 15, 2007. Traitement et conservation des archives des délégations du CNRS et des archives des unités de recherche et de service). Public archives are freely accessible, except for information subject to communication deadlines defined by the Code du patrimoine, in article L.213-2.<br/>The disclosure, reuse and dissemination of public archives that qualify as a work of the mind, as defined by the Code de la propriété intellectuelle, are regulated by the same code. Researchers and teacher-researchers, as public servants, retain their intellectual property rights (article L.111-1 of the Code de la propriété intellectuelle).</td></tr></table>

## What ethical issues and codes of conduct are there, and how will they be taken into account?

<table><tr><td>Description</td><td>The Code de la recherche establishes a link between scientific integrity and the preservation of scientific data, in accordance with the Code du patrimoine. In the long term, the archives department of the MSH Mondes will be responsible for the preservation and regulatory communication of the data, in line with the provisions set out in both codes.</td></tr></table>

## Data processing and analysis

### How and with what resources will the data be processed / analyzed?
<table><thead><tr><th>Description</th><th></th></tr></thead><tbody><tr><td>Data processing will be carried out primarily in RStudio, using tailored R scripts for the analysis of lithic technology variables. The dataset will first be compiled in .csv format, with each row representing either an individual artifact or a homogeneous batch. Quantitative variables (e.g., dimensions, weight, scar counts) and qualitative descriptors (e.g., raw material, typology, percussion technique) will be encoded following standardized taxonomies to ensure consistency and interoperability.<br>Processing will follow a structured pipeline:<br>1. <strong>Data Cleaning and Standardisation:</strong> Raw data from spreadsheets will be cleaned (e.g., correction of entry errors, removal of duplicates, standardisation of terminology) and formatted for analysis in R. Descriptive labels will be harmonised using controlled vocabularies.<br>2. <strong>Exploratory and Descriptive Analysis:</strong> Statistical summaries (e.g., distributions, central tendencies, variance measures) will be computed to describe key characteristics of the lithic assemblages. Batch-level and individual-level data will be treated separately where relevant.<br>3. <strong>Technological Categorisation:</strong> Based on chaîne opératoire approach, artefacts will be classified into production stages.<br>4. <strong>Visual Data Integration:</strong> Photographs and drawings will be linked to analytical records through persistent identifiers and file-naming conventions. Images will be processed in standard formats (.tif, .png), and metadata (e.g., scale, object ID, context) will be embedded or referenced in associated documentation.<br>5. <strong>Comparative and Interpretative Analysis:</strong> Descriptive data will be interpreted in relation to experimental reference collections (Technothèque UMR 8068). Comparative procedures will use qualitative pattern recognition as well as quantitative clustering methods where applicable.<br>6. <strong>Reproducibility and Sharing:</strong> All R scripts used for data processing and analysis will be documented and deposited alongside the dataset. The full protocol, including criteria definitions, classification logic, and variable descriptions, will be included in the metadata_lithicdatadictionary. Upon publication of the KA 1 results, the dataset, metadata, and code will be deposited on Nakala, ensuring persistent access.</td></tr></tbody></table>

## Storage and backup during the research process

### How will data be stored and backed up during the research?

<table><thead><tr><th>Storage needs</th><th></th></tr></thead><tbody><tr><td>During the project, data will be stored and backed up in multiple secure environments to ensure both accessibility and protection against loss:<ul><li><strong>Primary Storage:</strong> Data will be stored on the professional, institutionally managed computer of Solène Denis, with access restricted to authorized project personnel.</li><li><strong>Secondary Backup:</strong> A monthly backup of project data will be saved to a dedicated external hard drive maintained by the project team.</li></ul>The project's shared workspace on RESANA (a secure platform provided by the French Direction Interministérielle du Numérique - DINUM) will serve as an additional storage and collaboration space. Résana hosts data on nationally managed secured servers, ensuring institutional compliance and reliability.<br>A ShareDoc (CNRS IN2P3) project-specific file manager for MOBILITH will be set up, with weekly backups, providing robust redundancy and automated version control.<br>The use of at least three independent storage spaces - local, institutional online, and external managed backup - ensures the ability to recover data in the event of hardware failure, accidental deletion, or other incidents. In case of data loss or corruption, the most recent backup from ShareDoc or the external drive will be restored, with coordination from institutional IT support if needed.<br>Access to project data during the research phase will be restricted to MOBILITH project members and designated external experts. Controlled access is managed through institutional credentials for Résana and ShareDoc platforms. FileSender, the institutional secure file transfer service, will be used for any sensitive file exchanges between partners, ensuring encrypted transmission.<br>While the project does not involve highly sensitive personal data, appropriate data protection measures will be observed. In cases where potentially sensitive information is handled (e.g., site
locations or unpublished archaeological findings), access will be limited, and data will be pseudonymized or aggregated as appropriate.

Data management and protection practices will comply with institutional and national policies, in alignment with GDPR and best practices for handling research data securely.

Perennial archiving costs are covered by the MSH Mondes archive service (CNRS servers) and, for definitive archiving, by the French National Archives and the Centre informatique national de l'enseignement supérieur (CINES), under the supervision of the Ministry of Higher Education.

The cost of storing and sharing the data that will be made public will be borne by the institutions for which the project participants work (data on portable PCs, by the IR* Huma-Num (storage on Sharedocs and dissemination via the SHS Nakala data warehouse), under the supervision of the CNRS, Aix Marseille University and the Condorcet campus, by the French government's Direction du Numérique (document sharing via the Resana collaborative platform), by CERN for the Zenodo generalist warehouse, and by the Centre de la Communication Scientifique Directe (CCSD) under the supervision of CNRS, INRIA and INRAE for the distribution of open access publications.

Processing will be carried out by those responsible for the research products, using tools already funded by the institutions (e.g. Excel) or free open-source tools such as OpenRefine and Calc, or QGIS.

**Estimated volume of data**

20

**Unit**

GB

**Measures taken for data security**

Data security will be ensured through a combination of physical, digital, and procedural safeguards. All digital data will be stored on secure, institutionally managed servers with regular automated backups and controlled access based on user roles (see below). Sensitive or unpublished data will be protected by password-restricted folders, and encryption will be used when transferring data between devices or collaborators.

**Resana :**

Resana is hosted in Outscale's SecNumCloud 3DS in data centres in France. The operator is responsible for the availability of the service and for maintaining it in operational and security condition. The integrity and confidentiality of the information circulating are ensured by encryption mechanisms (HTTPS protocol). RESANA is not considered a "critical" service, in the sense of continuity of government action. In nominal mode, the service is available 24/7/365. However, it may be interrupted in the event of a technical incident or maintenance operation. DINUM aims to guarantee a maximum downtime of 4 hours and a maximum data loss time of 24 hours. RESANA is an information system that has been security-approved (RGS) by the qualified authority (Interministerial Digital Directorate) for the sharing of standard data. The information system takes into account the needs of confidentiality, integrity and availability of the service. All content uploaded to the platform is encrypted (AES 128 bit) and hosted on the Outscale SecNumCloud 3DS with 24/7 facilities management. However, its use is not authorised to convey sensitive information or information marked "Restricted Distribution", in accordance with II901 (NOR: PRMD1503279J).

Cf : https://resana.numerique.gouv.fr/public/utilisateur/afficherPageConnexionAnnexe?page=apropos

**Sharedocs :**

ShareDocs is a file manager implemented by IR* Huma-Num, on its own servers, which can be used via a web browser, a WebDAV client or file synchronisation software. The platform is based on the FileRun application. It provides remote online storage on the French research network (similar to tools such as DropBox, which are hosted on the public cloud). Hosted data can be easily encrypted using tools such as ZED encrypt.

ShareDocs is designed for research projects that want to store, exchange, share and work on file-type data (sets of photos, transcribed texts, etc.). For example, ShareDocs can be used to prepare files for online publishing or for distribution in NAKALA.

A ShareDocs project account facilitates data sharing and collaborative work between several members of a project or research team in the social sciences and humanities. The project account is adapted to collaboration via collaborative editing and file versioning tools, as the project account is accessible to several members of a team (unlike an individual account). It allows the creation of a tree structure of folders and it is necessary to define access and editing rights in detail, as soon as they have been created and for a list of identified collaborators. The principle is to create a folder and file tree when a project account is opened, and then to grant different access and editing rights depending on the role of each team member.

For the 2023-2025 forecasts, the volume of a project account is 300 GB of storage.

A project account can only be accessed by a list of people who have been declared and registered with Huma-Num by the project account manager.

The data stored on Sharedocs is hosted and backed up at the IN2P3 computing centre in Lyon, on Huma-Num servers. In the event of data loss, Huma-Num assures us that it will be possible to contact their helpdesk to recover it, via one of its backups.

https://documentation.huma-num.fr/sharedocs-stockage/

**Nakala :**

The data deposited in NAKALA is stored on servers managed by Huma-Num and hosted at the
IN2P3 computing centre. This centre was set up to manage data produced in particle physics, nuclear physics and astroparticle physics.

This major national centre is secure from a hardware point of view (e.g. redundant power
supply, network devices, cooling systems).

NAKALA data is stored on a NAS-type network storage device. A snapshot of the data is taken at regular intervals, enabling data to be restored quickly in the event of problems. In addition, a tape backup is made daily on the CCIN2P3 backup robot using TSM software published by IBM. NAKALA's metadata are stored in a SQL database (MariaDB) which is backed up daily on Huma-Num's infrastructure. The metadata is also exposed in RDF format via a Triple-Store (GraphDB) which is also backed up daily on the Huma-Num infrastructure. Continuity of the NAKALA¶ service

The NAKALA service is hosted on the Huma-Num infrastructure, which has a general disaster
recovery plan. More specifically, the redundancy of the NAKALA service is ensured by :

- the NAKALA application is redundant on two different machines using a distribution tool (HAProxy), which avoids service interruptions in the event of a breakdown;

- the data is stored on a NAS-type device, so that data can be restored quickly. In addition, backups are made on magnetic tapes on a daily basis;

- Metadata is stored in a 'classic' relational database, which is backed up daily. This metadata is also stored in RDF format in a Triple-Store, which is backed up daily.

Source : https://documentation.huma-num.fr/nakala-faq/#comment-sont-sauvegardees-les-donnees

PAC CINES :

The long-term archiving platform at CINES - PAC v3.0 has been in production since 2008.
Capacity: 300 TB on 2 DELL storage bays of 150 TB each.

Arcsys archiving software (Infotel), Redundant virtualised architecture with 2 PowerEdge R730 hypervisors, 2 IBM TS-3500 tape libraries, with LTO4 and JAGUAR drives (use adapted to requirements), 1 Fiber chanel interconnection network. cf https://www.cines.fr/ressources/

Data sharing and long-term preservation

How will data be shared?
## Modalities of sharing

The data will be stored in open and widely used formats to promote interoperability and sustainability. If any proprietary or non-standard formats are required due to specific research tools or instruments, a corresponding open version or export (when possible) will also be provided.

The CC-BY licensed datasets will be stored in the Nakala repository for the humanities and social sciences and will be assigned a persistent identifier (Datacite Digital Object Identifier). The Nakala data repository is managed by the French research infrastructure IR* Huma-Num, under the supervision of the French National Centre for Scientific Research, Aix-Marseille University and the Condorcet Campus.

The Dublin Core metadata Terms Vocabulary (ISO 15836) that must be entered in Nakala includes the type of data, the title, the author(s), the creation date and the licence associated with the dataset. It is possible to add additional metadata (qualified Dublin Core). Keywords (filled in using the PACTOLS interoperable multilingual thesaurus for Archaeology), language and a description of each dataset will be filled in. A readme file will be associated with each dataset deposited in the Nakala repository. The datasets will be "harvested" by the Isidore search engine and OpenAire Explore, and thus easily findable and accessible.

All datasets will be made available under a **Creative Commons Attribution (CC BY)** license, allowing broad reuse with appropriate credit. In cases involving sensitive or restricted data (e.g., personal data requiring anonymization), access may be restricted to specific user groups or require a data sharing agreement. Measures will be taken to minimize restrictions, including data anonymization and the provision of aggregated or de-identified versions where applicable.

Data will be made available within a reasonably short period after the conclusion of the project, or at the time of any related publication, whichever comes first. This allows time for quality assurance, documentation, and the preparation of metadata.

The datasets will be particularly relevant to researchers focusing on lithic technology in Central Europe. The data may be used for comparative analyses, technological studies and regional syntheses, but also for developing and testing methodological frameworks in lithic analysis.

## Reusability

The data produced during this project can be reused in future research to support further analysis, validation, or new investigations.

## Data repository/catalogs

* Nakala: https://cat.opidor.fr/index.php/Nakala (CoSO)

## How will data be long-term preserved? Which data?

## Justification

The long-term preservation of the lithic technology dataset is essential due to its scientific, cultural, and methodological value. First, the dataset documents unique prehistoric technological traditions across Belgium, the Netherlands, and the German Rhineland, offering a valuable reference for future archaeological, anthropological, and heritage research. Given the irreversible nature of excavation and the potential inaccessibility of physical collections over time (due to curation limitations or degradation), the digital dataset serves as a crucial record of primary observations.

Moreover, the dataset is structured to support **comparative studies**, including re-analysis and replication of chaîne opératoire-based research. Preserving it ensures that future scholars can engage with the material using updated methods or in light of new discoveries. The use of open, standard formats (.csv, .tif, .txt) and rich metadata makes it interoperable and suitable for reuse across disciplines and platforms.

Finally, as archaeological research is increasingly data-driven, long-term preservation supports transparency, reproducibility, and open science. It aligns with international best practices in data stewardship and fulfills ethical obligations to safeguard irreplaceable scientific information for future generations.

The precise data selection and archiving process will be developed in close collaboration with the archives department of MSH Mondes.

In accordance with the Code of Heritage, the archives produced by the UMRs within the scope of UAR3225 are managed by the archives department of MSH Mondes. At the end of the research project, the documents and data produced will be transferred to the archives department. Indeed, the department is responsible for managing the public, administrative, and scientific archives of the units at MSH Mondes, from their production (current archives) throughout their entire conservation period after transfer (intermediate archives), regardless of their format (textual, graphic, photographic documents, etc.) and their medium (physical documents, electronic documents) (address: https://www.mshmondes.cnrs.fr/accompagnement/archives).

Once transferred, these data are classified, described, and inventoried. The inventory is published online (address: https://archives.mshmondes.cnrs.fr), and the archives are accessible to anyone who requests them, in compliance with the rules set out in the Code of Heritage and
the Code of Intellectual Property.

A selection and, if necessary, regulatory destruction of the archives are carried out based on their administrative usefulness and scientific interest, with the approval of the Interministerial Archives Service of France (SIAF).

These operations are governed by a management table established in line with administrative and scientific needs. Finally, according to a schedule defined in agreement with the National Archives and the needs of the research, the project archives will, ultimately, be transferred to the National Archives for permanent conservation.

Extract of the Archive Department's management table :

<table><thead><tr><th>Activités et documents</th><th>DUA</th><th>Sort final</th><th>Observations</th></tr></thead><tbody><tr><td><strong>1. Direction d'équipe</strong></td><td></td><td></td><td></td></tr><tr><td><strong>1.1. Réunions internes et séminaires</strong><br>Ordre du jour, compte rendu de réunion et documents afférents, programme, support de présentation (texte, slide, vidéo...).</td><td>10 ans</td><td>C</td><td></td></tr><tr><td><strong>1.2. Suivi de l'activité des membres</strong><br>Dossier de membre (projet scientifique, rapport, attestation, demande de bourse), note interne.</td><td>10 ans</td><td>C</td><td></td></tr><tr><td><strong>2. Recherche</strong></td><td></td><td></td><td></td></tr><tr><td><strong>2.1. Programme/projet</strong> Le programme/projet peut être financé par des organismes extérieurs à l'unité (ANR, Labex, ministère des Affaires étrangères...) ou ne pas être financé. Le programme/projet génère des documents/données issus des activités scientifiques listées en 3.2-3.10.</td><td></td><td></td><td>Le programme/projet peut être financé par des organismes extérieurs à l'unité (ANR, Labex, ministère des Affaires étrangères...) ou ne pas être financé. Le programme/projet génère des documents/données issus des activités scientifiques listées en 3.2-3.10.</td></tr><tr><td><strong>2.1.1. Direction et gestion</strong></td><td></td><td></td><td></td></tr><tr><td><strong>Direction des activités</strong><br>Appel d'offres, appel à projet, texte de projet, dossier de candidature (accepté ou refusé), rapport d'activité, versions préliminaires (dossier de candidature, rapport), contrat de recherche, convention de collaboration, protocole d'accord, charte de sécurité, autorisation, permis, programme de travail, note d'information, plan de gestion de données, planning, agenda, lettre, courriel.</td><td>Durée du projet scientifique + 5 ans</td><td>T</td><td>Détruire les versions préliminaires (rapport, projet). Conserver les courriels les plus significatifs.</td></tr></tbody></table>
<table><tr><td>Gestion financière</td><td></td><td></td><td></td></tr><tr><td>Gestion par le responsable de projet</td><td></td><td></td><td></td></tr><tr><td>Budget prévisionnel, budget réalisé, notification de crédits, facture, justificatif de dépenses, bilan des dépenses, relevé de compte, attestation, lettre, courriel.</td><td>10 ans</td><td>D</td><td>C'est le cas par exemple des missions archéologiques françaises à l'étranger. Les budgets et les bilans de dépenses sont éliminés car ils figurent dans les rapports.</td></tr><tr><td>Gestion par l'unité ou une autre institution</td><td></td><td></td><td></td></tr><tr><td>Budget prévisionnel, budget réalisé, notification de crédits, facture, justificatif de dépenses, bilan des dépenses, relevé de compte, attestation, courriel.</td><td>Validité</td><td>D</td><td>Les documents sont des copies. Les documents originaux sont archivés par la cellule gestion financière de l'unité ou de l'institution.</td></tr><tr><td>Gestion des personnels (CDD, stagiaires)</td><td></td><td></td><td></td></tr><tr><td>Gestion par le responsable de projet</td><td></td><td></td><td></td></tr><tr><td>CV, lettre de motivation, bulletin d'inscription, attestation, convention de stage (copie), demande et ordre de mission (copie), demande de visa (copie), document relatif aux assurances (copie), courriel.</td><td>10 ans</td><td>D</td><td></td></tr><tr><td>Gestion par l'unité ou autre institution</td><td></td><td></td><td></td></tr><tr><td>CV, lettre de motivation, contrat (copie), convention de stage (copie), documents relatifs aux missions (copies), courriel.</td><td>Validité</td><td>D</td><td>Les documents sont des copies. Les documents originaux sont archivés par la cellule gestion financière de l'unité ou de l'institution.</td></tr><tr><td>Gestion de locaux, d'équipement</td><td></td><td></td><td></td></tr><tr><td>Inventaire d'équipement, documents d'organisation de la vie quotidienne, documentation technique, documents relatifs à la gestion et à l'entretien de véhicule, documents relatifs à la location de locaux.</td><td>10 ans</td><td>T</td><td>Cette rubrique concerne par exemple les missions archéologiques françaises à l'étranger. Détruire les documents relatifs à la gestion et à l'entretien de véhicule et la documentation technique. Conserver les inventaires d'équipement et les documents d'organisation de la vie quotidienne.</td></tr><tr><td>2.1.2. Participation (documents de gestion)</td><td></td><td></td><td></td></tr><tr><td>Texte de projet, rapport, programme de travail, notes, courriel.</td><td>Durée du projet scientifique + 5 ans</td><td>T</td><td>Les tri porte sur les notes et les courriels : conserver selon l'intérêt.</td></tr></table>
<table><tr><td>2.1.3. Réunions scientifiques internes (équipe projet, partenaires)</td><td>Durée du projet scientifique + 5 ans</td><td>C</td><td>Il s'agit de tout type de données (issues de fouilles archéologiques, d'une enquête sociologique, historique, géographique...) quelles que soient leurs formes (textes, images, sons...) et leurs supports. Lorsqu'il y a obligation de gestion des archives intermédiaires au sein d'un autre service, les documents/données ne sont pas pris en compte (par exemple, pour l'archéologie, les services régionaux de l'archéologie, l'Ecole française d'Athènes...). Conserver la version achevée des documents. Certaines versions préparatoires peuvent être conservées en fonction de l'expertise du chercheur. Conserver les masters en format compressé ; détruire les rushes et les masters en format non compressé.</td></tr><tr><td>2.2. Collecte et analyse de documents/données</td><td>Durée du projet scientifique + 5 ans</td><td>T</td><td>Il s'agit de tout type de données (issues de fouilles archéologiques, d'une enquête sociologique, historique, géographique...) quelles que soient leurs formes (textes, images, sons...) et leurs supports. Lorsqu'il y a obligation de gestion des archives intermédiaires au sein d'un autre service, les documents/données ne sont pas pris en compte (par exemple, pour l'archéologie, les services régionaux de l'archéologie, l'Ecole française d'Athènes...). Conserver la version achevée des documents. Certaines versions préparatoires peuvent être conservées en fonction de l'expertise du chercheur. Conserver les masters en format compressé ; détruire les rushes et les masters en format non compressé.</td></tr><tr><td>2.3. Préparation de publication (ouvrages, article, compte rendu...)</td><td>Durée de la préparation + 5 ans</td><td>T</td><td>Le tri porte principalement sur les textes préliminaires et illustrations : conserver uniquement la première version soumise. Détruire les épreuves. Documentation, courriel : conserver les documents les plus significatifs.</td></tr><tr><td>2.4. Congrès, colloque, journée d'étude (organisation ou participation)</td><td>10 ans</td><td>T</td><td>Le tri porte principalement sur les textes préliminaires et illustrations : conserver uniquement la première version soumise. Détruire les épreuves. Documentation, lettres, courriels : conserver les documents les plus significatifs. Détruire les copies de documents financiers et de missions.</td></tr><tr><td>2.5. Sites Web (carnets de recherche, blogs...)</td><td>Validité</td><td>D</td><td>Depuis 2006, la BNF assurer le dépôt légal de l'internet français.</td></tr></table>
<table><tr><td>2.6. Documentation<br/>Photographies, dessins, cartes, enregistrements sonores, produit audiovisuel et multimédia, publications électroniques ou papier, rapport, notes de travail, notes de lecture, courriel, lettre, photothèque, collections de cartes, plans, dessins, collections de référence ou de comparaison (objet fabriqué), base de données.</td><td>Durée d'exploitation + 5 ans</td><td></td><td>Conserver les documents selon l'intérêt. Seule la version finale de la base de données sera conservée. Publications : conserver seulement les textes lorsqu'ils participent à la cohérence scientifique d'un dossier contenant d'autres documents.</td></tr><tr><td>2.7. Médiation scientifique<br/>(Exposition, conférence, atelier grand public, émission de radio, émission de télévision, produit pédagogique...) Produit audiovisuel et multimédia (film, vidéo...), podcast, site Web, support de communication (catalogue, livret, programme, affiche, slides de présentation, vidéo...), poster, rushes, master, autorisation, invitation, documentation, courriel, document financier et de mission (copies).</td><td>Durée du projet + 5 ans</td><td>T</td><td>Documentation, courriels : conserver les documents les plus significatifs. Détruire les copies de documents financiers et de missions. Conserver les masters en format compressé ; détruire les rushes et les masters en format non compressé. Les podcasts et sites Web ne sont pas pris en compte.</td></tr><tr><td>2.8. Correspondance<br/>boîte aux lettres électronique, lettre.</td><td>10 ans</td><td>T</td><td>Le tri porte sur les courriels : conserver les courriels et pièces jointes selon l'intérêt. Détruire les courriels privés.</td></tr><tr><td>2.9. Enseignement et formation<br/>2.9.1. Enseignement dispensé<br/>Programme, support de cours (texte/illustration, slide, vidéo...) et documents afférents, plaquette pédagogique, documentation, notes, lettre, courriel.</td><td>10 ans</td><td>T</td><td>Le tri porte sur la documentation, les notes, lettres et courriels : conserver selon l'intérêt.</td></tr><tr><td>2.9.2. Direction et suivi de travaux d'étudiants<br/>Travaux d'étudiants (thèses, mémoires), rapport (sur les mémoires et sur les soutenances), procès-verbal de soutenance, convocations, courriel, lettres, notes.</td><td>10 ans</td><td>T</td><td>Travaux d'étudiants : les thèses sont archivées par le CINES (Arrêté du 25 mai 2016 fixant le cadre national de la formation et les modalités conduisant à la délivrance du diplôme national de doctorat, titre IV, art. 24-25). Les mémoires (master 1 et 2) sont archivés par les universités. Toutefois, certains documents peuvent être versés en fonction de l'expertise du chercheur et de leur apport au fonds. D pour les autres documents qui sont gérés par les universités.</td></tr><tr><td>2.9.3. Accueil de chercheurs et de stagiaires<br/>Dossier de chercheur invité (candidature (copie), projet de recherche, attestation (copie), rapport scientifique, lettre,</td><td>10 ans</td><td>T</td><td>Conserver les documents scientifiques en fonction de l'expertise du chercheur. Détruire les candidatures, conventions, attestations,</td></tr></table>
courriel.

Dossier de stagiaire (convention de stage
(copie), rapport de stage).

lettres, courriels.

Estimated volume of data 5

Unit GB

Datasets for the lithic study in Key Area 2 - Saxony

Data description and collection or re-use of existing data

Research output description
<table><tr><td>Name</td><td>Datasets for the lithic study in Key Area 2 - Saxony</td></tr><tr><td>Description</td><td>This dataset will comprise documentation of the lithic analysis of Key Area 2 (Saxony, Germany). It will include:<ul><li><strong>Spreadsheets:</strong><ul><li>archaeological sites of the key area and the timeframe concerned with essential data data (location, chronology, publications)</li><li>recording of features and elements of the raw material analysis</li><li>recording of the technological analysis of pieces, either as single or group recording. The columns will describe various observed variables, both quantitative and qualitative.</li></ul></li><li><strong>Textual:</strong><ul><li>Reports of the recording including a description of the assemblage, context of the site and reasoning for the assemblage being selected.</li><li>R codes of the lithic analysis</li></ul></li><li><strong>Images:</strong> photographic documentation and/or drawings of lithic objects.</li></ul></td></tr><tr><td>Type</td><td>Dataset</td></tr><tr><td>Workpackage</td><td>WP2</td></tr><tr><td>Keywords</td><td><ul><li>lame (Pactols sujets)</li><li>débitage laminaire (Pactols sujets)</li><li>mode de production (Pactols sujets)</li><li>Saxe (Pactols lieux)</li><li>Néolithique (Pactols sujets)</li><li>technologie lithique (Pactols sujets)</li></ul></td></tr><tr><td>Keywords (free-text)</td><td></td></tr><tr><td>Language</td><td>eng</td></tr><tr><td>Issued Date</td><td></td></tr><tr><td>Persistent identifier</td><td></td></tr><tr><td>May contain personal data?</td><td>No</td></tr><tr><td>May contain sensible data?</td><td>No</td></tr><tr><td>May take ethical issues into account?</td><td>Yes</td></tr></table>

## Will existing data be reused?

**Justification**
The re-use of existing data may concern existing recordings of finds or data of sites. These are connected to licence constraints regarding their use.
This comprises:

* **Reports and documentation** of excavations, sites and archaeological objects

* **Georeferenced data** of sondages, features and/or objects

Their use will be agreed with the Saxony State Office for Archaeology (Landesamt für Archäologie Sachsen).

## How new data will be collected or produced?
<table><tr><td>Name of the method</td><td>Analysis of lithic technology</td></tr><tr><td>Description</td><td>The method is based on a technological analysis of lithic industries, aiming to reconstruct the production process chains (chaîne opératoire). It incorporates various complementary types of sorting, categorised by raw material and production stage. Data recording is tailored to the quality of information provided by each piece. Finished products will undergo detailed analysis using approximately thirty criteria, while production waste will be documented based on around ten criteria. The practical aspects of the study are adapted to the material's packaging (e.g., marking, storage in pits, by stratigraphic unit) and the study location (e.g., whether the material can be spread out for analysis).<br>The elements are observed with the naked eye or under the microscope if necessary for certain very specific aspects such as preparations for detachment. The pieces and specific elements are measured with an electronic calliper. The pieces are counted and weighed. All the data are registered in a database that will be exported to excel/ or text files (.csv or .txt).<br>Technical scars are described and interpreted through comparisons with experimental data, which are extensively available in the Technothèque of UMR 8068.</td></tr><tr><td>Data Nature</td><td>Observational data</td></tr><tr><td>Equipments, technical platforms used</td><td><ul><li>Dino-Lite AM7915MZTL : Microscope numérique USB : https://www.dino-litefrance.fr/produits/la-gamme/microscopes/longue-distance/am7915mztl-microscope-numérique-usb-dino-lite/</li><li>Technothèque of the UMR 8068 lab : https://teknotek.pretech.cnrs.fr/s/fr/page/accueil</li></ul></td></tr><tr><td>Costs</td><td><ul><li>Personnel cost : 68 999 EUR</li></ul></td></tr></table>

## Documentation and data quality

What metadata and documentation (for example way of organising data) will accompany the data?
<table><tr><td>Description</td><td><p><strong>The data</strong> will be recorded and stored on the professional laptop of Lisa Bauer.</p><p><strong>Metadata</strong> standards of Dublin Core Metadata Terms (DCMT) will be used. The following <strong>metadata</strong> will be given for this dataset:</p><ul><li>a <strong>lithic data dictionary</strong> will be associated with the spreadsheets for the key areas in order to unify the lithic databases. It will include descriptions of codes and the structuring of data as well as drawings for particular features.</li><li>for assemblages with specific documentation of elements and features, a <strong>spreadsheet for documentation</strong> (images and drawings) will be produced.</li><li>A <strong>readme file</strong> will be produced with specific informations about the process of recording and indications of specific aspects (differences in recording etc.).</li><li>A <strong>readme file</strong> will be produced within the "documentation" folder in order to document specific aspects and problems regarding the existing data for each site.</li><li>a <strong>readme file</strong> will be produced within the "GIS" folder in order to document any custom changes of the data (modifications of points and polygons, addition of columns etc.).</li></ul><p><strong>Naming conventions</strong> of files will be as follows:</p><ul><li>spreadsheets for sites: "mobilit_h_KA2_sitename_YYYY-MM-DD"</li><li>a metadata sheet: "mobilit_h_KA2_lithicdatadictionary_YYYY-MM-DD"</li><li>images of finds: "mobilit_h_KA2_sitename_ID-picture_1"</li><li>drawings of finds: "mobilit_h_KA2_sitename_ID-drawing_1"</li></ul><p>The <strong>folder structure</strong> will be organized in order to be identifiable easily for each site. Versions of data will be archived with their respective date. The hierarchy of folders will be as follows:</p><ul><li>"KAx" (here "KA2")</li><li>"KA2 sites": Contains a spreadsheet with sites for this key area.</li><li>"KA2_CODE_sitename" (e.g., "KA2_THK-01_Thekla")</li><li>"Documentation" (raw data of reports, images, drawings and georeferenced data if available, readme files),</li><li>"Data" (containing data spreadsheets, readme files and lithic data dictionary)</li><li>"Images"</li><li>"Drawings"</li><li>"Analysis" (containing R codes and files, figures and sketches of refitting, readme file, etc.)</li><li>"GIS" (containing modified shapefiles for each site, on the basis of the raw data, but customized to the research questions, as well as a readme file)</li></ul></td></tr><tr><td>Metadata/data standards</td><td><ul><li>Dublin Core: https://rdamsc.bath.ac.uk/api2/m15</li></ul></td></tr><tr><td>Metadata language code</td><td>eng</td></tr></table>

## What methods will be used to ensure their scientific quality?

<table><tr><td>Description</td><td><p><strong>Data cleaning:</strong> The database will be cleaned with free software, e.g., OpenRefine.</p><p><strong>Peer review of data:</strong> The data will be cross-tested by the lithic research group (Pierre Allard, Lisa Bauer, Solène Denis).</p><p><strong>Data entry validation:</strong> The validation of data will be ensured by using a customized database (in MS Access) with the pre-defined structure of data entries. This can easily be exported as various spreadsheet formats.</p><p><strong>Representation with controlled vocabularies:</strong> This will be achieved by recording in the database and the lithic dictionary file.</p></td></tr></table>

## Legal and ethical requirements, codes of conduct

How will other legal issues, such as intellectual property rights and ownership, be managed? What legislation is applicable?
<table><tr><td>Description</td><td>The project data are public archives within the meaning of the Code du patrimoine, article L211-4. This status was reiterated by the directive issued by CNRS and Archives de France in 2007 (Instruction No. DAF/DPACI/RES/2007/002 of January 15, 2007. Traitement et conservation des archives des délégations du CNRS et des archives des unités de recherche et de service). Public archives are freely accessible, except for information subject to communication deadlines defined by the Code du patrimoine, in article L.213-2.<br/>The disclosure, reuse, and dissemination of public archives that qualify as a work of the mind, as defined by the Code de la propriété intellectuelle, are regulated by the same code. Researchers and teacher-researchers, as public servants, retain their intellectual property rights (article L.111-1 of the Code de la propriété intellectuelle).</td></tr></table>

**What ethical issues and codes of conduct are there, and how will they be taken into account?**

<table><tr><td>Description</td><td>The Code de la recherche establishes a link between scientific integrity and the preservation of scientific data, in accordance with the Code du patrimoine. In the long term, the archives department of the MSH Mondes will be responsible for the preservation and regulatory communication of the data, in line with the provisions set out in both codes.</td></tr></table>

## Data processing and analysis

**How and with what resources will the data be processed / analyzed?**
<table><thead><tr><th>Description</th><th></th></tr></thead><tbody><tr><td></td><td>Data processing will be carried out primarily in RStudio, using tailored R scripts for the analysis of lithic technology variables. The dataset will first be compiled in .csv format, with each row representing either an individual artifact or a homogeneous batch. Quantitative variables (e.g., dimensions, weight, scar counts) and qualitative descriptors (e.g., raw material, typology, percussion technique) will be encoded following standardized taxonomies to ensure consistency and interoperability.<br>Processing will follow a structured pipeline:<ol><li><strong>Data Cleaning and Standardisation:</strong> Raw data from spreadsheets will be cleaned (e.g., correction of entry errors, removal of duplicates, standardisation of terminology) and formatted for analysis in R. Descriptive labels will be harmonised using controlled vocabularies.</li><li><strong>Exploratory and Descriptive Analysis:</strong> Statistical summaries (e.g., distributions, central tendencies, variance measures) will be computed to describe key characteristics of the lithic assemblages. Batch-level and individual-level data will be treated separately where relevant.</li><li><strong>Technological Categorisation:</strong> Based on the chaîne opératoire approach, artefacts will be classified into production stages.</li><li><strong>Visual Data Integration:</strong> Photographs and drawings will be linked to analytical records through persistent identifiers and file-naming conventions. Images will be processed in standard formats (.tif, .png), and metadata (e.g., scale, object ID, context) will be embedded or referenced in associated documentation.</li><li><strong>Comparative and Interpretative Analysis:</strong> Descriptive data will be interpreted in relation to experimental reference collections (Technothèque UMR 8068). Comparative procedures will use qualitative pattern recognition as well as quantitative clustering methods where applicable.</li><li><strong>Reproducibility and Sharing:</strong> All R scripts used for data processing and analysis will be documented and deposited alongside the dataset. The full protocol, including criteria definitions, classification logic, and variable descriptions, will be included in the metadata_lithicdatadictionary. Upon publication of the KA 2 results, the dataset, metadata, and code will be deposited on Nakala, ensuring persistent access.</li></ol></td></tr></tbody></table>

## Storage and backup during the research process

### How will data be stored and backed up during the research?

<table><thead><tr><th>Storage needs</th><th></th></tr></thead><tbody><tr><td>During the project, data will be stored and backed up in multiple secure environments to ensure both accessibility and protection against loss:<ul><li><strong>Primary Storage:</strong> Data will be stored on the professional, institutionally managed computer of Lisa Bauer, with access restricted to authorized project personnel.</li><li><strong>Secondary Backup:</strong> A monthly backup of project data will be saved to a dedicated external hard drive maintained by the project team.</li></ul>The project's shared workspace on RESANA (a secure platform provided by the French Direction Interministérielle du Numérique - DINUM) will serve as an additional storage and collaboration space. Résana hosts data on nationally managed secured servers, ensuring institutional compliance and reliability.<br>A ShareDoc (CNRS IN2P3) project-specific file manager for MOBILITH will be set up, with weekly backups, providing robust redundancy and automated version control.<br>The use of at least three independent storage spaces - local, institutional online, and external managed backup - ensures the ability to recover data in the event of hardware failure, accidental deletion, or other incidents. In case of data loss or corruption, the most recent backup from ShareDoc or the external drive will be restored, with coordination from institutional IT support if needed.<br>Access to project data during the research phase will be restricted to MOBILITH project members and designated external experts. Controlled access is managed through institutional</td><td></td></tr></tbody></table>
credentials for Résana and ShareDoc platforms. FileSender, the institutional secure file transfer service, will be used for any sensitive file exchanges between partners, ensuring encrypted transmission.

While the project does not involve highly sensitive personal data, appropriate data protection measures will be observed. In cases where potentially sensitive information is handled (e.g., site locations or unpublished archaeological findings), access will be limited, and data will be pseudonymized or aggregated as appropriate.

Data management and protection practices will comply with institutional and national policies, in alignment with GDPR and best practices for handling research data securely.

Perennial archiving costs are covered by the MSH Mondes archive service (CNRS servers) and, for definitive archiving, by the French National Archives and the Centre informatique national de l'enseignement supérieur (CINES), under the supervision of the Ministry of Higher Education.

The cost of storing and sharing the data that will be made public will be borne by the institutions for which the project participants work (data on portable PCs, by the IR* Huma-Num (storage on Sharedocs and dissemination via the SHS Nakala data warehouse), under the supervision of the CNRS, Aix Marseille University and the Condorcet campus, by the French government's Direction du Numérique (document sharing via the Resana collaborative platform), by CERN for the Zenodo generalist warehouse, and by the Centre de la Communication Scientifique Directe (CCSD) under the supervision of CNRS, INRIA and INRAE for the distribution of open access publications.

Processing will be carried out by those responsible for the research products, using tools already funded by the institutions (e.g. Excel) or free open-source tools such as OpenRefine and Calc, or QGIS.

**Estimated volume of data** 50

**Unit** GB

**Measures taken for data security**

Data security will be ensured through a combination of physical, digital, and procedural safeguards. All digital data will be stored on secure, institutionally managed servers with regular automated backups and controlled access based on user roles (see below). Sensitive or unpublished data will be protected by password-restricted folders, and encryption will be used when transferring data between devices or collaborators.

**Resana :**

Resana is hosted in Outscale's SecNumCloud 3DS in data centres in France. The operator is responsible for the availability of the service and for maintaining it in operational and security condition. The integrity and confidentiality of the information circulating are ensured by encryption mechanisms (HTTPS protocol). RESANA is not considered a "critical" service, in the sense of continuity of government action. In nominal mode, the service is available 24/7/365. However, it may be interrupted in the event of a technical incident or maintenance operation. DINUM aims to guarantee a maximum downtime of 4 hours and a maximum data loss time of 24 hours. RESANA is an information system that has been security-approved (RGS) by the qualified authority (Interministerial Digital Directorate) for the sharing of standard data. The information system takes into account the needs of confidentiality, integrity and availability of the service. All content uploaded to the platform is encrypted (AES 128 bit) and hosted on the Outscale SecNumCloud 3DS with 24/7 facilities management. However, its use is not authorised to convey sensitive information or information marked "Restricted Distribution", in accordance with II901 (NOR: PRMD1503279J).

Cf : https://resana.numerique.gouv.fr/public/utilisateur/afficherPageConnexionAnnexe? page=apropos

**Sharedocs :**

ShareDocs is a file manager implemented by IR* Huma-Num, on its own servers, which can be used via a web browser, a WebDAV client or file synchronisation software. The platform is based on the FileRun application. It provides remote online storage on the French research network (similar to tools such as DropBox, which are hosted on the public cloud). Hosted data can be easily encrypted using tools such as ZED encrypt.

ShareDocs is designed for research projects that want to store, exchange, share and work on file-type data (sets of photos, transcribed texts, etc.). For example, ShareDocs can be used to prepare files for online publishing or for distribution in NAKALA.

A ShareDocs project account facilitates data sharing and collaborative work between several members of a project or research team in the social sciences and humanities. The project account is adapted to collaboration via collaborative editing and file versioning tools, as the project account is accessible to several members of a team (unlike an individual account). It allows the creation of a tree structure of folders and it is necessary to define access and editing rights in detail, as soon as they have been created and for a list of identified collaborators. The principle is to create a folder and file tree when a project account is opened, and then to grant different access and editing rights depending on the role of each team member.

For the 2023-2025 forecasts, the volume of a project account is 300 GB of storage.

A project account can only be accessed by a list of people who have been declared and registered with Huma-Num by the project account manager.
The data stored on Sharedocs is hosted and backed up at the IN2P3 computing centre in Lyon, on Huma-Num servers. In the event of data loss, Huma-Num assures us that it will be possible to contact their helpdesk to recover it, via one of its backups.

https://documentation.huma-num.fr/sharedocs-stockage/

**Nakala :**

The data deposited in NAKALA is stored on servers managed by Huma-Num and hosted at the IN2P3 computing centre. This centre was set up to manage data produced in particle physics, nuclear physics and astroparticle physics.

This major national centre is secure from a hardware point of view (e.g. redundant power supply, network devices, cooling systems).

NAKALA data is stored on a NAS-type network storage device. A snapshot of the data is taken at regular intervals, enabling data to be restored quickly in the event of problems. In addition, a tape backup is made daily on the CCIN2P3 backup robot using TSM software published by IBM. NAKALA's metadata are stored in a SQL database (MariaDB) which is backed up daily on Huma-Num's infrastructure. The metadata is also exposed in RDF format via a Triple-Store (GraphDB) which is also backed up daily on the Huma-Num infrastructure. Continuity of the NAKALA¶ service

The NAKALA service is hosted on the Huma-Num infrastructure, which has a general disaster recovery plan. More specifically, the redundancy of the NAKALA service is ensured by :

- the NAKALA application is redundant on two different machines using a distribution tool (HAProxy), which avoids service interruptions in the event of a breakdown;

- the data is stored on a NAS-type device, so that data can be restored quickly. In addition, backups are made on magnetic tapes on a daily basis;

- Metadata is stored in a 'classic' relational database, which is backed up daily. This metadata is also stored in RDF format in a Triple-Store, which is backed up daily.

Source : https://documentation.huma-num.fr/nakala-faq/#comment-sont-sauvegardees-les-donnees

**PAC CINES :**

The long-term archiving platform at CINES - PAC v3.0 has been in production since 2008.
Capacity: 300 TB on 2 DELL storage bays of 150 TB each.

Arcsys archiving software (Infotel), Redundant virtualised architecture with 2 PowerEdge R730 hypervisors, 2 IBM TS-3500 tape libraries, with LTO4 and JAGUAR drives (use adapted to requirements), 1 Fiber channel interconnection network. cf https://www.cines.fr/ressources/

# Data sharing and long-term preservation

## How will data be shared?
## Modalities of sharing

The data will be stored in open and widely used formats to promote interoperability and sustainability. If any proprietary or non-standard formats are required due to specific research tools or instruments, a corresponding open version or export (when possible) will also be provided.

The CC-BY licensed datasets will be stored in the Nakala repository for the humanities and social sciences and will be assigned a persistent identifier (Datacite Digital Object Identifier). The Nakala data repository is managed by the French research infrastructure IR* Huma-Num, under the supervision of the French National Centre for Scientific Research, Aix-Marseille University and the Condorcet Campus.

The Dublin Core metadata Terms Vocabulary (ISO 15836) that must be entered in Nakala includes the type of data, the title, the author(s), the creation date and the licence associated with the dataset. It is possible to add additional metadata (qualified Dublin Core). Keywords (filled in using the PACTOLS interoperable multilingual thesaurus for Archaeology), language and a description of each dataset will be filled in. A readme file will be associated with each dataset deposited in the Nakala repository. The datasets will be "harvested" by the Isidore search engine and OpenAire Explore, and thus easily findable and accessible.

All datasets will be made available under a **Creative Commons Attribution (CC BY)** license, allowing broad reuse with appropriate credit. In cases involving sensitive or restricted data (e.g., personal data requiring anonymization), access may be restricted to specific user groups or require a data sharing agreement. Measures will be taken to minimize restrictions, including data anonymization and the provision of aggregated or de-identified versions where applicable.

Data will be made available within a reasonably short period after the conclusion of the project, or at the time of any related publication, whichever comes first. This allows time for quality assurance, documentation, and the preparation of metadata.

The datasets will be particularly relevant to researchers focusing on lithic technology in Central Europe. The data may be used for comparative analyses, technological studies and regional syntheses, but also for developing and testing methodological frameworks in lithic analysis.

## Reusability

The data produced during this project can be reused in future research to support further analysis, validation, or new investigations.

## Data repository/catalogs

* Nakala: https://cat.opidor.fr/index.php/Nakala (CoSO)

## How will data be long-term preserved? Which data?

## Justification

The long-term preservation of the lithic technology dataset is essential due to its scientific, cultural, and methodological value. First, the dataset documents unique prehistoric technological traditions across the settlement areas in Saxony, offering a valuable reference for future archaeological, anthropological, and heritage research. Given the irreversible nature of excavation and the potential inaccessibility of physical collections over time (due to curation limitations or degradation), the digital dataset serves as a crucial record of primary observations.

Moreover, the dataset is structured to support **comparative studies**, including re-analysis and replication of chaîne opératoire-based research. Preserving it ensures that future scholars can engage with the material using updated methods or in light of new discoveries. The use of open, standard formats (.csv, .tif, .txt) and rich metadata makes it interoperable and suitable for reuse across disciplines and platforms.

Finally, as archaeological research is increasingly data-driven, long-term preservation supports transparency, reproducibility, and open science. It aligns with international best practices in data stewardship and fulfills ethical obligations to safeguard irreplaceable scientific information for future generations.

The precise data selection and archiving process will be developed in close collaboration with the archives department of MSH Mondes.

In accordance with the Code of Heritage, the archives produced by the UMRs within the scope of UAR3225 are managed by the archives department of MSH Mondes. At the end of the research project, the documents and data produced will be transferred to the archives department. Indeed, the department is responsible for managing the public, administrative, and scientific archives of the units at MSH Mondes, from their production (current archives) throughout their entire conservation period after transfer (intermediate archives), regardless of their format (textual, graphic, photographic documents, etc.) and their medium (physical documents, electronic documents) (address:

https://www.mshmondes.cnrs.fr/accompagnement/archives).

Once transferred, these data are classified, described, and inventoried. The inventory is published online (address: https://archives.mshmondes.cnrs.fr), and the archives are accessible to anyone who requests them, in compliance with the rules set out in the Code of Heritage and
the Code of Intellectual Property.

A selection and, if necessary, regulatory destruction of the archives are carried out based on their administrative usefulness and scientific interest, with the approval of the Interministerial Archives Service of France (SIAF).

These operations are governed by a management table established in line with administrative and scientific needs. Finally, according to a schedule defined in agreement with the National Archives and the needs of the research, the project archives will, ultimately, be transferred to the National Archives for permanent conservation.

Extract of the Archive Department's management table :

<table><thead><tr><th>Activités et documents</th><th>DUA</th><th>Sort final</th><th>Observations</th></tr></thead><tbody><tr><td><strong>1. Direction d'équipe</strong></td><td></td><td></td><td></td></tr><tr><td><strong>1.1. Réunions internes et séminaires</strong><br>Ordre du jour, compte rendu de réunion et documents afférents, programme, support de présentation (texte, slide, vidéo...).</td><td>10 ans</td><td>C</td><td></td></tr><tr><td><strong>1.2. Suivi de l'activité des membres</strong><br>Dossier de membre (projet scientifique, rapport, attestation, demande de bourse), note interne.</td><td>10 ans</td><td>C</td><td></td></tr><tr><td><strong>2. Recherche</strong></td><td></td><td></td><td></td></tr><tr><td><strong>2.1. Programme/projet</strong> Le programme/projet peut être financé par des organismes extérieurs à l'unité (ANR, Labex, ministère des Affaires étrangères...) ou ne pas être financé. Le programme/projet génère des documents/données issus des activités scientifiques listées en 3.2-3.10.</td><td></td><td></td><td>Le programme/projet peut être financé par des organismes extérieurs à l'unité (ANR, Labex, ministère des Affaires étrangères...) ou ne pas être financé. Le programme/projet génère des documents/données issus des activités scientifiques listées en 3.2-3.10.</td></tr><tr><td><strong>2.1.1. Direction et gestion</strong></td><td></td><td></td><td></td></tr><tr><td><strong>Direction des activités</strong><br>Appel d'offres, appel à projet, texte de projet, dossier de candidature (accepté ou refusé), rapport d'activité, versions préliminaires (dossier de candidature, rapport), contrat de recherche, convention de collaboration, protocole d'accord, charte de sécurité, autorisation, permis, programme de travail, note d'information, plan de gestion de données, planning, agenda, lettre, courriel.</td><td>Durée du projet scientifique + 5 ans</td><td>T</td><td>Détruire les versions préliminaires (rapport, projet). Conserver les courriels les plus significatifs.</td></tr></tbody></table>
<table><tr><td>Gestion financière</td><td></td><td></td><td></td></tr><tr><td>Gestion par le responsable de projet</td><td></td><td></td><td></td></tr><tr><td>Budget prévisionnel, budget réalisé, notification de crédits, facture, justificatif de dépenses, bilan des dépenses, relevé de compte, attestation, lettre, courriel.</td><td>10 ans</td><td>D</td><td>C'est le cas par exemple des missions archéologiques françaises à l'étranger. Les budgets et les bilans de dépenses sont éliminés car ils figurent dans les rapports.</td></tr><tr><td>Gestion par l'unité ou une autre institution</td><td></td><td></td><td></td></tr><tr><td>Budget prévisionnel, budget réalisé, notification de crédits, facture, justificatif de dépenses, bilan des dépenses, relevé de compte, attestation, courriel.</td><td>Validité</td><td>D</td><td>Les documents sont des copies. Les documents originaux sont archivés par la cellule gestion financière de l'unité ou de l'institution.</td></tr><tr><td>Gestion des personnels (CDD, stagiaires)</td><td></td><td></td><td></td></tr><tr><td>Gestion par le responsable de projet</td><td></td><td></td><td></td></tr><tr><td>CV, lettre de motivation, bulletin d'inscription, attestation, convention de stage (copie), demande et ordre de mission (copie), demande de visa (copie), document relatif aux assurances (copie), courriel.</td><td>10 ans</td><td>D</td><td></td></tr><tr><td>Gestion par l'unité ou autre institution</td><td></td><td></td><td></td></tr><tr><td>CV, lettre de motivation, contrat (copie), convention de stage (copie), documents relatifs aux missions (copies), courriel.</td><td>Validité</td><td>D</td><td>Les documents sont des copies. Les documents originaux sont archivés par la cellule gestion financière de l'unité ou de l'institution.</td></tr><tr><td>Gestion de locaux, d'équipement</td><td></td><td></td><td></td></tr><tr><td>Inventaire d'équipement, documents d'organisation de la vie quotidienne, documentation technique, documents relatifs à la gestion et à l'entretien de véhicule, documents relatifs à la location de locaux.</td><td>10 ans</td><td>T</td><td>Cette rubrique concerne par exemple les missions archéologiques françaises à l'étranger. Détruire les documents relatifs à la gestion et à l'entretien de véhicule et la documentation technique. Conserver les inventaires d'équipement et les documents d'organisation de la vie quotidienne.</td></tr><tr><td>2.1.2. Participation (documents de gestion)</td><td></td><td></td><td></td></tr><tr><td>Texte de projet, rapport, programme de travail, notes, courriel.</td><td>Durée du projet scientifique + 5 ans</td><td>T</td><td>Les tri porte sur les notes et les courriels : conserver selon l'intérêt.</td></tr></table>
<table><tr><td>2.1.3. Réunions scientifiques internes (équipe projet, partenaires)</td><td>Durée du projet scientifique + 5 ans</td><td>C</td><td></td></tr><tr><td>Ordre du jour, compte rendu de réunion et documents afférents, programme, support de présentation (texte, slide, vidéo...).</td><td></td><td></td><td>Il s'agit de tout type de données (issues de fouilles archéologiques, d'une enquête sociologique, historique, géographique...) quelles que soient leurs formes (textes, images, sons...) et leurs supports. Lorsqu'il y a obligation de gestion des archives intermédiaires au sein d'un autre service, les documents/données ne sont pas pris en compte (par exemple, pour l'archéologie, les services régionaux de l'archéologie, l'Ecole française d'Athènes...). Conserver la version achevée des documents. Certaines versions préparatoires peuvent être conservées en fonction de l'expertise du chercheur. Conserver les masters en format compressé ; détruire les rushes et les masters en format non compressé.</td></tr><tr><td>2.2. Collecte et analyse de documents/données</td><td>Durée du projet scientifique + 5 ans</td><td>T</td><td></td></tr><tr><td>Carnet/cahier/journal de terrain, notes d'enquête, notes d'entretien, transcription d'entretien oral, guide d'entretien, questionnaire, fichier d'enregistrement, fiches individuelles, inventaire, document graphique (relevé de terrain, plan, coupe, restitution, dessin d'objet...), document cartographique, photographie, photographie aérienne, image satellitaire, modèle 3D, base de données, système d'information géographique, enregistrement sonore, produit audiovisuel et multimédia (film, vidéo...), échantillons, moulages, maquettes, rapport d'analyse, étude préliminaire, transcription et traduction de textes, guide/note méthodologique, documentation, programme de travail, notes, courriel.</td><td></td><td></td><td>Il s'agit de tout type de données (issues de fouilles archéologiques, d'une enquête sociologique, historique, géographique...) quelles que soient leurs formes (textes, images, sons...) et leurs supports. Lorsqu'il y a obligation de gestion des archives intermédiaires au sein d'un autre service, les documents/données ne sont pas pris en compte (par exemple, pour l'archéologie, les services régionaux de l'archéologie, l'Ecole française d'Athènes...). Conserver la version achevée des documents. Certaines versions préparatoires peuvent être conservées en fonction de l'expertise du chercheur. Conserver les masters en format compressé ; détruire les rushes et les masters en format non compressé.</td></tr><tr><td>2.3. Préparation de publication (ouvrages, article, compte rendu...)</td><td>Durée de la préparation + 5 ans</td><td>T</td><td>Le tri porte principalement sur les textes préliminaires et illustrations : conserver uniquement la première version soumise. Détruire les épreuves. Documentation, courriel : conserver les documents les plus significatifs.</td></tr><tr><td>Texte préliminaire, illustration originale, épreuves, documentation préparatoire, compte rendu de réunion et documents afférents, vidéo de visioconférence, convention de collaboration, contrat de recherche, avis des rapporteurs, lettre, courriel.</td><td></td><td></td><td></td></tr><tr><td>2.4. Congrès, colloque, journée d'étude (organisation ou participation)</td><td>10 ans</td><td>T</td><td>Le tri porte principalement sur les textes préliminaires et illustrations : conserver uniquement la première version soumise. Détruire les épreuves. Documentation, lettres, courriels : conserver les documents les plus significatifs. Détruire les copies de documents financiers et de missions.</td></tr><tr><td>Support de communication (texte/illustration, slide, vidéo...), résumé, texte et illustration préliminaires des actes, épreuves, poster scientifique, affiche, plaquette, documentation, documents d'organisation (programme, circulaire, résumés des communications...), ordre du jour, compte rendu de réunion et documents afférents, lettre, courriel, copies de documents relatifs à la gestion financière et aux missions.</td><td></td><td></td><td></td></tr><tr><td>2.5. Sites Web (carnets de recherche, blogs...)</td><td>Validité</td><td>D</td><td>Depuis 2006, la BNF assurer le dépôt légal de l'internet français.</td></tr><tr><td>Texte de projet, cahier des charges, compte rendu de réunion, texte et illustration préparatoires, courriel.</td><td></td><td></td><td></td></tr></table>
<table>
  <tr>
    <td>2.6. Documentation<br>Photographies, dessins, cartes, enregistrements sonores, produit audiovisuel et multimédia, publications électroniques ou papier, rapport, notes de travail, notes de lecture, courriel, lettre, photothèque, collections de cartes, plans, dessins, collections de référence ou de comparaison (objet fabriqué), base de données.</td>
    <td>Durée d'exploitation + 5 ans</td>
    <td></td>
    <td>Conserver les documents selon l'intérêt. Seule la version finale de la base de données sera conservée. Publications : conserver seulement les textes lorsqu'ils participent à la cohérence scientifique d'un dossier contenant d'autres documents.</td>
  </tr>
  <tr>
    <td>2.7. Médiation scientifique<br>(Exposition, conférence, atelier grand public, émission de radio, émission de télévision, produit pédagogique...) Produit audiovisuel et multimédia (film, vidéo...), podcast, site Web, support de communication (catalogue, livret, programme, affiche, slides de présentation, vidéo...), poster, rushes, master, autorisation, invitation, documentation, courriel, document financier et de mission (copies).</td>
    <td>Durée du projet + 5 ans</td>
    <td>T</td>
    <td>Documentation, courriels : conserver les documents les plus significatifs. Détruire les copies de documents financiers et de missions. Conserver les masters en format compressé ; détruire les rushes et les masters en format non compressé. Les podcasts et sites Web ne sont pas pris en compte.</td>
  </tr>
  <tr>
    <td>2.8. Correspondance<br>boîte aux lettres électronique, lettre.</td>
    <td>10 ans</td>
    <td>T</td>
    <td>Le tri porte sur les courriels : conserver les courriels et pièces jointes selon l'intérêt. Détruire les courriels privés.</td>
  </tr>
  <tr>
    <td>2.9. Enseignement et formation<br>2.9.1. Enseignement dispensé<br>Programme, support de cours (texte/illustration, slide, vidéo...) et documents afférents, plaquette pédagogique, documentation, notes, lettre, courriel.</td>
    <td>10 ans</td>
    <td>T</td>
    <td>Le tri porte sur la documentation, les notes, lettres et courriels : conserver selon l'intérêt.</td>
  </tr>
  <tr>
    <td>2.9.2. Direction et suivi de travaux d'étudiants<br>Travaux d'étudiants (thèses, mémoires), rapport (sur les mémoires et sur les soutenances), procès-verbal de soutenance, convocations, courriel, lettres, notes.</td>
    <td>10 ans</td>
    <td>T</td>
    <td>Travaux d'étudiants : les thèses sont archivées par le CINES (Arrêté du 25 mai 2016 fixant le cadre national de la formation et les modalités conduisant à la délivrance du diplôme national de doctorat, titre IV, art. 24-25). Les mémoires (master 1 et 2) sont archivés par les universités. Toutefois, certains documents peuvent être versés en fonction de l'expertise du chercheur et de leur apport au fonds. D pour les autres documents qui sont gérés par les universités.</td>
  </tr>
  <tr>
    <td>2.9.3. Accueil de chercheurs et de stagiaires<br>Dossier de chercheur invité (candidature (copie), projet de recherche, attestation (copie), rapport scientifique, lettre,</td>
    <td>10 ans</td>
    <td>T</td>
    <td>Conserver les documents scientifiques en fonction de l'expertise du chercheur. Détruire les candidatures, conventions, attestations,</td>
  </tr>
</table>
courriel.

Dossier de stagiaire (convention de stage
(copie), rapport de stage).

lettres, courriels.

Start date

End date

Archive

Final dispositions

Title Huma-Num : Archivage à long terme

Repository ID https://cat.opidor.fr/index.php/Huma-Num_/_Archivage_à_long_terme

Identifier type URL

Geo location
(country) FR

Certification

# Datasets for the lithic study in Key Area 3 - Bavaria

## Data description and collection or re-use of existing data

### Research output description
**Name** Datasets for the lithic study in Key Area 3 - Bavaria

**Description** This dataset will comprise documentation of the lithic analysis of Key Area 3 (Bavaria, Germany). It will include:

* **spreadsheets:**

* archaeological sites of the key area and the timeframe concerned with essential data data (location, chronology, publications)

* recording of features and elements of the raw material analysis

* recording of the technological analysis of pieces, either as single or group recording. The columns will describe various observed variables, both quantitative and qualitative.

* **Textual:** Reports of the recording including a description of the assemblage, context of the site and reasoning for the assemblage being selected.

* **images:** photographic documentation and/or drawings of lithic objects.

Persistent identifiers will be pursued so that the data can be reliably and efficiently located and referred

to. The dataset will be made available online on the platform Nakala.

As far as possible, we always favour open and standard formats to encourage data sharing and re-use: spreadsheets in .csv or .txt format; photographs in .tif or .png formats; documents in .pdf or .txt format.

**Type** Dataset

**Workpackage** WP2

**Keywords**

* Bavière (Pactols lieux)

* débitage laminaire (Pactols sujets)

* technologie lithique (Pactols sujets)

* lame (Pactols sujets)

* mode de production (Pactols sujets)

* circulation de matière première (Pactols sujets)

**Keywords (free-text)**

**Language** eng

**Issued Date**

**May contain personal data?** No

**May contain sensible data?** No

**May take ethical issues into account?** Yes

**Will existing data be reused?**

**Justification** The re-use of existing data may concern existing recordings of finds or data of sites. These are connected to licence constraints regarding their use.

This comprises:

* **Reports and documentation** of excavations, sites and archaeological objects

* **Georeferenced data** of sondages, features and/or objects if available

Their use will be agreed with the Bavarian State Office for Archaeology (Bayerisches Landesamt für Denkmalpflege) as well as partners from other archaeological departments (e.g. Lower monument protection authority or museums).
## How new data will be collected or produced?

<table><tr><td>Name of the method</td><td>Analysis of lithic technology and raw material analysis</td></tr><tr><td>Description</td><td>The method is based on a technological analysis of lithic industries, aiming to reconstruct the production process chains (chaîne opératoire). It incorporates various complementary types of sorting, categorised by raw material and production stage. Data recording is tailored to the quality of information provided by each piece. Finished products will undergo detailed analysis using approximately thirty criteria, while production waste will be documented based on around ten criteria. The practical aspects of the study are adapted to the material's packaging (e.g., marking, storage in pits, by stratigraphic unit) and the study location (e.g., whether the material can be spread out for analysis).<br>The elements are observed with the naked eye or under the microscope if necessary for certain very specific aspects such as preparations for detachment. The pieces and specific elements are measured with an electronic calliper. The pieces are counted and weighed. All the data are registered in a database that will be exported to excel/ or text files (.csv or .txt).<br>Technical scars are described and interpreted through comparisons with experimental data, which are extensively available in the Technothèque of UMR 8068.<br>Raw material analysis will be conducted with macroscopic sorting and microscopic documentation of variants.</td></tr><tr><td>Data Nature</td><td>Observational data</td></tr><tr><td>Equipments, technical platforms used</td><td><ul><li>Technothèque of the UMR 8068 lab : https://teknotek.pretech.cnrs.fr/s/fr/page/accueil</li><li>Dino-Lite AM7915MZTL : Microscope numérique USB : https://www.dino-litefrance.fr/produits/la-gamme/microscopes/longue-distance/am7915mztl-microscope-numerique-usb-dino-lite/</li></ul></td></tr><tr><td>Costs</td><td><ul><li>Personnel cost : 68 998 EUR</li></ul></td></tr></table>

## Documentation and data quality

### What metadata and documentation (for example way of organising data) will accompany the data?

<table><tr><td>Description</td><td><strong>The data</strong> will be recorded and stored on the professional laptop of Lisa Bauer as well as in a Cloud storage.<br><br><strong>Metadata</strong> standards of Dublin Core Metadata Terms (DCMT) will be used. The following <strong>metadata</strong> will be given for this dataset:<ul><li>a <u>lithic data dictionary</u> will be associated with the spreadsheets for the key areas in order to unify the lithic databases. It will include descriptions of codes and the structuring of data as well as drawings for particular features.</li><li>for assemblages with specific documentation of elements and features a <u>spreadsheet for documentation</u> (images and drawings) will be produced</li><li>A <u>readme file</u> will be produced with specific informations about the process of recording and indications of specific aspects (differences in recording etc.)</li><li>A <u>readme file</u> will be produced within the "documentation" folder in order to document specific aspects and problems</li></ul></td></tr></table>
regarding the existing data for each site

* a **readme file** will be produced within the **GIS** folder in order to document any custom changes of the data (modifications of points and polygons, addition of columns etc.).

**Naming conventions** of files will be as follows:

* spreadsheets for sites: "mobilith_KA3_sitename_YYYY-MM-DD"

* a metadata sheet: "mobilith_KA3_lithicdatadictionary_YYYY-MM-DD"

* images of finds: "mobilith_KA3_sitename_ID-picture_1"

* drawings of finds: "mobilith_KA3_sitename_ID-drawing_1"

The **folder structure** will be organized in order to be identifiable easily for each site. Versions of data will be archived with their respective date. The hierarchy of folders will be as follows:

* "KAx" (here "KA3")

* "KA3_sites": Contains a spreadsheet with sites for this key area.

* "KA3_CODE_sitename" (e.g., "KA3_LA-01_Sallmannsberg")

* "Documentation" (raw data of reports, images, drawings, georeferenced data, readme files)

* "Data" (containing data spreadsheets, readme files and lithic data dictionary)

* "Images"

* "Drawings"

* "Analysis" (containing R codes and files, figures and sketches of refitting, readme file, etc.)

* "GIS" (containing modified shapefiles for each site, on the basis of the raw data, but customized to the research questions, as well as a readme file)

**Metadata language code** eng

**What methods will be used to ensure their scientific quality?**

**Description**

**Data cleaning:** The database will be cleaned with free software, e.g., OpenRefine

**Peer review of data:** The data will be cross-tested by the lithic research group (Pierre Allard, Lisa Bauer, Solène Denis).

**Data entry validation:** The validation of data will be ensured by using a customized database (in MS Access) with the pre-defined structure of data entries. This can easily be exported as various spreadsheet formats.

**Representation with controlled vocabularies:** This will be achieved by recording in the database and the lithic dictionary file.
## Legal and ethical requirements, codes of conduct

### How will other legal issues, such as intellectual property rights and ownership, be managed? What legislation is applicable?

<table><tr><td>Description</td><td>The project data are public archives within the meaning of the Code du patrimoine, article L211-4. This status was reiterated by the directive issued by CNRS and Archives de France in 2007 (Instruction No. DAF/DPACI/RES/2007/002 of January 15, 2007. Traitement et conservation des archives des délégations du CNRS et des archives des unités de recherche et de service). Public archives are freely accessible, except for information subject to communication deadlines defined by the Code du patrimoine, in article L.213-2.<br/>The disclosure, reuse, and dissemination of public archives that qualify as a work of the mind, as defined by the Code de la propriété intellectuelle, are regulated by the same code. Researchers and teacher-researchers, as public servants, retain their intellectual property rights (article L.111-1 of the Code de la propriété intellectuelle).</td></tr></table>

### What ethical issues and codes of conduct are there, and how will they be taken into account?

<table><tr><td>Description</td><td>The Code de la recherche establishes a link between scientific integrity and the preservation of scientific data, in accordance with the Code du patrimoine. In the long term, the archives department of the MSH Mondes will be responsible for the preservation and regulatory communication of the data, in line with the provisions set out in both codes.</td></tr></table>

## Data processing and analysis

### How and with what resources will the data be processed / analyzed?
<table><thead><tr><th>Description</th><th></th></tr></thead><tbody><tr><td>Data processing will be carried out primarily in RStudio, using tailored R scripts for the analysis of lithic technology variables. The dataset will first be compiled in .csv format, with each row representing either an individual artifact or a homogeneous batch. Quantitative variables (e.g., dimensions, weight, scar counts) and qualitative descriptors (e.g., raw material, typology, percussion technique) will be encoded following standardized taxonomies to ensure consistency and interoperability.<br>Processing will follow a structured pipeline:<br>1. <strong>Data Cleaning and Standardisation:</strong> Raw data from spreadsheets will be cleaned (e.g., correction of entry errors, removal of duplicates, standardisation of terminology) and formatted for analysis in R. Descriptive labels will be harmonised using controlled vocabularies.<br>2. <strong>Exploratory and Descriptive Analysis:</strong> Statistical summaries (e.g., distributions, central tendencies, variance measures) will be computed to describe key characteristics of the lithic assemblages. Batch-level and individual-level data will be treated separately where relevant.<br>3. <strong>Technological Categorisation:</strong> Based on chaîne opératoire approach, artefacts will be classified into production stages.<br>4. <strong>Visual Data Integration:</strong> Photographs and drawings will be linked to analytical records through persistent identifiers and file-naming conventions. Images will be processed in standard formats (.tif, .png), and metadata (e.g., scale, object ID, context) will be embedded or referenced in associated documentation.<br>5. <strong>Comparative and Interpretative Analysis:</strong> Descriptive data will be interpreted in relation to experimental reference collections (Technothèque UMR 8068). Comparative procedures will use qualitative pattern recognition as well as quantitative clustering methods where applicable.<br>6. <strong>Reproducibility and Sharing:</strong> All R scripts used for data processing and analysis will be documented and deposited alongside the dataset. The full protocol, including criteria definitions, classification logic, and variable descriptions, will be included in the metadata_lithicdictionary. Upon publication of the KA 1 results, the dataset, metadata, and code will be deposited on Nakala, ensuring persistent access.</td></tr></tbody></table>

## Storage and backup during the research process

### How will data be stored and backed up during the research?

<table><thead><tr><th>Storage needs</th><th></th></tr></thead><tbody><tr><td>During the project, data will be stored and backed up in multiple secure environments to ensure both accessibility and protection against loss:<ul><li><strong>Primary Storage:</strong> Data will be stored on the professional, institutionally managed computer of Lisa Bauer, with access restricted to authorized project personnel.</li><li><strong>Secondary Backup:</strong> A monthly backup of project data will be saved to a dedicated external hard drive maintained by the project team.</li></ul>The project's shared workspace on RESANA (a secure platform provided by the French Direction Interministérielle du Numérique - DINUM) will serve as an additional storage and collaboration space. Résana hosts data on nationally managed secured servers, ensuring institutional compliance and reliability.<br>A ShareDoc (CNRS IN2P3) project-specific file manager for MOBILITH will be set up, with weekly backups, providing robust redundancy and automated version control.<br>The use of at least three independent storage spaces - local, institutional online, and external managed backup - ensures the ability to recover data in the event of hardware failure, accidental deletion, or other incidents. In case of data loss or corruption, the most recent backup from ShareDoc or the external drive will be restored, with coordination from institutional IT support if needed.<br>Access to project data during the research phase will be restricted to MOBILITH project members and designated external experts. Controlled access is managed through institutional credentials for Résana and ShareDoc platforms. FileSender, the institutional secure file transfer</td></tr></tbody></table>
service, will be used for any sensitive file exchanges between partners, ensuring encrypted transmission.

While the project does not involve highly sensitive personal data, appropriate data protection measures will be observed. In cases where potentially sensitive information is handled (e.g., site locations or unpublished archaeological findings), access will be limited, and data will be pseudonymized or aggregated as appropriate.

Data management and protection practices will comply with institutional and national policies, in alignment with GDPR and best practices for handling research data securely.

Perennial archiving costs are covered by the MSH Mondes archive service (CNRS servers) and, for definitive archiving, by the French National Archives and the Centre informatique national de l'enseignement supérieur (CINES), under the supervision of the Ministry of Higher Education.

The cost of storing and sharing the data that will be made public will be borne by the institutions for which the project participants work (data on portable PCs, by the IR* Huma-Num (storage on Sharedocs and dissemination via the SHS Nakala data warehouse), under the supervision of the CNRS, Aix Marseille University and the Condorcet campus, by the French government's Direction du Numérique (document sharing via the Resana collaborative platform), by CERN for the Zenodo generalist warehouse, and by the Centre de la Communication Scientifique Directe (CCSD) under the supervision of CNRS, INRIA and INRAE for the distribution of open access publications.

Processing will be carried out by those responsible for the research products, using tools already funded by the institutions (e.g. Excel) or free open-source tools such as OpenRefine and Calc, or QGIS.

**Estimated volume of data**

50

**Unit**

GB

**Measures taken for data security**

Data security will be ensured through a combination of physical, digital, and procedural safeguards. All digital data will be stored on secure, institutionally managed servers with regular automated backups and controlled access based on user roles (see below). Sensitive or unpublished data will be protected by password-restricted folders, and encryption will be used when transferring data between devices or collaborators.

**Resana :**

Resana is hosted in Outscale's SecNumCloud 3DS in data centres in France. The operator is responsible for the availability of the service and for maintaining it in operational and security condition. The integrity and confidentiality of the information circulating are ensured by encryption mechanisms (HTTPS protocol). RESANA is not considered a "critical" service, in the sense of continuity of government action. In nominal mode, the service is available 24/7/365. However, it may be interrupted in the event of a technical incident or maintenance operation. DINUM aims to guarantee a maximum downtime of 4 hours and a maximum data loss time of 24 hours. RESANA is an information system that has been security-approved (RGS) by the qualified authority (Interministerial Digital Directorate) for the sharing of standard data. The information system takes into account the needs of confidentiality, integrity and availability of the service. All content uploaded to the platform is encrypted (AES 128 bit) and hosted on the Outscale SecNumCloud 3DS with 24/7 facilities management. However, its use is not authorised to convey sensitive information or information marked "Restricted Distribution", in accordance with II901 (NOR: PRMD1503279J).

Cf : https://resana.numerique.gouv.fr/public/utilisateur/afficherPageConnexionAnnexe? page=apropos

**Sharedocs :**

ShareDocs is a file manager implemented by IR* Huma-Num, on its own servers, which can be used via a web browser, a WebDAV client or file synchronisation software. The platform is based on the FileRun application. It provides remote online storage on the French research network (similar to tools such as DropBox, which are hosted on the public cloud). Hosted data can be easily encrypted using tools such as ZED encrypt.

ShareDocs is designed for research projects that want to store, exchange, share and work on file-type data (sets of photos, transcribed texts, etc.). For example, ShareDocs can be used to prepare files for online publishing or for distribution in NAKALA.

A ShareDocs project account facilitates data sharing and collaborative work between several members of a project or research team in the social sciences and humanities. The project account is adapted to collaboration via collaborative editing and file versioning tools, as the project account is accessible to several members of a team (unlike an individual account). It allows the creation of a tree structure of folders and it is necessary to define access and editing rights in detail, as soon as they have been created and for a list of identified collaborators. The principle is to create a folder and file tree when a project account is opened, and then to grant different access and editing rights depending on the role of each team member.

For the 2023-2025 forecasts, the volume of a project account is 300 GB of storage.

A project account can only be accessed by a list of people who have been declared and registered with Huma-Num by the project account manager.

The data stored on Sharedocs is hosted and backed up at the IN2P3 computing centre in Lyon,
on Huma-Num servers. In the event of data loss, Huma-Num assures us that it will be possible
to contact their helpdesk to recover it, via one of its backups.

https://documentation.huma-num.fr/sharedocs-stockage/

Nakala :

The data deposited in NAKALA is stored on servers managed by Huma-Num and hosted at the IN2P3 computing centre. This centre was set up to manage data produced in particle physics, nuclear physics and astroparticle physics.

This major national centre is secure from a hardware point of view (e.g. redundant power
supply, network devices, cooling systems).

NAKALA data is stored on a NAS-type network storage device. A snapshot of the data is taken at regular intervals, enabling data to be restored quickly in the event of problems. In addition, a tape backup is made daily on the CCIN2P3 backup robot using TSM software published by IBM. NAKALA's metadata are stored in a SQL database (MariaDB) which is backed up daily on Huma-Num's infrastructure. The metadata is also exposed in RDF format via a Triple-Store (GraphDB) which is also backed up daily on the Huma-Num infrastructure. Continuity of the NAKALA¶ service

The NAKALA service is hosted on the Huma-Num infrastructure, which has a general disaster
recovery plan. More specifically, the redundancy of the NAKALA service is ensured by :

- the NAKALA application is redundant on two different machines using a distribution tool (HAProxy), which avoids service interruptions in the event of a breakdown;

- the data is stored on a NAS-type device, so that data can be restored quickly. In addition, backups are made on magnetic tapes on a daily basis;

- Metadata is stored in a 'classic' relational database, which is backed up daily. This metadata is also stored in RDF format in a Triple-Store, which is backed up daily.

Source : https://documentation.huma-num.fr/nakala-faq/#comment-sont-sauvegardees-les-donnees

PAC CINES :

The long-term archiving platform at CINES - PAC v3.0 has been in production since 2008.
Capacity: 300 TB on 2 DELL storage bays of 150 TB each.

Arcsys archiving software (Infotel), Redundant virtualised architecture with 2 PowerEdge R730 hypervisors, 2 IBM TS-3500 tape libraries, with LTO4 and JAGUAR drives (use adapted to requirements), 1 Fiber channel interconnection network. cf https://www.cines.fr/ressources/

Data sharing and long-term preservation

How will data be shared?
## Modalities of sharing

The data will be stored in open and widely used formats to promote interoperability and sustainability. If any proprietary or non-standard formats are required due to specific research tools or instruments, a corresponding open version or export (when possible) will also be provided.

The CC-BY licensed datasets will be stored in the Nakala repository for the humanities and social sciences and will be assigned a persistent identifier (Datacite Digital Object Identifier). The Nakala data repository is managed by the French research infrastructure IR* Huma-Num, under the supervision of the French National Centre for Scientific Research, Aix-Marseille University and the Condorcet Campus.

The Dublin Core metadata Terms Vocabulary (ISO 15836) that must be entered in Nakala includes the type of data, the title, the author(s), the creation date and the licence associated with the dataset. It is possible to add additional metadata (qualified Dublin Core). Keywords (filled in using the PACTOLS interoperable multilingual thesaurus for Archaeology), language and a description of each dataset will be filled in. A readme file will be associated with each dataset deposited in the Nakala repository. The datasets will be "harvested" by the Isidore search engine and OpenAire Explore, and thus easily findable and accessible.

All datasets will be made available under a **Creative Commons Attribution (CC BY)** license, allowing broad reuse with appropriate credit. In cases involving sensitive or restricted data (e.g., personal data requiring anonymization), access may be restricted to specific user groups or require a data sharing agreement. Measures will be taken to minimize restrictions, including data anonymization and the provision of aggregated or de-identified versions where applicable.

Data will be made available within a reasonably short period after the conclusion of the project, or at the time of any related publication, whichever comes first. This allows time for quality assurance, documentation, and the preparation of metadata.

The datasets will be particularly relevant to researchers focusing on lithic technology in Central Europe. The data may be used for comparative analyses, technological studies and regional syntheses, but also for developing and testing methodological frameworks in lithic analysis.

## Reusability

The data produced during this project can be reused in future research to support further analysis, validation, or new investigations.

## Data repository/catalogs

* Nakala: https://cat.opidor.fr/index.php/Nakala (CoSO)

## How will data be long-term preserved? Which data?

## Justification

The long-term preservation of the lithic technology dataset is essential due to its scientific, cultural, and methodological value. First, the dataset documents unique prehistoric technological traditions in different settlement regions of Bavaria, offering a valuable reference for future archaeological, anthropological, and heritage research. Given the irreversible nature of excavation and the potential inaccessibility of physical collections over time (due to curation limitations or degradation), the digital dataset serves as a crucial record of primary observations.

Moreover, the dataset is structured to support **comparative studies**, including re-analysis and replication of the chaîne opératoire-based research. Preserving it ensures that future scholars can engage with the material using updated methods or in light of new discoveries. The use of open, standard formats (.csv, .tif, .txt) and rich metadata makes it interoperable and suitable for reuse across disciplines and platforms.

Finally, as archaeological research is increasingly data-driven, long-term preservation supports transparency, reproducibility, and open science. It aligns with international best practices in data stewardship and fulfills ethical obligations to safeguard irreplaceable scientific information for future generations.

The precise data selection and archiving process will be developed in close collaboration with the archives department of MSH Mondes.

In accordance with the Code of Heritage, the archives produced by the UMRs within the scope of UAR3225 are managed by the archives department of MSH Mondes. At the end of the research project, the documents and data produced will be transferred to the archives department. Indeed, the department is responsible for managing the public, administrative, and scientific archives of the units at MSH Mondes, from their production (current archives) throughout their entire conservation period after transfer (intermediate archives), regardless of their format (textual, graphic, photographic documents, etc.) and their medium (physical documents, electronic documents) (address:

https://www.mshmondes.cnrs.fr/accompagnement/archives).

Once transferred, these data are classified, described, and inventoried. The inventory is published online (address: https://archives.mshmondes.cnrs.fr), and the archives are accessible to anyone who requests them, in compliance with the rules set out in the Code of Heritage and
the Code of Intellectual Property.

A selection and, if necessary, regulatory destruction of the archives are carried out based on their administrative usefulness and scientific interest, with the approval of the Interministerial Archives Service of France (SIAF).

These operations are governed by a management table established in line with administrative and scientific needs. Finally, according to a schedule defined in agreement with the National Archives and the needs of the research, the project archives will, ultimately, be transferred to the National Archives for permanent conservation.

Extract of the Archive Department's management table :

<table><thead><tr><th>Activités et documents</th><th>DUA</th><th>Sort final</th><th>Observations</th></tr></thead><tbody><tr><td><strong>1. Direction d'équipe</strong></td><td></td><td></td><td></td></tr><tr><td><strong>1.1. Réunions internes et séminaires</strong><br>Ordre du jour, compte rendu de réunion et documents afférents, programme, support de présentation (texte, slide, vidéo...).</td><td>10 ans</td><td>C</td><td></td></tr><tr><td><strong>1.2. Suivi de l'activité des membres</strong><br>Dossier de membre (projet scientifique, rapport, attestation, demande de bourse), note interne.</td><td>10 ans</td><td>C</td><td></td></tr><tr><td><strong>2. Recherche</strong></td><td></td><td></td><td></td></tr><tr><td><strong>2.1. Programme/projet</strong> Le programme/projet peut être financé par des organismes extérieurs à l'unité (ANR, Labex, ministère des Affaires étrangères...) ou ne pas être financé. Le programme/projet génère des documents/données issus des activités scientifiques listées en 3.2-3.10.</td><td></td><td></td><td>Le programme/projet peut être financé par des organismes extérieurs à l'unité (ANR, Labex, ministère des Affaires étrangères...) ou ne pas être financé. Le programme/projet génère des documents/données issus des activités scientifiques listées en 3.2-3.10.</td></tr><tr><td><strong>2.1.1. Direction et gestion</strong></td><td></td><td></td><td></td></tr><tr><td><strong>Direction des activités</strong><br>Appel d'offres, appel à projet, texte de projet, dossier de candidature (accepté ou refusé), rapport d'activité, versions préliminaires (dossier de candidature, rapport), contrat de recherche, convention de collaboration, protocole d'accord, charte de sécurité, autorisation, permis, programme de travail, note d'information, plan de gestion de données, planning, agenda, lettre, courriel.</td><td>Durée du projet scientifique + 5 ans</td><td>T</td><td>Détruire les versions préliminaires (rapport, projet). Conserver les courriels les plus significatifs.</td></tr></tbody></table>
<table><tr><td>Gestion financière</td><td></td><td></td><td></td></tr><tr><td>Gestion par le responsable de projet</td><td></td><td></td><td></td></tr><tr><td>Budget prévisionnel, budget réalisé, notification de crédits, facture, justificatif de dépenses, bilan des dépenses, relevé de compte, attestation, lettre, courriel.</td><td>10 ans</td><td>D</td><td>C'est le cas par exemple des missions archéologiques françaises à l'étranger. Les budgets et les bilans de dépenses sont éliminés car ils figurent dans les rapports.</td></tr><tr><td>Gestion par l'unité ou une autre institution</td><td></td><td></td><td></td></tr><tr><td>Budget prévisionnel, budget réalisé, notification de crédits, facture, justificatif de dépenses, bilan des dépenses, relevé de compte, attestation, courriel.</td><td>Validité</td><td>D</td><td>Les documents sont des copies. Les documents originaux sont archivés par la cellule gestion financière de l'unité ou de l'institution.</td></tr><tr><td>Gestion des personnels (CDD, stagiaires)</td><td></td><td></td><td></td></tr><tr><td>Gestion par le responsable de projet</td><td></td><td></td><td></td></tr><tr><td>CV, lettre de motivation, bulletin d'inscription, attestation, convention de stage (copie), demande et ordre de mission (copie), demande de visa (copie), document relatif aux assurances (copie), courriel.</td><td>10 ans</td><td>D</td><td></td></tr><tr><td>Gestion par l'unité ou autre institution</td><td></td><td></td><td></td></tr><tr><td>CV, lettre de motivation, contrat (copie), convention de stage (copie), documents relatifs aux missions (copies), courriel.</td><td>Validité</td><td>D</td><td>Les documents sont des copies. Les documents originaux sont archivés par la cellule gestion financière de l'unité ou de l'institution.</td></tr><tr><td>Gestion de locaux, d'équipement</td><td></td><td></td><td></td></tr><tr><td>Inventaire d'équipement, documents d'organisation de la vie quotidienne, documentation technique, documents relatifs à la gestion et à l'entretien de véhicule, documents relatifs à la location de locaux.</td><td>10 ans</td><td>T</td><td>Cette rubrique concerne par exemple les missions archéologiques françaises à l'étranger. Détruire les documents relatifs à la gestion et à l'entretien de véhicule et la documentation technique. Conserver les inventaires d'équipement et les documents d'organisation de la vie quotidienne.</td></tr><tr><td>2.1.2. Participation (documents de gestion)</td><td></td><td></td><td></td></tr><tr><td>Texte de projet, rapport, programme de travail, notes, courriel.</td><td>Durée du projet scientifique + 5 ans</td><td>T</td><td>Les tri porte sur les notes et les courriels : conserver selon l'intérêt.</td></tr></table>
<table><tr><td>2.1.3. Réunions scientifiques internes (équipe projet, partenaires)</td><td>Durée du projet scientifique + 5 ans</td><td>C</td><td></td></tr><tr><td>Ordre du jour, compte rendu de réunion et documents afférents, programme, support de présentation (texte, slide, vidéo...).</td><td></td><td></td><td>Il s'agit de tout type de données (issues de fouilles archéologiques, d'une enquête sociologique, historique, géographique...) quelles que soient leurs formes (textes, images, sons...) et leurs supports. Lorsqu'il y a obligation de gestion des archives intermédiaires au sein d'un autre service, les documents/données ne sont pas pris en compte (par exemple, pour l'archéologie, les services régionaux de l'archéologie, l'Ecole française d'Athènes...). Conserver la version achevée des documents. Certaines versions préparatoires peuvent être conservées en fonction de l'expertise du chercheur. Conserver les masters en format compressé ; détruire les rushes et les masters en format non compressé.</td></tr><tr><td>2.2. Collecte et analyse de documents/données</td><td>Durée du projet scientifique + 5 ans</td><td>T</td><td></td></tr><tr><td>Carnet/cahier/journal de terrain, notes d'enquête, notes d'entretien, transcription d'entretien oral, guide d'entretien, questionnaire, fichier d'enregistrement, fiches individuelles, inventaire, document graphique (relevé de terrain, plan, coupe, restitution, dessin d'objet...), document cartographique, photographie, photographie aérienne, image satellitaire, modèle 3D, base de données, système d'information géographique, enregistrement sonore, produit audiovisuel et multimédia (film, vidéo...), échantillons, moulages, maquettes, rapport d'analyse, étude préliminaire, transcription et traduction de textes, guide/note méthodologique, documentation, programme de travail, notes, courriel.</td><td></td><td></td><td>Le tri porte principalement sur les textes préliminaires et illustrations : conserver uniquement la première version soumise. Détruire les épreuves. Documentation, courriel : conserver les documents les plus significatifs.</td></tr><tr><td>2.3. Préparation de publication (ouvrages, article, compte rendu...)</td><td>Durée de la préparation + 5 ans</td><td>T</td><td></td></tr><tr><td>Texte préliminaire, illustration originale, épreuves, documentation préparatoire, compte rendu de réunion et documents afférents, vidéo de visioconférence, convention de collaboration, contrat de recherche, avis des rapporteurs, lettre, courriel.</td><td></td><td></td><td>Le tri porte principalement sur les textes préliminaires et illustrations : conserver uniquement la première version soumise. Détruire les épreuves. Documentation, courriel : conserver les documents les plus significatifs.</td></tr><tr><td>2.4. Congrès, colloque, journée d'étude (organisation ou participation)</td><td>10 ans</td><td>T</td><td></td></tr><tr><td>Support de communication (texte/illustration, slide, vidéo...), résumé, texte et illustration préliminaires des actes, épreuves, poster scientifique, affiche, plaquette, documentation, documents d'organisation (programme, circulaire, résumés des communications...), ordre du jour, compte rendu de réunion et documents afférents, lettre, courriel, copies de documents relatifs à la gestion financière et aux missions.</td><td></td><td></td><td>Le tri porte principalement sur les textes préliminaires et illustrations : conserver uniquement la première version soumise. Détruire les épreuves. Documentation, lettres, courriels : conserver les documents les plus significatifs. Détruire les copies de documents financiers et de missions.</td></tr><tr><td>2.5. Sites Web (carnets de recherche, blogs...)</td><td>Validité</td><td>D</td><td></td></tr><tr><td>Texte de projet, cahier des charges, compte rendu de réunion, texte et illustration préparatoires, courriel.</td><td></td><td></td><td>Depuis 2006, la BNF assurer le dépôt légal de l'internet français.</td></tr></table>
<table>
  <tr>
    <td>2.6. Documentation<br>Photographies, dessins, cartes, enregistrements sonores, produit audiovisuel et multimédia, publications électroniques ou papier, rapport, notes de travail, notes de lecture, courriel, lettre, photothèque, collections de cartes, plans, dessins, collections de référence ou de comparaison (objet fabriqué), base de données.</td>
    <td>Durée d'exploitation + 5 ans</td>
    <td></td>
    <td>Conserver les documents selon l'intérêt. Seule la version finale de la base de données sera conservée. Publications : conserver seulement les textes lorsqu'ils participent à la cohérence scientifique d'un dossier contenant d'autres documents.</td>
  </tr>
  <tr>
    <td>2.7. Médiation scientifique<br>(Exposition, conférence, atelier grand public, émission de radio, émission de télévision, produit pédagogique...) Produit audiovisuel et multimédia (film, vidéo...), podcast, site Web, support de communication (catalogue, livret, programme, affiche, slides de présentation, vidéo...), poster, rushes, master, autorisation, invitation, documentation, courriel, document financier et de mission (copies).</td>
    <td>Durée du projet + 5 ans</td>
    <td>T</td>
    <td>Documentation, courriels : conserver les documents les plus significatifs. Détruire les copies de documents financiers et de missions. Conserver les masters en format compressé ; détruire les rushes et les masters en format non compressé. Les podcasts et sites Web ne sont pas pris en compte.</td>
  </tr>
  <tr>
    <td>2.8. Correspondance<br>boîte aux lettres électronique, lettre.</td>
    <td>10 ans</td>
    <td>T</td>
    <td>Le tri porte sur les courriels : conserver les courriels et pièces jointes selon l'intérêt. Détruire les courriels privés.</td>
  </tr>
  <tr>
    <td>2.9. Enseignement et formation<br>2.9.1. Enseignement dispensé<br>Programme, support de cours (texte/illustration, slide, vidéo...) et documents afférents, plaquette pédagogique, documentation, notes, lettre, courriel.</td>
    <td>10 ans</td>
    <td>T</td>
    <td>Le tri porte sur la documentation, les notes, lettres et courriels : conserver selon l'intérêt.</td>
  </tr>
  <tr>
    <td>2.9.2. Direction et suivi de travaux d'étudiants<br>Travaux d'étudiants (thèses, mémoires), rapport (sur les mémoires et sur les soutenances), procès-verbal de soutenance, convocations, courriel, lettres, notes.</td>
    <td>10 ans</td>
    <td>T</td>
    <td>Travaux d'étudiants : les thèses sont archivées par le CINES (Arrêté du 25 mai 2016 fixant le cadre national de la formation et les modalités conduisant à la délivrance du diplôme national de doctorat, titre IV, art. 24-25). Les mémoires (master 1 et 2) sont archivés par les universités. Toutefois, certains documents peuvent être versés en fonction de l'expertise du chercheur et de leur apport au fonds. D pour les autres documents qui sont gérés par les universités.</td>
  </tr>
  <tr>
    <td>2.9.3. Accueil de chercheurs et de stagiaires<br>Dossier de chercheur invité (candidature (copie), projet de recherche, attestation (copie), rapport scientifique, lettre,</td>
    <td>10 ans</td>
    <td>T</td>
    <td>Conserver les documents scientifiques en fonction de l'expertise du chercheur. Détruire les candidatures, conventions, attestations,</td>
  </tr>
</table>
courriel.

Dossier de stagiaire (convention de stage
(copie), rapport de stage).

lettres, courriels.

Estimated volume of data 5

Unit GB

Start date

End date

Final dispositions

# Datasets for the lithic study in Key Area 4

## Data description and collection or re-use of existing data

### Research output description

Name Datasets for the lithic study in Key Area 4

Description This dataset will be created to record the lithic technology characteristics of LBK and post-LBK sites from Moravia (Czech Republic). It will consist of:

* **A spreadsheet** compiling all studied artifacts, where each row corresponds to a single piece or a batch of pieces. The columns will describe various observed variables, both quantitative and qualitative.

* **A series of photographs** taken at different scales (meso- and microscopic) to illustrate key technical scars.

* **A series of drawings** to visually represent the overall composition of the studied assemblages.

* **Textual** will potentially include reports of the recording, including a description of the assemblage, context of the site and reasoning for the assemblage being selected and R codes of the lithic analysis.

Persistent identifiers will be pursued so that the data can be reliably and efficiently located and referred to. The dataset will be made available online on the **Nakala** platform.

As far as possible, we always favour open and standard formats to encourage data sharing and re-use: spreadsheets in .csv or .txt format; photographs in .tif or .png formats; documents in .pdf or .txt format.

Type Dataset

Workpackage WP2

Keywords

* technologie lithique (Pactols sujets)

* Moravie (Pactols lieux)

* débitage laminaire (Pactols sujets)

Keywords (free-text)

Language eng

Issued Date

May contain personal data? No

Will existing data be reused?
## Justification

The dataset will consist of two types of data:

1. **New data** from sites where no detailed technological studies have been conducted.

2. **Reused data** from research conducted during the postdoctoral projects of Solène Denis. These data may be supplemented with additional variables when necessary. These data have been collected between 2020 and 2024 but are not yet published.

## How new data will be collected or produced?

### Name of the method

Lithic Technology

### Description

The method is based on a technological analysis of lithic industries, aiming to reconstruct the production process chains (*chaîne opératoire*). It incorporates various complementary types of sorting, categorised by raw material and production stage. Data recording is tailored to the quality of information provided by each piece. Finished products will undergo detailed analysis using approximately thirty criteria, while production waste will be documented in batches based on around ten criteria. The practical aspects of the study are adapted to the material's packaging (e.g., marking, storage in pits, by stratigraphic unit) and the study location (e.g., whether the material can be spread out for analysis).

The artefacts are observed with the naked eye or under the microscope if necessary for certain very specific aspects such as preparations for detachment. The pieces and specific elements are measured with an electronic calliper. They are are counted and weighed. All the data are registered in an excel spreadsheet.

Technical scars are described and interpreted through comparisons with experimental data, which are extensively available in the **Technothèque** of UMR 8068.

### Data Nature

Observational data

### Equipments, technical platforms used

* Microscope numérique mobile Dino-Lite AM7915MZT :

* Technothèque of the UMR 8068 lab : https://teknotek.pretech.cnrs.fr/s/fr/page/accueil

## Documentation and data quality

What metadata and documentation (for example way of organising data) will accompany the data?
<table><tr><td>Description</td><td><p>The data will be recorded and stored on the professional laptop of Solène Denis.</p><p>Metadata standards of Dublin Core Metadata Terms (DCMT) will be used. The following metadata will be given for this dataset:</p><ul><li>a <u>lithic data dictionary</u> will be associated with the spreadsheets for the key areas in order to unify the lithic databases. It will include descriptions of codes and the structuring of data as well as drawings for particular features.</li><li>for assemblages with specific documentation of elements and features a <u>spreadsheet for documentation</u> (images and drawings) will be produced</li><li>A <u>readme file</u> will be produced with specific informations about the process of recording and indications of specific aspects (differences in recording etc.)</li><li>a <u>readme file</u> will be produced within the "documentation" folder in order to document specific aspects and problems regarding the existing data for each site</li><li>a <u>readme file</u> will be produced within the "GIS" folder in order to document any custom changes of the data (modifications of points and polygons, addition of columns etc.).</li></ul><p><strong>Naming conventions</strong> of files will be as follows:</p><ul><li>spreadsheets for sites: "mobilit_h_KA4_sitename_YYYY-MM-DD"</li><li>a metadata sheet: "mobilit_h_KA4_lithicdatadictionary_YYYY-MM-DD"</li><li>images of finds: "mobilit_h_KA4_sitename_ID-picture_1"</li><li>drawings of finds: "mobilit_h_KA4_sitename_ID-drawing_1"</li></ul><p>The <strong>folder structure</strong> will be organized in order to be identifiable easily for each site. Versions of data will be archived with their respective date. The hierarchy of folders will be as follows:</p><ul><li>"KAx" (here "KA4")</li><li>"KA4 sites": Contains a spreadsheet with sites for this key area.</li><li>"KA4_CODE_sitename" (e.g., "KA4_THK-01_Thekla")</li><li>"Documentation" (raw data of reports, images, drawings, georeferenced data, readme files),</li><li>"Data" (containing data spreadsheets, readme files and lithic data dictionary)</li><li>"Images"</li><li>"Drawings"</li><li>"Analysis" (containing R codes and files, figures and sketches of refitting, readme file, etc.)</li><li>"GIS" (containing modified shapefiles for each site, on the basis of the raw data, but customized to the research questions, as well as a readme file)</li></ul></td></tr><tr><td>Metadata/data standards</td><td><ul><li>Dublin Core: https://rdamsc.bath.ac.uk/api2/m15</li></ul></td></tr><tr><td>Metadata language code</td><td>eng</td></tr></table>

## What methods will be used to ensure their scientific quality?

<table><tr><td>Description</td><td><p><strong>Data cleaning:</strong> The database will be cleaned with free software, e.g., OpenRefine.</p><p><strong>Peer review of data:</strong> The data will be cross-tested by the lithic research group (Pierre Allard, Lisa Bauer, Solène Denis).</p><p><strong>Data entry validation:</strong> The validation of data will be ensured by using a customized database (in MS Access) with the pre-defined structure of data entries. This can easily be exported as various spreadsheet formats.</p><p><strong>Representation with controlled vocabularies:</strong> This will be achieved by recording in the database and the lithic dictionary file.</p></td></tr></table>

## Legal and ethical requirements, codes of conduct

How will other legal issues, such as intellectual property rights and ownership, be managed? What legislation is applicable?
<table><tr><td>Description</td><td>The project data are public archives within the meaning of the Code du patrimoine, article L211-4. This status was reiterated by the directive issued by CNRS and Archives de France in 2007 (Instruction No. DAF/DPACI/RES/2007/002 of January 15, 2007. Traitement et conservation des archives des délégations du CNRS et des archives des unités de recherche et de service). Public archives are freely accessible, except for information subject to communication deadlines defined by the Code du patrimoine, in article L.213-2.<br/>The disclosure, reuse, and dissemination of public archives that qualify as a work of the mind, as defined by the Code de la propriété intellectuelle, are regulated by the same code. Researchers and teacher-researchers, as public servants, retain their intellectual property rights (article L.111-1 of the Code de la propriété intellectuelle).</td></tr></table>

## What ethical issues and codes of conduct are there, and how will they be taken into account?

<table><tr><td>Description</td><td>The Code de la recherche establishes a link between scientific integrity and the preservation of scientific data, in accordance with the Code du patrimoine. In the long term, the archives department of the MSH Mondes will be responsible for the preservation and regulatory communication of the data, in line with the provisions set out in both codes.</td></tr></table>

## Data processing and analysis

### How and with what resources will the data be processed / analyzed?

<table><tr><td>Description</td><td>Data processing will be carried out primarily in RStudio, using tailored R scripts for the analysis of lithic technology variables. The dataset will first be compiled in .csv format, with each row representing either an individual artifact or a homogeneous batch. Quantitative variables (e.g., dimensions, weight, scar counts) and qualitative descriptors (e.g., raw material, typology, percussion technique) will be encoded following standardized taxonomies to ensure consistency and interoperability.<br/>Processing will follow a structured pipeline:</td></tr></table>

1. **Data Cleaning and Standardisation:** Raw data from spreadsheets will be cleaned (e.g., correction of entry errors, removal of duplicates, standardisation of terminology) and formatted for analysis in R. Descriptive labels will be harmonised using controlled vocabularies.

2. **Exploratory and Descriptive Analysis:** Statistical summaries (e.g., distributions, central tendencies, variance measures) will be computed to describe key characteristics of the lithic assemblages. Batch-level and individual-level data will be treated separately where relevant.

3. **Technological Categorisation:** Based on chaîne opératoire approach, artefacts will be classified into production stages.

4. **Visual Data Integration:** Photographs and drawings will be linked to analytical records through persistent identifiers and file-naming conventions. Images will be processed in standard formats (.tif, .png), and metadata (e.g., scale, object ID, context) will be embedded or referenced in associated documentation.

5. **Comparative and Interpretative Analysis:** Descriptive data will be interpreted in relation to experimental reference collections (Technothèque UMR 8068). Comparative procedures will use qualitative pattern recognition as well as quantitative clustering methods where applicable.

6. **Reproducibility and Sharing:** All R scripts used for data processing and analysis will be documented and deposited alongside the dataset. The full protocol, including criteria definitions, classification logic, and variable descriptions, will be included in the metadata_lithicdatadictionary. Upon publication of the KA 1 results, the dataset, metadata, and code will be deposited on Nakala, ensuring persistent access.
# Storage and backup during the research process

## How will data be stored and backed up during the research?

### Storage needs

During the project, data will be stored and backed up in multiple secure environments to ensure both accessibility and protection against loss:

* **Primary Storage:** Data will be stored on the professional, institutionally managed computer of **Solène Denis**, with access restricted to authorized project personnel.

* **Secondary Backup:** A monthly backup of project data will be saved to a dedicated external hard drive maintained by the project team.

The project's shared workspace on RESANA (a secure platform provided by the French Direction Interministérielle du Numérique - DINUM) will serve as an additional storage and collaboration space. Résana hosts data on nationally managed secured servers, ensuring institutional compliance and reliability.

A ShareDoc (CNRS IN2P3) project-specific file manager for MOBILITH will be set up, with weekly backups, providing robust redundancy and automated version control.

The use of at least three independent storage spaces - local, institutional online, and external managed backup - ensures the ability to recover data in the event of hardware failure, accidental deletion, or other incidents. In case of data loss or corruption, the most recent backup from ShareDoc or the external drive will be restored, with coordination from institutional IT support if needed.

Access to project data during the research phase will be restricted to MOBILITH project members and designated external experts. Controlled access is managed through institutional credentials for Résana and ShareDoc platforms. FileSender, the institutional secure file transfer service, will be used for any sensitive file exchanges between partners, ensuring encrypted transmission.

While the project does not involve highly sensitive personal data, appropriate data protection measures will be observed. In cases where potentially sensitive information is handled (e.g., site locations or unpublished archaeological findings), access will be limited, and data will be pseudonymized or aggregated as appropriate.

Data management and protection practices will comply with institutional and national policies, in alignment with GDPR and best practices for handling research data securely.

Perennial archiving costs are covered by the MSH Mondes archive service (CNRS servers) and, for definitive archiving, by the French National Archives and the Centre informatique national de l'enseignement supérieur (CINES), under the supervision of the Ministry of Higher Education.

The cost of storing and sharing the data that will be made public will be borne by the institutions for which the project participants work (data on portable PCs, by the IR* Huma-Num (storage on Sharedocs and dissemination via the SHS Nakala data warehouse), under the supervision of the CNRS, Aix Marseille University and the Condorcet campus, by the French government's Direction du Numérique (document sharing via the Resana collaborative platform), by CERN for the Zenodo generalist warehouse, and by the Centre de la Communication Scientifique Directe (CCSD) under the supervision of CNRS, INRIA and INRAE for the distribution of open access publications.

Processing will be carried out by those responsible for the research products, using tools already funded by the institutions (e.g. Excel) or free open-source tools such as OpenRefine and Calc, or QGIS.

**Estimated volume of data** 20

**Unit** GB

### Measures taken for data security

Data security will be ensured through a combination of physical, digital, and procedural safeguards. All digital data will be stored on secure, institutionally managed servers with regular automated backups and controlled access based on user roles (see below). Sensitive or unpublished data will be protected by password-restricted folders, and encryption will be used when transferring data between devices or collaborators.

**Resana:**

Resana is hosted in Outscale's SecNumCloud 3DS in data centres in France. The operator is responsible for the availability of the service and for maintaining it in operational and security condition. The integrity and confidentiality of the information circulating are ensured by encryption mechanisms (HTTPS protocol). RESANA is not considered a "critical" service, in the sense of continuity of government action. In nominal mode, the service is available 24/7/365. However, it may be interrupted in the event of a technical incident or maintenance operation. DINUM aims to guarantee a maximum downtime of 4 hours and a maximum data loss time of 24 hours. RESANA is an information system that has been security-approved (RGS) by the qualified authority (Interministerial Digital Directorate) for the sharing of standard data. The information
system takes into account the needs of confidentiality, integrity and availability of the service. All content uploaded to the platform is encrypted (AES 128 bit) and hosted on the Outscale SecNumCloud 3DS with 24/7 facilities management. However, its use is not authorised to convey sensitive information or information marked "Restricted Distribution", in accordance with II901 (NOR: PRMD1503279J).

Cf : https://resana.numerique.gouv.fr/public/utilisateur/afficherPageConnexionAnnexe? page=apropos

## Sharedocs :

ShareDocs is a file manager implemented by IR* Huma-Num, on its own servers, which can be used via a web browser, a WebDAV client or file synchronisation software. The platform is based on the FileRun application. It provides remote online storage on the French research network (similar to tools such as DropBox, which are hosted on the public cloud). Hosted data can be easily encrypted using tools such as ZED encrypt.

ShareDocs is designed for research projects that want to store, exchange, share and work on file-type data (sets of photos, transcribed texts, etc.). For example, ShareDocs can be used to prepare files for online publishing or for distribution in NAKALA.

A ShareDocs project account facilitates data sharing and collaborative work between several members of a project or research team in the social sciences and humanities. The project account is adapted to collaboration via collaborative editing and file versioning tools, as the project account is accessible to several members of a team (unlike an individual account). It allows the creation of a tree structure of folders and it is necessary to define access and editing rights in detail, as soon as they have been created and for a list of identified collaborators. The principle is to create a folder and file tree when a project account is opened, and then to grant different access and editing rights depending on the role of each team member.

For the 2023-2025 forecasts, the volume of a project account is 300 GB of storage.

A project account can only be accessed by a list of people who have been declared and registered with Huma-Num by the project account manager.

The data stored on Sharedocs is hosted and backed up at the IN2P3 computing centre in Lyon, on Huma-Num servers. In the event of data loss, Huma-Num assures us that it will be possible to contact their helpdesk to recover it, via one of its backups.

https://documentation.huma-num.fr/sharedocs-stockage/

## Nakala :

The data deposited in NAKALA is stored on servers managed by Huma-Num and hosted at the IN2P3 computing centre. This centre was set up to manage data produced in particle physics, nuclear physics and astroparticle physics.

This major national centre is secure from a hardware point of view (e.g. redundant power supply, network devices, cooling systems).

NAKALA data is stored on a NAS-type network storage device. A snapshot of the data is taken at regular intervals, enabling data to be restored quickly in the event of problems. In addition, a tape backup is made daily on the CCIN2P3 backup robot using TSM software published by IBM. NAKALA's metadata are stored in a SQL database (MariaDB) which is backed up daily on Huma-Num's infrastructure. The metadata is also exposed in RDF format via a Triple-Store (GraphDB) which is also backed up daily on the Huma-Num infrastructure. Continuity of the NAKALA¶ service

The NAKALA service is hosted on the Huma-Num infrastructure, which has a general disaster recovery plan. More specifically, the redundancy of the NAKALA service is ensured by :

- the NAKALA application is redundant on two different machines using a distribution tool (HAProxy), which avoids service interruptions in the event of a breakdown;

- the data is stored on a NAS-type device, so that data can be restored quickly. In addition, backups are made on magnetic tapes on a daily basis;

- Metadata is stored in a 'classic' relational database, which is backed up daily. This metadata is also stored in RDF format in a Triple-Store, which is backed up daily.

Source : https://documentation.huma-num.fr/nakala-faq/#comment-sont-sauvegardees-les-donnees

## PAC CINES :

The long-term archiving platform at CINES - PAC v3.0 has been in production since 2008. Capacity: 300 TB on 2 DELL storage bays of 150 TB each.

Arcsys archiving software (Infotel), Redundant virtualised architecture with 2 PowerEdge R730 hypervisors, 2 IBM TS-3500 tape libraries, with LTO4 and JAGUAR drives (use adapted to requirements), 1 Fiber channel interconnection network. cf https://www.cines.fr/ressources/
## How will data be shared?

### Modalities of sharing

The data will be stored in open and widely used formats to promote interoperability and sustainability. If any proprietary or non-standard formats are required due to specific research tools or instruments, a corresponding open version or export (when possible) will also be provided.

The CC-BY licensed datasets will be stored in the Nakala repository for the humanities and social sciences and will be assigned a persistent identifier (Datacite Digital Object Identifier). The Nakala data repository is managed by the French research infrastructure IR* Huma-Num, under the supervision of the French National Centre for Scientific Research, Aix-Marseille University and the Condorcet Campus.

The Dublin Core metadata Terms Vocabulary (ISO 15836) that must be entered in Nakala includes the type of data, the title, the author(s), the creation date and the licence associated with the dataset. It is possible to add additional metadata (qualified Dublin Core). Keywords (filled in using the PACTOLS interoperable multilingual thesaurus for Archaeology), language and a description of each dataset will be filled in. A readme file will be associated with each dataset deposited in the Nakala repository. The datasets will be "harvested" by the Isidore search engine and OpenAire Explore, and thus easily findable and accessible.

All datasets will be made available under a **Creative Commons Attribution (CC BY)** license, allowing broad reuse with appropriate credit. In cases involving sensitive or restricted data (e.g., personal data requiring anonymization), access may be restricted to specific user groups or require a data sharing agreement. Measures will be taken to minimize restrictions, including data anonymization and the provision of aggregated or de-identified versions where applicable. Data will be made available within a reasonably short period after the conclusion of the project, or at the time of any related publication, whichever comes first. This allows time for quality assurance, documentation, and the preparation of metadata.

The datasets will be particularly relevant to researchers focusing on lithic technology in Central Europe. The data may be used for comparative analyses, technological studies and regional syntheses, but also for developing and testing methodological frameworks in lithic analysis.

### Reusability

The data produced during this project can be reused in future research to support further analysis, validation, or new investigations.

### Data repository/catalogs

* Nakala: https://cat.opidor.fr/index.php/Nakala (CoSO)

## How will data be long-term preserved? Which data?

### Justification

The long-term preservation of the lithic technology dataset is essential due to its scientific, cultural, and methodological value. First, the dataset documents unique prehistoric technological traditions across Belgium, the Netherlands, and the German Rhineland, offering a valuable reference for future archaeological, anthropological, and heritage research. Given the irreversible nature of excavation and the potential inaccessibility of physical collections over time (due to curation limitations or degradation), the digital dataset serves as a crucial record of primary observations.

Moreover, the dataset is structured to support **comparative studies**, including re-analysis and replication of the chaîne opératoire-based research. Preserving it ensures that future scholars can engage with the material using updated methods or in light of new discoveries. The use of open, standard formats (.csv, .tif, .txt) and rich metadata makes it interoperable and suitable for reuse across disciplines and platforms.

Finally, as archaeological research is increasingly data-driven, long-term preservation supports transparency, reproducibility, and open science. It aligns with international best practices in data stewardship and fulfills ethical obligations to safeguard irreplaceable scientific information for future generations.

The precise data selection and archiving process will be developed in close collaboration with the archives department of MSH Mondes.

In accordance with the Code of Heritage, the archives produced by the UMRs within the scope of UAR3225 are managed by the archives department of MSH Mondes. At the end of the research project, the documents and data produced will be transferred to the archives department. Indeed, the department is responsible for managing the public, administrative, and scientific archives of the units at MSH Mondes, from their production (current archives)
throughout their entire conservation period after transfer (intermediate archives), regardless of their format (textual, graphic, photographic documents, etc.) and their medium (physical documents, electronic documents) (address: https://www.mshmondes.cnrs.fr/accompagnement/archives).

Once transferred, these data are classified, described, and inventoried. The inventory is published online (address: https://archives.mshmondes.cnrs.fr), and the archives are accessible to anyone who requests them, in compliance with the rules set out in the Code of Heritage and the Code of Intellectual Property.

A selection and, if necessary, regulatory destruction of the archives are carried out based on their administrative usefulness and scientific interest, with the approval of the Interministerial Archives Service of France (SIAF).

These operations are governed by a management table established in line with administrative and scientific needs. Finally, according to a schedule defined in agreement with the National Archives and the needs of the research, the project archives will, ultimately, be transferred to the National Archives for permanent conservation.

Extract of the Archive Department's management table :

<table><thead><tr><th>Activités et documents</th><th>DUA</th><th>Sort final</th><th>Observations</th></tr></thead><tbody><tr><td><strong>1. Direction d'équipe</strong></td><td></td><td></td><td></td></tr><tr><td><strong>1.1. Réunions internes et séminaires</strong><br>Ordre du jour, compte rendu de réunion et documents afférents, programme, support de présentation (texte, slide, vidéo...).</td><td>10 ans</td><td>C</td><td></td></tr><tr><td><strong>1.2. Suivi de l'activité des membres</strong><br>Dossier de membre (projet scientifique, rapport, attestation, demande de bourse), note interne.</td><td>10 ans</td><td>C</td><td></td></tr><tr><td><strong>2. Recherche</strong></td><td></td><td></td><td></td></tr><tr><td><strong>2.1. Programme/projet</strong> Le programme/projet peut être financé par des organismes extérieurs à l'unité (ANR, Labex, ministère des Affaires étrangères...) ou ne pas être financé. Le programme/projet génère des documents/données issus des activités scientifiques listées en 3.2-3.10.</td><td></td><td></td><td>Le programme/projet peut être financé par des organismes extérieurs à l'unité (ANR, Labex, ministère des Affaires étrangères...) ou ne pas être financé. Le programme/projet génère des documents/données issus des activités scientifiques listées en 3.2-3.10.</td></tr><tr><td><strong>2.1.1. Direction et gestion</strong></td><td></td><td></td><td></td></tr><tr><td><strong>Direction des activités</strong><br>Appel d'offres, appel à projet, texte de projet, dossier de candidature (accepté ou refusé), rapport d'activité, versions préliminaires (dossier de candidature, rapport), contrat de recherche, convention de collaboration, protocole d'accord, charte de sécurité, autorisation, permis, programme de travail, note d'information, plan de gestion de données, planning, agenda, lettre, courriel.</td><td>Durée du projet scientifique + 5 ans</td><td>T</td><td>Détruire les versions préliminaires (rapport, projet). Conserver les courriels les plus significatifs.</td></tr></tbody></table>
<table><tr><td>Gestion financière</td><td></td><td></td><td></td></tr><tr><td>Gestion par le responsable de projet</td><td></td><td></td><td></td></tr><tr><td>Budget prévisionnel, budget réalisé, notification de crédits, facture, justificatif de dépenses, bilan des dépenses, relevé de compte, attestation, lettre, courriel.</td><td>10 ans</td><td>D</td><td>C'est le cas par exemple des missions archéologiques françaises à l'étranger. Les budgets et les bilans de dépenses sont éliminés car ils figurent dans les rapports.</td></tr><tr><td>Gestion par l'unité ou une autre institution</td><td></td><td></td><td></td></tr><tr><td>Budget prévisionnel, budget réalisé, notification de crédits, facture, justificatif de dépenses, bilan des dépenses, relevé de compte, attestation, courriel.</td><td>Validité</td><td>D</td><td>Les documents sont des copies. Les documents originaux sont archivés par la cellule gestion financière de l'unité ou de l'institution.</td></tr><tr><td>Gestion des personnels (CDD, stagiaires)</td><td></td><td></td><td></td></tr><tr><td>Gestion par le responsable de projet</td><td></td><td></td><td></td></tr><tr><td>CV, lettre de motivation, bulletin d'inscription, attestation, convention de stage (copie), demande et ordre de mission (copie), demande de visa (copie), document relatif aux assurances (copie), courriel.</td><td>10 ans</td><td>D</td><td></td></tr><tr><td>Gestion par l'unité ou autre institution</td><td></td><td></td><td></td></tr><tr><td>CV, lettre de motivation, contrat (copie), convention de stage (copie), documents relatifs aux missions (copies), courriel.</td><td>Validité</td><td>D</td><td>Les documents sont des copies. Les documents originaux sont archivés par la cellule gestion financière de l'unité ou de l'institution.</td></tr><tr><td>Gestion de locaux, d'équipement</td><td></td><td></td><td></td></tr><tr><td>Inventaire d'équipement, documents d'organisation de la vie quotidienne, documentation technique, documents relatifs à la gestion et à l'entretien de véhicule, documents relatifs à la location de locaux.</td><td>10 ans</td><td>T</td><td>Cette rubrique concerne par exemple les missions archéologiques françaises à l'étranger. Détruire les documents relatifs à la gestion et à l'entretien de véhicule et la documentation technique. Conserver les inventaires d'équipement et les documents d'organisation de</td></tr></table>
<table><tr><td>2.1.2. Participation (documents de gestion)<br/>Texte de projet, rapport, programme de travail, notes, courriel.</td><td>Durée du projet scientifique + 5 ans</td><td>T</td><td>La vie quotidienne.<br/>Les tri porte sur les notes et les courriels : conserver selon l'intérêt.</td></tr><tr><td>2.1.3. Réunions scientifiques internes (équipe projet, partenaires)<br/>Ordre du jour, compte rendu de réunion et documents afférents, programme, support de présentation (texte, slide, vidéo...).</td><td>Durée du projet scientifique + 5 ans</td><td>C</td><td></td></tr><tr><td>2.2. Collecte et analyse de documents/données<br/>Carnet/cahier/journal de terrain, notes d'enquête, notes d'entretien, transcription d'entretien oral, guide d'entretien, questionnaire, fichier d'enregistrement, fiches individuelles, inventaire, document graphique (relevé de terrain, plan, coupe, restitution, dessin d'objet...), document cartographique, photographie, photographie aérienne, image satellitaire, modèle 3D, base de données, système d'information géographique, enregistrement sonore, produit audiovisuel et multimédia (film, vidéo...), échantillons, moulages, maquettes, rapport d'analyse, étude préliminaire, transcription et traduction de textes, guide/note méthodologique, documentation, programme de travail, notes, courriel.</td><td>Durée du projet scientifique + 5 ans</td><td>T</td><td>Il s'agit de tout type de données (issues de fouilles archéologiques, d'une enquête sociologique, historique, géographique...) quelles que soient leurs formes (textes, images, sons...) et leurs supports. Lorsqu'il y a obligation de gestion des archives intermédiaires au sein d'un autre service, les documents/données ne sont pas pris en compte (par exemple, pour l'archéologie, les services régionaux de l'archéologie, l'Ecole française d'Athènes...). Conserver la version achevée des documents. Certaines versions préparatoires peuvent être conservées en fonction de l'expertise du chercheur. Conserver les masters en format compressé ; détruire les rushes et les masters en format non compressé.</td></tr><tr><td>2.3. Préparation de publication (ouvrages, article, compte rendu...)<br/>Texte préliminaire, illustration originale, épreuves, documentation préparatoire, compte rendu de réunion et documents afférents, vidéo de visioconférence, convention de collaboration, contrat de recherche, avis des rapporteurs, lettre, courriel.</td><td>Durée de la préparation + 5 ans</td><td>T</td><td>Le tri porte principalement sur les textes préliminaires et illustrations : conserver uniquement la première version soumise. Détruire les épreuves. Documentation, courriel : conserver les documents les plus significatifs.</td></tr><tr><td>2.4. Congrès, colloque, journée d'étude (organisation ou participation)<br/>Support de communication (texte/illustration, slide, vidéo...), résumé, texte et illustration préliminaires des actes, épreuves, poster scientifique, affiche, plaquette, documentation, documents d'organisation (programme, circulaire, résumés des communications...), ordre du jour, compte rendu de réunion et documents afférents, lettre, courriel, copies de documents relatifs à la gestion financière et aux</td><td>10 ans</td><td>T</td><td>Le tri porte principalement sur les textes préliminaires et illustrations : conserver uniquement la première version soumise. Détruire les épreuves. Documentation, lettres, courriels : conserver les documents les plus significatifs. Détruire les copies de documents financiers et de missions.</td></tr></table>
<table><tr><td>missions.</td><td></td><td></td><td></td></tr><tr><td>2.5. Sites Web (carnets de recherche, blogs...)</td><td></td><td></td><td></td></tr><tr><td>Texte de projet, cahier des charges, compte rendu de réunion, texte et illustration préparatoires, courriel.</td><td>Validité</td><td>D</td><td>Depuis 2006, la BNF assurer le dépôt légal de l'internet français.</td></tr><tr><td>2.6. Documentation</td><td></td><td></td><td></td></tr><tr><td>Photographies, dessins, cartes, enregistrements sonores, produit audiovisuel et multimédia, publications électroniques ou papier, rapport, notes de travail, notes de lecture, courriel, lettre, photothèque, collections de cartes, plans, dessins, collections de référence ou de comparaison (objet fabriqué), base de données.</td><td>Durée d'exploitation + 5 ans</td><td>T</td><td>Conserver les documents selon l'intérêt. Seule la version finale de la base de données sera conservée. Publications : conserver seulement les textes lorsqu'ils participent à la cohérence scientifique d'un dossier contenant d'autres documents.</td></tr><tr><td>2.7. Médiation scientifique</td><td></td><td></td><td></td></tr><tr><td>(Exposition, conférence, atelier grand public, émission de radio, émission de télévision, produit pédagogique...) Produit audiovisuel et multimédia (film, vidéo...), podcast, site Web, support de communication (catalogue, livret, programme, affiche, slides de présentation, vidéo...), poster, rushes, master, autorisation, invitation, documentation, courriel, document financier et de mission (copies).</td><td>Durée du projet + 5 ans</td><td>T</td><td>Documentation, courriels : conserver les documents les plus significatifs. Détruire les copies de documents financiers et de missions. Conserver les masters en format compressé ; détruire les rushes et les masters en format non compressé. Les podcasts et sites Web ne sont pas pris en compte.</td></tr><tr><td>2.8. Correspondance</td><td></td><td></td><td></td></tr><tr><td>boîte aux lettres électronique, lettre.</td><td>10 ans</td><td>T</td><td>Le tri porte sur les courriels : conserver les courriels et pièces jointes selon l'intérêt. Détruire les courriels privés.</td></tr><tr><td>2.9. Enseignement et formation</td><td></td><td></td><td></td></tr><tr><td>2.9.1. Enseignement dispensé</td><td></td><td></td><td></td></tr><tr><td>Programme, support de cours (texte/illustration, slide, vidéo...) et documents afférents, plaquette pédagogique, documentation, notes, lettre, courriel.</td><td>10 ans</td><td>T</td><td>Le tri porte sur la documentation, les notes, lettres et courriels : conserver selon l'intérêt.</td></tr><tr><td>2.9.2. Direction et suivi de travaux d'étudiants</td><td></td><td></td><td></td></tr><tr><td>Travaux d'étudiants (thèses, mémoires), rapport (sur les mémoires et sur les soutenances), procès-verbal de soutenance, convocations, courriel, lettres, notes.</td><td>10 ans</td><td>T</td><td>Travaux d'étudiants : les thèses sont archivées par le CINES (Arrêté du 25 mai 2016 fixant le cadre national de la formation et les modalités conduisant à la délivrance du diplôme national de doctorat, titre IV, art. 24-25). Les mémoires (master 1 et 2) sont archivés par les universités. Toutefois, certains documents peuvent être versés en fonction de l'expertise du chercheur et de leur apport au fonds. D pour les autres documents</td></tr></table>
<table><tr><td>2.9.3. Accueil de chercheurs et de stagiaires</td><td></td><td></td><td>qui sont gérés par les universités.</td></tr><tr><td>Dossier de chercheur invité (candidature (copie), projet de recherche, attestation (copie), rapport scientifique, lettre, courriel.</td><td>10 ans</td><td>T</td><td>Conserver les documents scientifiques en fonction de l'expertise du chercheur. Détruire les candidatures, conventions, attestations, lettres, courriels.</td></tr><tr><td>Dossier de stagiaire (convention de stage (copie), rapport de stage).</td><td></td><td></td><td></td></tr></table>

Estimated volume of data 5

Unit GB

Start date

End date

Final dispositions

# Results of the Experimentation

## Data description and collection or re-use of existing data

### Research output description
<table><tr><td>Name</td><td>Results of the Experimentation</td></tr><tr><td>Description</td><td>The experiments that will take place as part of the ANR MOBILITH programme will aim to document the different ways in which indirect percussion can be applied.<br/>Various documents will be added to this dataset:<ul><li>Reports of experiments</li><li>Documentation of the knapping tools, knappers/participants and gestures involved in the knapping process (positioning, number of people involved, etc.)</li><li>Short video documentation of gestures</li><li>Images at different scales</li><li>Grid for the interpretation of technical scars</li></ul>Persistent identifiers will be pursued so that the data can be reliably and efficiently located and referred to. The dataset will be added to the UMR8068 Technothèque and a representative selection will be made available online on the Nakala platform.<br/>As far as possible, we always favour open and standard formats to encourage data sharing and re-use: spreadsheets in .csv or .txt format; photographs in .tif or .png formats; documents in .pdf or .txt format; videos in .mkv format.</td></tr><tr><td>Type</td><td>Dataset</td></tr><tr><td>Workpackage</td><td>WP1</td></tr><tr><td>Keywords</td><td><ul><li>archéologie expérimentale (Pactols sujets)</li></ul></td></tr><tr><td>Keywords (free-text)</td><td></td></tr><tr><td>Language</td><td>eng</td></tr><tr><td>Issued Date</td><td></td></tr><tr><td>May contain personal data?</td><td>Yes</td></tr><tr><td>May contain sensible data?</td><td>Yes</td></tr><tr><td>May take ethical issues into account?</td><td>Yes</td></tr><tr><td>Will existing data be reused?</td><td></td></tr><tr><td>Justification</td><td>This work package will mostly create new data. For comparison purposes, we may use existing data from the Technothèque (UMR 8068).</td></tr><tr><td>Reused data</td><td><ul><li>Data from the Technothèque : https://teknotek.pretech.cnrs.fr/s/fr/page/accueil#</li></ul></td></tr></table>

How new data will be collected or produced?
<table><tr><td>Name of the method</td><td>Experimental Archaeology</td></tr><tr><td>Description</td><td>In this work package, data collection is conducted through experimental archaeology, specifically the controlled reproduction of prehistoric knapping techniques. This method involves systematically replicating stone tool production processes to better understand the technological, functional, and behavioural aspects of past human activities. The experimental approach enables the creation of a reference collection of lithic artefacts and by-products, which serve as comparative material for archaeological assemblages. All experiments are carefully documented, including the selection of raw materials, tool use, reduction sequences, and resultant debris. These reference datasets are essential for identifying diagnostic features of knapping techniques in archaeological contexts and contribute to a standardised framework for lithic analysis.<br/>Data will be produced by replicating blade debitage conducted by indirect percussion. The gestures will be filmed and photographed. The pieces produced will be described using the naked eye and a binocular microscope. The data will be gathered in a database (.csv) alongside a catalogue of macro- and microtraces (pictures).</td></tr><tr><td>Data Nature</td><td>Experimental data</td></tr></table>

## Documentation and data quality

What metadata and documentation (for example way of organising data) will accompany the data?
<table><tr><td>Description</td><td><p><strong>The data</strong> will be recorded and stored on the professional laptop of Solène Denis, Pierre Allard and Lisa Bauer.</p><p>Data generated through experimental knapping will be systematically organized to ensure consistency, accessibility, and long-term usability. Each experimental sequence will be assigned a unique identifier, linked to detailed metadata. All artefact and associated by-product will be assigned a unique identifier which enables the connection between experimental sequence and its products. Data will be structured in standardised spreadsheets. Visual documentation such as high-resolution photographs, 3D scans (if successful), and videos of knapping sequences will be catalogued and referenced with standardised filenames and metadata. Comprehensive documentation, including a data dictionary, controlled vocabularies, and protocols for data collection and analysis, will accompany the datasets to ensure transparency and reproducibility. All records will be stored in open, non-proprietary formats (e.g., CSV, JPEG, MKV) to support long-term preservation and interoperability.</p><p><strong>Metadata</strong> standards of Dublin Core Metadata Terms (DCMT) will be used. The following metadata will be given for this dataset, in English:</p><ul><li><strong>Metadata for each experimental sequence</strong>: Date of experiment, knapper/participants, knapping tools involved, raw material, block volume etc.</li><li><strong>Metadata for each artefact produced during the experiment</strong>: raw material type, reduction method, experimental parameters, and participant details.</li><li><strong>Metadata for the produced images and videos produced for each experimental sequence.</strong></li><li><strong>A readme file</strong> will be produced with specific informations about the process of recording and indications of specific aspects (differences in recording etc.).</li><li>protocols for data collection.</li></ul><p><strong>Naming conventions</strong> of files will be as follows:</p><ul><li>spreadsheets of experimental sequences: "mobilitih_EXP_YYYY-MM-DD"</li><li>spreadsheets for artefacts of one experimental sequence: "mobilitih_EXP_x_artefacts_YYYY-MM-DD"</li><li>spreadsheets of image files of the experiment: "mobilitih_EXP_x_images_YYYY-MM-DD"</li><li>spreadsheets of the images of the artefacts resulting from an experiment: "mobilitih_EXP_x_artefact_images_YYYY-MM-DD"</li><li>spreadsheets of videos from each experiment: "mobilitih_EXP_x_videos_YYYY-MM-DD"</li><li>a metadata sheet: "mobilitih_WP1_lithicdatadictionary_YYYY-MM-DD"</li><li>images of the experiment: "mobilitih_EXP_x_image_ID"</li><li>images of artefacts: "mobilitih_EXP_x_artefactID_image_ID"</li><li>videos of experiments: "mobilitih_EXP_xvideo_ID"</li></ul><p>The folder structure will be organized in order to be identifiable easily for each site. Versions of data will be archived with their respective date. The hierarchy of folders will be as follows:</p><ul><li>"WP1"</li><li>Contains the spreadsheet of experimental sequences.</li><li>"EXP_x": Contains all data linked to one experimental sequence.</li><li>"Documentation" (protocols of data collection, spreadsheet with image IDs, metadata and readme file),</li><li>"Images"</li><li>"Videos"</li><li>"Artefacts" (containing data spreadsheets of the artefacts, as well as images of them)</li><li>"Analysis" (containing R codes and files, figures and sketches of the experimental parameters, readme file, etc.)</li></ul></td></tr><tr><td>Metadata/data standards</td><td><ul><li>Dublin Core: https://rdamsc.bath.ac.uk/api2/m15</li></ul></td></tr><tr><td>Metadata language code</td><td>eng</td></tr><tr><td>Documentation software</td><td></td></tr></table>

What methods will be used to ensure their scientific quality?
<table><thead><tr><td>Description</td><td>To ensure the integrity and reliability of the data, rigorous quality control procedures will be applied throughout the data lifecycle. Experimental protocols will be standardised and documented in advance to minimise variation between trials and practitioners. Data entry will follow controlled templates with predefined fields to reduce inconsistencies and errors. Cross-checks will be routinely performed to validate the accuracy of recorded measurements, observations, and metadata against physical artefacts and photographic records. Visual media will be reviewed for clarity, resolution, and correct labelling. Any anomalies or deviations from expected procedures will be recorded and flagged in the dataset. Peer review of selected experiments and datasets by other researchers within the UMR TEMPS team will serve as an additional layer of verification. Version control systems will be employed to track changes to digital files and ensure traceability of all modifications.</td></tr></thead></table>

## Legal and ethical requirements, codes of conduct

If personal data are processed, how will compliance with legislation on personal data and on security be ensured?

<table><thead><tr><td>Description</td><td>This work package involves the collection of limited personal data, specifically names, and in some cases age, years of experience, and gender of participants (e.g., specialists or contributors to lithic analysis). These data will be processed in accordance with the General Data Protection Regulation (GDPR) and relevant national laws and institutional policies.<br>All individuals whose personal data are collected will provide informed consent for the use, preservation, and, where applicable, sharing of their data. Consent forms will clearly outline the scope of data use, the purposes of processing, and the rights of participants, including the right to withdraw consent at any time.<br>Where possible, personal identifiers will be removed to ensure that the data used for publication or sharing are fully anonymised. If retaining certain personal attributes (e.g., years of experience or gender) is necessary for research value, data will be pseudonymised, with identifying information stored securely and separately. This allows for controlled internal use while protecting individual identities in publicly shared datasets.<br>All files containing personal data will be encrypted and stored on secure, access-controlled platforms (e.g., RESANA and ShareDoc). The encryption keys will be stored separately and access will be restricted to designated members of the research team. Data stored locally will be password-protected and in compliance with institutional IT security protocols.<br>Personal data will not be included in publicly shared datasets. Access to the identifiable data will be limited to authorized personnel within the project team. If any request for access to personal data is made (e.g., for replication or follow-up research), it will be evaluated through a managed access procedure, subject to ethical approval and additional consent if required.</td></tr></thead></table>

How will other legal issues, such as intellectual property rights and ownership, be managed? What legislation is applicable?

<table><thead><tr><td>Description</td><td>The project data are public archives within the meaning of the Code du patrimoine, article L211-4. This status was reiterated by the directive issued by CNRS and Archives de France in 2007 (Instruction No. DAF/DPACI/RES/2007/002 of January 15, 2007. Traitement et conservation des archives des délégations du CNRS et des archives des unités de recherche et de service). Public archives are freely accessible, except for information subject to communication deadlines defined by the Code du patrimoine, in article L.213-2.<br>The disclosure, reuse, and dissemination of public archives that qualify as a work of the mind, as defined by the Code de la propriété intellectuelle, are regulated by the same code. Researchers and teacher-researchers, as public servants, retain their intellectual property rights (article L.111-1 of the Code de la propriété intellectuelle).</td></tr></thead></table>

What ethical issues and codes of conduct are there, and how will they be taken into account?
**Description**
The Code de la recherche establishes a link between scientific integrity and the preservation of scientific data, in accordance with the Code du patrimoine. In the long term, the archives department of the MSH Mondes will be responsible for the preservation and regulatory communication of the data, in line with the provisions set out in both codes.

## Data processing and analysis

**How and with what resources will the data be processed / analyzed?**

**Description**
Data processing will follow standardised protocols designed to ensure consistency, traceability, and analytical utility. Raw data collected during experimental knapping sessions—such as measurements, observational notes, and media files—will first be cleaned to correct errors, fill missing values where appropriate, and ensure coherence across datasets. Quantitative data (e.g., dimensions, scar patterns) will be normalised and formatted for statistical analysis (conducted under RStudio), while qualitative observations will be coded using predefined criteria to facilitate comparison and pattern recognition. All artefacts will be catalogued and digitally linked to their corresponding metadata, including experimental context and toolmaker actions. Visual data (photos, 3D scans, video) will be processed using standardised workflows for editing, compression, and file naming to ensure uniformity. Documentation of all processing steps, including software used, parameter settings, and data transformation rules, will be maintained to support transparency and reproducibility. We will comply with the GDPR and pseudonymise or anonymise the data in datasets that might include personal information regarding the knappers.

## Storage and backup during the research process

**How will data be stored and backed up during the research?**

**Storage needs**
During the project, data will be stored and backed up in multiple secure environments to ensure both accessibility and protection against loss:

* **Primary Storage:** Data will be stored on the professional, institutionally managed computer of **Solène Denis and Lisa Bauer**, with access restricted to authorized project personnel.

* **Secondary Backup:** A **monthly backup** of project data will be saved to a dedicated **external hard drive** maintained by the project team.

The project's shared workspace on RESANA (a secure platform provided by the French Direction Interministérielle du Numérique - DINUM) will serve as an additional storage and collaboration space. Résana hosts data on nationally managed secured servers, ensuring institutional compliance and reliability.

A ShareDoc (CNRS IN2P3) project-specific file manager for MOBILITH will be set up, with weekly backups, providing robust redundancy and automated version control.

The use of at least three independent storage spaces - local, institutional online, and external managed backup - ensures the ability to recover data in the event of hardware failure, accidental deletion, or other incidents. In case of data loss or corruption, the most recent backup from ShareDoc or the external drive will be restored, with coordination from institutional IT support if needed.

Access to project data during the research phase will be restricted to MOBILITH project members and designated external experts. Controlled access is managed through institutional credentials for Résana and ShareDoc platforms. FileSender, the institutional secure file transfer service, will be used for any sensitive file exchanges between partners, ensuring encrypted transmission.

While the project does not involve highly sensitive personal data, appropriate data protection measures will be observed. In cases where potentially sensitive information is handled (e.g.,
personal data of participants in the experiments), access will be limited, and data will be pseudonymized or aggregated as appropriate.

Data management and protection practices will comply with institutional and national policies, in alignment with GDPR and best practices for handling research data securely.

Perennial archiving costs are covered by the MSH Mondes archive service (CNRS servers) and, for definitive archiving, by the French National Archives and the Centre informatique national de l'enseignement supérieur (CINES), under the supervision of the Ministry of Higher Education.

The cost of storing and sharing the data that will be made public will be borne by the institutions for which the project participants work (data on portable PCs, by the IR* Huma-Num (storage on Sharedocs and dissemination via the SHS Nakala data warehouse), under the supervision of the CNRS, Aix Marseille University and the Condorcet campus, by the French government's Direction du Numérique (document sharing via the Resana collaborative platform), by CERN for the Zenodo generalist warehouse, and by the Centre de la Communication Scientifique Directe (CCSD) under the supervision of CNRS, INRIA and INRAE for the distribution of open access publications.

Processing will be carried out by those responsible for the research products, using tools already funded by the institutions (e.g. Excel) or free open-source tools such as OpenRefine and Calc, or QGIS.

**Estimated volume of data**

50

**Unit**

GB

**Measures taken for data security**

Data security will be ensured through a combination of physical, digital, and procedural safeguards. All digital data will be stored on secure, institutionally managed servers with regular automated backups and controlled access based on user roles (see below). Sensitive or unpublished data will be protected by password-restricted folders, and encryption will be used when transferring data between devices or collaborators.

**Resana :**

Resana is hosted in Outscale's SecNumCloud 3DS in data centres in France. The operator is responsible for the availability of the service and for maintaining it in operational and security condition. The integrity and confidentiality of the information circulating are ensured by encryption mechanisms (HTTPS protocol). RESANA is not considered a "critical" service, in the sense of continuity of government action. In nominal mode, the service is available 24/7/365. However, it may be interrupted in the event of a technical incident or maintenance operation. DINUM aims to guarantee a maximum downtime of 4 hours and a maximum data loss time of 24 hours. RESANA is an information system that has been security-approved (RGS) by the qualified authority (Interministerial Digital Directorate) for the sharing of standard data. The information system takes into account the needs of confidentiality, integrity and availability of the service. All content uploaded to the platform is encrypted (AES 128 bit) and hosted on the Outscale SecNumCloud 3DS with 24/7 facilities management. However, its use is not authorised to convey sensitive information or information marked "Restricted Distribution", in accordance with II901 (NOR: PRMD1503279J).

Cf : https://resana.numerique.gouv.fr/public/utilisateur/afficherPageConnexionAnnexe?page=apropos

**Sharedocs :**

ShareDocs is a file manager implemented by IR* Huma-Num, on its own servers, which can be used via a web browser, a WebDAV client or file synchronisation software. The platform is based on the FileRun application. It provides remote online storage on the French research network (similar to tools such as DropBox, which are hosted on the public cloud). Hosted data can be easily encrypted using tools such as ZED encrypt.

ShareDocs is designed for research projects that want to store, exchange, share and work on file-type data (sets of photos, transcribed texts, etc.). For example, ShareDocs can be used to prepare files for online publishing or for distribution in NAKALA.

A ShareDocs project account facilitates data sharing and collaborative work between several members of a project or research team in the social sciences and humanities. The project account is adapted to collaboration via collaborative editing and file versioning tools, as the project account is accessible to several members of a team (unlike an individual account). It allows the creation of a tree structure of folders and it is necessary to define access and editing rights in detail, as soon as they have been created and for a list of identified collaborators. The principle is to create a folder and file tree when a project account is opened, and then to grant different access and editing rights depending on the role of each team member.

For the 2023-2025 forecasts, the volume of a project account is 300 GB of storage.

A project account can only be accessed by a list of people who have been declared and registered with Huma-Num by the project account manager.

The data stored on Sharedocs is hosted and backed up at the IN2P3 computing centre in Lyon, on Huma-Num servers. In the event of data loss, Huma-Num assures us that it will be possible to contact their helpdesk to recover it, via one of its backups.

https://documentation.huma-num.fr/sharedocs-stockage/

**Nakala :**

The data deposited in NAKALA is stored on servers managed by Huma-Num and hosted at the
IN2P3 computing centre. This centre was set up to manage data produced in particle physics, nuclear physics and astroparticle physics.

This major national centre is secure from a hardware point of view (e.g. redundant power
supply, network devices, cooling systems).

NAKALA data is stored on a NAS-type network storage device. A snapshot of the data is taken at regular intervals, enabling data to be restored quickly in the event of problems. In addition, a tape backup is made daily on the CCIN2P3 backup robot using TSM software published by IBM. NAKALA's metadata are stored in a SQL database (MariaDB) which is backed up daily on Huma-Num's infrastructure. The metadata is also exposed in RDF format via a Triple-Store (GraphDB) which is also backed up daily on the Huma-Num infrastructure. Continuity of the NAKALA¶ service

The NAKALA service is hosted on the Huma-Num infrastructure, which has a general disaster recovery plan. More specifically, the redundancy of the NAKALA service is ensured by :

- the NAKALA application is redundant on two different machines using a distribution tool (HAProxy), which avoids service interruptions in the event of a breakdown;

- the data is stored on a NAS-type device, so that data can be restored quickly. In addition, backups are made on magnetic tapes on a daily basis;

- Metadata is stored in a 'classic' relational database, which is backed up daily. This metadata is also stored in RDF format in a Triple-Store, which is backed up daily.

Source : https://documentation.huma-num.fr/nakala-faq/#comment-sont-sauvegardees-les-donnees

PAC CINES :

The long-term archiving platform at CINES - PAC v3.0 has been in production since 2008.
Capacity: 300 TB on 2 DELL storage bays of 150 TB each.

Arcsys archiving software (Infotel), Redundant virtualised architecture with 2 PowerEdge R730 hypervisors, 2 IBM TS-3500 tape libraries, with LTO4 and JAGUAR drives (use adapted to requirements), 1 Fiber chanel interconnection network. cf https://www.cines.fr/ressources/

Data sharing and long-term preservation

How will data be shared?
## Modalities of sharing

The data will be stored in open and widely used formats to promote interoperability and sustainability. If any proprietary or non-standard formats are required due to specific research tools or instruments, a corresponding open version or export (when possible) will also be provided.

The CC-BY licensed datasets will be stored in the Nakala repository for the humanities and social sciences and will be assigned a persistent identifier (Datacite Digital Object Identifier). The Nakala data repository is managed by the French research infrastructure IR* Huma-Num, under the supervision of the French National Centre for Scientific Research, Aix-Marseille University and the Condorcet Campus.

The Dublin Core metadata Terms Vocabulary (ISO 15836) that must be entered in Nakala includes the type of data, the title, the author(s), the creation date and the licence associated with the dataset. It is possible to add additional metadata (qualified Dublin Core). Keywords (filled in using the PACTOLS interoperable multilingual thesaurus for Archaeology), language and a description of each dataset will be filled in. A readme file will be associated with each dataset deposited in the Nakala repository. The datasets will be "harvested" by the Isidore search engine and OpenAire Explore, and thus easily findable and accessible.

All datasets will be made available under a **Creative Commons Attribution (CC BY)** license, allowing broad reuse with appropriate credit. In cases involving sensitive or restricted data (e.g., personal data requiring anonymization), access may be restricted to specific user groups or require a data sharing agreement. Measures will be taken to minimize restrictions, including data anonymization and the provision of aggregated or de-identified versions where applicable.

Data will be made available within a reasonably short period after the conclusion of the project, or at the time of any related publication, whichever comes first. This allows time for quality assurance, documentation, and the preparation of metadata.

The datasets will be particularly relevant to researchers focusing on lithic technology in Central Europe. The data may be used for comparative analyses, technological studies and regional syntheses, but also for developing and testing methodological frameworks in lithic analysis. The datasets could serve as teaching resources in higher education programs, but also related to lithic technology, knapping techniques and artefact analysis. Additionally, the datasets could be adapted for educational use in school programs, particularly in modules related to archaeology, prehistoric tools, and stone knapping, helping to engage younger audiences with tangible examples from archaeological research.

## Reusability

The data produced during this project can be reused in future research to support further analysis, validation, or new investigations.

## How will data be long-term preserved? Which data?

## Justification

The long-term preservation of the lithic technology dataset is essential due to its scientific, cultural, and methodological value. First, the dataset documents unique prehistoric technological traditions across Belgium, the Netherlands, and the German Rhineland, offering a valuable reference for future archaeological, anthropological, and heritage research. Given the irreversible nature of excavation and the potential inaccessibility of physical collections over time (due to curation limitations or degradation), the digital dataset serves as a crucial record of primary observations.

Moreover, the dataset is structured to support **comparative studies**, including re-analysis and replication of chaîne opératoire-based research. Preserving it ensures that future scholars can engage with the material using updated methods or in light of new discoveries. The use of open, standard formats (.csv, .tif, .txt) and rich metadata makes it interoperable and suitable for reuse across disciplines and platforms.

Finally, as archaeological research is increasingly data-driven, long-term preservation supports transparency, reproducibility, and open science. It aligns with international best practices in data stewardship and fulfills ethical obligations to safeguard irreplaceable scientific information for future generations.

In accordance with the Code of Heritage, the archives produced by the UMRs within the scope of UAR3225 are managed by the archives department of MSH Mondes. At the end of the research project, the documents and data produced will be transferred to the archives department. Indeed, the department is responsible for managing the public, administrative, and scientific archives of the units at MSH Mondes, from their production (current archives) throughout their entire conservation period after transfer (intermediate archives), regardless of their format (textual, graphic, photographic documents, etc.) and their medium (physical documents, electronic documents) (address:

https://www.mshmondes.cnrs.fr/accompagnement/archives).

Once transferred, these data are classified, described, and inventoried. The inventory is published online (address: https://archives.mshmondes.cnrs.fr), and the archives are accessible to anyone who requests them, in compliance with the rules set out in the Code of Heritage and
the Code of Intellectual Property.

A selection and, if necessary, regulatory destruction of the archives are carried out based on their administrative usefulness and scientific interest, with the approval of the Interministerial Archives Service of France (SIAF).

These operations are governed by a management table established in line with administrative and scientific needs. Finally, according to a schedule defined in agreement with the National Archives and the needs of the research, the project archives will, ultimately, be transferred to the National Archives for permanent conservation.

Extract of the Archive Department's management table :

<table><thead><tr><th>Activités et documents</th><th>DUA</th><th>Sort final</th><th>Observations</th></tr></thead><tbody><tr><td><strong>1. Direction d'équipe</strong></td><td></td><td></td><td></td></tr><tr><td><strong>1.1. Réunions internes et séminaires</strong><br>Ordre du jour, compte rendu de réunion et documents afférents, programme, support de présentation (texte, slide, vidéo...).</td><td>10 ans</td><td>C</td><td></td></tr><tr><td><strong>1.2. Suivi de l'activité des membres</strong><br>Dossier de membre (projet scientifique, rapport, attestation, demande de bourse), note interne.</td><td>10 ans</td><td>C</td><td></td></tr><tr><td><strong>2. Recherche</strong></td><td></td><td></td><td></td></tr><tr><td><strong>2.1. Programme/projet</strong> Le programme/projet peut être financé par des organismes extérieurs à l'unité (ANR, Labex, ministère des Affaires étrangères...) ou ne pas être financé. Le programme/projet génère des documents/données issus des activités scientifiques listées en 3.2-3.10.</td><td></td><td></td><td>Le programme/projet peut être financé par des organismes extérieurs à l'unité (ANR, Labex, ministère des Affaires étrangères...) ou ne pas être financé. Le programme/projet génère des documents/données issus des activités scientifiques listées en 3.2-3.10.</td></tr><tr><td><strong>2.1.1. Direction et gestion</strong></td><td></td><td></td><td></td></tr><tr><td><strong>Direction des activités</strong><br>Appel d'offres, appel à projet, texte de projet, dossier de candidature (accepté ou refusé), rapport d'activité, versions préliminaires (dossier de candidature, rapport), contrat de recherche, convention de collaboration, protocole d'accord, charte de sécurité, autorisation, permis, programme de travail, note d'information, plan de gestion de données, planning, agenda, lettre, courriel.</td><td>Durée du projet scientifique + 5 ans</td><td>T</td><td>Détruire les versions préliminaires (rapport, projet). Conserver les courriels les plus significatifs.</td></tr></tbody></table>
<table><tr><td>Gestion financière</td><td></td><td></td><td></td></tr><tr><td>Gestion par le responsable de projet</td><td></td><td></td><td></td></tr><tr><td>Budget prévisionnel, budget réalisé, notification de crédits, facture, justificatif de dépenses, bilan des dépenses, relevé de compte, attestation, lettre, courriel.</td><td>10 ans</td><td>D</td><td>C'est le cas par exemple des missions archéologiques françaises à l'étranger. Les budgets et les bilans de dépenses sont éliminés car ils figurent dans les rapports.</td></tr><tr><td>Gestion par l'unité ou une autre institution</td><td></td><td></td><td></td></tr><tr><td>Budget prévisionnel, budget réalisé, notification de crédits, facture, justificatif de dépenses, bilan des dépenses, relevé de compte, attestation, courriel.</td><td>Validité</td><td>D</td><td>Les documents sont des copies. Les documents originaux sont archivés par la cellule gestion financière de l'unité ou de l'institution.</td></tr><tr><td>Gestion des personnels (CDD, stagiaires)</td><td></td><td></td><td></td></tr><tr><td>Gestion par le responsable de projet</td><td></td><td></td><td></td></tr><tr><td>CV, lettre de motivation, bulletin d'inscription, attestation, convention de stage (copie), demande et ordre de mission (copie), demande de visa (copie), document relatif aux assurances (copie), courriel.</td><td>10 ans</td><td>D</td><td></td></tr><tr><td>Gestion par l'unité ou autre institution</td><td></td><td></td><td></td></tr><tr><td>CV, lettre de motivation, contrat (copie), convention de stage (copie), documents relatifs aux missions (copies), courriel.</td><td>Validité</td><td>D</td><td>Les documents sont des copies. Les documents originaux sont archivés par la cellule gestion financière de l'unité ou de l'institution.</td></tr><tr><td>Gestion de locaux, d'équipement</td><td></td><td></td><td></td></tr><tr><td>Inventaire d'équipement, documents d'organisation de la vie quotidienne, documentation technique, documents relatifs à la gestion et à l'entretien de véhicule, documents relatifs à la location de locaux.</td><td>10 ans</td><td>T</td><td>Cette rubrique concerne par exemple les missions archéologiques françaises à l'étranger. Détruire les documents relatifs à la gestion et à l'entretien de véhicule et la documentation technique. Conserver les inventaires d'équipement et les documents d'organisation de la vie quotidienne.</td></tr><tr><td>2.1.2. Participation (documents de gestion)</td><td></td><td></td><td></td></tr><tr><td>Texte de projet, rapport, programme de travail, notes, courriel.</td><td>Durée du projet scientifique + 5 ans</td><td>T</td><td>Les tri porte sur les notes et les courriels : conserver selon l'intérêt.</td></tr></table>