#72: Node renaming tool ---------------------------------------+------------------------------------ Reporter: earle | Owner: dom Type: enhancement | Status: new Priority: normal | Component: openguides Version: | Severity: normal Keywords: utilities, database, admin | ---------------------------------------+------------------------------------ There should be a tool for admins to rename nodes. As I see it the steps of doing so are: {{{ #!html <ol> <li>Pick node, new node name.</li> <li>Get error if new name exists. Otherwise, confirm rename yes/no.</li> <li>All node data, metadata gets copied with new name.</li> <li>For each node in the metadata shown as linking to the old node, copy the content, replace the old name with new in the content and save it.</li> <li>Replace occurrences of old name with new in link metadata just mentioned.</li> <li>Delete all node data for old node.</li> <li>Display confirmation.</li> </ol> }}}
#72: Node renaming tool --------------------------+------------------------------------------------- Reporter: earle | Owner: dom Type: enhancement | Status: new Priority: normal | Component: openguides Version: | Severity: normal Resolution: | Keywords: utilities, database, admin --------------------------+------------------------------------------------- Comment (by earle):
I forgot to mention "update indices", which should go between items 6 & 7 on the list above.
#72: Node renaming tool --------------------------+------------------------------------------------- Reporter: earle | Owner: dom Type: enhancement | Status: new Priority: normal | Component: openguides Version: | Severity: normal Resolution: | Keywords: utilities, database, admin --------------------------+------------------------------------------------- Comment (by ivorw):
What about the node's version history?
One option would be to leave this against the old node.
An alternative is that renaming drags across the history as well.
We could possibly get the best of both worlds by copying the history to the new node and leaving it in the old one as well.
Thoughts please.
#72: Node renaming tool ----------------------------------------+----------------------------------- Reporter: earle | Owner: dom Type: enhancement | Status: new Priority: normal | Milestone: Component: openguides | Version: Severity: normal | Resolution: Keywords: utilities, database, admin | ----------------------------------------+----------------------------------- Comment (by dom):
This can be done more efficiently by the CGI::Wiki changes yet to be released.
#72: Node renaming tool ----------------------------------------+----------------------------------- Reporter: earle | Owner: dom Type: enhancement | Status: new Priority: normal | Milestone: Component: openguides | Version: Severity: normal | Resolution: Keywords: utilities, database, admin | ----------------------------------------+----------------------------------- Comment (by dom):
There's a command-line node renaming tool in Wiki::Toolkit (wiki-toolkit- rename-node) which uses rename_node in Wiki::Toolkit. Might be nice to use that in Openguides.
#72: Node renaming tool ----------------------------------------+----------------------------------- Reporter: earle | Owner: dom Type: enhancement | Status: new Priority: normal | Milestone: Component: openguides | Version: Severity: normal | Resolution: Keywords: utilities, database, admin | ----------------------------------------+----------------------------------- Comment (by earle):
The node renaming tool does indeed work very well. I'd like to extend my original description above with "creates a new node with the old name that redirects to the new one", so this ticket now relies on #164 being done first.
openguides-tickets@lists.openguides.org
-
OpenGuides