New Hotel Room Finder: Testing Opportunity

[len]

@missoverexcited The Lobby Distance/Transportation Distance issue from post 137 should be resolved with the next release, probably tomorrow. That was an interesting one. I learned something there. Thanks!

[len]

Thanks @pfrankfa. This will be fixed in the next release, probably tomorrow. And I’ve extended your subscription through the end of the decade.

I updated the walking distances at buildings 1, 3, 4, 5, 6, and 10 to be < 3 minutes from the bus and 3 minutes from the Skyliner. All of those rooms appear to be less than ~900 feet from those.

Parts of building 9 might be close enough to the bus stop to be < 3 minutes away. But it involves cutting through an active driveway where carts and other vehicles are going in and out. I’m hesitant to suggest that to families with children, so going through the lobby is the best route.

[len]

@ryan1

I just tried a similar thing with Boardwalk…after selecting 1-Bedroom Resort view. The location preference has two options: Near Elevator, and Near Lobby. The “Near Lobby” option shows up in BOTH Location Preference 1 & 2. So, I selected “Near Lobby” for Location Preference 1, and it didn’t work correctly, finding 1 room. FYI.

I see your point. I verified that the data we got describes what’s happening correctly. There’s exactly one BWV 1-Bedroom Resort view with a Location Preference 1 of “Near Lobby”. And there are 3 of them with a Location Preference 2 of “Near Lobby.”

Changing this so that either LP1 or LP2 drop-down would match either LP1 or LP2 column would take some work. I don’t want to start changing that now, so I’ll defer this until after the release.

@ryan1

If I select “Near Lobby” for Location Preference 2, it shows 3 rooms only…only one of which are really “near lobby”…but one of which SEEMS to be, maybe, mis-labled as resort view? Room 2068…shouldn’t that be a Garden or Pool view room???

It’s definitely labeled as Resort View in the data we got. I checked. And yeah, that’s a decent view of the pool.

[len]

@missoverexcited This is fixed in the next release. Thanks!

[len]

Thanks @feep. I’ve updated the text about how the filters work to include a warning symbol in yellow, and offset the text so it’s more obvious:

[len]

@linsalt This will be fixed in the next update, probably tomorrow.

All of the Yacht Club rooms above Floor 1 have balconies. I’m trying to decide whether to put “Patio” in the Balcony drop-down for the first-floor rooms, all of which have a patio.

Technically, a patio isn’t a balcony. On the other hand, it would make explicit that the rooms without balconies are on the first floor and have patios.

Let me know what you think.

[janamelia]

I’m not @linsalt tho I’m responding anyway to say that distinguishing between patio and balcony could be helpful. Some folks want any floor as long as it’s not ground floor. (Not me - I don’t want no stinking tower rooms )

Patio would be an additional notice that this awesome room isn’t on the floor they thought it was.

[len]

@SirGreggLadyV The issue with “Accessibility == Not Accessible” will be fixed in the next release, probably tomorrow morning. Thanks for that!

[StinsyLinson]

@len

“Patio” in the Balcony drop-down for the first-floor rooms

I am also not linsalt…but I do think distinguishing between patio and balcony is worthwhile. With the current design, you wouldn’t even know there’s a 2nd egress on the ground floor.
Though, I don’t know if Disney language further complicates things since some of the time on Disney’s website they call it a porch and sometimes a patio. (Maybe just at Copper Creek it’s a porch?)

[len]

@OBNurseNH This will be fixed in the next release, probably tomorrow morning.

[len]

Thanks @mcalligan. This should be fixed in the next release, scheduled for tomorrow morning.

[len]

Thanks @rickblair_857523. This will be fixed in the next release, likely tomorrow morning. I was incorrectly identifying lock-off rooms.

[len]

Thanks @ryan1 .

I tried again just now to recreate this and still can’t. I suspect the issue was that some other filter code was crashing on the back-end, which prevented the “hide the spinner” code from running. And I might have already fixed that filter crashing, at least on my machine right now.

Let me know if you see this again, please, after tomorrow around noon.

I also went floor-by-floor multiple times at BLT, both changing and not changing filters, and it looked like it’s supposed to.

[ryan1]

@len

“hide the spinner”

Admittedly, I haven’t seen the spinner issue in the last few days, so perhaps that one has been addressed by some other fix, as you suggest.

As of today, I still see the select floor issue. I’m wondering if it could an issue tied to the browser? I am running using Firefox at the moment. I’ll try to find time to test on another browser.

[len]

Ah, I haven’t tried Firefox. Let me do that first.

[len]

Thank you all!

I also found some additional information that’ll help us fill in the ‘Balcony’ setting at Beach Club, when it’s not present in the current set of data. I’m working on that now.

[len]

Thank you @sjshaw. I think the “TP Picks” work with tomorrow morning’s release. I checked your specific choices at WL, and they seem to, anyway. And your subscription runs through the end of the decade. Thanks again!

[len]

Thanks for this @RhodyMary. Your subscription now runs through the end of the decade.

I’ve verified that the data and code are correct.

I think the issue here is that the stairwell photos we’re showing for the “TouringPlans Picks” aren’t what anyone would expect to see for “Water View”.

I verified that the rooms themselves have other photos that include views of water. As an example, here’s 4520:

I don’t know if this issue is fixable without going through at least the 1,500 OKW photos to manually say “This is the best photo to use for this room.” It’s not something we can address for this release. I will add it to my to-do list for OKW though. Thanks again for pointing this out.

[len]

Thank you for this @WildernessLodger. Your subscription runs through the end of the decade.

@WildernessLodger

Unless the very bespoke rack rate configuration is meant to match with Disney-tracked data points.

Yes, that’s exactly what’s happening. I’ve never looked at this drop-down for WL, but wow, that is some very narrow bands for rack rates. The folks in Disney’s Yield Management team must be working overtime here.

At this point for this project I don’t want to start adding new code to collapse the rack rates for just some hotels. I will add this and your map suggestions to my to-do list. I like your specific idea to include elevators and outside doors, along with directional signage. That’s not a terrible amount of work.

@WildernessLodger

The actual hotel room map of WL can only be scrolled horizontally and vertically within its frame, it can’t be resized smaller within the frame by “pinching” it. Is this true for all hotel maps?

Yes, it’s true for all hotel maps.

Thanks again!

[len]

Thanks for this. I think it’s resolved in the next release, if it’s not already. It should not be possible to select a second filter with incompatible options from a previous filter selection.