Morpho creates a duplicate dp that has an existing docid
I saved a dp as a duplicate of connolly.258.5. The new dp was named
connolly.261.1. The thing is that ecogrid://knb/connolly.261.1 was a table I had
in connolly.258.5, so when the duplicate was created, it overwrote that table.
I don't know if this has anything to do with the problem, but the original
connolly.261.1 (the table) was not created on the computer I used when creating
the duplicate dp (it was copied into
.morpho\profiles\<profilename>\data\connolly along with connolly.258.5).
#1 Updated by Callie Bowdish about 13 years ago
Please note the information managers in South Africa are hesitant to upgrade to the latest version of Morpho because it does not notify users when there is a duplicate version of the data package or data table on Metacat. Here is an email I received today for Nikki, working with SAOEN.
- I have a data package entitled Andover Vegetation Data nikkis34.15 which is saved locally
- I set my preferences to link to Judiths computer
- Then I saved package nikkis 34.15 to the network. No little box appears in the corner saying network and it doesnâ€™t appear online
- I then called Judith who suggested to search for the package and then right click on it and press synchonise
- When I press that it says â€™ there is a data conflict has been found in one or more of the identifiers. If you proceed th identifier for this package will be changed, are you sure you want to proceedâ€™
Here is an example of a profile file
The personal profile document title bowdish.xml at /Users/Callie/.morpho/profiles/bowdish/bowdish.xml conatins the information that sets the last id for Morpho. Note the last id information in this profile file.
The problem is that the same profile file can sit on another computer AND have the same scope with a different last id number. Also if Metacat creates an id that includes the login name (part of the scope) that is not "in sync" with a Morpho profile there can be update, insert problems.
I think we saw this with the uploading of the data package on the SAEON test site. (http://dev.nceas.ucsb.edu/knb/style/skins/saeon/) Someone logs in with a their login account associated with the profile on Morpho and uploads a package using the metacat skin. If that package is saved with their profile name (Data Package Identifer prefix) there could be a problem. Because if they use the same profile on a local machine with Morpho it does not know what the last id for a data package was on metacat and could create the same data package id. Then when they want to save it to the network the network will not let them insert because it already exists. It may let them update but they would be updating the wrong data package.
On the NCEAS skin every one who saves a document using the skin has the profile name of nceas even though it is owned by a personal profile. Bowdish can login and save something using the form but when it is saved it is nceas.900.4 and owned by bowdish. That helps prevent problems with last id's. No one uses nceas for their personal profile.