DMP 2026 Proposal - Clarifications on Implementation & Flow

Hey MOSIP team, I’ve gone through the issue and the related flows across the Admin and Student portals. Before writing the proposal, I wanted to clarify a few points to ensure alignment with the intended design:

  • Should the is_eligible flag be strictly stored and managed via admin updates, or is it expected to be re-validated dynamically during the certificate request flow in the Student Portal?

  • Once a student is marked as GRADUATED, if fields like final_result are updated later, should that affect already issued or in-progress certificate requests?

  • Is the Admin Portal expected to have any direct interaction with the issuance system (e.g., syncing with the issuer), or should it remain limited to managing student records and eligibility?

  • For authentication, is the current static email/password approach only for initial setup, or should we design with future extensions like role-based access or multi-institution support in mind?

I’m applying for DMP 2026 and wanted to ensure I’m aligned before proceeding.

Hi @CodeWith-sakib

Thank you for your interest in contributing to MOSIP. It’s great to see your enthusiasm.

The DMP tickets are specifically intended for interns who participated in MOSIP Decode, which was one of our student hackathons.

That said, we truly appreciate your interest in contributing. Please stay tuned! We will soon be publishing a list of GitHub issues that are open for the broader community to contribute to.

Looking forward to your participation!

Warm regards,
Community Manager
Pragya