v 1.5.13 release notes

CellarTracker Main Site

v 1.5.13 release notes

View related threads: (in this forum | in all forums)

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [Cellar Talk] >> Release Notes >> v 1.5.13 release notes

Page: [1]

Message

<< Older Topic Newer Topic >>

v 1.5.13 release notes - 12/7/2003 5:42:14 PM

Eric

Posts: 5743
Joined: 10/10/2003
From: Seattle, WA
Status: offline

This one went live very early this AM, but I was too tired to send out notes.

Drinking windows
Show "DRINKING SCORE" based on drinking window, inventory and rate of consumption. Much more on this below. Please note that this is just a fast beta of the feature that is intended for folks who are tracking both purchases and inventory. Paul Homchick spec'ed out the bulk of the approach, and we are quickly iterating on a bunch of ideas to make this better.

Bug fixes
(1) This one has been there forever. Trying to add inventory without an associated purchase caused an error on the Mac. (2) The text to be sent to WineSearcher is not munged to remove extended characters. (3) Suppress the "Print Labels" link on the Mac.

Courtesy of Paul Homchick, here is more information on the wine Availability Index Report report:

Availability Index Report: This report orders the wines in the cellar by an index number which shows whether a wine is being consumed faster or slower than a linear rate implied by the drinking window. For example: you buy a case of wine with a Wine Advocate suggested twelve-year drinking window. If you get five years into the window and you still have 12 bottles, your index is positive five (5): you have five bottles to drink. If you get five years into the window and you have consumed nine bottles, you have an index of negative four (-4): you are consuming the wine at a rate that will exhaust it before the window closes.

If you get beyond the window and you still have bottles left, the index will be a positive number greater than the number of bottles and it will keep increasing as time goes on.

If you have not yet gotten to the start of the drinking window, the index will be a negative number that will approach zero as the start-consume date approaches.

The index is dynamically calculated when the report is run based on the current date. The formula for the Availability Index (AI) is:

Days_into_Window / Total_Days_in_Window = Percent_Window_Used

Inventory + Consumed * Percent_Window_Used = Should_Have_Consumed

Availability Index (AI) = Should_Have_Consumed - Consumed

< Message edited by Eric -- 8/3/2004 11:10:17 PM >

_____________________________

Cheers!
-Eric LeVine

Post #: 1

RE: v 1.5.13 release notes - 12/9/2003 8:59:04 AM

patlee

Posts: 102
Joined: 11/3/2003
From: Piedmont, CA
Status: offline

I found that Print Labels link did show up on the Mac still with the latest build, so I decided to do some testing.

I am not using IE for Mac, it hasn't been updated in a while and is slower on Mac OS X. The Print Labels link still does shows up on the Mac when using Safari (Apple's web browser), Mozilla Firebird (the browser only), or Camino (Mac OS X native widget Mozilla). When I tested it on IE, the Print Labels link was suppressed.

Since less and less people are using IE on the Mac, I thought I would report it to you. To make it easier to suppress the other browsers, here are the user agents for the four browsers mentioned above. It appears that if you also add "Macintosh" as part of your check, it will get all the non IE browsers I mentioned.

For your reference, here are the User Agents in question.

IE 5.23 Mac OS X
Mozilla/4.0 (compatible; MSIE 5.23; Mac_PowerPC)

Mozilla Firebird
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6b) Gecko/20031118 Firebird/0.7+

Safari
Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/85.7 (KHTML, like Gecko) Safari/85.6

Camino
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6b) Gecko/20031118 Camino/0.7+

It took me a while, but I found a useful web site to dump the user agent info and it is:

http://www.garykeith.com/browsers/your-browser.asp

Hope this helps.

Pat

< Message edited by patlee -- 12/9/2003 9:07:16 AM >

(in reply to Eric)

Post #: 2

RE: v 1.5.13 release notes - 12/9/2003 11:38:39 AM

Eric

Posts: 5743
Joined: 10/10/2003
From: Seattle, WA
Status: offline

Sweet, that is awesome Pat, thank you! I went ahead and updated to filter based on the presence of "Macintosh".

FYI, if you ever want to know what your own browser returns, hit this link: http://www.cellartracker.com/ua.asp

_____________________________

Cheers!
-Eric LeVine

(in reply to patlee)

Post #: 3

RE: v 1.5.13 release notes - 12/9/2003 4:33:31 PM

patlee

Posts: 102
Joined: 11/3/2003
From: Piedmont, CA
Status: offline

Thanks for making the change Eric, it looks good in all four Mac OS X browsers I tested against earlier.

Pat

(in reply to Eric)

