Meelis (Gofore) had previously mentioned that work is already being done on the API and points for the happy flow, which will be ready by the end of May. Details are awaited.
MIFOS - Account Mapper and Account Lookup APIs for the MVP
It was mentioned that the account mapper APIs have been shared and can be used for the happy flow process mapping.
However, there are also other unresolved deployment issues related to MIFOS integration, and the Gofore team are waiting for updated information from MIFOS.
There is a also discussion about how to collect payment-related details from users and navigate between UIs of different building blocks. The guidelines suggest that each building block should provide its own UI for sensitive data collection.
MOSIP - eSignet Integration and API Test Harness compliance
Technoforte is trying out the compliance of the MOSIP with the GovStack API test harness.
There is a need for clarification regarding the integration of the eSignet module. The handshake process and proper integration of this module into the MVP should be ensured.
There are discrepancies and confusion regarding the workflow and data flow between different components. Clarifications are needed regarding the use of mock applications, registration forms, data fetching, Citizens Registry, and foundational IDs.
There was a discussion about the possibility of linking or mapping IDs from an external civil registry to local foundational IDs. However, it was mentioned that these were additional phases and not part of the current scope.
The ID building block in MOSIP only stores ID-related credentials and demographic data. Post-registration, the beneficiary details may be stored in the SRIS portal or a separate Citizens Registry, but MOSIP's role is limited to authentication and returning data based on requirements.
As the scope and role of the Citizens Registry is not clearly defined, it was mentioned that data may be stored there, but the exact link between MOSIP and the Citizens Registry and data flow needs further clarification.
Front-end Integration and UI Compatibility
This is an ongoing discussion in multiple meetings that involves how different building blocks can reuse UI components and ensure seamless user experience.
The compatibility and transition between UI fragments of different building blocks need to be clarified.
The usability of building block UIs has not been extensively discussed. While the focus has been on APIs, reusing UI components from different building blocks would provide a seamless user experience. However, this raises complications related to UI styling, compatibility, and screen rendering.
The transition between screens or building blocks representing UI fragments is unclear. It is necessary to determine how the front-end integration will work and where the screens will be rendered. This topic is bigger and more complex than API reusability.
Due to the complexity of front-end issues, it is suggested to move the discussion to another forum. This includes UX, technology setup, technology selection, application security, cross-site scripting, and related topics.
Continuation of discussion for alignment issues between Payments BB and Registration/ Digital Registries BB
There was an offline discussion on the alignment between payments and registration building blocks in the previous week. Further updates are expected later.
UI Demonstration for Full-Scale Implementation of USCT use case
For the full-scale implementation of the USCT program, it is suggested that both API endpoint level integration demonstration and UI demonstration should be included. The deliverables of MOSIP and other teams should cater to the overall architecture in GovStack, beyond just the MVP.
It is important to consider the front end design when navigating between different building blocks. The application should be able to navigate between UIs of various building blocks without being forced to design a UI for every building block.
Action Items
Action Items
Responsible
Date
Action Items
Responsible
Date
Sandbox team to complete the API endpoint mapping for the MVP (HIGH PRIORITY)
@Meelis Zujev (Deactivated)
June 6, 2023
MOSIP - API test harness compliance, eSignet integration
