For this project, we require an intern who is qualified and willing to work core HTML5 offline functionality. If we able to add offline support in community-app then we can have same application working on all browsers with offline support and need of a desktop app will not be needed.

The project will involve the following:

• We can use IndexDB for storing data offline and once connected synchronize it, store actions that happened in same sequence and then fire against server.

• We can store some data in JSONs as key-value pair and offer pre-sychronize which will fetch data as JSON for creating clients and other actions in offline mode.

• Currently, HTML templates load from server everytime we refresh our application. As, discussed we should have some sort of template caching with expiry headers.

• We can make some template made available offline using application cache.

• With Template cache which is angular component. It looks for template in cache if not in the cache, it will load from server and then put in cache.

• Mimic synchronization back and forth mimic how you store, how you date it out.

We have released several versions of our Android app for field officers to go out in the field to process transactions, create clients, etc. Most recently, several outreaching interns added in significant new enhancements including refactoring, implementation of material design, offline, surveys, and new functionalities taking it from Version 1 to Version 2.

This project would continue that work and transform it into Version 3 - by following the refactoring design standards, providing a design refresh, and adding in new functionality.

Allows staff to go directly into the field to connect to the client. Reduces cost of operations by enabling organizations to go paperless and be more efficient.

https://github.com/openMF/android-client

Agent Banking has become a key new delivery channel to increase reach, lower cost, and broaden the depth of services available. We will be taking over the Egalite codebase that's being donated to the Mifos Initiative by BFSI Consulting - it's a fully functional Android-based app for agents that works with any core banking system. This project would involved extending the application so it fully integrates with and works on top of the Mifos X platform

The current codebase is stand-alone and can integrate with any core banking system. This project will involve converting it to work on top of Mifos X by leveraging the Mifos X APIs for all functionalities that exist in Mifos X and adding in APIs for the functionalities that aren't present in Mifos X but in Egalite. The project will consist of the following:

By enabling branchless banking, the costs of serving the poor are dramatically lowered, outreach can be extended to rural offerings, and brand new products and services that are more relevant can be delivered.

• Egalite Functional Overview - See http://bfsiconsulting.com/?page_id=179
• Egalite Architectural Overview
• Egalite User Manuals

This has a dependency on the Self-Service backend API's being available 

Allows a member/client in having a self-service channel allowing them more direct control and visibility into their financial livelihood. Enable members of the society on-demand access to their.financial records even with basic mobile handset

This project is a continuation of the initial PayGoSol foundation that was led by 2014 GSOC intern, Antonio Carella.

1. Create a pre-paid account mechanism as an account type or account option in Mifos (perhaps extending existing classes), zero fees.
2. Create a new API for consuming pre-paid account balances.  
3. Create a simple external model that mimics consumption by a household on a daily basis - imagined as a set of data received from solar panel (watts used, time of day, volts present).  
4. Load up pre-paid account by account transfer in P2P interface (my phone to your account) or via trusted agent - i.e. trusted agent receives cash and loads account on Mifos.

Work in 2015 will include adding the following features to make it an out-of-the-box solution that any PAYG hardware provider could use: 

Providers of pay-as-you-go solar can use MIFOS for their operations. MFIs can become such providers.

Mifos Android Client on MifosX

• CGAP Research on PAYG Business Models: http://www.cgap.org/publications/access-energy-digital-finance-models-innovation

Data migration can be one of the most challenging and time-consuming phases of an implementation of a core banking system. In 2013, GSOC intern, Avik Ganguly, built our data import tool for generating pre-configured Excel templates to migrate data into Mifos X. In 2014, Diunuge, extended this to other types of information in Mifos X along with integrating it from a stand-alone web app to a core part of the platform. The data import tool is now the foundation for all of our data migration tools.

This project would continue to extend the data import tool to new types of data and APIs that need to be imported, enabling office-level import, and continued integration into the platform. This project will also involve building on top of the data import tool to provide out of the box migrations from other legacy systems such as MicroBanker or Loan Performer. 

• Import for other types of data not currently supported
• Populate date using bulk APIs
• Enable office-level imports for larger organizations who find it too cumbersome to migrate an entire organizations worth of data at once
• Build out scripts on top of the data import tool to get data and transform it out of legacy systems like MicroBanker or Loan Performer.

It has many impacts

1. This drastically reduces the time to set up of initial configuration/data of Mifos X for organization adopting this system as MIS.
2. For data entry operator, this feature can be used as bulk creation option (such as import bulk loans, import clients)
3. These templates can be used as offline store. And once user has internet connectivity can upload these templates with captured data.

GSOC 2013 - Data Import Tool

GSoC 2014 - Data Import/Export feature

Data migration can be one of the most challenging and time-consuming phases of an implementation of a core banking system. It's often a barrier to financial institutions moving on to new and better more modern systems. It's critical to cleanly migrate over the historical data of a client and their transactions. Often the legacy system data needs to be cleaned up and transformed before it can be migrated into Mifos X and is one of the most costly and time-consuming phases of a deployment. We have an existing data migration tool for migrating from Mifos 2 to Mifos X that utilizes the Pentaho Kettle ETL tool.

