From the discussion going on in this forum, I have figured out that there several levels of awareness from user regarding audio file integrity.
- Basic users just let Media Center update tags on the fly (as they are editing them) and write to audio files at will;
- More advanced users disable writing on tags on the fly and let Media Center update tags only on demand.
I have found that even more advanced users can have some more needs about data file maintenance. I think MC can help them if a couple of fields were added into the Media Center database, natively managed by MC itself.
- An archive bit that, similarly to a standard file system, indicates whether the file is in sync with the tags in MC's library. When the archive bit is on, every tag is in sync between the file and the library. When the archive bit if off for a certain file, it means that tags in file need to be updated from library.
- A checksum field that stores the checksum (MD5) for the audio file. Using this field, a checksum verification can be run periodically as a batch (before starting a backup, for example). If some checksums fail, it means there is something wrong with the files, and they must be checked.
When file fields are updated from library, of course a new checksum needs to be computed in order to keep everything consistent.
It seems that the overall system (archive bit + checksum) is robust, but requires some administrative efforts. Are advanced users (who already work this way, but without the help of Media Center) ready to use such a powerful feature?