Size: 3822
Comment:
|
Size: 2610
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 26: | Line 26: |
1. Request Entry Pids changed since a given date. | 1. Request Entry Pids changed since a given date. List<Records> getChangedSince(Date since, boolean published, String viewAngle) |
Line 28: | Line 29: |
A record contain very little information Identifier State Date |
|
Line 29: | Line 34: |
== Design == The Update tracker will consist of a number of components. 1. A database, called DB. 1. A JMS client 1. The update tracker service. The database will have two tables. 1. Entry Pid - Date changed - View Name: Associates each entry pid/view name combo with a changed date 2. Object Pid - Entry Pid - View Name: Associates each pid in DOMS with a entry pid/view name combo. There are two main flows in the service 1. Update: 1. JMS client will be notified upon change to an object 1. The object pid is looked up in table 1 to a set of entry pid/view name combos. 1. Each of these combos gets the corresponding entry has date changed updated in table 1. 1. If the change was in RELS-EXT: 1. For each view name for the entry object 1. Request the view object list for this entry object, from ECM 1. Delete all entries for entry pid in table 2. 1. Add all objects from the ecm list to table 2. 1. Lookup(pid) 1. Lookup in 1. to get date changed. Secondly, there is the rebuild flow 1. Rebuild 1. Drop the contents of table 1 and table 2 1. From ECM, get all view angles 1. For each view angle 1. Get all entry pids for view angle 1. for each entry pid 1. Get the View object list for this object, from ECM 1. Add the corresponding entries to table 2. 1. Get the latest change-date from the view object list, and set this as the changed-date in table 1. |
If published is set to true, the lookup will only concern itself with the published objects. |
Task Update Tracker
- Title
- Task Update Tracker
- State
- Not started
- Time used
- Time estimated
Description
The goal of this task is to establish the Update Tracker mechanism in DOMS. The update tracker will provide the following functionality to DOMS
- Request Entry Pids changed since a given date.
List<Records> getChangedSince(Date since, boolean published, String viewAngle)
A record contain very little information
- Identifier State Date
If published is set to true, the lookup will only concern itself with the published objects.
Sub tasks
Title | State | Time used | Time estimated |
Documentation
Progress history
Iteration | Time used | Status | Notes | Tasks adressed |