 | MEMBER LOGIN |
|
|
 |
|
 | SERVICES & FEATURES |
|
|
 |
|
 | THE 20 LATEST PROJECTS |
|
|
Project: LAMP digital delivery 
ID: 1208520032 |  |
| Status: |
Frozen (No bidding. Waiting for action from project owner.)
|
| Budget: |
N/A
|
| Created: |
4/18/2008 at 8:00 EST
|
| Bidding Ends: |
5/13/2008 at 8:00 EST (Expired)
|
| Project Creator: |
theonionpeeler
Rating:
(No Feedback Yet)
|
| Description: |
LAMP web app: Version 1
First iteration of an Apache, PHP mySQL based system for secure delivery of sets of printable educational flashcards.
The app will create A4 PDF files (one for each set) on the fly from content stored in the database and on the server.
Standard webhosting limitations are to be respected … e.g. globals off.
Long term the aim is to stay with one developer and turn this into a central WAN server app that will feed and automatically update other local servers automatically.
It could also provide the basis for a multimedia delivery system rather than PDF/print output.
Note that even though we want to create A4 pdf's for printing purposes, the final physical flashcard format required is A5 (see examples attached), each card has two sides, e.g. cards contain either:
FRONT… text
BACK… text
Or
FRONT… an image, and text (could in rare cases be an image on its own)
BACK… text
Or
FRONT… an image, and text
BACK… an image, and text
At the moment the cards are printed manually from Word files or Freehand files… (see examples attached) Note that the first half of the pages of the doc contain all the front faces of the cards, then there is a blank that corresponds to the back of the front index card, and the remainders are the backs. (This way the user prints for example pages 1 to 5 then turns the printed output round and feeds them back into the printer and prints pages 6 to 10… then cuts the A4 pages in half to produce the finished product)
PDF FILE CREATION on the fly.
The application must be able to pull the correct content from the database/server and organise it so that the correct fronts and backs coincide on each flashcard… the PDF document must include the flashcard set id, version, and copyright info on each card, and number the cards correctly.
Future iterations will probably have to work within joomla CMS and community builder extension and use a credit based payment / download system similar to that found at istockphoto.com (e.g. for a basic joomla compatible system see vodes http://www.sakic.net/products/free_products/ )
SECURE LOGIN
The application requires a secure https login and user management with permissions… (Users, content managers and admin.)
USERS
- Registered users must be able to search for, browse and select, single or multiple sets for download (no credits system needed yet, at a later stage only users with credits will be allowed to download.)
- see thumbnails or previews clear enough to read for the sets they are interested in
- Sets selected for possible download during browsing should be listed apart for final acceptance or rejection before downloading (as in many shopping cart apps)
- must be able to download the files accepted
- Must be able to request edits, new or different sets, and report problems (post support requests) to Admin.
- must be able to logout
CONTENT MANAGERS
content they create will be used to build the PDF files the system creates “on the fly”.
They have the same permissions as users but can also:
access an interface / editor to:
Create a new flashcard set:
- Set number of cards in set
- Add content to Fronts,
Upload and place images
Add text alongside or overlapping images
- Add content to Backs
Upload and place images
Add text alongside or overlapping images
- create the front index card, (see examples)
this takes the form of the set ID (Title) and two lists side by side in the top right of the card in small type with the content of all the cards fronts in one list, and corresponding backs in the other, so people can see at a glance the content of the set. It is very important that this information is clear for the final user.
If images are used, one of the images appears reduced in size on the top left.
(the back of this card is always blank) (see examples)
Once the set id, version number, copyright and card number data is entered (obligatory) by the content manager, the editor automatically adds in small typeface in the Back, top right corner:
- the flashcard set id to each card in the set
- the version number to each card in the set
- the copyright info to each card in the set
On the Back, bottom right corner
- the correct card number to each card in the set (The front index card is not numbered)
- Preview the whole set or individual cards in that set, OK it, and save it
- They can place the flashcard set in any existing open (unlocked) category or sub category.
- Update / edit existing sets (adding, editing or removing fronts or backs)
- Move existing sets to different levels in the file tree
- delete an existing set.
- must add descriptive information and tags/metadata about the sets and/or the individual cards.
- view and respond to edit requests from users
- report problems (support requests) to Admin.
- logout
ADMINISTRATORS
must be able to do as the users and content managers can and also:
- manage the “file tree” … how the sets are organised…
- be able to create categories and sub categories that hold the sets…
- manage the users,
- manage their passwords,
- manage permissions
- block, limit or allow downloads, for all, or for specific users
- block or limit editing capabilities, for all, or for specific Content managers
- can lock and unlock categories or subcategories
- view statistics about who accessed what and when, and what they did.
- view ip addresses and access data
- manage logfiles
- must be able to view and respond to edit requests and support requests from users and content managers.
- must be able to logout
LEGACY FLASHCARD SET MANAGEMENT
I know it's a tall order, but if there is a way of capturing existing information from the .doc files and FH.11 files…that would be a great help
Design guidelines
The App does not have to be the most beautiful web creation ever… but certainly should not be a visual mess, a simple, clear unconfusing interface is the goal.
We want to work closely with you on this and make sure we are happy with the progress every step of the way… if you have a preferred way of working at a distance we are more than willing to listen, transparency and honest approaches are appreciated.
Payment
payment terms are negotiable but we envisage full and final payment to be via an escrow account upon receipt of a working version which we are happy with …in our server.
|
| Attached File: |
|
| Job Type: |
|
Messages Posted: 8
| |