This shows you the differences between two versions of the page.
|
developers:spec:discuss_a_translation [2012/07/02 12:44] friedelwolff |
developers:spec:discuss_a_translation [2012/07/03 08:29] (current) dwaynebailey A possible solution to the missing data scenario. |
||
|---|---|---|---|
| Line 120: | Line 120: | ||
| In this case, we wouldn't know if the change of target ("cow" -> "cow2") happened before or after the comment change on 2012-01-07. Even if we consider the dates of all the surrounding elements, we can only say that it happened somewhere between 2012-01-05 and 2012-01-09. The two entries with unknown dates might have happened as part of the same upload on 2012-01-06, for example. | In this case, we wouldn't know if the change of target ("cow" -> "cow2") happened before or after the comment change on 2012-01-07. Even if we consider the dates of all the surrounding elements, we can only say that it happened somewhere between 2012-01-05 and 2012-01-09. The two entries with unknown dates might have happened as part of the same upload on 2012-01-06, for example. | ||
| + | |||
| + | ==== Possible solution ==== | ||
| + | |||
| + | Simply state that we don't know when it happened. e.g. this is then visually displayed as something like: | ||
| + | |||
| + | | Between 2012-01-05 and 2012-01-09 | "cow2" | target | | ||
| + | |||
| + | If we use other cues like: | ||
| + | * Italic text | ||
| + | * Greyed our text | ||
| + | * Human readable ranges: Between 5-10 days ago, About 5 days ago, Last month, | ||
| + | then this becomes less of an issue. Some examples with these ideas: | ||
| + | |||
| + | | January 2012 | "cow2" | target | | ||
| + | | //6 months ago// | "cow2" | target | | ||
| + | |||
| + | I'm not sure what the cost would be of determining those dates. Might raise the issue that we want to store a real date or date range in the table to help performance. | ||