Project

General

Profile

Bug #2955

Date stamps for revisions of the concept relationships

Added by Robert Peet over 11 years ago. Updated over 11 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
atlas
Target version:
Start date:
09/09/2007
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
2955

Description

We need to be able to associate start and stop dates with the concept relationships during the editing process so as to handle versioning. We need this both in the table for concept realationships (or two tables if current and obsolete are kept separate) and in the ConceptMapper tool used for editing relationships.

History

#1 Updated by xianhua liu over 11 years ago

I implemented the function and changed the database to support time-stamp of concept relationships. My solution is:

1. added 2 new fields to the mappings table to store start and end dates of a relationship.
2. added a new table 'mappinghistory' to with the same fields as the mappings table to store the history of a relaitonship.
3. changed database proxy class in ConceptMapper so that: * start date of new relationship is set to current date and end date emmpty * whenever a relatonship is changed, the old relationship is stored in the mappinghistory table with end date set to current date. The updated record will have current date as its start date * when a relationship is deleted, the relationship will physically removed from the mappings table, and the relationship is stored in the mappinghistory table with its end date set to current date.

#2 Updated by Redmine Admin over 5 years ago

Original Bugzilla ID was 2955

Also available in: Atom PDF