# Add entities from the CLI

**This document assumes that you have installed Datashare** [**in server mode within Docker**](/datashare/server-mode/install-with-docker.md) **and already** [**added documents to Datashare**](/datashare/server-mode/add-documents-from-the-cli.md)**.**

In server [mode](/datashare/concepts/running-modes.md), it's important to understand that Datashare does not provide an interface to add documents. As there is no build-in roles and permission in Datashare's data model, we have no way to differentiate users to offer admin additional tools.

This is likely to be changed in the near future, but in the meantime, you can extract named entities using the command-line interface.

Datashare has the ability to detect email addresses, name of people, organizations and locations. This process use a Natural Language Processing (NLP) pipeline called CORENLP. Once your documents have been indexed in Datashare, you can perform the named entities extraction in the same fashion as the previous CLI's [stages](/datashare/concepts/cli-stages.md):

```bash
docker compose exec datashare_web /entrypoint.sh \
  stage run \
  --stages NLP \
  --defaultProject secret-project \
  --elasticsearchAddress http://elasticsearch:9200 \
  --nlpParallelism 2 \
  --nlpPipeline CORENLP
```

What's happening here:

* We ask to process the NLP [stage](/datashare/concepts/cli-stages.md)
* We tell Datashare to use the `elasticsearch` service
* Datashare will pull documents from ElasticSearch directly
* Up to 2 documents will be analyzed in parallel
* Datashare will use the CORENLP pipeline

Datashare will use the output queue from the previous `INDEX` stage (by default `extract:queue:nlp` in Redis) that contains all the document ids to be analyzed.

The first time you run this command you will have to wait a little bit because Datashare need to download CORENLP's models which can be big.

You can also use chain the 3 stages altogether:

```bash
docker compose exec datashare_web /entrypoint.sh \
  stage run \
  --stages SCAN,INDEX,NLP \
  --defaultProject secret-project \
  --elasticsearchAddress http://elasticsearch:9200 \
  --nlpParallelism 2 \
  --nlpPipeline CORENLP \
  --dataDir /home/datashare/Datashare/
```

As for the previous [stages](/datashare/concepts/cli-stages.md) you may want to restore the output queue from the `INDEX` stage. You can do:

```bash
docker compose exec datashare_web /entrypoint.sh \
  stage run \
  --stages ENQUEUEIDX,NLP \
  --defaultProject secret-project \
  --elasticsearchAddress http://elasticsearch:9200 \
  --nlpParallelism 2 \
  --nlpPipeline CORENLP
```

The added `ENQUEUEIDX` stage will read Elasticsearch index, find all documents that have not already been analyzed by the CORENLP NER pipeline, and put the IDs of those documents into the `extract:queue:nlp` queue.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://icij.gitbook.io/datashare/server-mode/add-entities-from-the-cli.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.