Post #: 4

RE: v 1.5.13 release notes - 2/24/2004 8:41:15 PM

WK Choy

Posts: 349
Joined: 2/12/2004
Status: offline

I've been trying to figure out the Availability Index.

quote:

(Total_Days_in_Window - Days_into_Window) / Total_Days_in_Window = Percent_Window_Used

Looks like percent window unused to me

quote:

If you have not yet gotten to the start of the drinking window, the index will be a negative number that will approach zero as the start-consume date approaches.................

AI = Should_Have_Consumed - Consumed

I have cases of unopened wine that have not reached drinking dates yet where AI is negative. But surely Should Have Consumed = 0 and Consumed = 0, therefore AI should be 0.

Regards,

(in reply to patlee)

Post #: 5

RE: v 1.5.13 release notes - 2/24/2004 8:50:03 PM

Eric

Posts: 5743
Joined: 10/10/2003
From: Seattle, WA
Status: offline

Paul Homchick and I debated this, and we decided the negative was useful since it tells you how far away you are from drinkability. Paul may have other comments, as it is really his algortithm.

_____________________________

Cheers!
-Eric LeVine

(in reply to WK Choy)

Post #: 6

RE: v 1.5.13 release notes - 2/25/2004 6:54:25 AM

PaulH

Posts: 251
Joined: 11/3/2003
From: San Francisco, CA USA
Status: offline

quote:

ORIGINAL: WK Choy

I've been trying to figure out the Availability Index.

quote:

(Total_Days_in_Window - Days_into_Window) / Total_Days_in_Window = Percent_Window_Used

Looks like percent window unused to me

Good catch! This is a botched description of the formula. What it actually does is:

Days_into_Window / Total_Days_in_Window = Percent_Window_Used

(Eric, can you edit the message above to limit further confusion?)

As to AI being negative for wines where the drinking window is in the future, I originally had extra logic to set these to zero. When Eric implemented it here, he didn't have that extra logic. After looking at the results, we decided it was fine the way he did it. The more negative the AI is, the more you should stay away from the wine. With the extra logic you would have gotten the following from the AI...

AI > 0.0 means within drinking window
AI = 0.0 means not to drinking window yet
AI < 0.0 means drinking too fast, slow down (for wines that are in the window)
(if you drank something before the window the AI would still show zero)

With the current logic it means the following

AI >= 0.0 means within drinking window and wine available
AI < 0.0 means drinking too fast, slow down or not to window yet

I like the current calcuation better, as it goes more negative if you open something too soon; you are robbing from future availability.

For purposes of historic documentation here is my original description of the Availability Index (note that the final two bits of logic ARE NOT in CellarTracker):

Calcuation of Availability Index for Yield Management.

Here is a simple example of yield management for 1994 Beringer Cab.

Drink Soonest = 1997 Drink Latest = 2007
1/1/2007 - 1/1/1997 = 3652 days
Today = 12/9/2003
Days used = 12/9/2003 - 1/1/1997 = 2503 days
2503 / 3652 = 0.658
Number Purchased = 12
Number should have consummed = 12 * 0.658 = 8.2 bottles
Number in inventory = 9
Number consummed = 12 - 9 = 3
"Availability Index" = Should have consummed - Actually consummed = 8.2 - 3 = 5.2 (behind)

Another example: 1990 Meyney

Drink Soonest = 1996 Drink Latest = 2010
1/1/2010 - 1/1/1996 = 5114 days
Today = 12/9/2003
Days used = 12/9/2003 - 1/1/1996 = 2869 days
2869 / 5114 = 0.561
Number Purchased = 14
Number should have consummed = 14 * 0.561 = 7.9 bottles
Number in inventory = 3
Number consummed = 14 - 3 = 11
"Availability Index" = Should have consummed - Actually consummed = 7.9 - 11 = -3.1 (ahead)

