Change priority of extracting 050 / 090 for ETL into Analytics LC Call number (Bib)
Currently, the ETL for a bib screen appears to overwrite the LC Classification Number (bibliographic record) with each 050 or 090 it reads. It is typical for the most 'authoritative' LC call number to be first on the record, while least authoritative (or even false) LC call numbers are last.
Consequently, when a bib record has more than one 050 or 090, Analytics is opting to report out the LEAST reliable call number for data.
Preferred would be that the ETL take only the first 050 in a record.
4
votes
Michael Johnson
shared this idea