Improvements and enhancements

We have been getting some suggestions for version 5 and I need some help prioritizing. Here are some of the suggestions:

Off sale options: this display an indication as to why an event is off sale
A new price setup with options for on and off sale, with maximum that can be sold in that category
RSS feed: This would be an expansion of the Events page displayed in an XML format.
Scheduled reporting: This would run reports for the promoters once a day and email them their reports
Gift tracking with gifts and donations in a separate table
Service charges and payments in separate tables
Unique publicity codes for each show
Bar coding the tickets and scanning them at the door

What order do you think they should be in? Is there anything left out?



Edited 1 time(s). Last edit at 03/07/2008 09:17AM by bruce.

Max sold in each category would be handy, and scheduled reporting with auto email would prpbably make many producers happy...

Price set up with on/off sale options and maximums would be great
Off sale with reasons - I like this!
RSS Feed: yes, yes, yes:)
Barcode/scanning at door

I'll leave the rest to those that use these options most.

Scheduled reporting - not so important with the ability to set up promoter reports via webtix
but I'm sure would be helpful for those that don't use that function. Our promoters/producers
were easily trained on this system and LOVE it. I don't think they'd want to go back to anything
else!

The RSS feed is basically the same thing that is in the Events.php page - just in an XML format.

The question is, what information do your clients and customers want in it?

Suggestions for new improvement and enhancements...

Free Event Listing: Educational institutions have many events that are free; creating a consolidated calendar and events feed is easier if listing a free event were possible in the base code.

Length of Program Time for better event feed and .ics export results. A hard coded 2 hours doesn't work for all events.

Dynamic site syntax (or word usage) as it relates to the type of event it is... for example theatre, sports, conferences, etc...
If you sell a sporting a event on Webtix5, the language the site uses isn't appropriate.

Dynamic form choice variables: For registration sometimes it is necessary to collect all the names. If someone can register for an event with 1 or 10 persons attending, having a dynamic response for the form choice options to require the collection of the desired information on each person is ideal. Currently the only option is to code the maximum number of responses possible and have no ability to force or require the entry before finalizing the registration.

We currently have customized workarounds for all of these, but I believe they would enhance the Webtix Product overall and should be incorporated into the core code.