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
  • Use till session variable (eg. $tillsession['scr_id'] instead of passing variables in function calls and urls (eg. $scr_id).

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

eposv2_1

• Debug function for displaying various levels of debug message.

• Separate dmo login from dmo ticket selling page so that it can be used for refunds and for logging in to perform the transaction (not just selecting tickets).

• Use same page for dmo sell tickets and normal sell tickets.

• Remove scr_id from url

• Implement refund option via the EPOS interface
  • Check all functions that count tickets check for refunded tickets
  • Check banking counts refunded tickets
  • Check number of seats remaining counts refunded tickets
  • Put refund link in requiring dmo session

• Integrate the current ticket printing functions to use the image.php include instead of the inbuilt function which is old and dated.
  • The title images for the receipts should either be taken from ticket image table (to be created) if exists or web title (change foreground colour) if not exists.

• 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.
    • Why bother with a seperate machine? Why not just have a backup system and basic web server installed on the laptops themselves? - Matt P
• 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.
• Option so that if someone is a SocsFed member, but does not want to join us, they can be hidden from the "Joining messages". i.e. If they don't want to join, then we should not ask them repeatedly everytime they visit.
• How about a tiny backup webserver with a 512Mb MMC hard drive measuring 10cm x 3.5cm x 2.5cm for £150?
• Denote in the search results (where there are multiple results) whether the person is a member or non-member (as was last known).
• Remove the permanent auto-ticket pre-selection which causes some confusion when people are trying to remove a (single remaining) ticket first before adding another one - may be open to further discusiion.
• Improve search system so it allows multiple words etc, i.e. searching "Matthew Knight" should return all the Matthew Knights in the university.
• Implement more strict control of the ticket rules. i.e. only one member ticket allowed per show. Any tickets sold outside of the rules should be sold via DM override.
• Improve display clarity, i.e. if there are errors, make sure they are consistent and well phrased in an obvious position!
• Allow show results reporting on a per-till basis now that till sessions are properly implemented.