Comment 5 for bug 1277194

I don't think there's much benefit to an active flag and worst case we end up with another biblio.record_entry (active AND deleted, who knows what code cares about each...) Since there's nothing *actually* final about deleting most things in Evergreen we may as well stick with it. It could also be used in a less enthusiastic way than most other deleted flags if need be (similar to Bill's comment in #3) That could be expanded into a more thorough deleted flag later without messing with the schema any further.