REGISTRATION: Registration forms. The differents type of registration forms are 1.)Schools 2.)Papers 3.)ASB 4.)Radio 5.)TV 6.)Individual Stepped registration process…in an ideal world, but whatever will get this up will do, too. -Ie, User types in school name/zip/type org registration (P, R, TV, ASB). Once info entered, if in database, info pulled up. If dupes, ddl to choose from. -For expansion, master database of around 50,000 schools to use as server side reference for relational needs as per the process of automating school demographic assignment. -Users assigned levels of access for feedback purposes-organization or individual. Organization will require at least email validation.-MANDATORY submit fields. Database login store for application and login feedback access as well as identity. -Acquire information about users through registration. Gather information from user activity (capturing link and media usage through proxy?) and provide data for analysis. FEEDBACK: -Need a customizable template for projects as much of the basic info remains the same on each. Needs to be database driven for both user access purposes and automated reports. -Each school organization will have organization specific info to provide feedback on. For example, a paper will tell us whether or not they are going to publish a review. That isn’t information we would need from radio. From radio, we need to find out whether or not they’re going to add the record. I would like the feedback forms to be tied relationally to types of users so the login will determine the feedback form pulled up. Obviously, individuals will get completely different feedback forms than school organizations. Individuals could not, for example, schedule an interview, whereas a school paper could. -I would like interviews to be scheduled online. Example, user logs on, listens, goes to feedback and gets to the part where there is a list of times available for interviews. They select the time they want and the next time a user logs on, the time that is already scheduled… is ‘greyed out’ so it is no longer something they can choose. -MANDATORY submit fields. -Must be able to produce project reports from feedback. -Must be able to trace project submitted for feedback and follow up emails to all registered users who have not submitted feedback. MISC: -Reference example of presentation, NOT feedback or registration functionality: [url removed, login to view] Note: Site was literally built [url removed, login to view] aesthetic. -Becoming a public showcase for teen talent with content driven by [url removed, login to view] simply content supplied, but rated as well. The best music will be rated by peers, the best writing, etc. A blog is a good start for a community driven site, but I am still more interested in proving a showcase opportunity where talent is concerned. -In an ideal world, the blog will be used as a high school newspaper wire service of sorts. -Need the ability to expand both membership and services. At some point, will want to add a store. 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Installation package that will install the software (in ready-to-run condition) on the platform(s) specified in this bid request. 3) Complete ownership and distribution copyrights to all work purchased.
Windox XP in IE, Netscape..prefer Mozilla & Opera, too Windows or Linux..what are you most comfortable with?