In II can you run multiple OGS with the same week?

[jp10558]

So, now that I have a little more II time playing with the site - I'm certainly agreeing with TUG that much of what's just out there isn't that great an exchange. However, it seems difficult for me to put in one OGS and wait a long time to see if it hits or not (or maybe I just don't understand the search system yet). Can I put in say something looking to match in a few locations (i.e. not just say Hawaii, but HHI, south FL, somewhere else) and create a new one if it hasn't matched if theres a new place I would be interested in and once one matches and I accept it the system (or I) cancel the others now that I've "used" the week?

 

[dioxide45]

Absolutely, but it is all part of the same ongoing search that you setup. You can setup multiple resorts with multiple dates.

 

[iftravel]

Absolutely, but it is all part of the same ongoing search that you setup. You can setup multiple resorts with multiple dates.

Yeah I do that too. Setting up multiple dates / locations for one search (so you don’t have to prepay more). One funny thing for OGS is it always move the date to the prior Thursday.

I probably asked this before but every time it confuses me a hell as I don’t know if it will still match the Friday after the last check in date on Thursday it changes to. So if I do want that Friday check in date, do I have to jump one week forward to set the last check in date?

 

[dioxide45]

Yeah I do that too. Setting up multiple dates / locations for one search (so you don’t have to prepay more). One funny thing for OGS is it always move the date to the prior Thursday.

I probably asked this before but every time it confuses me a hell as I don’t know if it will still match the Friday after the last check in date on Thursday it changes to. So if I do want that Friday check in date, do I have to jump one week forward to set the last check in date?

Yes, OGS are always Thursday to Thursday. So if you want to capture two weekends for possible checkin, then you need to make sure you make your end date the following Thursday.

 

[jp10558]

Yeah I do that too. Setting up multiple dates / locations for one search (so you don’t have to prepay more). One funny thing for OGS is it always move the date to the prior Thursday.

I probably asked this before but every time it confuses me a hell as I don’t know if it will still match the Friday after the last check in date on Thursday it changes to. So if I do want that Friday check in date, do I have to jump one week forward to set the last check in date?

Can you add more criteria to an existing OGS?

 

[jp10558]

Yes, OGS are always Thursday to Thursday. So if you want to capture two weekends for possible checkin, then you need to make sure you make your end date the following Thursday.

Wow, good to know. It really seems intentionally obtuse for some reason to me, but I'm learning.

 

[dioxide45]

Can you add more criteria to an existing OGS?

Yes, you can modify an existing OGS. Add resorts/dates or remove resorts and dates.

 

[iftravel]

Wow, good to know. It really seems intentionally obtuse for some reason to me, but I'm learning.

Yeah cannot think of any good reason why they did this other than perhaps the original coder got drunk or high that day and all coders after were either stupid or lazy.

 

[GrayFal]

Every time you add a resort or even adjust your dates they treat it as a “new” request so you go to the back of the line.
I had not realized this when I was doing a search for Hawaii last year.
I questioned why I had not matched and they said well you put in your search two weeks ago. I had put it in 14 months out.
this us when they explained how it works.

 

[Hindsite]

Every time you add a resort or even adjust your dates they treat it as a “new” request so you go to the back of the line.

I'm not sure it works as a "line" because its just about whether your request has the TP to pull the available units. Someone with higher TP who just put in a request will get the match before lower TP no matter when the lower TP request was submitted. CS have been known to tell people things that sound plausible even when they aren't how the system work.

 

[chriskre]

Every time you add a resort or even adjust your dates they treat it as a “new” request so you go to the back of the line.
I had not realized this when I was doing a search for Hawaii last year.
I questioned why I had not matched and they said well you put in your search two weeks ago. I had put it in 14 months out.
this us when they explained how it works.

Seriously? That's ridiculous. Good to know though. Wow.

 

[GrayFal]

Seriously? That's ridiculous. Good to know though. Wow.

I was surprised as well

 

[dioxide45]

I'm not sure it works as a "line" because its just about whether your request has the TP to pull the available units. Someone with higher TP who just put in a request will get the match before lower TP no matter when the lower TP request was submitted. CS have been known to tell people things that sound plausible even when they aren't how the system work.

