Air Compressor Bot
|
|
Home |
How it works |
Projects archive |
Contact Us Air Compressor Bot |
|
| The Career Path of Freelance Programming Jobs |
Community Software |
 |
Bidding Time: |
01/12/2004 22:02 - 08/12/2004 23:02 |
Budget: |
N/A |
Status: |
Closed |
|
|
|
Job Type: |
|
Description: |
This is a pre-gathered requirements list. Platform Restrictions Planned production platform is Debian (Sid/unstable branch). This platform has been chosen for ease of maintainence, availability and consistency. The language and application framework chosen is entirely up to the contracting group chosen. The single language restriction is that PHP is absolutely not permissable. The production RDBM will be PostgreSQL 7.4, or the most recent version in the sid package list at that time. Please keep this in mind when factoring in your PLSQL. Appliaction Type (Web Interface) Community / Ecommerce Software Similar Functionality slashdot.org Threadded conversations and user-contributed postings Polls cnn.com News blogging phpBB General Discussion Forum Amazon.com Shopping cart (and inteligent item relation) Yahoo Directory Myspace.com Profile/Finite home page Basic Implementation Requirements Templating System All dynamic data must be via cognant templates, the template language and library is up to the implementor. Pragmatic markup output or code embedded into markup is not acceptable. Database Database must be BNF 3 Features Accounts There will be four account types. All account types will have the same basic attributes, the account type will describe the access level. Each account will have some descriptive information about the user and up to (unknown number) images, one of which will be marked as the main image to display along side users articles. Home Page Each account will have a generated page, the page will be created by a dynamic list of fields which are edited by the user. The meaning of each field will be editable by the administrator. Biography Each account will have a small blurb, or "bio", which will describe the holder of their account. It will include the name, email, homepage and zip code of the account holder. This list of items should be editable by the administrator. Also, any of this information should be available to place in the templates when viewing anything contributed by this user. This is somewhat, but not entirely, seperate from the users home page. Account Types General A General account will have access to base features only. Moderator Moderators will have the ability to remove Comments, Photos and Forum posts provided by other users. Moderators will be provided with a list of new items they have yet to see, this way all moderators have a chance to view content contributed by general users. Editor An Editor account will have access to the editorial queue for user contributed items (polls, articles, products, etc). They will have access to publish and unpublish said items (Adding or removing them from public view), and they will have authority to edit, view, and or remove items from the editorial queue. This access level also has the privileges of general and moderator accounts. Administrator The administrator account will have access to alter all customizable behaviors of the software. Buddy List Users will be able to add other users to their buddy list, and will be able to see when the user is logged in (has an unexpired session) Messages Users will be able to send eachother simple text messages. A url which describes the user to send a message to should exist in order to add "Send poster a message" type of links in comments or articles. Personal Score Keeping Users will each have the ability to record events. The data for each record will be a date (user input), event name, event type, and a score of float value. User Statistics Users and those viewing a User's profile will be provided a list of articles, product suggestions, polls and other things contributed by that user. In addition, they will be provided a total count of all posts and comments of all types (complete total and break down by type), and the number of points (spent, or not) the account has accumulated since its creation. Calandar Personalization Users will have a personalized calandar, which will display to them all global events, all local events within a range they specify (calculated by postal code). Users who add local themselves (see Calandar -> Local Events below) events will have the option to send invitations to users in their buddy list, after the scheduled date of the event they will be able to record the score of each player invited, and the attendance status. All scores for users recorded as attending will automatically be provided with an entry in their score sheet (see Personal Score Keeping, above) Bookmarks Users will be able to keep a local "favorites" or bookmark list, where they can store the location to any items in the system. News Articles Articles will be one of the core entities of this application. Articles can be submited by regular users, upon which time they will get added to a queue for review from the editor. Some WYSIWYG formatting should be provided. WYSIWYG Formatting What you see is what you get formatting. Should provide some visual to hyper text mark up language translation. Also, some formatting for tags or limited valid html should be provided. Images Each article can have up to (unknown amount) of data worth of images. These images can be added or deleted by the creator of the article or the editor. Submission Once the article is submited to the editor the author no longer has access to it. Users may select a category to place the item in when it is submited, however this is only a suggestion as the editor may place it in a different category prior to publishing it. Polls Polls will be contributed by general members, and upon editorial approval will be listed and available for users to take. Accounts with editorial access can select a poll to be featured in the main index of the system (the front page). Question Polls will generally ask only a single question, although the ability for polls to ask multiple questions should exist. Answers Up to (configurable amount) of multiple choice answers will be provided, and a user upon taking the poll will simply answer one of the above questions. Shopping Products Product suggestions can be submitted by users. They should either let a user provide a little "what they think we need", or they should allow the user to draw up a complete product entry. Product items are not necessarily for sale on this site, although some are. The main functionality is to provide reviews for products, and connections to affiliated entities which do have this product for sale. Features The features list would be one similar to Amazon.com's Action Shots Should allow multiple image uploads with a description for each image. Members can submit action shots. Price Points Items we do carry directly will be available for purchase with not only credit cards and etc, but with points associated with the account as well. In addition, not all products that are purchasable with points will be purchasable with currency, and vice versa. Other Calandar Events Global events will be added by the editor accounts. These events will be viewable on all users calandars. Events will include a name, a short description of the event, a location, and an optional URL for additional information. Local Events Users will be able to post local events in their area, and will be able to view events posted by other users within a selectable radius of their location. Events, as all things user contributed that bypass the editorial queue, should be removable by moderators if they are inappropriate. Something to talk about In addition to the above types of items, there will be a slightly more constrictive meta-item which administrators can create. In creating it, the administrator should have an interface to add any number of small fields. These fields will be filled in by users, and the items can post it to the editorial queue. This does not allow the free-form entry that articles provide, but rather each administrator-added item type will simply provide a list if fields the administrator can label for users to input. Much of this will be used for a directory. Each of these items will be automatically placed in the category selected for the item when it is described. All things above Awards Items can be given awards which will be shown in the items view. Awards will have an uploadable image, an exiration date (at which time the award remains attached to the article, but the article is no longer featured in the section associated with the award) Example: "Article of the week" Ranking Users will be able to rank items, and their vote should be counted only once. The ranking will be displayed along side the items listing, and when viewing the item directly. Threadded Comments Threadded comment views or items that use serials to make parent child relations reguardless of content. A member of the site should be able to comment any item, including another comment. Comments will have the some of the attributes of other items. Forum The forum is quite simple. Its functionality is much like that of phpBB or other bullitien board software, however it will need to be connected with the accounts and points of the rest of the system. Special Topics In addition to a general forum, there will be special topics where users tell their stories related to a specific topic. The entries will be ranked by viewing users. Searching An advanced search vector will be needed. The tsearch2 library for PostgreSQL should be sufficient to implement this. Each item should have two search vectors, one for key words of the item (Either extractred from the title of said item or added manually), and the second for searching all content in the item. Results should be sorted giving the manually associated key words highest prescedence. Related Items List The high prescedence keyword list will also be used to provide contextual referencing to other things on the site. If one is viewing an article for instance, there should be (unknown number) related links. Advanced Search Advanced search interface will allow users to sort specific item types (Articles, Products, etc) or all items, and allow users to sort in order of any combination of relevance, ranking, and age. Contextual Menu A complex hierarchial menu will be the used for the categorization of all items. The hierarchial menu will be editable by the administrator account. Each item in the account will resolve to a viewer for a specific type of item, and any items placed in that category should be listed thusforth. Any category in the list can have child categories. A navigation similar to google's Directory will be caused for general browsing of all items in the site. Points System Any action a user makes adds a number of points to an account. An active tally is kept, giving the user a classification. These points can be spent on merchandise, and spending these points will not change the users status, however points can only be spent once. An indefinite number of classifications will be editable by the administration interface. Additional Points In addition to collecting points by contributing information users will be able to collect additional points for reffering other users to the site, having their item awarded. Arbirtrary Points Along with just about every other detail of the system, the administrator should have the ability to arbitrarily award points to an account. Related Projects:  Database To Form Simple Php Template Changes Add Content To Site /addresses Custom Filesharing App Weekly Pick'emThis project is the proprietary information of .
Click here to remove this project from OUR database.
|
Operating System: |
Linux |
Database System: |
PostgreSQL |
| <<< back |
|
| Home | Projects archive | RSS | Resources | Links | Contact Us | © 2004-2008 ProjectsList.biz /4.538 |