[Data-modeling] Date/Time type requires a specific year when all Iwant is to capture a yearly calendar event

[Jeff Prucher]

If I understand you correctly, you want to have properties that will accept
values like "June 17". If that's what you want, you can use the type
/time/day_of_year. As far as a range goes, you can either create a new CVT,
or just have two properties: "earliest date of shower" and "latest date of
shower" or some such.

Jeff

> -----Original Message-----
> From: data-modeling-bounces at freebase.com 
> [mailto:data-modeling-bounces at freebase.com] On Behalf Of 
> Gordon Mackenzie
> Sent: Thursday, January 10, 2008 5:16 PM
> To: Freebase data modeling mailing list
> Subject: [Data-modeling] Date/Time type requires a specific 
> year when all Iwant is to capture a yearly calendar event
> 
> For Meteor Showers, there is a range of dates the shower 
> occurs within and a peak date when the Zenithal Hourly Rate 
> (the maximal number of meteors observed within an hour when 
> observational conditions are
> optimal) is at its highest.
> 
> I could simply make the new properties, and give them the Text type.  
> That seems a shame for I think it would be more useful to 
> have a calendar year date-range type (either one that 
> includes the option to just enter the hour/month/date with 
> the ability to add a second set of values to form the range 
> or two separate types, one for specific calendar date and one 
> for range of calendar dates).
> 
> I've been informed this is a variant of an anniversary issue. 
> Where it is not a simple task to get a MQL query result of 
> say of that of an anniversary like all the people sharing a 
> birthday in a instantly useable form.
> 
> ~ Gordon
> 
> <<< gordon at metaweb.com >>>
> 
> 
> 
> _______________________________________________
> Data-modeling mailing list
> Data-modeling at freebase.com
> http://lists.freebase.com/mailman/listinfo/data-modeling
>