If "Days Used" is negative (haven't reached the start of the drinking window yet) the Availability Index is 0 (NOT IN CellarTracker)

If "Days Used" is greater than the drinking window (fallen off the far end of the window), I add 100 to the calculated Availability Index to emphasize the need to drink up. (NOT IN Cellartracker. This isn't absolutely necessary, as once you exceed the drinking window, the number you should have consummed becomes greater than the number you had to begin with and the Availablity Index is always positive).

For this system to work, you have to know how many you bought, how many you have, and you need a window with a start and end date.

< Message edited by PaulH -- 2/25/2004 7:12:45 AM >

(in reply to WK Choy)

Post #: 7

RE: v 1.5.13 release notes - 2/25/2004 12:31:46 PM

Eric

Posts: 5743
Joined: 10/10/2003
From: Seattle, WA
Status: offline

quote:

ORIGINAL: PaulH
(Eric, can you edit the message above to limit further confusion?)

Better now?

_____________________________

Cheers!
-Eric LeVine

(in reply to PaulH)

Post #: 8

RE: v 1.5.13 release notes - 8/3/2004 11:12:41 PM

Eric

Posts: 5743
Joined: 10/10/2003
From: Seattle, WA
Status: offline

I updated the description somewhat. When I first created this report, the site did not track consumption data in a structured now. As such, we could only derive this by comparing purchases to current inventory. Alas, purchase data is optional, and many users have elected to only track inventory. As such, I modified the report to use the consumption and current inventory to figure out what percent of your bottles have consumed.

_____________________________

Cheers!
-Eric LeVine

(in reply to Eric)

Post #: 9

RE: v 1.5.13 release notes - 1/5/2005 11:05:12 PM

1800kidney

Posts: 246
Joined: 7/17/2004
From: Birmingham, AL
Status: offline

re: Availability Index (AI)

a) would like to have it added to the custom report pull down lists

b) just noticed that single bottles that are beyond the drinking window (ie drink by 2004) show up with AI = 1.0; I would like to bring these up closer to the top of my availability list. I have added an if/then statement to my off-line calculation of AI that arbitrarily doubles their availability index:
If Today > Last Date, then AI = 2 * (Should have consumed - Consumed)

Comments, suggestions?

1800kidney

< Message edited by 1800kidney -- 1/5/2005 11:06:23 PM >

(in reply to Eric)

Post #: 10

RE: v 1.5.13 release notes - 1/6/2005 10:20:28 AM

Eric

Posts: 5743
Joined: 10/10/2003
From: Seattle, WA
Status: offline

quote:

ORIGINAL: 1800kidney

re: Availability Index (AI)

a) would like to have it added to the custom report pull down lists

b) just noticed that single bottles that are beyond the drinking window (ie drink by 2004) show up with AI = 1.0; I would like to bring these up closer to the top of my availability list. I have added an if/then statement to my off-line calculation of AI that arbitrarily doubles their availability index:
If Today > Last Date, then AI = 2 * (Should have consumed - Consumed)

Comments, suggestions?

1800kidney

a) Availability is a bit tricky to pivot on so the first request is difficult. That said, you can do custom filters for the Availability report. Just click the Refine Search button at the top.

b) The value is not capped and will keep climbing. It sounds like you are really asking to also see which wines are past their drinking window. Here are two ways to do that:

1) Have you looked at the report sorted like this: http://www.cellartracker.com/list.asp?O=EndConsume&table=Availability
The only problem there is that you first have to wade through wines which don't have a drinking window. (I am a bad boy and still have a bunch of my own wines to attend to in this regard).
2) Click the "Drink By" link at the left: http://www.cellartracker.com/list.asp?table=DrinkBy

_____________________________

Cheers!
-Eric LeVine

(in reply to 1800kidney)

Post #: 11

RE: v 1.5.13 release notes - 1/6/2005 9:37:02 PM

1800kidney

Posts: 246
Joined: 7/17/2004
From: Birmingham, AL
Status: offline

a) appreciate being directed to Refine Search on drinkability summary; how about adding "drink by" to the list of options that are currently available?
b) want to view all of my drinkable wines, but am trying to increase the weighting for those that are past the drink before date. Using the 2 as the multiplier throws them higher on the drinkability index list; as you know I have my entire data base in parallel in FileMaker Pro and have made the described adjustment to the availability index, works very nicely! By increasing the weighting, the rate at which the wines past the drink now date climb on the availability index is accelerated
1 and 2) could try this, but will the list end up sorted by availability index?

DGW

(in reply to Eric)

Post #: 12

RE: v 1.5.13 release notes - 4/5/2005 11:31:23 PM

Eric

Posts: 5743
Joined: 10/10/2003
From: Seattle, WA
Status: offline

So I am in the middle of rewriting this document to post a fresh copy and explain all of the new fanciness around different drinking algorithms. In doing so, I noticed this comment from above:

quote:

ORIGINAL: PaulH
If "Days Used" is greater than the drinking window (fallen off the far end of the window), I add 100 to the calculated Availability Index to emphasize the need to drink up. (NOT IN Cellartracker. This isn't absolutely necessary, as once you exceed the drinking window, the number you should have consummed becomes greater than the number you had to begin with and the Availablity Index is always positive).

This enhancement was actually very trivial to add (I missed it before) and also happens to handle David's request rather trivially. So now it is in there!