bit of code needed

[Nathan Collins]

Looks like a chicken/egg problem to me!

On Thursday, 4 August 2016, Paola Di Maio <paola.dimaio at gmail.com> wrote:

> Thank you Martin
>
> I thought if someone is up to do a bit of coding would respond and I d send
> the spec offlist
> but I attach here it, does it come through the list?
>
> On Thu, Aug 4, 2016 at 12:55 PM, Martin McGrath <mcgrath.martin at gmail.com
> <javascript:;>>
> wrote:
>
> > From experience there's a lot less pain involved for both parties if you
> > provide a specification.
> >
> > There really isn't close to enough detail in terms of platform, language
> or
> > tools here for an approximate response, let alone an informed one.
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL: <
> >
> http://www.electronclub.org/pipermail/members/attachments/20160804/57998ddf/attachment.html
> > >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://www.electronclub.org/pipermail/members/attachments/20160804/ff49bdf4/attachment.html
> >
> -------------- next part --------------
>
>
> OPEN EPROCUREMENT/OPEN TENDERING SYSTEM
>
> THE SYSTEM WILL BE AN ONLINE EPROCUREMENT PLATFORM, IMPLENENTED USING OPEN
> SOURCE SOFTWARE
> AND CUSTOMISED TO SUPPORT THE MAIN REQUIREMENTS AND WORKFLOW OUTLINE BELOW
>
> VERY ROUGH PROJECT OUTLINE
> ------------------------------
>
> 1. MAKE A RECOMMENDATION FOR WHICH OPEN SOURCE PLATFORM TO USE
> (SEE THE AVAILABLE OPTIONS BY SEARCHING ONLINE FOR OPEN SOURCE E
> PROCUREMENT/TENDERING SOFTWARE
> such as vprocure
> EXAMPLE: https://sourceforge.net/projects/tendersystem/
>  RATIONALE FOR CHOICE SHOULD BE: OFFERS THE REQUIRED FEATURES, SIMPLEST
> AND LIGHTEST SYSTEM TO DEPLOY AND MAINTAIN)
>
> 2.  CUSTOMISE THE IMPLEMENTATION AS FOLLOWS
>     1. ENABLE WORKFLOW  *see below
>     2. CUSTOMIZE DESIGN AND GUI - see separate mockup to follow
>
>
> 3. MAIN REQUIREMENTS AND FUNCTIONS
>
> -  USERS CREATE ACCOUNT  (TWO TYPES OF ACCOUNTS, EITHER A CUSTOMER ACCOUNT
> OR A SUPPLIER ACCOUNT)
>
> =  A CUSTOMER ACCOUNT SHOULD CONTAINT  GENERAL PROFILE  ATTRIBUTE (TYPE OF
> CUSTOMER (company or individual, company type, location etc) CONTACT
> DETAILS, TYPE OF JOB.....NUMBER OF JOBS POSTED, SUPPLIER FEEDBACK ETC)
>
> -  A SUPPLIER ACCOUNT SHOULD CONTAIN GENERAL PROFILE (TYPE OF SUPPLIER,
> size, location, skills, equipment they have, CONTACT DETAILS,  TYPE OF
> JOB.... NUMBER OF JOBS STARTED AND NUMBER OF JOBS DELIVERED, CUSTOMER
> FEEDBACK ETC)
> note" this function is similar to freelancer.com
>
> -  BOTH USERS MUST SELECT A 'TYPE OF JOB' PREFERENCE IN THEIR PROFILE
> (1.JOB BASED ON OPEN DESIGN  2. JOB SPEC IS BASED ON PROPRIETARY DESIGN 3.
> BOTH
>    (the system should hae a MATCH function where the jobs will be matched
> according to the PREFERENCE)
>
> -  CUSTOMER ACCOUNT WORKFLOW:  ( CUSTOMER SHOULD BE ABLE TO CREATE AND
> POST JOB SPECIFICATION , SELECT SOME DESIRABLE SUPPLIER ATTRIBUTES SUCH AS
> SKILLS, LOCATION, LANGUAGE ETC- ENTER TEXT, UPLOAD DOCUMENTS TO THE POST,
> THESE COULD BE DRAWINGS)
>
> = ALL SUPPLIERS WHO MATCH THE ATTRIBUTES SPECIFIED BY THE CUSTOMERS, TO BE
> NOTIFIED OF NEW JOB POSTING
>
> =  SUPPLIERS WHO QUALIFY (WHO MATCH THE ATTRIBUTES SPECIFIED BY THE
> CUSTOMER) CAN BID TO FULFIL THE JOB SPECIFICATION OFFERING
> -  PRICE, TIME OF DELIVERY AND OFFERING QUALITY ASSURANCE
>
> -  CUSTOMER AND SUPPLIER NEGOTIATE TERMS FOR PROJECT COMPLETION AND AGREE
> TO VARIOUS POLICIES *POLICIES FOLLOW
>
> =  AFTER THE CUSTOMER AWARDS THE PROJECT TO THE PREFERRED SUPPLIER, THEY
> BOTH ENTER AN AGREEMENT WHERE THEY AGREE TO A WORK SCHEDULE (HOW MANY
> ITERATIONS THE SUPPLIER IS EXPECTED TO COMPLETE THE WORK ETC) AND TERMS OF
> PAYMENT
> -  AFTER THEY ARE BOTH SATISFIED WTTH THE AGREED SCHEDULE, FULL PAYMENT IS
> MADE TO THE PLATFORM BY THE CUSTOMER FOR THE ORDER,
> -  ONLY 10% IS TRANSFERRED TO THE SUPPLIER (NON REFUNDABLE) TO COMMENCE
> THE WORK
> -  BOTH CUSTOMER AND SUPPLIER SHARE A COLLABORATION SPACE WHERE THE
> SUPPLIERS SHARES DESIGNS, DRAFTS, POSTS QUESTIONS AND COMMUNICATION TO
> PROGRESS THE PROJECT
> - AT THE COMPLETION OF EACH SUCCESSFUL ITERATION, THE SUPPLIERS RECEIVES
> 10% OF THE TOTAL PAYMENT, FOR A TOTAL OF 5 ITEREATIONS
> - IF CUSTOMER IS NOT SATISFIED AT ANY POINT, WITHDRAWS THE CONTRACT AND
> PROCEEDS WITH ANOTHER SUPPLIER
> -  AFTER SUCCESSFUL COMPLETION OF 5 ITERATIONS, (AND PAYMENT OF 50% OF THE
> TOTAL PROJECT COST)
>     A) CUSTOMER ACCEPTS THE COMPLETE PROTOTYPE AND APPROVES THE FINAL
> PAYMENT  TO THE SUPPLIER (COMPLETED SATISFACORILY)
>     B) or  CUSTOMER  DOES NOT ACCEPT THE COMPLETE PROTOTYPE BUT APPROVES
> FINAL PAYMENT TO OBTAIN FULL RIGHTS TO THE PROTOTYPE (COMPLETED BUT NOT
> SATISFIED)
>     C) CUSTOMER DOES NOT ACCEPT THE  PROTOTYPE, AND EITHER MOVES ON WITH
> ANOTHER SUPPLIER (KEEP THE PAYMENT IN THE PLATFORM JUST FIND ANOTHER
> SUPPLIER)  or OBTAINS A 50% REFUND OF THE INITIAL FULL PAYMENT THEY MADE
>
> -  PROJECT CLOSED, CUSTOMER AND SUPPLIER GIVE FEEDBACK AND RATING
>
>
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.electronclub.org/pipermail/members/attachments/20160804/62c7fc16/attachment.html>