Closed mbjones closed 6 years ago
Original Redmine Comment Author Name: Jing Tao (Jing Tao) Original Date: 2013-01-17T01:31:34Z
Currently, the step to increase revisions is separated into the local and network service. If we save to the both locations, it will save to the network first, then to the local. In the network saving process, the identifier had been increased. So it will be treated as a new id (rather than a updated it ) in the local saving process.
In the processing the new id, i added code to set up revision history if the system metadata has obsoletes element. It works.
Original Redmine Comment Author Name: Redmine Admin (Redmine Admin) Original Date: 2013-03-27T21:31:40Z
Original Bugzilla ID was 5785
Author Name: Jing Tao (Jing Tao) Original Redmine Issue: 5785, https://projects.ecoinformatics.org/ecoinfo/issues/5785 Original Date: 2013-01-16 Original Assignee: Jing Tao
I created a data package by the new data package wizard and saved it to the both local and network. Then I updated a data package and save it again to the both local and network.
I searched the title in the morpho and found the newer version in the local and network. Well, so far so good. However, it also showed up the previous version in the local. So the set of obsoletes doesn't work for the local.
However, i repeated the above steps except only saving locally. Everything worked well.