Comment 4 for bug 1175766

Even with something like a copy/resource map we would still need a trigger for updates and that kind of makes my right eye twitch. Purely in the spirit of brainstorming it seem like it would be conceptually easiest to have resources become a child table of asset.copy. There would be some upgrade hurdles but I'm imagining that would be a major set of workflow changes for people using these resources since copies have a lot more requirements than resources. And thus a lot of UI changes too. There would also be a need to audit various logic. I'm assuming that is not a realistic option at this time.