Remove org specific translations

[mahalakshme]

Motivation:

This is to avoid confusion for the new orgs when they want to translate keys for their organisation. They get confused when they see terms that don't belong to their organisation in lokalise and see that as unnecessary work to translate.

Acceptance criteria:

• Remove keys that doesn't belong to Avni platform(mobile app/webapp respectively) ie.,org specific keys like Record JCB details and myDawaPrapatra in client and webapp codebase.
• Output a excel file/any file with details of keys removed, should have headings like - 'Key removed', 'Language', 'Translation value', 'Organisation that belonged to', 'Entity type'(which means Report card name or concept name or menu item name, or form name etc.,), 'Platform(Mobile/Web)'
• Review the above file with implementation team to confirm the necessity of inserting them into translation table because some orgs might not be in use or if we are not sure of the org. After informing the implementation team move this card to 'on Hold'.
• After reviewing, insert the keys into translation table for the respective organisation, if the key removed is not present

Analysis details:

Some of the keys dont seem to exist as any entity(concept, etc.,) in any of the orgs.

[vinayvenu]

• How do we figure out the organisation that the key belonged to?
• The scope of this story can stop at creating the excel file and attaching them to this story.

[mahalakshme]

@vinayvenu we will know when we check for the entity(concept/ report card name etc.,) to which the key belongs to in the db. Or can be figured out as much as possible, and implementors will know better and can be figured out during the discussion with the implementation team. For most of the orgs, will be available in translations table since from lokalise when we upload it creates entry in translations table. But for orgs like RWB2023 I dont see any entries in translations table. for those ll help.

[mahalakshme]

@vinayvenu I have added this After informing the implementation team move this card to 'on Hold'. The developer need not wait for their response after informing. From a card completion perspective have retained the other points since I think it is better if product team itself completes it to prevent it from missing out and tech knowledge.

[petmongrels]

Removed from en.json and mr.json in both web app and android app. impl specific ones in en.json also removed from all languages.

Spreadsheet

• https://docs.google.com/spreadsheets/d/12deGycOlFbv-mOjY3gorqkc7YyGsf-K524bWMHOyH-s/edit#gid=0

including this commit

• avniproject/avni-client@d64180f

[mahalakshme]

Found that none the active orgs use any of the wordings removed in any active concepts. The active orgs that use as well have translations uploaded. So no need to upload translations. Checked with form names in couple of orgs as well.
CK and IHMP orgs also have translations uploaded, so should not be a problem for them as well.

[AchalaBelokar]

• I login with maha@rwbniti22 and select language is marathi in the dashboard card approved word is not translated in marathi
• Then I try to register the work order name should be marathi
• 3rd page is not translated

• In the general encounter site Audit translation is not present
• In the work order daily recording form log book image1 Log book image2 Quantity diesel filled

• Site Audit form

• Site Preparedness

[petmongrels]

missing translations are implementation translations

[mahalakshme]

@Dinesh2019 can you test with prod org with 6.0 apk - the above missing translations are not because of 6.1.0 code change, it was missing from before.
Anything that u see for which translation displaying in prod and not on prerelease is only an issue
Check the above attached excel sheet to ease your work