|
Size: 2512
Comment:
|
← Revision 12 as of 2010-06-09 09:26:42 ⇥
Size: 2614
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 17: | Line 17: |
| Time estimated:: | Time estimated:: 12md |
| 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: |
| The Update tracker will consist of a number of components. | A record contain very little information Identifier State Date |
| Line 30: | Line 34: |
| 1. A database, called DB. 1. A jms client 1. The update tracker service. |
If published is set to true, the lookup will only concern itself with the published objects. |
| Line 34: | Line 36: |
| The DB will have |
Task Update Tracker
- Title
- Task Update Tracker
- State
- Not started
- Time used
- Time estimated
- 12md
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 |