Update 04/20/2011

[shmax]

- Increased the range of dates used when polling auction data for appraisal info from 6 months to 5 years
- fixed issue where the min and max appraisal data points weren't respecting the date range

[shmax]

- put the range back to 6 months... don't know what I was thinking
- fixed an issue with scrolling of long lists in table management interface (moderator only)

[spaceharfang]

- put the range back to 6 months... don't know what I was thinking

To solve that point, maybe we could use a data "degradation" technique.  When the ebay data is over 6 month old, instead of keeping all of the records, we could create a single record that represent the trend of a given month.  It would only need a new field defining how many records were used to create it.  The original records could then be put in an archive table that is not used by the queries.

That way we could go back 5 year back without having the performance hit.

[shmax]

I've thought about doing something like that so that our graphs are a bit easier to read, but I didn't switch back to 6 months for performance reasons, I did it because you really want a smaller window to make sure that the appraisal data represents recent trends, so that you know what an item is worth right now...

[spaceharfang]

Ok then.

I just finished my finance class dealing with in time.  Maybe we can use that to whip something up that would be able to go farther back.  Do you have an example that don't go well when you use 5 years?

[shmax]

We'll definitely need someone with some recent coursework in statistics to go over this stuff, but for now we have shmax 2.0 to work on!