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
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 ReifSent: Monday, July 02, 2012 1:12 PMTo: Nicole KeatingSubject: 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!
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.