This project would extend the existing Mifos 2 to Mifos X Kettle-based migration tool to provide a standard migration tool from Loan Performer - a low-cost, widely adopted system in use by hundreds of microfinance institutions throughout Africa and Latin America. It would provide one standard tool that any partner or financial institution could use for migrating from that specific system - it wouldn't require new tools to be made each time a migration is done. 

Extend the existing Kettle-based Mifos to Mifos X migration tool

• Write ETL scripts to get data and transform data it from Mambu format to Mifos format

It has many impacts

1. This drastically reduces the time to set up of initial configuration/data of Mifos X for organization adopting this system as MIS.
2. It widely opens the market that Mifos X is applicable for as it lessens the burden of converting from Loan Performer - a system that is widely used but not as modern and sophisticated as Mifos X.
3. It dramatically lowers the cost of implementing a system like Mifos X by reducing the complexity of the deployment
4. It increases transparency by ensuring financial institutions using Mifos can retain the full history for their clients.

http://nayan.github.io/move-to-mifosx/

https://github.com/openMF/move-to-mifosx

For better usability system needs to have notifications to the logged in user about actions he/she needs to perform in the application.

Build near-real time notification system in the web application to notify the user about action she needs to take. For example, if a branch manager is logged in the application and a new loan is created and is pending for approval by her, then the system should notify her about the pending action.

This involves both invoking and triggering these notifications based on actions or activities in the server as well as the extension of the user interface to support the display of the notifications along with the ability of the user to take action upon the notifications.

Notes on the proposed approach to invoking and triggering these notification can be found at: https://goo.gl/SD0HgC

It outlines:

1. Piggybacking on response header to send notifications
2. Create a new set of database tables for notifications
3. Implementing Queuing system like SpringXD for Notifications

Right now Mifos X contains core client management functionalities including tracking basic demographic information, know your customer information, document management, and survey collection through data tables. As financial institutions serving the poor begin to offer a more in-depth and diverse range of financial inclusion products, the need for more robust client management and in-depth client understanding has grows. Their core system needs to provide more and more CRM-type functionality that complement the portfolio management and financial/social reporting the Mifos X provides.

This project will work to deliver the initial set of customer relationship management functionalities including a module for tracking inquiries, complaints

This module will have a request management functionality. A request can be of 2 types: Complaints and Service Requests. Each request must be against a customer and optionally against an account of the customer. Each request will go through a simple workflow.

Actions that can be performed on a request:

Assign -> will change status to "assigned"

Start Work --> will change status to "in progress"

Close --> will change status to "closed" (with a sub-reason code)

At each step user can enter comments.

The customer summary screen will have a link to view the requests of the customer - along with a summary and current status - with option to click-through to get the complete history of each request.

Deepening the client relationship and ensuring fair, responsible, and transparent financial services to the poor is a core piece of the industry's roadmap for financial inclusion. Providing customers the ability to voice their concerns and feedback about the services they're receiving provides a simple yet powerful tool to protect the client. Empowering the financial institution with the ability to track these inquiries and overall maintain a more holistic relationship tracking entire lifecycle of their clients gives them a much better ability to understand their clients and respond to their needs with appropriately designed services and products.

Integrate MifosX with an opensource Point of Sale (POS) called JPOS.

Use case would be to get a debit transaction (cash withdraw from checking account) thru the POS device /local runtime with 2FA.  In India, the ability to get cash out through a point of sale network is provided for under RBI regulations. In production there will likely need to be an intermediate "Merchant Acquisition" or "Payment Processor" in between a single POS and MifosX Instance, but this could be abstracted out as a payment gateway only (primarily data mapping). The implementation target is the ability to do a 2 factor authentication on a POS device running JPOS (emulator ok), input account number (via some simple method), then be able to do a (cash-out) account withdrawal in real time to the MifosX account. Additional use cases would be to implement a transaction for payment for goods. i.e. enter specific goods, then do payment from MifosX account to Merchant Account (probably also in Mifos).

Familiarity with API work. Understanding of transactional flows.

Java.

Two-factor authentication - see other project idea .

https://github.com/jpos/jPOS/

We believe the Mifos X platform is super secure and impenetrable. Your mission, should you choose to accept it, is to prove us wrong, and help close gaps you may find.

Beyond a one time exercise, you should integrate (some of) the tools you've used into our build chain so that, even after you've gone, tools flag up future newly introduced potential vulnerabilities.

https://www.owasp.org/index.php/Main_Page

https://code.google.com/p/zaproxy/

http://wapiti.sourceforge.net

Run FindBugs & related tools for some serious static code analysis

http://en.wikipedia.org/wiki/Penetration_test

Develop ETL scripts to create OLAP cubes (fact and dimension tables in MySQL). This will allow managers to perform ad hoc slicing and dicing of their data 
to answer important questions about their operations.

• Create ETL scripts and tests
• Create a Mondrian schema to work with Saiku Analytics

This project would extend off of the work of a previous GSOC intern in building out integration with Saiku