> For the complete documentation index, see [llms.txt](https://icij.gitbook.io/datashare/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://icij.gitbook.io/datashare/server-mode/create-the-neo4j-graph/create-and-update-the-graph.md).
# Create and update Neo4j graph
This page describes how to create and maintain your Neo4j graph up to date with your server's Datashare projects
## Run the Neo4j extension CLI
The Neo4j related features are added to the DatashareCLI through the extension mechanism. In order to run the extended CLI, the Java `CLASSPATH` must be extended with the path of the `datashare-extension-neo4j` jar. By default, this jar is located in `/home/.local/share/datashare/extensions/*`, so the CLI will be run as following:
```bash
docker compose exec \
# if you are not using the default extensions directory
# you have to specify it extending the CLASSPATH variable ex:
# -e CLASSPATH=/home/datashare/extensions/* \
datashare_web /entrypoint.sh \
--ext neo4j \
...
```
## Create the graph
In order to create the graph, run the `--fullImport` command for your project:
```bash
docker compose exec \
datashare_web /entrypoint.sh \
--ext neo4j \
--full-import \
--project secret-project
```
The CLI will display the import task progress and log import related information.
## Update the graph
When new documents or entities are added or modified inside Datashare, you will need to update the Neo4j graph to reflect these changes.
To update the graph, you can just re-run the full export:
```bash
docker compose exec \
datashare_web /entrypoint.sh \
--ext neo4j \
--full-import \
--project secret-project
```
The update will **always add missing nodes and relationships, update existing ones if they were modified, but will never delete graph nodes or relationships**.
To detect whether a graph update is needed, go to the '**Projects'** page and open your project:
Open your project
Compare the number of documents and entities found in Datashare in '**Projects**' > '**Your project**' > '**Insights**'...
Statistics of one project
...with the numbers found in your project in the '**Graph' tab**. Run an update in case of mismatch:
The update will **always add missing nodes and relationships, update existing ones if they were modified, but will never delete graph nodes or relationships**.
You can now [explore your graph](/datashare/usage/explore-the-neo4j-graph.md#exploring-your-graph) using your favorite visualization tool.
---
# 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://icij.gitbook.io/datashare/server-mode/create-the-neo4j-graph/create-and-update-the-graph.md?ask=&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.
