Difference between revisions of "EposRoadmap"
(→Potential Ideas for Future Versions) |
(→Features to be included in the EPOS system) |
||
Line 17: | Line 17: | ||
*Store ticket_day_table data in memory instead of DB |
*Store ticket_day_table data in memory instead of DB |
||
**It would probably be helpful to represent tickets and transactions as objects to make this possible. |
**It would probably be helpful to represent tickets and transactions as objects to make this possible. |
||
+ | |||
+ | *Integrate the current ticket printing functions to use the image.php include instead of the inbuilt function which is old and dated. |
||
==Potential Ideas for Future Versions== |
==Potential Ideas for Future Versions== |
Revision as of 09:29, 26 October 2006
Features to be included in the EPOS system
The EPOS system is currently in a bug fix stage. Please branch the epos system before adding features and please help to bug fix before adding new features
- Improve performance
- Details of current performance can be found on the EposPerformance page.
- Find a way to allow use of FreeMemberTickets after the end of october
- Implement session ids for till sessions. This will mean that the till sessions can actually do something.
- Implement refund option via the EPOS interface
- Basket that allows multiple transactions to be grouped together
- To be included in what ever release follows 2.0 (presumably 2.1 or 3.0)
- Store ticket_day_table data in memory instead of DB
- It would probably be helpful to represent tickets and transactions as objects to make this possible.
- Integrate the current ticket printing functions to use the image.php include instead of the inbuilt function which is old and dated.
Potential Ideas for Future Versions
- Backup EPOS system
- A standalone server which can be used when there is a problem with the network or webserver, etc.
- Instead of connecting tills to network, just plug into this machine.
- Serves a replacement www.filmsoc.warwick.ac.uk EPOS
- Allows selling of a standard rate 'backup' ticket.
- Afterwards can insert data into main ticket_log, etc so we have proper data for the show.
- Could allow refunds for people who are entitled to a pass at their next show.
- Looks more consistent than raffle tickets.
- Could cache our members db beforehand.
- How about a tiny backup webserver with a 512Mb MMC hard drive measuring 10cm x 3.5cm x 2.5cm for £150?