> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/1.3/social-registry/features/unique-reference-id.md).

# Unique Reference ID

### Description <a href="#description" id="description"></a>

This feature aims to streamline the identification process of registrants in the social registry system by providing unique reference IDs. It is essential for ensuring accurate and efficient tracking and updating of records. The need arose to enhance data consistency and integration with other systems within the registry. The unique ID is generated by the MOSIP [id-generator](https://docs.mosip.io/1.1.5/modules/kernel/uin-and-vid-generation-service-functionality) service.

### Features <a href="#features" id="features"></a>

* Uniquely identifies each registrant.
* Facilitates quick and accurate identification.
* Aids in tracking and updating records.
* Ensures seamless integration with other systems.
* Enhances data consistency and integrity.

{% embed url="<https://miro.com/app/board/uXjVKsusfaU=/?share_link_id=212808513356>" %}

### Technical design

* It is implemented as an [Odoo](https://www.odoo.com/documentation/17.0/) module.
* It involves two new table creation.
  * **g2p.reference.id.config** table for the Configurations.
  * **g2p.pending.reference\_id** table for storing the registrant if reference ID is not generated for them.

### Source Code

WIP

### Dependencies

It requires the MOSIP [id-generator](https://docs.mosip.io/1.1.5/modules/kernel/uin-and-vid-generation-service-functionality) service.


---

# 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.openg2p.org/1.3/social-registry/features/unique-reference-id.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.