This disposition is fairly rare, since in general when you are restructuring content you are better off doing it in the new or revised system. This is because the system should be enforcing structural constrains you are putting on the content in the target state. That said, sometimes there are no new structures in the new situation for some content, in which case you modifying the content in the current system can be a timesaver (especially since you can start the content work before the new system is complete).
To be clear, in this disposition you are:
Manually modifying the content in the current system.
Automatically moving the content to the new system (or automatically transform it to the new model in the current system).
There may be some setup required in the current system to help enforce new structural constraints, so you are confident that changes in the current system will "stick" when automatically moved to the new system.
| Step | Effort | What is this? |
|---|---|---|
| Sort | low | Decide what to do with content item |
| Place | skipped | Place in IA |
| Edit | low | Edit text/content (NOT technical) |
| Move / Transform | low | Physically move/enter/transform content (NOT the words) |
| Enhance / Tag | skipped | Prepare the metadata, especially tagging/retagging |
| QA | skipped | Review content for quality |