Difference between revisions of "EposRoadmap"
(→Features to be included in the EPOS system) |
|||
| Line 1: | Line 1: | ||
==Features to be included in the EPOS system== |
==Features to be included in the EPOS system== |
||
| + | ==EposV2== |
||
| − | '''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''' |
||
| + | *Fix any bugs in [[EposBugs]] |
||
*Improve performance |
*Improve performance |
||
**Details of current performance can be found on the [[EposPerformance]] page. |
**Details of current performance can be found on the [[EposPerformance]] page. |
||
| + | *<strike>Implement session ids for till sessions. This will mean that the till sessions can actually do something</strike> - Done. |
||
| − | *Find a way to allow use of [[FreeMemberTickets]] after the end of october |
||
| + | *Incorporate all session varibles into till session |
||
| − | *Implement session ids for till sessions. This will mean that the till sessions can actually do something. |
||
| + | *Sort out functions into separate files. Check they are in the appropriate include file (eg. pass functions in pass.inc). |
||
| − | *Implement refund option via the EPOS interface |
||
| + | *Check authentication is done on all pages that require it. (Some pages do nothing except display information from another page that is authenticated). |
||
| − | *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) |
||
| + | *Implement refund option via the EPOS interface |
||
| − | *Store ticket_day_table data in memory instead of DB |
||
| + | **Refunds use transaction_type=REFUND |
||
| − | **It would probably be helpful to represent tickets and transactions as objects to make this possible. |
||
| + | **Count of tickets must be SOLD-REFUND |
||
*Integrate the current ticket printing functions to use the image.php include instead of the inbuilt function which is old and dated. |
*Integrate the current ticket printing functions to use the image.php include instead of the inbuilt function which is old and dated. |
||
| Line 32: | Line 33: | ||
**Looks more consistent than raffle tickets. |
**Looks more consistent than raffle tickets. |
||
**Could cache our members db beforehand. |
**Could cache our members db beforehand. |
||
| + | *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. |
||
*How about a tiny backup webserver with a 512Mb MMC hard drive measuring 10cm x 3.5cm x 2.5cm for £150? |
*How about a tiny backup webserver with a 512Mb MMC hard drive measuring 10cm x 3.5cm x 2.5cm for £150? |
||
[[Category:EposSystem]] |
[[Category:EposSystem]] |
||
Revision as of 13:21, 12 December 2006
Features to be included in the EPOS system
EposV2
- Fix any bugs in EposBugs
- Improve performance
- Details of current performance can be found on the EposPerformance page.
Implement session ids for till sessions. This will mean that the till sessions can actually do something- Done.
- Incorporate all session varibles into till session
- Sort out functions into separate files. Check they are in the appropriate include file (eg. pass functions in pass.inc).
- Check authentication is done on all pages that require it. (Some pages do nothing except display information from another page that is authenticated).
- Implement refund option via the EPOS interface
- Refunds use transaction_type=REFUND
- Count of tickets must be SOLD-REFUND
- Integrate the current ticket printing functions to use the image.php include instead of the inbuilt function which is old and dated.
- Work on getting a unique key field for members from the union, so people who are external members don't get hidden from the system.
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.
- 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.
- How about a tiny backup webserver with a 512Mb MMC hard drive measuring 10cm x 3.5cm x 2.5cm for £150?
