1. ALEPH500 ALEPH500: Authority Control Management

2. ALEPH500 Creation of BIB-AUT links AUT record 100 $$a Plato 400 $$a Aplaton BIB record 100 $$a Aplaton BIB Headings 100 $$a Aplaton AUT Headings(GEN) 100 $$a Plato 400 $$a Aplaton  Bibliographic and authority record fields are sent to the headings index. Authority library index MUST be called GEN  The corresponding headings entries in the BIB and AUT database must be identical. Keep in Mind subfields, filing procedure, display text. ex. 100 $$a Plato and 100 $$a PLATO will not match ue_08

3. ALEPH500 Creation of BIB-AUT links AUT record 100 $$a Plato 400 $$a Aplaton BIB record 100 $$a Aplaton BIB Headings 100 $$a Aplaton AUT Headings 100 $$a Plato 400 $$a Aplaton  If a match is found, the usage code (008 pos.14/15/16) is checked ue_08

4. ALEPH500 Authority Control - ACC and X-refs AUT record 100 $$a Plato 400 $$a Aplaton BIB record 100 $$a Aplaton Headings 100 $$a Aplaton ue_08  If a match is found and the usage code is ‘a’(appropriate), a link is made between the bibliographic database heading (Z01) and the authority database document record.

5. ALEPH500 Authority Control - ACC and X-refs AUT record 100 $$a Plato 400 $$a Aplaton BIB record 100 $$a Aplaton ue_08 Headings $$a Aplaton see $$a Plato Pointers The preferred term is opened as a heading in the BIB database  The original term (seen from) is changed into a cross reference

6. ALEPH500 Authority Control - ACC and X-refs AUT record 100 $$a Plato 400 $$a Aplaton UPD Y BIB record 100 $$a Plato Headings $$a Aplaton see $$a Plato ue_08 Pointers  If update flag is Y or there is no update flag,the BIB record related to the non-preferred term is corrected

7. ALEPH500 Authority Control - ACC and X-refs AUT record 100 $$a Plato 400 $$a Aplaton UPD N BIB record 100 $$a Aplaton ue_08 Headings $$a Aplaton see $$a Plato Pointers  If update flag is N,the BIB record related to the non- preferred term is not corrected

8. ALEPH500 Sub-Divisions USMARC authorities can have standard sub-divisions $ v - Form subdivision $x - General subdivision $y - Chronological subdivision $z - Geographic subdivision Headings in the bibliographic database may not match those in the authority database. When the system does not find a match it will strip each sub-division and search for a match without it. When an authority record is updated, the system will update the matching headings and record in the bibliographic database even if they have sub-divisions.

9. ALEPH500 Authority Control:util e_08 aut_library........… NEW aut_library....… CHK aut_library........… USM10 Util e_08 Ue_08 daemon takes z01s [headings] marked NEW, checks them and updates them either by inserting the AUT library and record number or by marking it CHK if no match is found.

10. ALEPH500 Updating AUThority Records : the COR Field 100 $$aKreindler, Isabelle 400 $$aKreindler, I UPD Y Original AUT record 100 $$aKreindler, I 400 $$aKreindler, Isabel UPD Y Updated to: 100 $$aKreindler, Isabel 400 $$aKreindler, I COR $$aKreindler, Isabelle UPD Y When record is inserted the system adds COR Field (fix_doc_usm _preferred)

11. ALEPH500 Updating AUT Records : UE_11 BIB record 100 $$a Kreindler Isabelle Headings $$a Kreindler, I. see $$a Kreindler, Isabelle ue_11 (AUT) AUT record 100 $$aKreindler, Isabel 400 $$aKreindler, I COR $$aKreindler, Isabelle UPD $$aY ue_11 (BIB) Ue_11 will change The heading to “new”

12. ALEPH500 Updating AUT Records : UE_11 BIB record 100 $$a Kreindler Isabel Headings $$a Kreindler, I. $$aKreindler, Isabelle see $$a Kreindler, Isabel AUT record 100 $$aKreindler, Isabel 400 $$aKreindler, I COR $$aKreindler, Isabelle UPD $$aY ue_08 ue_08 will re-check the heading against the authority database