Re: [CK-Ledger-users] Re: I would like to help
Status: Beta
Brought to you by:
ckwu
|
From: C K Wu <ck...@ch...> - 2002-05-23 03:22:16
|
Hi, Robert,
robert del huerto wrote:
> On Wednesday 22 May 2002 07:19 am, C K Wu wrote:
> >
> > Welcome on board. Please go ahead and develop the Rental module.
> >
>
> Thanks, I'll try. ;)
>
> > .... Substantial testing will have to be made
> > to ensure that the new 'accno' field is useable by other modules.
>
> Will do.
>
> > e) Please ensure that you can assign copyright of your finished
> > work to the public under GPL.
>
> I won't be working on ck-ledger at work. All development will be done on my
> free time. The GPL will be the license for the code.
>
> > f) When developing the Rental module, you may like to make
> > provision for turnover rent, rent free period and other
> > non-recurring charges, like air-conditioning, off-hour lighting
> > etc. These would be useful for rentals over a commercial
> > office/arcade complex.
>
> What we do now is to manually enter these types of transactions. Would that
> work for you?
>
Fine by me. But, just as a suggestion, I have seen design like this,
Recurring charge (stable over the course of one year) kept in master table:
- rental, municipal rate, fixed monthly water, gas, electricity charges
Non-recurring charge (changes every month or fortnight) kept in transaction
table:
- aircon, offhour services, overdue interest, penalty, etc.
It's your call.
>
> > g) The collection of private household information is a rather
> > touchy issue.
>
> The sensitive data will be kept in a separate and optional module that will
> provide HUD compliance to those that need it.
>
> I'll start off with the waiting list. Here's a quick run down:
> - applicant is added to the waiting list and is date/time stamped
> - optional preferences are given to affect the position in the waiting list
> - applicants are transferred to newly available units based on waiting list
> sort criteria
>
With any waiting list, there is always a suspicion of official corruption,
ie buying off officials to jump ahead of the queue. I would suggest, besides
date/time stamping, to add,
a) audit trail on 'who' ($phpgw_info["user']["userid"]) performs a position
modification transaction
b) control over 'who' is allowed to perform such transaction.
[BTW, you may have already guess this. I have been a computer auditor for a
number of years,
so I am pretty interested in ensuring auditability and control of the finished
system.]
>
> Since tenants are a/r accounts, should I use the same a/r ledger to keep track
> of tenants? Or should I put them into an a/r subsidiary ledger and track
> them in a different set of tables? What do you think?
With ck-ledger's design, the customer(tenant) debt balance and invoice history
(ie the entire A/R module) is the equivalent of an a/r subsidiary ledger and the
'Account Receivable' in the main ledger is really serving the purpose of an A/R
control account.
>
>
> Hey, CK, will you be adding the prefix 'phpgw_ckledger_' to all of the tables?
> Is it cool if I add it to the tables I create?
>
The reason why I haven't follow phpgw's table naming convention was while
porting sql-ledger to phpgw, I was using sql-ledger's tables as a starting point,
making sure that the initial system is able to read/write sql-ledger tables
correctly.
I must admit, by now, I am not too keen on adding back the prefix, since it
involves
modifying just about everyone of the script files. So, if you prefer, do add in
the prefix for the tables you create, but I wouldn't consider it a necessity. If
necessary,
I'll dedicate a single release for adding back the prefix in the future.
>
> robert
>
> _______________________________________________________________
>
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>
> _______________________________________________
> CK-Ledger-users mailing list
> CK-...@li...
> https://lists.sourceforge.net/lists/listinfo/ck-ledger-users
Cheers,
CK
|