Sunbird RC
v0.0.14
v0.0.14
  • Learn
    • Introduction
    • Verifiable Credentials
      • What issues will Verifiable Credentials address?
      • What are the key roles in Verifiable Credentials?
      • What are the components of Verifiable Credentials?
      • What are the benefits of Verifiable Credentials?
      • Digital Credentials vs Verifiable Credentials
      • QR code vs Verifiable QR code
      • Use Cases
    • Electronic Registries
      • Evolution of Electronic Registries
      • What issues will Electronic Registries address?
      • Benefits of Electronic Registries
      • Registry vs Database
      • Design Principles
      • Use Cases
    • Sunbird RC Overview
      • Features
      • Core Registry Verbs
      • Why do we need Sunbird RC?
      • What Sunbird RC is and what it's not? (WIP)
      • Core Capabilities
      • Technical Specification Draft
      • Workflows
      • High level architecture
    • Sunbird RC in action
      • Implementations (Work in Progress)
      • Possibilities
  • Use
    • Technical Requirements
    • Releases
    • Setup the Backend
    • Setup the Frontend
    • Leveraging Existing data stores
    • SSO with existing systems
      • Digilocker Meripehchaan SSO
  • Developer Documentation
    • Installation Guide
      • Registry CLI
        • Setup A Registry Instance
      • Manual installation through docker-compose
      • Production setup through Helm
    • Introduction To Schemas
    • Creating Your Own Schemas
    • Schema Configuration
    • Using The APIs
    • Create Schemas With Custom Password
    • Admin Portal
      • Login
      • Get Started
        • Create Schema
        • Attestation Workflows (WIP)
        • VC Template
          • Custom VC Template (WIP)
        • Ownership (WIP)
        • Publish (WIP)
      • Dashboard
    • Configuration
    • Developer Setup
    • VC Verification Module
    • Audit Configuration
    • Custom Keycloak Build
    • Metrics
    • Digilocker Integration
    • Custom QR Code design
    • Notifications Configuration
    • View Templates Configuration
    • Generic Identity And Access Management
    • Backup and Restore
      • PostgreSQL
        • SQL Dump
        • File System Level Backup
        • Continuous Archiving and Point-in-Time Recovery (PITR)
      • Cassandra
        • Snapshot-based backup method
        • Incremental backup method
        • Data Restore
    • Frontend Configurations
    • Frontend - Proxy configuration
  • API Reference
    • Registry
      • Create An Entity
      • Invite An Entity
      • Generate token
      • Generate admin token
      • Get An Entity
      • Get An Entity By Id
      • Update An Entity
      • Create A Property Of An Entity
      • Update A Property Of An Entity
      • Revoke a Credential
      • Delete An Entity
    • Schema
      • Create Schema
      • Get Schema
      • Update Schema
      • Delete Schema
      • Publish A Schema
    • Attestation API
      • Raise An Attestation
      • Get Attestation Certificate
    • Claims API
      • Get All Claims
      • Get Claim by ID
      • Attest A Claim
    • Discovery API
      • Search An Entity
    • File Storage API
      • Upload A File
      • Get Uploaded File
      • Delete A File/ Multiple Files
    • Bulk Issuance API
      • Get Sample Template
      • Upload CSV
      • Get all uploaded Files
      • Download a Report File
    • Metrics APIs
      • Get Count
      • Get Aggregates
    • Other APIs
      • Sign API
      • Verify API
      • Swagger JSON API
      • Health API
  • Reference Solutions
    • Education
      • Education Ecosystem
        • Installation
      • Education Registries
        • Installation
    • Certificate Issuance
      • Installation(WIP)
      • User Guide
    • eLocker
      • High Level Diagram
      • Installation (WIP)
        • Frontend Setup E-locker
      • User Guide
    • Health Registries
      • Organ Registries
        • Frontend Setup
        • Backend Setup
        • User Guide
    • Vaccination Platform
    • Skills & Work Credentials
    • Govt to Person (G2P)
    • Unified Learners Passport (ULP)
      • ULP Capabilities
      • Example Scenario
      • Technical Components (WIP)
      • Demo/Sandbox Links (WIP)
      • Installation Guide (WIP)
        • Frontend Setup
        • Installation through docker-compose
        • Dummy records setup for refrence
  • Links
    • Source Code
    • Releases & Changelogs
    • Website
    • Roadmap
    • Reference links
    • Design
  • Community
    • Discussion Forum
    • Contributing
    • Contributors
    • Contribution Guidebook
    • Code of Conduct
    • Community Events
    • Status By Track
  • HELP
    • Roadmap
    • FAQs
    • Glossary
Powered by GitBook

Copyright (c) 2023 EkStep Foundation under MIT License

On this page
  • Vision
  • Problem Statement
  • Personas
  • Solution
  • ULP Ecosystem
  1. Reference Solutions

Unified Learners Passport (ULP)

Unified Learners Passport (ULP) is a single source of digital credentials for learners across levels, that will help them easily discover and avail opportunities for academic or professional growth

Vision

To revolutionize the way educational credentials are accessed, shared, and trusted in India

Problem Statement

In the current scenario, students face a series of barriers in accessing growth opportunities (such as jobs, internships, scholarships, courses, competitions etc). They are often required to present proof of their degree/diploma attainment, academic or non-academic achievements, etc. On top of that, ‘trust’ in these proofs often needs to be established, and is not inherent. Hence, significant time and effort is required from both students and the ecosystem - institutions, employers, government etc, in verifying the authenticity of the required documents.

Learners’ key obstacles:

  1. Non-shareable student records

  2. Time consuming verification process

Ecosystem players face the following obstacles:

  1. Inability to reach eligible students

  2. Time consuming verification process

Personas

ULP, in educational context, involves 3 main personas who form the basic ecosystem -

  • Issuer: The Issuer persona represents institutions such as schools and colleges responsible for issuing credentials.Key Characteristics:

  • Learner: The Learner persona represents the students who utilize the ULP platform to receive, view, and share their credentials. They can easily access their credentials, showcase them to potential opportunity providers, and share verified information to establish their qualifications.

  • Verifier: The Verifier persona represents benefit providers, such as employers, scholarship organizations, etc, who need to verify the credentials presented by learners.

Solution

The above-mentioned challenges can be solved through implementation of digital credentials of a learner’s experience and achievements, which can be accessed and shared easily by the learner, with trust being an inherent property of each credential.

The proposed solution is Universal Learner's Passport (ULP)

ULP will provide learners with a comprehensive platform to consolidate and showcase their educational achievements, skills, and experiences. The platform will allow for seamless sharing of credentials, simplifying the verification process for both learners and opportunity providers.

ULP Ecosystem

ULP involves an ecosystem of 3 actors namely the Issuer, the Holder and the Verifier interacting with each other on a level of digital trust backed by a governance authority. The Issuer is in charge of issuing verifiable credentials to the Holder which is stored in a central Verifiable Data Registry. The Holder can share the issued credentials with Verifiers for an opportunity or benefit. The Verifiers can verify the authenticity of the credential by reading from the Verifiable Data Registry. A system of mutual trust is formed where the governance authority (who is trusted by the Verifier) trusts the Issuer. By transitive trust the Verifier trusts the Issuer resulting in a high trust ecosystem overall.

The interconnection of stake holders in the ULP Ecosystem can be showed as below:

PreviousGovt to Person (G2P)NextULP Capabilities

Last updated 1 year ago

ULP Ecosystem