Project

General

Profile

Story #3591

Content consistency checks for new member nodes

Added by Rob Nahf almost 12 years ago. Updated almost 7 years ago.

Status:
In Progress
Priority:
Normal
Assignee:
Rob Nahf
Category:
MNWebChecker
Target version:
Release Backlog
Start date:
2014-10-01
Due date:
2014-10-01
% Done:

30%

Story Points:
Sprint:
Infrastructure backlog

Description

Want to be able to detect systematic content errors for new Member nodes:
1) systemMetadata is parseable - existing getSystemMetadata() test should fail when it can't deserialize the systemMetadata, yes?
2) resourceMaps are parseable - pull a resourceMap listObjects(formatId=, use ResourceMapFactory to deserialize
3) checksum stability - content should have the same checksum every time it is pulled.

Subtasks

Task #3592: write test that checks checksum consistencyClosedRob Nahf

Task #3593: write a test for parsing ResourceMapsClosedRob Nahf

Task #3924: Pids in ObjectList should be the same as pids in the systemMetadata MapNewRob Nahf

Task #2956: content-checking tests for MNs entering an environmentIn ProgressRob Nahf

Task #3925: navigate through the ResourceMap confirm existence of identifiers on the MNNewRob Nahf

History

#1 Updated by Rob Nahf almost 12 years ago

  • Status changed from New to In Progress

possibly write a test for checking metadata (not just resource maps) the tricky part is figuring out how to isolate metadata objects from the objectList....

#2 Updated by Dave Vieglais about 10 years ago

  • Due date set to 2014-10-01
  • Target version set to Release Backlog
  • Start date set to 2014-10-01

#3 Updated by Andrei Buium over 9 years ago

  • % Done changed from 40 to 30

#4 Updated by Dave Vieglais almost 7 years ago

  • Sprint set to Infrastructure backlog

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)