Project

General

Profile

Actions
Copy link

Bug #5795

closed

Centralize identifier conflict resolution during save LOCAL+NETWORK

Added by ben leinfelder over 11 years ago. Updated over 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
ben leinfelder
Category:
morpho - general
Target version:
2.0.0
Start date:
01/18/2013
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5795

Description

After splitting the identifier conflict resolution code into separate Local and Network classes, it turns out this can be problematic for keeping the two copies in sync (see related bug #5792).

We should use a single class to check for existing identifiers in both target locations and choose an identifier that is valid in both locations before proceeding with the save in either location.

Related issues

Blocked by Morpho - Bug #5792: In some situation, morpho uses the same frame to display two data package with different ids (one in local and one in network)Resolvedben leinfelder01/18/2013

Actions
Blocked by Morpho - Bug #5736: Morpho DataONE refactor - trackerNewben leinfelder11/19/2012

Actions
Actions
Copy link
 #1

Updated by ben leinfelder over 11 years ago

I have moved this into the DataStoreServiceController. Now the identifiers are generated as needed before either the local or network save is attempted.

I am not alerting the user when the identifiers are updated since there only seems to be one choice: generate a new identifier. Before we gave users an option to increment the revision number or generate a new id. We only have the later and I think we should assume that saves on the same package are meant to be included in the revision history.

I am closing this bug, but more should be opened if errors are found while testing this feature.

Actions
Copy link
 #2

Updated by Redmine Admin about 11 years ago

Original Bugzilla ID was 5795

Actions
Copy link

Also available in: Atom PDF