Story #1033
Cn should receive and respond to variety of schema & API releases
Status:
Closed
Priority:
Normal
Assignee:
Robert Waltz
Category:
d1_common_java
Target version:
-
Start date:
Due date:
% Done:
100%
Story Points:
Sprint:
Description
There will need to be a translation/transform from previous released schema.
So, If a 1.0 MN is replicated to a 1.5 MN, there should be a update of 1.0 MN Systemmetadata to 1.5.
What about replication downward? Do not allow for a downgrade of schemas.
How do we cover communications between different MNs of different API versions?
Related issues
History
#1 Updated by Robert Waltz about 13 years ago
- Position set to 36
#2 Updated by Robert Waltz almost 13 years ago
- Assignee set to Robert Waltz
#3 Updated by Dave Vieglais over 12 years ago
- Position set to 49
- Position deleted (
127)
#4 Updated by Robert Waltz over 10 years ago
- Milestone set to CCI-2.0
- translation missing: en.field_remaining_hours set to 0.0
- Start date deleted (
2010-10-29) - Product Version set to 2.0.0
#5 Updated by Skye Roseboom over 9 years ago
- Status changed from New to Closed
