31.12.2014 Views

SirsiDynix Symphony Training Guide - FTP Directory Listing

SirsiDynix Symphony Training Guide - FTP Directory Listing

SirsiDynix Symphony Training Guide - FTP Directory Listing

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Case-Insensitive Checking<br />

If the system is configured for case-insensitive checking, any time a<br />

bibliographic record is added or edited; all bibliographic headings under<br />

authority control will be checked against the appropriate authority<br />

indexes. Headings that do not match an authoritative term are marked<br />

|UNAUTHORIZED. When matching best suited bibliographic headings<br />

against the authority indexes, the capitalization of the bibliographic<br />

heading need not exactly match that of the authorized term from the<br />

authority record.<br />

For example, the following bibliographic heading would be considered a<br />

match to the following authorized term from the authority record if<br />

checking is case-insensitive:<br />

Bazaars, charitable (Bibliographic heading)<br />

Bazaars, Charitable (Authorized term)<br />

Case-Sensitive Checking<br />

The case-sensitive checking configuration option is similar to caseinsensitive<br />

checking, except that bibliographic headings must exactly<br />

match the capitalization of authoritative terms in authority records. This<br />

configuration of authority control is best suited to libraries with sufficient<br />

staff to handle day-to-day authority control functions.<br />

For example, the following bibliographic heading would not be<br />

considered a match to the following authorized heading in the authority<br />

record if checking is case-sensitive.<br />

Navigation Acts, 1649-1696 (Bibliographic heading)<br />

Navigation acts, 1649-1696 (Authorized term)<br />

174 | S i r s i D y n i x S y m p h o n y T r a i n i n g

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!