> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/local-governance/access/local-governance-stack/dashboards-and-analytics/dashboards-and-analytics-service-configuration/national-dashboard-ingest-service/national-dashboard-adaptor-service.md).

# National Dashboard Adaptor Service

## Overview <a href="#overview" id="overview"></a>

Provides a detailed walk-through of how to set up, configure and deploy Airflow DAGs on the state side to extract data from the Elastic Search server to push to the National Dashboard Adaptor.

## **Scope**

Design and develop an adaptor service which will extract data from the state DIGIT installations and push it onto the National Dashboard instance periodically.&#x20;

A list of tasks for this has been tracked for the Adaptor&#x20;

[Jira - Dashboard](https://digit-discuss.atlassian.net/jira/software/projects/NDA/boards/120)

* Adaptor to be deployed on state DIGIT installations&#x20;
* Periodically, the adaptor extracts data and aggregates it from the different DIGIT modules
* Posts the data to the National Dashboard for the state
* Bookkeeping is done for every adaptor data extract and pushes for audit and debugging&#x20;
* Out of scope: Extraction from non-DIGIT sources&#x20;

&#x20;A national dashboard adaptor extracts data from the state DSS at a scheduled time which can be configured and then would ingest in the National Dashboard. The adaptor ingests data at the state/ULB/Ward level for each module on a daily basis. The adapter sends the data in a batch size of 50 to the national dashboard.

<figure><img src="https://content.gitbook.com/content/OorNqx5By246mkjipsn7/blobs/5PWTi1HIEDsG1PEDaT88/image.png" 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://docs.digit.org/local-governance/access/local-governance-stack/dashboards-and-analytics/dashboards-and-analytics-service-configuration/national-dashboard-ingest-service/national-dashboard-adaptor-service.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.
