A Move feature would also be nice. If using the parent_id column to structure assets into a hierarchy, parent-sibling relationships exist. If an asset with child assets is moved to another building or different site, the hierarchy branch needs to be recreated in the new location (assuming it is treated as an asset) and the old records need to be deleted. That is, you can't move a parent if the asset has siblings. The SQL for doing this as well as copying nodes for the adjacency list model has existed for some time (e.g., see Joe Celko's small book on trees and hierarchies).
