[ILUG] [Sort of OT] PHP-MySQL developer team required for small project

[Andres Jimenez]

Dear all,

I know there is a PHP users list, but I posted there already :-)


I am working on a Purchase Order System for the Dublin Institute for
Advanced Studies. I want to modify (I have already started) Assetman (
 http://www.bctree.com/~assetman/   demo:
http://www.bctree.com/~assetman/assetman-gpl/login.php ), a PHP &
MySQL application (it uses ADOdb for accessing the database) with some
extra scripts for generating PDF files.

The modifications already done are just a few:

-"Email address" replaces "username" as userid field.
-Added a few extra datafield for some items.
-Hide any reference to Invoicing (we don't sell anything).
-Forms have been made simpler.

The current code is here: http:/www.stp.dias.ie/~ajimenez/DIASpo.tar.bz2
It includes Assetsman before being modified.

The code is very simple, with almost no separation between application
and presentation layers. We don't need any fancy look or a full
redesign of the application, so it can just be kept simple.

The code is GPL'ed, so feel free to reuse any code from any GPL project on this.

I need this team to develop this features:

--STAGE 1 Functionality

* Implementing a user & groups structure based in roles
     A user has to be part of at least 1 group. In every group 1 user
will have "supervisor" role and will be able to pass that "supervisor"
role to any user member of the group.
There will be 1 special group (Finance Department) and 1 special role
(Registrar). They ("Finance Department" group and "Registrar" user)
will be able to see any kind or order in the system and
approve/disapprove it.
For the rest of users, a non-"supervisor" user will be able of seing
his own orders only, while a "supervisor" user would be able to see
and approve the orders sent by the whole group

A graphic showing the path an order has to follow can be found here:
http://www.stp.dias.ie/~ajimenez/DIASpo.png

* A PO number will be assigned by the Finance Office only and not
being showed before of that. Something like a "Draft ID" would be fine
until the order has been finally aproved.

--STAGE 2    Tracking

* A tracking system, able of logging any order's change (creation,
modification, approval and deletion),including who,
when and IP.

--STAGE 3  LDAP authentication

*Password (and only password) will be taken from an openLDAP/Active
Directory  server. Username (email address) and any other information
about users would be taken from the MySQL database.


STAGE 1 has to be finished ASAP (during October). STAGE 2 & 3
can be delivered in November.

I know it's friday evening and possibly I haven't given enough detail.
We will allow some paid time for studying the code and discussing the
speciffic features required.

Feel free of sending any questions, quotes or samples of your work.

I will keep working on this this weekend, so don't wait until Monday
for contacting me.

Regards,

--
Andres Jimenez
IT System Administrator
School of Theoretical Physics
Dublin Institute for Advanced Studies
10 Burlington Road
Dublin 4
Tel. +353 1 614 0132

ajimenez at stp.dias.ie