Reword the scan status section
- Possible enums (check on pickling)
-
Status persistence [Maybe a separate user enabled/disabled flag with message presentation]
- The code flagged the scan invalid for some reason
- The user marks the scan valid - The original codes are wiped out
- The user then marks the scan invalid again
- The original scan invalidity should be maintained somewhere. If the user marked it disabled again in the event of enabling it in error, they can no longer see the original status