Task #6986
MNDeployment #3228: NCEI - National Centers for Environmental Information
Story #6809: NODC: Design, code and component test a new MN implementation
Strategy for synchronrizing content after it changes on the NODC server
Start date:
2015-04-01
Due date:
% Done:
100%
Story Points:
Sprint:
Description
eg. Science metadata documents are updated daily. Data objects seem to be updated arbitrarily.
Need to determine if object has changed, workflow for obsoleting old content and assigning new identifiers
History
#1 Updated by Dave Vieglais about 9 years ago
- Assignee set to Dave Vieglais
- Status changed from New to In Progress
- % Done changed from 0 to 30
See Etherpad at:
#2 Updated by Dave Vieglais about 8 years ago
- % Done changed from 30 to 50
- Status changed from In Progress to Testing
Using an intermediate cache to speed comparison of harvested vs new content.
#3 Updated by Amy Forrester about 6 years ago
- % Done changed from 50 to 100
- Status changed from Testing to Closed
