Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing Localization for MDMS Schemas Created via Postman #575

Open
jagankumar-egov opened this issue Sep 25, 2024 · 3 comments
Open

Missing Localization for MDMS Schemas Created via Postman #575

jagankumar-egov opened this issue Sep 25, 2024 · 3 comments
Assignees
Labels

Comments

@jagankumar-egov
Copy link
Contributor

Description:
Currently, MDMS schemas are being created through Postman, which bypasses the creation of necessary localization messages. This leads to several issues when users access the MDMS/Workbench UI:

  1. Localization Absence:

    • Users do not create localization when adding data via Postman. As a result, when they visit the MDMS or Workbench UI, they see fields displayed as code since the screen expects localized messages for every field name.
  2. Non-Readable UI:

    • The entire screen displays non-user-readable codes for fields, which impacts usability and clarity. This is because the UI assumes and expects localization messages for each field in the schema.

    Attachment
    Screenshot 2024-09-25 at 2 46 42 PM

  3. Proposed Approach:

    • We should implement an event-based approach or an alternative mechanism that ensures a localization message is automatically created for every property in a schema when it is created.
    • This default localization message would provide a more user-friendly interface, displaying proper messages when users visit the screen.
  4. Standardization for Localization:

    • To ensure uniqueness and consistency, a prefix should be added to every field's localization key. This prefix should follow the format: {schemaCode}_fieldName. This will help standardize how localization messages are created for each schema field.

Steps to Reproduce:

  1. Create an MDMS schema via Postman without providing localization.
  2. Access the MDMS or Workbench UI.
  3. Observe that the screen displays non-localized codes instead of user-friendly messages.

Expected Behavior:

  • Localization messages should automatically be generated for every property in the schema with a default message, ensuring that users see proper, user-readable fields on the UI.

Additional Notes:

  • Implementing this approach will help improve the user experience and ensure that fields are localized appropriately across the MDMS and Workbench UI.

#574

@jagankumar-egov
Copy link
Contributor Author

We previously discussed this issue during the "Localization <> Master Data" meeting held on Wednesday, September 25, from 12:00 PM to 1:00 PM. The attendees were @jagankumar-egov @eGovMan @Rishabh-egov @varunreddy-egov Krishna

@Rishabh-egov , please add the discussion points and proposed approaches from the meeting here.

@eGovMan
Copy link

eGovMan commented Sep 25, 2024

@jagankumar-egov - I thought we are calling it Admin Console and not Workbench. 😀

@zeel991
Copy link

zeel991 commented Oct 2, 2024

Hello Everone!!
I am Zeel Darji , C4GT community Lead and Open source Lead of Development Wing of IIITN . I am organizing an open source event in my college's techfest which higlights the importance of DPGs and DPIs .

I wanted to ask you if participants could contribute to the repos of eGovernments for our Event ?
Thank You!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants