ADA Changes and Best Available Seating

We are working on enhancing our website for the upcoming changes to the ADA.  We have SYOS covered thanks to the new "Reserve Held Seats" option for T_DEFAULTS with V10, which now works with ReserveTicketsSpecifiedSeats and that we use holds for wheelchair seats.

Initially we decided we would only enhance the SYOS ticketing path, but we have situations where we deliberately disable SYOS due to volumes, leaving Best Available as the only option.  The problem is that while ReserveTicketsEx allows the parameter for special requests, wheelchair being one of them, that will not work for held seats.

Has anyone done anything dealing with wheelchair seats and Best Available?

Thank you in advance.

Paul

  • It would be up to the web developer to decide how to handle such a situation.  If you request a specific hold code, that is all the best seating process will look for.

  • I just wanted to chime in and state that we have essentially implemented our ADA Ticketing using the methods Chuck describes below and it has worked incredibly well.   The ability to use a specific hold code made all the difference.     We are using it for wheelchair/companion seating, as well as sign-interpreted seating.     We use Seat Types to designate actual wheelchair seats, but then we set all of the wheelchair seats and companion seats to the hold code.   It allows us to seat those requiring wheelchair seats properly and get the best companion seats near them.     We do allow patrons to select companion seats from unheld available inventory if there are not enough held companion seats nearby.    We were also able to make it work not only on Best Seating but also in Select-Your-Own-Seat.     Chuck and his team really came through in enabling us to meet the ADA requirements when they added the ability to specify a hold code and use held seats in Best Seating.      We’re also able to handle situations where we have a special offer on seats in a particularl price zone, but have no wheelchair seats in that price zone.     We can recognize that and allow the patron to purchase accessible seats in a different price zone, but at the price of the special offer.   We’d be happy to review the details of all of this if anyone is interested.

     

    Alan

     

    From: Tessitura Web Forum [mailto:forums-tessitura-web@tessituranetwork.com] On Behalf Of Chuck Reif
    Sent: Monday, July 02, 2012 2:12 PM
    To: Levine, Alan
    Subject: RE: [Tessitura Web Forum] ADA Changes and Best Available Seating

     

    It would be up to the web developer to decide how to handle such a situation.  If you request a specific hold code, that is all the best seating process will look for.

    From: Nicole Keating <bounce-nicolekeating9176@tessituranetwork.com>
    Sent: 7/2/2012 12:20:00 PM

    Chuck – In V11, if there are no “Companion” holds nearby will it select Companion Seats from unheld available inventory?

     

    Thanks!

    Nicole

     

    From: Tessitura Web Forum [mailto:forums-tessitura-web@tessituranetwork.com] On Behalf Of Chuck Reif
    Sent: Monday, July 02, 2012 1:12 PM
    To: Nicole Keating
    Subject: Re: [Tessitura Web Forum] ADA Changes and Best Available Seating

     

    We experimented with the plan that you mentioned, trying to find companion seats as close as possible to the selected wheelchair seats.  The problem that we ran across was that it worked as expected for some house configurations and in a totally unexpected manner for other facilities, depending on how they were built.  We could never succeed in making the process consistent enough to release.

    So we decided to take another approach and added the ability to do best seating out of a specific hold code.  In v11 you can pass a special request of a holdcode to the ReserveTicketsEx method and the best seat request will honor that hold code.  This allows a web developer to take special action on ADA seating requests and even have different pools of seats for different situations--one hold code for wheelchair locations and a different hold code for hearing impaired seats, for example. 

    This has proven to be a better solution overall.  In addition, we added the hc_no (hold code number) element to the GetSeats methods to facilitate indicating special pools of seats in any seatmap rendering a developer might want to do.

    A quick note to v11 developers--we discovered a problem with this functionality in the released version of the web api and a hotfix has been posted in TASK under the Version Upgrades and Patches project, in the v11 Post v11.0.3 Hot Fixes solution.

    From: Dan Taraborrelli <bounce-dantaraborrelli3098@tessituranetwork.com>
    Sent: 6/28/2012 1:17:21 PM

    Was this ever implemented? Did I miss the solution in another thread?




    You were sent this email automatically because you subscribed to the Tessitura Web forum. You may reply to this message to post to the Web forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!




    You were sent this email automatically because you subscribed to the Tessitura Web forum. You may reply to this message to post to the Web forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!




    This e-mail message is intended only for the recipient(s) named above. This message may contain trade secrets, attorney-client communication, or other privileged and confidential information. Any review, re-transmission, dissemination, reproduction or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the Sender and delete the material from any computer.
  • Former Member
    Former Member $organization

    Sounds like a conference presentation to me – or at least a mini-Magic?

     

    ________________________________
    Ken McSwain

    Systems and Technology Manager

    Australian Chamber Orchestra

     

    ken.mcswain@aco.com.au

    Ph   +61 2 8274 3833 ::  Mob +61 418 659 360 :: Fax  +61 2 8274 3801

    PO Box R21, Royal Exchange NSW 1225

    2 East Circular Quay, Sydney NSW 2000

     

    From: Tessitura Web Forum [mailto:forums-tessitura-web@tessituranetwork.com] On Behalf Of Alan Levine
    Sent: Wednesday, 4 July 2012 05:04
    To: Ken McSwain
    Subject: RE: [Tessitura Web Forum] ADA Changes and Best Available Seating

     

    I just wanted to chime in and state that we have essentially implemented our ADA Ticketing using the methods Chuck describes below and it has worked incredibly well.   The ability to use a specific hold code made all the difference.     We are using it for wheelchair/companion seating, as well as sign-interpreted seating.     We use Seat Types to designate actual wheelchair seats, but then we set all of the wheelchair seats and companion seats to the hold code.   It allows us to seat those requiring wheelchair seats properly and get the best companion seats near them.     We do allow patrons to select companion seats from unheld available inventory if there are not enough held companion seats nearby.    We were also able to make it work not only on Best Seating but also in Select-Your-Own-Seat.     Chuck and his team really came through in enabling us to meet the ADA requirements when they added the ability to specify a hold code and use held seats in Best Seating.      We’re also able to handle situations where we have a special offer on seats in a particularl price zone, but have no wheelchair seats in that price zone.     We can recognize that and allow the patron to purchase accessible seats in a different price zone, but at the price of the special offer.   We’d be happy to review the details of all of this if anyone is interested.

     

    Alan

     

    From: Tessitura Web Forum [mailto:forums-tessitura-web@tessituranetwork.com] On Behalf Of Chuck Reif
    Sent: Monday, July 02, 2012 2:12 PM
    To: Levine, Alan
    Subject: RE: [Tessitura Web Forum] ADA Changes and Best Available Seating

     

    It would be up to the web developer to decide how to handle such a situation.  If you request a specific hold code, that is all the best seating process will look for.

    From: Nicole Keating <bounce-nicolekeating9176@tessituranetwork.com>
    Sent: 7/2/2012 12:20:00 PM

    Chuck – In V11, if there are no “Companion” holds nearby will it select Companion Seats from unheld available inventory?

     

    Thanks!

    Nicole

     

    From: Tessitura Web Forum [mailto:forums-tessitura-web@tessituranetwork.com] On Behalf Of Chuck Reif
    Sent: Monday, July 02, 2012 1:12 PM
    To: Nicole Keating
    Subject: Re: [Tessitura Web Forum] ADA Changes and Best Available Seating

     

    We experimented with the plan that you mentioned, trying to find companion seats as close as possible to the selected wheelchair seats.  The problem that we ran across was that it worked as expected for some house configurations and in a totally unexpected manner for other facilities, depending on how they were built.  We could never succeed in making the process consistent enough to release.

    So we decided to take another approach and added the ability to do best seating out of a specific hold code.  In v11 you can pass a special request of a holdcode to the ReserveTicketsEx method and the best seat request will honor that hold code.  This allows a web developer to take special action on ADA seating requests and even have different pools of seats for different situations--one hold code for wheelchair locations and a different hold code for hearing impaired seats, for example. 

    This has proven to be a better solution overall.  In addition, we added the hc_no (hold code number) element to the GetSeats methods to facilitate indicating special pools of seats in any seatmap rendering a developer might want to do.

    A quick note to v11 developers--we discovered a problem with this functionality in the released version of the web api and a hotfix has been posted in TASK under the Version Upgrades and Patches project, in the v11 Post v11.0.3 Hot Fixes solution.

    From: Dan Taraborrelli <bounce-dantaraborrelli3098@tessituranetwork.com>
    Sent: 6/28/2012 1:17:21 PM

    Was this ever implemented? Did I miss the solution in another thread?




    You were sent this email automatically because you subscribed to the Tessitura Web forum. You may reply to this message to post to the Web forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!




    You were sent this email automatically because you subscribed to the Tessitura Web forum. You may reply to this message to post to the Web forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

     



    This e-mail message is intended only for the recipient(s) named above. This message may contain trade secrets, attorney-client communication, or other privileged and confidential information. Any review, re-transmission, dissemination, reproduction or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the Sender and delete the material from any computer.




    You were sent this email automatically because you subscribed to the Tessitura Web forum. You may reply to this message to post to the Web forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!


    Visit our new website at www.aco.com.au

    This email is confidential. If you are not the intended recipient you must not disclose or use the information contained in it. If you have received this email in error please notify us immediately by return email and delete the document. The ACO is not responsible for any changes made to a document other than those made by the ACO or for the effect of the changes on the document's meaning. The ACO accepts no liability for any damage caused by this email or its attachments due to viruses interference, interception, corruption or unauthorised access.