In cleaning up bibliographic data after years of laissez faire cataloguing practice, we have run into a consistent stumbling block that requires us to backtrack. Certain bytes, especially in the 007 and 008 fields appear to require consistency across them to properly read at an item level (we became aware of this when getting red toasts scanning items for a weeding record set, that appeared initially to be in the inclusion criteria).

By way of example: If you input in 007 an 01 byte of 'd - Videodisc', than the 04 byte would have to be 'g' 'h' 's' or 'v' - if it were any other, like 'b - VHS', than the system would flag the error to you upon trying to save bib edits.

This could extend to have the 007 match on key bytes of the 008 field (if the 007 has an 01 byte of 'd - Videodisc' than the 033 byte of 008 would have to be 'v - Videorecording')

If there were a way to have Polaris check control field data in this holistic manner, it would save us having to go into the same bib five or six times trying to figure out which byte is inconsistent with the rest of them.