Project

General

Profile

Bug #1415

How do we use the dates in VegBank

Added by Michael Lee over 18 years ago. Updated over 18 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
misc
Target version:
Start date:
03/30/2004
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
1415

Description

We have 2 prevailing options, which are mixed and therefore confusing:

This pertains to dates in fields that are like dateStart, dateStop, not obsStartDate

1) this is the date the party decided whatever it is deciding
2) this is the date it goes into VegBank

****WE MUST DECIDE WHICH OF THESE IT WILL BE AND STICK TO IT, ESPECIALLY IF
WE ARE TO USE THESE FIELDS FOR SHOWING WHAT A PLOT LOOKED LIKE IN THE
PAST!!!
****

History

#1 Updated by Robert Peet over 18 years ago

Ah, this is a problem. I think we all along were tracking a party perspective
and its changes, and not what was in our database. Any reason not to stick
with this?

#2 Updated by Michael Lee over 18 years ago

OK, let's do it that way: make the date the date that the user changed stuff,
not when database (necessarily) changed. These dates may well be the same
sometimes.

#3 Updated by Michael Lee over 18 years ago

OK, this is resolved. Dates in vegbank do NOT apply to the dates that the
things were put into vegbank (necessarily) but rather when the party made that
decision. This means we will have to use revision for the "view of the db
entity at past date."

#4 Updated by Redmine Admin over 9 years ago

Original Bugzilla ID was 1415

Also available in: Atom PDF