search

NCEAS / morpho

Morpho metadata editor
GNU General Public License v2.0
3 stars 1 forks source link

Default save behavior to always include local store #983

Closed mbjones closed 5 months ago

mbjones commented 6 years ago

Author Name: ben leinfelder (ben leinfelder) Original Redmine Issue: 5809, https://projects.ecoinformatics.org/ecoinfo/issues/5809 Original Date: 2013-01-24 Original Assignee: ben leinfelder

Currently you can opt to save your datapackage changes to either LOCAL, NETWORK, or BOTH. This means you can make changes to a package then opt to save them only to the NETWORK. This can leave your local store a version behind and I don't undersand the usecase for that.

I am proposing that we always save changes locally (if local does not already have the latest version).

I started thinking about this because of a related bug that displayed different local and network revisions simultaneously (#5805). I think we should still try to address that bug, but I'm not exactly sure how to guarantee it will not continue to be a problem especially if we maintain distinct revision histories for local and network content. (This may qualify as yet another bug for discussion).

mbjones commented 6 years ago

Original Redmine Comment Author Name: ben leinfelder (ben leinfelder) Original Date: 2013-02-18T20:40:36Z

Does this effectively communicate that Local saving is required?

mbjones commented 6 years ago

Original Redmine Comment Author Name: Redmine Admin (Redmine Admin) Original Date: 2013-03-27T21:31:45Z

Original Bugzilla ID was 5809