About the program

Description An implementer on Avni is someone who configures Avni for an NGO An NGO is setup as an organisation on Avni The implementer typically works with a dozen different NGOs Avni requires mechanisms for these implementers to be able to configure Avni easily and without making mistakes A list of changes that will help is given below Scroll further down for details on each Organisation health verification M 1.Overall organisation metadata health verification 2.Overall organisation data health verification 3.Apply immediate health verifications when making changes such as setting up subject types Organisation metadata migration L 1.Allow definition of organisation types test production etc 2.Create mechanisms to migrate metadata across organisation types This will include ways to visualise a metadata diff across organisations 3.Allow mechanisms to recreate test environments from production 4.Bonus Allow partial migrations across organisation Improve usability of the csv upload feature on Avni S 1.Good error messages 2.Good sample files with data Miscellanous S 1.Verification and fix of documentation 2.Ability to remove fast sync for an organisation 3.Disallow fast sync for an organisation 4.Disallow all sync for an organisation Organisation health verification When running an organisation on Avni it is important to pinpoint any data or metadata problems in the system so that we prevent problems in the future by easily fixing them Specific problems include 1.Sync attributes set up incorrectly in data 2.Subject types that have sync attributes that do not match the way it is setup 3.Duplicate form mappings 4.Users who do not have the right configuration to allow for correct sync 5.Identifier settings wrongly setup or not enough identifiers allotted 6.Features such as Glific integration turned on but not set up correctly The Organisation health verification will identify these problems and report them so that an administrator can take corrective actions This feature will also include instant verifications that prevent the user from making incorrect changes to configuration Organisation metadata migration When developing an app on Avni there are usually two organisations testUAT and production This is essential to be able to test changes on one and apply them on another The current mechanism of doing this is using a metada download and upload The download creates a zip file of all changes and can be used to upload to another organisation Some of the issues with this mechanism is that 1.There is no protection against uploading to the wrong organisation 2.There is no way to know what changes are really going to be applied 3.There is no way to upload partial changes This is really important when there are multiple changes going in parallel and only part of the changes are required to be applied 4.It is hard to migrate to organisation groups where multiple organisations need the same metadata The purpose of this feature is to mitigate the above issues and provide an errorfree and easy migration of metadata on Avni Improve usability of the csv upload feature on Avni and Miscellanous These changes are small pieces of work that can be worked on as a warmup to work on Avni These changes help immensely in maintaining organisations Goals MidPoint Milestone Goals 1.Set up of project complete 2.S feature 1 completed 3.M feature completed 4.Goals Achieved By Midpoint Milestone 5.M feature completed 6.L feature completed SetupInstallation 1.Setup documentation here 2.Ensure you set up avniserver and avniwebapp for this project Others are not necessary Expected Outcome Each item once implemented will do one or more of the following 1.Improve the implementer experience 2.Reduce mistakes and rework. Acceptance Criteria Detailed acceptance criteria will be created on individual stories before the start of the project Implementation Details avniserver is JavaSpring Boot while avniwebapp is a static react based app

Perks

1. Lucrative stipend of INR 1 lakh over a period of 3 months. 2. Dedicated 11 mentorship by industry experts. 3. Handson experience to hone your skills. 4. Access to bootcamps and expert sessions. 5. Potential job extended internship opportunities. 6. Opportunity to network with global opensource tech leaders.

Who can apply?

Only those candidates can apply who:

1. are from Any,
2. and specialisation from Any,
3. are available for duration of 3 Months
4. have relevant skills and interests

Terms of Engagement

1. 50000 received on completion of midpoint milestone as decided with mentor. 2. 50000 received on completion of final milestone as decided with mentor. 3. Certificate of completion received on successful completion of internship.

Number of openings

1