Comment 2 for bug 1441301

I was thinking about this because I ran into this issue with a test system where some experiments were being done by a customer with changing how metarecords are built so existing ones had to be wiped and that affected holds. The approach I used was to map to newly built metarecords with identical or similar values and formats. We could build in a trigger to do that but it seems the scope of use would be awfully narrow, so is it worth it? My instinct is to say that this would be better as a SQL script on the WIKI than worrying about it on the software level until a situation occurs that causes metarecords to have a greater level of churn.