Re: [sahana-maindev] Pledges are not send to inventories in RMS

[Chamindra De S. <cha...@op...>]

Hi Chamara,

Thanks for taking the time to elaborate and for looking to improve the RMS
module. I agree it needs more improvement. In my opinion a pledge should not
be associate to an inventory and they should be no need for an approval for
someone to make a pledge.

However there should be a facility to transfer the pledge to an inventory or
request as a separate action.

Also a another very important feature then is the report and tracking of
where pledges went, totals of the requests from a location, such that some
estimation and tracking is available to potential donors.

Be careful of putting an authorization workflow though as this can introduce
bottlenecks during a disaster. Rather we should depend on heavy auditing of
who did what transaction for future reference. This should be enabled in our
security framework as well. To make it more readable we need a action to
action description mapping. Ravith we can automate this.

On Wed, Jun 25, 2008 at 11:20 AM, chamara caldera <cha...@gm...>
wrote:

> Hi all,
> The previous description seems to be not very clear to everybody. Let me
> explain it in a little bit more detail.
>
> I have attached two diagrams to this mail, one which shows the method which
> requests are fulfilled in the existing RMS, and another shows a method that
> IMHO would be a better way of fulfilling requests.
>
> The following describes how pledges and requests are linked in the existing
> RMS.
>
> 1. Various entities make pledges in the RMS.
> 2. Various entities make requests in the RMS
> 3. When fulfilling requests, the RMS considers both pledges and items in
> the inventories. (The pledges are maintained outside of the inventories).
>
> Please see diagram old.jpg
>
> What I suggest is described below.
>
> 1. Various entities make pledges in the RMS.
> 2. An authorized person accepts the pledges and they get added to the
> inventory.
> 3. A pledge may not get added to an inventory if it is not accepted by an
> authorized person.
> 4. When fulfilling requests items in the inventory are used. (assuming that
> inventory contains items from accepted pledges)
> 5. Further in special cases where pledging entity does not want their
> pledge to be added to any inventory, we can allow requests to be fulfilled
> directly by a pledge. (Denoted by the dotted arrow).
>
> See diagram rmsnew.jpg for the method suggested by me.
>
> Please send in your comments on this.
>
> Best Regards.
>
> Chamara.
>
>
> On Wed, Jun 25, 2008 at 9:44 AM, chamara caldera <cha...@gm...>
> wrote:
>
>> Hi all,
>> In Request/aid management system(RMS) when new pledge action performs it
>> ask the inventory. But those pledges are not tracked in the inventories.
>> They are in a separate table. But if they store in a separate table  no
>> point of asking inventory in performing the pledge action. So there are to
>> solutions.
>> 1. Remove inventory completely from the new pledge interface and table.
>> 2. Send pledges to inventory when they delivered. And use those to fulfill
>> request instead of taking items from pledges and inventories as two
>> entities.
>> In practical situation i think second solution is more suitable. What we
>> can do is keep this as a known issue in release and fix it in trunk.
>> cheers
>>
>>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Sahana-maindev mailing list
> Sah...@li...
> https://lists.sourceforge.net/lists/listinfo/sahana-maindev
>
>


-- 
Chamindra de Silva
http://chamindra.googlepages.com