Difference between revisions of "EposRoadmap"
| Line 14: | Line 14: | ||
*Basket that allows multiple transactions to be grouped together |
*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) |
**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. |
||
[[Category:EposSystem]] |
[[Category:EposSystem]] |
||
Revision as of 08:32, 25 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.