This is correct. Though, when trade power is equal the exchange will go to the earlier request. Trade power being equal is probably fairly rare but can come up when someone is using points for an exchange. We don't know how II prioritized one point system over another (say Hyatt vs Sheraton Flex). That said, and as you noted, a perceived line for weeks based exchange simply doesn't exist.

 

[Fido Chuckwagon]

That said, and as you noted, a perceived line for weeks based exchange simply doesn't exist.

What if two people have the same week at the same resort deposited? Or will the tiebreaker go to which one of them deposited first?

 

[GrayFal]

What if two people have the same week at the same resort deposited? Or will the tiebreaker go to which one of them deposited first?

If one deposited at 12 months and the other at 10 months and both requested the same exchange on the same day, the earlier deposit would win.

But if the 10 month deposit requests an exchange at 10 months out and the 12 month waited until 6 months out to request, likely the 10 month would win.
Clear as mud.

I just did not realize any update is considered "new".

Now when I want to check what I requested, I go in two or three screens then hit the home button. Even if you don't change anything but click all tbd way thru it generates an email to you about your request.

This is new in the last 18 months.

 

[GrayFal]

I'm not sure it works as a "line" because its just about whether your request has the TP to pull the available units. Someone with higher TP who just put in a request will get the match before lower TP no matter when the lower TP request was submitted. CS have been known to tell people things that sound plausible even when they aren't how the system work.

If all things are equal. Time of deposit, trade power, unit size then yes, the request is given to the oldest request - hence my use of "first in line"

Your mud week at a ski resort is not going to trump my platinum beach week regardless of request time line.

 

[dioxide45]

But if the 10 month deposit requests an exchange at 10 months out and the 12 month waited until 6 months out to request, likely the 10 month would win.

It still all depends on the trade power of the two different deposits. If the 6 month request is using a week with much higher trade power than the week used for the request at 10 months, the 6 month request is going to match first if both requests are still running at the same time.

 

[GrayFal]

It still all depends on the trade power of the two different deposits. If the 6 month request is using a week with much higher trade power than the week used for the request at 10 months, the 6 month request is going to match first if both requests are still running at the same time.

Please read post # 15, that’s what I said.

 

[dioxide45]

Please read post # 15, that’s what I said.

What I said isn't the same. You said that the 10-month request is likely to match first. I am saying that the 6-month request is likely to match first if it has higher trade power.

If you're saying to read post #16, then that is what you said but it is then somewhat contradictory to what I quoted from post #15.

 

[GrayFal]

What I said isn't the same. You said that the 10-month request is likely to match first. I am saying that the 6-month request is likely to match first if it has higher trade power.

If you're saying to read post #16, then that is what you said but it is then somewhat contradictory to what I quoted from post #15.

I was responding to two different sceneries.

I was responding to the two different scenarios.
The “everything is equal” so earliest request wins.
And the “everything is equal week/unit but one deposits sooner“ Who gets it scenario.

When II had a representative participating here he was very clear that deposit times matter.
12 month plus = top trade power For your unit/season.
Before 10 months = slightly less
Before 8 months = less
And every two months it decreases.

So it definitely matters when you deposit as well as when you request.

 

[dioxide45]

What if two people have the same week at the same resort deposited? Or will the tiebreaker go to which one of them deposited first?

Trade power is more than just same week and resort. It can also be based on when the week was deposited and the expected demand and supply at the time of deposit. Trade power is highly variable. This is documented somewhere in the II Buyer's Guide but when trade power is equal, it goes to the the first to request not the first to deposit. That said, an earlier deposit may have better trade power if they are depositing the same week.

 

[Hindsite]

If all things are equal. Time of deposit, trade power, unit size then yes, the request is given to the oldest request - hence my use of "first in line"

Your mud week at a ski resort is not going to trump my platinum beach week regardless of request time line.

I was told that only the new items added went to the back of the line, the rest of the items in the OGS stay where they were.

That, plus the variable nature of TP, including a manual element, means that the statement about going to the back of the queue is an oversimplification and more about CS pacifying you than explaining the system.

 

[GrayFal]

I was told that only the new items added went to the back of the line, the rest of the items in the OGS stay where they were.

That, plus the variable nature of TP, including a manual element, means that the statement about going to the back of the queue is an oversimplification and more about CS pacifying you than explaining the system.

That would be great if it is true.

My particular request had me changing resorts, dates, etc.
I don’t think my original request was even there any more! So more me screwing up then pacification, it was true it was two weeks old.