EposRoadmap

EposV2

• Fix any bugs in EposBugs

• 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
• Film name & number of seats need to be added to till session
  • Till session also needs to retrive all session info
  • Till session vars need to be made global so that they don't need to be passed
  • Once till sessions are global, $scr_id can be removed from urls and function passes

• The available_tickets function needs to return the number of available tickets with the other ticket info so that a is_sale_valid call is not required to determine whether to show the add/remove ticket buttons.

• 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.

• Style sheet for sell tickets page to keep all the boxes in static positions.

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.
• Improve performance
  • Details of current performance can be found on the EposPerformance page.
• How about a tiny backup webserver with a 512Mb MMC hard drive measuring 10cm x 3.5cm x 2.5cm for £150?