> For the complete documentation index, see [llms.txt](https://guides.data.gouv.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.data.gouv.fr/passe-marche/socle-de-base/6.-archiver-un-champ.md).

# 6. Archiver un champ

Lorsqu’un champ ne doit plus être utilisé, il peut être **archivé**.

L’archivage permet de retirer un champ de l’usage courant sans le supprimer définitivement de la base.

Un champ archivé :

* n’apparaît plus dans la liste active du socle de base,
* n’est plus proposé dans les nouveaux usages ou formulaires,
* mais reste conservé dans le système.

L’archivage n’efface pas les données déjà associées à ce champ.\
Les informations existantes restent donc disponibles dans les dossiers ou formulaires où ce champ a déjà été utilisé.

Cette logique permet de préserver la cohérence des données historiques tout en retirant le champ des usages futurs.\ <br>

<figure><img src="https://4185883586-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fn1tA9TcP34YIO4dY7Wz3%2Fuploads%2Fgit-blob-340fd804bde422e71bc395a1787c48a30b764ea0%2Fimage%20(7)%20(2)%20(1).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guides.data.gouv.fr/passe-marche/socle-de-base/6.-archiver-un-champ.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
