DAL (diagnostic assembly line system - compliance) passes things up to LIMS (information management system - accountability/tracking through process life cycle) & ERP (like SAP).
Industry/company policies / regulations set what is considered a deterministic resolution for a LIMS/ERP process item aka successful process life cycle completion and/or what needs to be done for a non-deterministic / incomplete life cycle process. Information from or not received from one or more DAL's or other sources may/may not contribue to a non-deterministic outcome/resolution.
Project didn't have a deterministic way to figure out if individual songs being added already esisited in 'database'. Song(s) packaged differently so 'same' audio song need multiple methods to figure out if already in database. Not all computation methods / automated methods for finding songs were 'available'. aka no code to determinsticily go through all various ways to find duplicates.
Vs program acoustid provides a unique identifying 'fingerprint' (DAL level item) passed to LIMS -> beets/musicbrains. LIMS then uses unique identifying 'fingerprint' as a way to associate other addition DAL level data (artist, record lable, what else released with). Undiscussed, what if 2 recored lables released same song?
LIMS might contain information on which format to keep/convert to if two song fingerprints are the same). Missing information on to ignore file format or convert to a specific file format would lead to a non-deterministic result of only difference between 'identical' song fingerprints was song file format. Different formats (file & recording) do generate different quality recordings. LIMS level usually is level sort/resolve conflicting data from DAL's. Note: 'how to deterministially resolve issue(s)' may be a feature request by a user after LIMS (SAP) has been set up.
Business view of lims/dal:
DAL (diagnostic assembly line system - compliance) passes things up to LIMS (information management system - accountability/tracking through process life cycle) & ERP (like SAP). Industry/company policies / regulations set what is considered a deterministic resolution for a LIMS/ERP process item aka successful process life cycle completion and/or what needs to be done for a non-deterministic / incomplete life cycle process. Information from or not received from one or more DAL's or other sources may/may not contribue to a non-deterministic outcome/resolution.
Contrived example: "Oh man, music data strucures are a rabbit hole." : https://news.ycombinator.com/item?id=50200065
Project didn't have a deterministic way to figure out if individual songs being added already esisited in 'database'. Song(s) packaged differently so 'same' audio song need multiple methods to figure out if already in database. Not all computation methods / automated methods for finding songs were 'available'. aka no code to determinsticily go through all various ways to find duplicates.
Vs program acoustid provides a unique identifying 'fingerprint' (DAL level item) passed to LIMS -> beets/musicbrains. LIMS then uses unique identifying 'fingerprint' as a way to associate other addition DAL level data (artist, record lable, what else released with). Undiscussed, what if 2 recored lables released same song? LIMS might contain information on which format to keep/convert to if two song fingerprints are the same). Missing information on to ignore file format or convert to a specific file format would lead to a non-deterministic result of only difference between 'identical' song fingerprints was song file format. Different formats (file & recording) do generate different quality recordings. LIMS level usually is level sort/resolve conflicting data from DAL's. Note: 'how to deterministially resolve issue(s)' may be a feature request by a user after LIMS (SAP) has been set up.