Bug #2428
closedMorpho incorrectly tries to update instead of insert when saving a dp to a second metacat
0%
Description
To recreate this bug:
Create a data package and save it to a metacat server, (and locally, if you'd like). Make at least one change and save it a second time locally (i.e., so you're on the second revision of the document). Then go to set preferences and change to a different metacat sever (which doesn't have the dp on it yet). Open the dp, and try to save it to the new metacat. You will get an error saying "Problem Saving Data: Document not found for Accession number!", and the save will fail. Looking at stderr.log you can see that morpho tried to do an update instead of an insert.
Name: action => update
Name: public => no
message from server:
<error>
Document not found for Accession number bowdish.46
</error>
MetacatUpload Exception in EML200DataPackage!
<error>
Document not found for Accession number bowdish.46
</error>
Updated by Will Tyburczy over 18 years ago
A side note: you do not need to do the extra revision to have morpho fail to save on the second metacat. However, it fails silently, and the stderr.log doesn't seem to be as clear on what went wrong.
Updated by Callie Bowdish over 17 years ago
Gail Steinhart from Cornell University's Research Data & Environmental Sciences Library has been working with Morpho. They have a test Metacat server. She made a Duplicate data package that had previously been saved up to the test server. Then she connected to the KNB with that duplicate. The duplicate had a data table file with the version set at x.5 (the fifth save). This was a new data package but it contained data table that had a version number of 5. She did not remember the error but the data package saved with an error and the new data package uploaded but the link to the data table did not find the table.
Next the data package was deleted on the KNB server but not in Morpho. The Data Table was deleted and a new one was created. When it was uploaded the Morpho log (stderr) reported.
.....
</unitList>
</additionalMetadata>
</eml:eml>
Name: action => update
Name: public => no
message from server:
<error>
Document not found for Accession number gss1.8
</error>
MetacatUpload Exception in EML200DataPackage!
<error>
Document not found for Accession number gss1.8
</error>
Problem Saving Data: Document not found for Accession number
Problem Saving
<error>
Document not found for Accession number gss1.8
</error>
Morpho did not have a way to know that the KNB gss1.8 had been deleted on the server and it used update instead of input. There was an accession error because there was no gss1.8 to be found on the KNB. In order to update there has to be a file with that name on the server that it is being saved to.
We created a new duplicate data package with a table that only had a version one on it. This saved up to the KNB and we were able to download the data table using the link. (? note it was saved two times and the first time might not of worked?)
Updated by ben leinfelder about 14 years ago
The robust docid conflict resolution seems to be preventing this error now. I had a document on rev 6 locally that was from KNB then tried saving it to my development instance of Metacat - no error as it correctly inserted rather than attempting to update it.