An open source software that will help organisations build electronic registries. The project embodies principles of extensibility at its core, and enables adopters to rapidly deploy secure electronic registries. For more, please visit opensaber.io 

What is a registry?

Registries are shared digital infrastructure onto which authorised issuing agencies publish digitally signed data about users, entities, or other assets/resources allowing consented and controlled access to other authorised service providers for digital verification and usage.

An electronic registry is to data, what the stern bank official from yesteryears was to the bank. A gatekeeper who is a worthy custodian for protection of valuables or documents, one who would provide controlled access to an account based on your profile. 

A registry allows for authorised data repositories to publish data about actors in a digitally signed form via secure API, for service providers and other partners to consume in a trustworthy fashion. It can thus empower isolated data islands to 'free' their data to enable trusted transactions. 

 

Why is a registry useful?

Large scale inter-dependent digital systems require access to machine readable and trusted registries of people, organisation and other assets/resources. 

These registries are typically setup for a purpose made available for controlled access to an ecosystem. Such registries allow for seamless and automated integration of data and information at scale. 

Custodians of various registries may host their own registry infrastructure or use a shared infrastructure to which they publish data, while still retaining control of lifecycle management of data. Registries may follow a federated structure within a domain, or be used in a linked fashion across domains. 

 

Features of OpenSABER

 

1. Master Data Store : Use the registry as a master data store of actors (people, entities or things)

  • Vocabulary creation and modelling
  • Employ flexible schema to define entity attributes and validations using JSON, JSON-LD
  • Attach rules for data validation, lifecycle operations and relationships

2. Data operations : Issue data into, as well as read data from Registry

  • Secure API driven CRUD operations 
  • Data operations via secure, open APIs for data publishing and access, data discovery and search
  • Key-value pair driven search, attribute search 

3. Data protection : Encryption and data security

  • Data encryption and masking
  • Support for custom encryption services - open end points to replace the bundled in encryption services with services of the adopters choice
  • Audit trails and logging

4. Single source of truth : Employing the registry as a single source of truth for reliable data

  • Digital signatures for trust worthiness and non-repudiation
  • Open end points to replace the bundled in encryption services with services of the adopters choice

5. Business led Database choice : Ability to make a business led choice of databased to the registry

  • Support for multiple databases employing out-of-the-box adapters for multiple DB support - including graphs DBs(Neo4j), RDBMS(Postgres)

 

The following are a list of indicative exploratory questions intended to assist missions that are evaluating a registry infrastructure. It is vital to articulate the need for a registry service and define its value addition to the mission. 

1. What are your data and workflow requirements?

2. How will the registry infrastructure help with your mission/program?

3. Who will be the users of the registry, and what will the data sources for it be?

4. How will it be ensured that data flowing into registry is trustworthy and clean?