Project

General

Profile

Bug #5401

Workflow archiving dataturbine data to metacat should check the last archiving time through repository

Added by Jing Tao almost 8 years ago.

Status:
New
Priority:
Normal
Category:
sensor-view
Target version:
Start date:
05/12/2011
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5401

Description

Currently the workflow check the last archiving time through a local database.
If the workflow run on different machine, it will cause conflict. If we search the metadata (EML) documents in the repository and get the last archiving time by pass them, the process will be more robust. However, cost is high.

If this workflow only be run by a scheduler and execution engine (this means the workflow will be run on one machine), checking the last archiving time through the local DB will be fine.

History

#1 Updated by Redmine Admin about 6 years ago

Original Bugzilla ID was 5401

Also available in: Atom PDF