Re: Issue 260 in arctos: Dates: Store partial

[arc...@googlecode.com]

Updates:
Status: Started

Comment #5 on issue 260 by dustymc: Dates: Store partial
http://code.google.com/p/arctos/issues/detail?id=260

(No comment was entered for this change.)

[arc...@googlecode.com]

Comment #6 on issue 260 by dustymc: Dates: Store partial
http://code.google.com/p/arctos/issues/detail?id=260

Implemented for began_date and ended_date. Will test for a few weeks and
continue to other date fields if all goes well.

[arc...@googlecode.com]

Updates:
Cc: heliu...@gmail.com
Labels: Usability

Comment #7 on issue 260 by dust...@gmail.com: Dates: Store partial
http://code.google.com/p/arctos/issues/detail?id=260

No functionality complaints in a year and a half - I think we can assume
this is going to work and proceed with implementation.

It may be worth discussing precision limits. For example, it would never
make sense to have a collecting_event.began_date have less than 1-day
precision since it's part of a bracket, but we do want to allow
better-than-day precision, e.g., "caught between 8 and 9 AM."

All (data) columns with DATE datatype are in a spreadsheet at
http://goo.gl/xCqcw. AC, do your thing.

[arc...@googlecode.com]

Updates:
Cc: arctos...@googlegroups.com

Comment #8 on issue 260 by dust...@gmail.com: Dates: Store partial
http://code.google.com/p/arctos/issues/detail?id=260

Implemented for identification, attribute, lat_long. Still waiting for AC
input....

[arc...@googlecode.com]

Updates:
Status: Fixed

Comment #9 on issue 260 by dust...@gmail.com: Dates: Store partial
http://code.google.com/p/arctos/issues/detail?id=260

tired of ignoring this all by myself - closing....