cataloging:authorities:2.0
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| authorities:2.0 [2010/12/28 18:04] – Link tasks dbs | cataloging:authorities:2.0 [2018/05/29 19:16] – ↷ Page moved from authorities:2.0 to cataloging:authorities:2.0 sandbergja | ||
|---|---|---|---|
| Line 14: | Line 14: | ||
| Some of the limitations of authorities in Evergreen 2.0 include: | Some of the limitations of authorities in Evergreen 2.0 include: | ||
| - | * Searches | + | * " |
| * Field mappings for authority searches are currently hard-coded into the following categories: | * Field mappings for authority searches are currently hard-coded into the following categories: | ||
| * **Author**: 100‡a, 110‡a, 111‡a | * **Author**: 100‡a, 110‡a, 111‡a | ||
| Line 20: | Line 20: | ||
| * **Title**: 130‡a | * **Title**: 130‡a | ||
| * **Topic**: 150‡a | * **Topic**: 150‡a | ||
| - | * //See from// (4XX) and //see also from// (5XX) tracings are not currently supported | ||
| * Authority records can only control bibliographic records; no linkage from authority record to authority record is currently supported. So, for example, an authority record containing a 5XX //see also from// field cannot have that field controlled by the appropriate authority record that contains the value as its 1XX field. | * Authority records can only control bibliographic records; no linkage from authority record to authority record is currently supported. So, for example, an authority record containing a 5XX //see also from// field cannot have that field controlled by the appropriate authority record that contains the value as its 1XX field. | ||
cataloging/authorities/2.0.txt · Last modified: 2022/02/10 13:34 by 127.0.0.1