Any progress on offline client ? 

Thx


On Tuesday, November 15, 2011 at 5:04:59 PM UTC+4, George wrote:
>
> Dear Colleagues , 
>
> As Previous discussion  has many messages I decided to create separate 
> topic with the definition what we need on current stage and in future for 
> our current project – your ideas are very welcome!
>
>  
> 1.      Off line data collection is a very simple module which will allow  
> credit officer to collect data from the remote centers without internet 
> connection on his laptop.
> 2.      During the data collection (manual input) credit officer has to 
> see some outputs ( savings,  repayments for previous period and many 
> statistical information.
> 3.     Business  process can be described as following:
> a)      Loan Office (LO) downloads data from Mifos for certain Center ( or 
> branch ). I was thinking it is possible with Pentaho BI  
> b)      LO  brings this data on his Netbook to  remote center | brunch ;
> c)      LO officer is filling new transactions in off line data 
> collection  module ( I was thinking about Spreadsheet)
> d)      LO brings back his Netbook or USB  and importing data in to MIFOS. 
> For that he has to login into Mifos , click on nice link called “import 
> data”  ,  select the file and define center | group | branch and click 
> IMPORT.
> e)      After validation system will imort the data: like LO entered it 
> into Mifos one by one.
>
> Now questions:
> 1.      Which format has to be used for Export/Import ?  
> XML|JSON|CSV|EXCEL| OTHER
>           As a business user I prefer EXCEL , as a Developer XML .
>          YOU?
>
> 2.     Develop client (Web or Gui) or use Spreadsheet?
>        I prefer to use spreadsheet – it is MUCH MORE USEFUL , allot of 
> time will be saved, we will transfer risk from Mifos to Spreadsheet, (by 
> other words from Community to Client).
> 3.      Which are the steps for development? (whatever client will be 
> used)? See my approach :
>          STEP 1: Define Format
>          STEP 2: Server side development: IMPORT API
>          STEP 3: Try to download Information using BI   (if that is 
> impossible try to do it from app)  
>          STEP 4: 1st ITERATION testing / user story  ( THAT IS WITHOUT 
> CLIENT ! NO NEED FOR CLIENT AT THIS POINT)
>          STEP 5: Redesign/ refactoring (if needed)
>         STEP6: Make decision about Client ( Web, GUI or Spreadsheet)
>         STEP 7: 2nd Iteration testing / user story
>         STEP 8:  Corrections, final testing;
>
>  NOTE: that API actually is implemented and can import transactions one by 
> one. All is needed to call that function in cycle and path correct 
> parameters . Not a nice solution (may have a performance problem) but will 
> be enough to build a model and do following development / improvements.  
>
> And last thing: Dear developers please now put number of days you need for 
> development  for each steps.
>
> Best Regards,
> George | Cleaner@MifosMIS Project
>
> P.S. Hope you will not ask me why I  am not doing all those steps  :-)
>
>  
>
>  
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mifos Developer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mifosdeveloper.
For more options, visit https://groups.google.com/d/optout.

Reply via email to