search

metadatacenter / cedar-project

Build project for all CEDAR Java repositories
https://github.com/metadatacenter/cedar-docs/wiki
Other
12 stars 1 forks source link

Edit elements in situ #607

Open graybeal opened 7 years ago

graybeal commented 7 years ago

(I'm using the word "element" here to refer to an included artifact; in future it could be a template, but same issue applies.)

When the user includes an element in another element or template (the 'parent document'), and is working in the parent document, it may be necessary to edit the original element. It would save a lot of time if the user could edit the original element without leaving the parent document.

For this to happen, the user would have to be able to indicate, either when starting or saving the edits, that the original element should be changed, rather than just the local (parent) document.

Functionally this is no different than exiting the parent document, going to the original element, editing it, saving it, returning to the parent document, deleting the original element, and re-importing it. But it saves a lot of steps. (Correction: It could be different, in that the original element might have gone through many changes, so re-importing it might bring in many other changes. When we have versioned elements, it will be possible to see if the edited element has been changed since it was included the last time.)

This is an advancement of the capability described in https://github.com/metadatacenter/cedar-template-editor/issues/458.

graybeal commented 7 years ago

Tagged it LD4P although it is not LD4P specific. Reference https://github.com/LD4P/requirements/issues/13 and https://github.com/LD4P/requirements/issues/152.