|
Size: 3246
Comment:
|
Size: 2352
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 26: | Line 26: |
| 1. Request Entry Pids changed since a given date. == 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 to a set of entry pid/ view name combos. 1. Each of these combos is looked up, and the corresponding entry has date changed updated. 1. If the change was in RELS-EXT: 1. For each view for the entry object 1. Request the view from ECM 1. Update the pid-entry-view table 1. Lookup 1. Lookup in the first table |
1. Request Entry Pids changed since a given date. |
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.
Sub tasks
| Title | State | Time used | Time estimated |
Documentation
Progress history
| Iteration | Time used | Status | Notes | Tasks adressed |