Verified Credentials

Intro & Goal

The goal of the Verified Credentials (VC) product is to provide a reliable and efficient system for generating and sharing verified badges and certificates. This system aims to empower users with a tangible and credible representation of their achievements, such as DPG points, and facilitate seamless sharing on various social media and professional platforms.

Who’s it for?

• Contributors
• Mentors
• Program Administrators
• Organizations

Why build it?

• Acknowledge and reward contributors for their achievements.
• Enhance the credibility of program participants (both mentors, contributors and organizations) through verified credentials.
• Streamline the process of sharing achievements on social media and other professional platforms.

Current form in which it exists

Currently this system exists as a bff for ULP APIs

Usecases for which BFF was designed

1. Inauguration

• Generate 3 links corresponding to 3 individuals.
• Email these links to these individuals.
• The clicking of these links by individuals will be recorded as a verifiable credential.
• Three clicks together mark an inauguration.
• There is a simple frontend that tracks clicks for a triplet of links generated and marks completion of inauguration.

This was used while inaugurating and closing Dedicated Mentorship Program 2023

2. Certificate Generation

• Given contributor details, generate a VC corresponding to their achievement.
• Given a VC and an HTML template, generate PDF versions of the certificate.
• Given a PDF Certificate, email this to the participant.

This was used to give certificates to Mentorship Program Contributors
PDF Generation API was also used in community program to generate milestone certificates

Tech Debt

• Various configurations such as which email ID sends the email or whose names appear in the inauguration frontend or filenames are hardcoded.
• There are more than one functions doing the same thing, and only one might be working.
• Some modules are empty and their functionalities are buried in other files.
• Other unknown bugs/issues.

Suggestion

We should overhaul the BFF with a clean sheet vision of functionality in mind, and leverage existing service to speed up development instead of trying to fix the current service on a feature by feature basis.

New form being envisioned

The new system will automate the issuance of verified badges and credentials, providing contributors with a visually appealing and standardized representation of their achievements.

The new features includes:

• A user-friendly interface for contributors to access and share their verified credentials.
• Integration with social media and professional platforms for seamless sharing.
• APIs to facilitate bulk email communication for mentoring programs, allowing customization through templates and recipient CSV files.

Note: By implementing these changes, the verified credentials product seeks to provide a more efficient, user-centric experience and can be used in various programs and initiatives.

Usecases

• Badge -> Certificate (Badge should also has QR)- Once contributor PR merged, instead of badge image it should also have QR code.
• After scanning QR on Badge (image of contributor level) -> Green tick watermark with certi-
• After scanning QR on Certificate of milestone -> Green tick watermark with certi
• Analytics image is having verified badge, Image can be verified data
  • Contributor level
  • Contributor Info
  • Verified Identity
    Note: This image has 2 QRS -> 1. Badge QR, 2. Image QR
• Mentoring Program Certi generation

C4GT Team to design

• Badges
• Certifactes
• Scanned Screen
• Analytics Image Design
• Accessibility
• Mentor Certification

@omkar309 @KDwevedi

Scoping doc: https://docs.google.com/document/d/1efbXWjhI9rtYSMMJk6LGZRN05hhx6VmMNH-7MjgA03E/edit

PT to get back on the exact requirements- features in a sheet, which PM will break down into usecases, and dev can be picked when tickets are created for those usecases.

Scoping doc: https://docs.google.com/document/d/1efbXWjhI9rtYSMMJk6LGZRN05hhx6VmMNH-7MjgA03E/edit
Use cases sheet: https://docs.google.com/spreadsheets/d/1asTGVqKD1FsAmyNboDvZrGRzDjpL5RG-OZgndpjSt60/edit#gid=1747214811

Use cases tickets being created separately