The LKR field in Cataloging Version 16 and up

Slides:



Advertisements
Similar presentations
Alma: To Have and To Hold
Advertisements

ALEPH version Course Reading & Reserves Course Documents South Dakota Library Network 1200 University, Unit 9672 Spearfish, SD
Version 18 Upgrade: General Systems. 2 All of the information in this document is the property of Ex Libris Ltd. It may NOT, under any circumstances,
South Dakota Library Network ALEPH v21 Staff User Upgrade Information Cataloging and Systems South Dakota Library Network 1200 University, Unit 9672 Spearfish,
Version 18 Upgrade: Web OPAC. Version 18 Upgrade: Web OPAC Customization 2 All of the information in this document is the property of Ex Libris Ltd. It.
Weeding in ALEPH Library Staff Training © South Dakota Library Network, 2013 ©Ex Libris (USA), 2011 Modified for SDLN Version
Serials: Version 18 Upgrade Training. 2 All of the information in this document is the property of Ex Libris Ltd. It may NOT, under any circumstances,
Sending sets of records via . Sending via 2 All of the information in this document is the property of Ex Libris Ltd. It may NOT, under any.
How to transfer 85x prediction patterns from ADM library to HOL library Presenter: Yoel Kortick.
1 Pick and Scan Voyager 9. 2 Copyright Statement All of the information and material inclusive of text, images, logos, product names is either the property.
How to use the SDI RSS Feed Version 18 Yoel Kortick.
V. 21. Automatic LKR field creation from item. Rep_ver and Yoel Kortick Aleph Support Manager.
Items Version 18 Upgrade Training. Items: Version 18 Upgrade Training 2 All of the information in this document is the property of Ex Libris Ltd. It may.
Preparing and sending records to ULI. 2 All of the information in this document is the property of Ex Libris Ltd. It may NOT, under any circumstances,
How to use the Offline Circulation Version 16 Yoel Kortick.
How to retrieve orders which were sent to vendor and not arrived Version 16 and up Yoel Kortick.
How to Combine Items of Separate Bibliographic Records Version 16 and up Yoel Kortick.
How to create and use authority records Version 16 and up Yoel Kortick.
How to control bracket and parentheses appearance in right to left display of web Presenter: Yoel Kortick.
The LKR field in Cataloging Version 16 and up Yoel Kortick.
How to view and manipulate an ALEPH report in Excel Version 16 Yoel Kortick.
How to send Serial claims to vendor (Batch) Version 16 Yoel Kortick.
1 Designing and using normalization rules Yoel Kortick Senior Librarian, Ex Libris.
1 Yoel Kortick Senior Librarian Working with the Alma Community Zone and Electronic Resources.
1 Discovery Interface Display Logic Yoel Kortick Senior Librarian.
Setting up and using Acquisitions-related indexes and logical bases. Version 18 and up Yoel Kortick.
1 Yoel Kortick | Senior Librarian Serials automation tasks for summary holdings.
1 Yoel Kortick Senior Librarian Alma Product Management Mapping the bibliographic call number to the holding record call number.
1 How to manually package PO Lines Yoel Kortick Alma Global Support Manager.
Version 18 Upgrade: Privileges. 2 All of the information in this document is the property of Ex Libris Ltd. It may NOT, under any circumstances, be distributed,
1 RDA in Aleph 500 Version 21 Yoel Kortick. Aleph support manager Nov
An Introduction to the Bibliographic Metadata Profile in Alma
How to use the job list Version Yoel Kortick.
How to send to the vendor an analytics report of items which have or have not arrived (Legal Deposit) Yoel Kortick Senior Librarian.
New service, p-ret-adm-03 (Advanced General Retrieval Form) Version 21 rep_ver # Yoel Kortick Alma Global Support Manager
Defining and using an external search profile with multiple targets for copy cataloging Yoel Kortick Senior Librarian Alma Product Management.
How to add a non-Analytics widget to the Alma Dashboard
How to set up an RSS feed New Book List in Alma
How to print barcodes in batch mode via item-03
An article in an anthology and derive new record
How to “expand” holding library fields to bibliographic record
How to add a fix procedure for copy cataloging from a Z39.50 base
Overview of Acquisition Claiming in Alma
Digital Assets Module Services adam-01 and adam-02 versions 17 and up
Patron Driven Acquisition (PDA) Demand Driven Acquisition (DDA)
Receiving New Lending requests
Heading maintenance via the GUI
Authorities in Alma and F3
Prediction Patterns and Serial Check-in
Accessing and Using the Alma Link Resolver from Outside Primo
Yoel Kortick Senior Librarian
Presenter: Yoel Kortick
Building bases according to sub library
Publishing to OCLC Yoel Kortick Senior Librarian.
How to configure and use the Holdings record Accession Number
Introduction This presentation will show two ways of making a report of newly acquired records: Via services Retrieve Catalog Records (ret-01) and Print.
Interoperability Between Aleph and Primo: Aleph Restful APIs
Importing Serial Prediction Patterns Via the Service Import 85X records (Serial-52) Yoel Kortick.
Multi item ILL requests in Aleph 500 Version 21 (rep ver and 17844)
In House Use and Alma Analytic reports for In House use
ALEPH Version 22 Beginning Cataloging
תוכניות שירות במודול רכש של אלף
An article in an anthology and derive new record
Link article to one specific issue of a journal
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
Acquisitions: Version 18 Upgrade Training
Aleph Implementation Where we are in the process Data Review
How to use SDI Version 16 Yoel Kortick.
Prediction Patterns and Summary Holdings
Presentation transcript:

The LKR field in Cataloging Version 16 and up Yoel Kortick

All of the information in this document is the property of Ex Libris Ltd.  It may NOT, under any circumstances, be distributed, transmitted, copied, or displayed without the written permission of Ex Libris Ltd. The information contained in this document has been prepared for the sole purpose of providing information for the members of the ICC Israel College Consortium.  The material herein contained has been prepared in good faith; however, Ex Libris disclaims any obligation or warranty as to its accuracy and/or suitability for any usage or purpose other than that for which it is intended. © Ex Libris Ltd., 2006

Introduction The LKR field may appear in a record for two reasons: It has been generated by the system (system-generated) It has been entered by a cataloger (user-generated) We will first discuss system-generated links, then user-generated links

System-Generated Links The ALEPH system holds information in different types of records and different types of "libraries" (databases). For example, a standard system has a bibliographic database for storing bibliographic data, and an administrative database for storing administrative data. The total picture of a record is dependent on the links between the other records in the system. The LKR field is an ALEPH field used to create these links.

Automatic creation of System-Generated Links When creating a holdings or an administrative record for the bibliographic record in the Catalog module, the new record automatically includes the LKR field. The following is an example of an LKR field for an administrative record. Note that subfield $a of the LKR field (administrative record) is set to ADM and subfield $b contains the system number of the bibliographic record.

Bibliographic Record We have the following record in library USM01

Holding Record When the HOL record is created for the bibliographic record, it automatically receives an LKR field

ADM Record Similarly, when an item is created, an Administrative record is also created, and contains an LKR field.

Structure of the system-generated LKR The system-generated LKR field contains three subfields Subfield a: type of link HOL: link from HOL record to BIB record. Link is built from BIB to HOL. ADM: link from ADM record to BIB record. Link is built from BIB to ADM.

Structure of the system-generated LKR Subfield l: library to which record is linked In the examples here the HOL record and the ADM record are linked to the USM01 library Subfield b: system number of record to which current record is linked

Structure of the system-generated LKR This is a Holding Record linked to system number 67341 in library USM01

Structure of the system-generated LKR This is an Administrative Record linked to system number 67341 in library USM01

User-generated LKR field You can use the LKR field to create links from one bibliographic record to another for example for analytical purposes for changed titles for serial publications

User-generated LKR field The available types of links and the values that must be entered to generate these links are shown in the next slides. Note that the LKR field is only cataloged in one of the records; the system creates the other side of the link. First we will discuss LKR subfield a, then the other subfields

User-generated LKR field – subfield a UP An up link to another bibliographic record. A record can have only one link of this type. A DN link is automatically built in the opposite direction. DN A down link to another bibliographic record. Multiple links are possible. An UP link is automatically built in the opposite direction.

User-generated LKR field – subfield a PAR A parallel link from one bibliographic record to another. A PAR link is automatically built in the opposite direction. ANA The ANA link creates both ITM and UP-DN type links. In other words, it creates a link between the two bibliographic records and to the item/s. * Note that subfield $b for this type of link contains the system number of the bibliographic record to which the record is linked (unlike the ITM type link).

User-generated LKR field – subfield a ITM The ITM link creates a link between one bibliographic record and the items of another bibliographic record. The item filter fields ($y, $v, $p, and $i must be used for this type of link). *Note that subfield $b for this type of link contains the ADM system number.

User-generated LKR field – other subfields System number of the linked record (the target record) i Issue link k Pages l Library where target record is located. It must be entered in uppercase

User-generated LKR field – other subfields m Down link note n Up link note p Part link r MARC tag link

User-generated LKR field – other subfields Sort sequence; can be alphanumeric (more information on the way this field affects the display of the link can be found in tab_fix_z103) v Volume link y Year link

Up and Down links The DN (down) link creates a down link from the record that has the LKR field to the record to which it is linked. An UP (up) link is created automatically from the linked record back to the record with the LKR field. The UP (up) link creates an up link from the record that has the LKR field to the record to which it is linked. A DN (down) link is created automatically from the linked record back to the record with the LKR field.

Up and Down links Example: we have Sysno 67342: Economic History of Europe Sysno 67343: Economic History of Poland Sysno 67344: Economic History of Portugal We will make a DN link from 67342 to both 67343 and 67344. An UP link will automatically be created from 67343 and 67344 to 67342

Up and Down links Thus, in record 67342 we will add the following: LKR L $$a DN $$b 67343 $$l USM01 $$n The economic history of Poland $$m The economic history of Europe $$b 67344 $$n The economic history of Portugal

Up and Down links And therefore when user views record 67342 in web OPAC he will see the following as part of the record: Clicking “The economic history of Poland” will link to record 67343 Clicking “The economic history of Portugal” will link to record 67344

Up and Down links And therefore when user views record 67343 or record 67344 in web OPAC he will see the following as part of the record: Clicking “The economic history of Europe” will link to record 67342

The PAR (parallel) link The PAR (parallel) link creates a parallel link from one record to another. For example, we may have two similar bibliographic records, and we want to tell the reader to see the other bibliographic record when he views one of them in the web OPAC. (Perhaps for example we have two editions of the same monograph).

The PAR (parallel) link Scenario We have record 67348: 24504 L $$a<<The>> Cambridge economic history of Europe;$$cgeneral editors, M.M. Postan and H.J. Habakkuk. 250 L $$a1st ed. And we have record 67342: 24504 L $$a<<The>> Cambridge economic history of Europe;$$cgeneral editors, M.M. Postan and H.J. Habakkuk. 250 L $$a2nd ed. We can make a parallel link between the two records

The PAR (parallel) link In record 67342, which is 2nd edition, cataloger can catalog as follows LKR L $$a PAR $$b 67348 $$l USM01 $$n other edition available:1st edition $$m other edition available:2nd edition The subfield “n” points to the other record (not the record in which the LKR field is being cataloged

The PAR (parallel) link When web OPAC user views record 67348, which is 1st edition, he will see as follows: Clicking the link will cause user to arrive to record 67342 (2nd edition) When web OPAC user views record 67342, which is 2nd edition, he will see as follows: Clicking the link will cause user to arrive to record 67348 (1st edition)

The ITM (item) link ITM Links The ITM link creates a link between a bibliographic record and the items of another bibliographic record. The following is an example of an ITM link. In this example, Northern Albania (system number 67350) is the first volume of the series Albania (system number 67349) . Central Albania (system number 67351) is the second volume of the series Albania. The items for all volumes are managed under the record Albania.

The ITM (item) link All items are entered via GUI in record Albania which is Bibliographic record number 67349 and Administrative record number 67349 Vol. 1 Vol. 2 No items are entered for 67350 and 67351

The ITM (item) link Bibliographic record 67350 (Volume 1) contains the following LKR field: LKR L $$a ITM $$b 67349 (ADM record of the item) $$l USM50 (ADM library of the item) $$v 01 (Volume Enum. Level 1) Bibliographic record 67351 (Volume 2) contains the following LKR field: LKR L $$a ITM $$b 67349 (ADM record of the item) $$l USM50 (ADM library of the item) $$v 02 (Volume Enum. Level 1)

The ITM (item) link User goes to web and views Bibliographic record 67350 (Volume 1) and he gets the following link: Which brings the following item:

The ITM (item) link User goes to web and views Bibliographic record 67351 (Volume 2) and he gets the following link: Which brings the following item:

The ITM (item) link But… When user view the “main” record, 67349, where all of the items are entered, he will get the following link (to all items): Which brings all items:

The ANA (analytic) link Analytic Links ANA is a link between bibliographic records of different levels. When an analytic link is created the system generates UP / DWN links between the two records and an item link between the source record and the item that corresponds to it (according to vol. ,part, year and pages) on the ADM record of the second record. For a list of all possible subfields for the ANA link see the “tag information” tab of the cataloging module

The ANA (analytic) link Scenario 1: We have the following records 67352 Studies in library science 67353 Vol. 1 of the series, titled “Developments in cataloging” 67354 Vol. 2 of the series, titled “Developments in acquisitions”

The ANA (analytic) link In record 67352, which is the “main” record, we add no LKR field, and we add items:

The ANA (analytic) link In record 67353 (Vol. 1) we add: LKR L $$a ANA $$b 67352 (number of the linked document record) $$l USM01 (bibliographic library) $$v 01 (vol. enum. Level of linked item) $$n Studies in library science (text for UP link) $$m Developments in cataloging (text for DWN link) And no items are added to this record

The ANA (analytic) link In record 67354 (Vol. 2) we add: LKR L $$a ANA $$b 67352 (number of the linked document record) $$l USM01 (bibliographic library) $$v 02 (vol. enum. Level of linked item) $$n Studies in library science (text for UP link) $$m Developments in acquisitions (text for DWN link) And no items are added to this record

The ANA (analytic) link Users views “main” record (67352) in web and sees link to all items And sees both items

The ANA (analytic) link Also in “main” record (67352) in web user sees links to both bibliographic records of the series: Clicking these links will cause user to arrive to each of the bibliographic records

The ANA (analytic) link In record 67353 and 67354 (Vol. 1 and Vol. 2) the user in web will have an UP link to the “main” record (67352)

The ANA (analytic) link Record 67353 (Vol. 1) will also have an item link which will bring only volume 1

The ANA (analytic) link Record 67354 (Vol. 2) will have an item link which will bring only volume 2

The ANA (analytic) link It is also possible to make an analytic link to a specific section of a bibliographic record. For example we have a record titled “Academic libraries: a collection of papers “. It is system number 67355 It includes many articles, two of them: Academic libraries in North America (pp 23-67) History of Academic Libraries (pp 68-97)

The ANA (analytic) link Bibliographic record 67355 is catalogued and one item entered (There are no volumes) Bibliographic record 67356 is cataloged as the first article from the previous slide “Academic libraries in North America” Bibliographic record 67357 is cataloged as the second article from the previous slide “History of Academic Libraries”

The ANA (analytic) link Bibliographic record 67356 is catalogued and one item entered (there are no volumes). Bibliographic record 67356 is cataloged as the first article from the previous slide “Academic libraries in North America”. Bibliographic record 67357 is cataloged as the second article from the previous slide “History of Academic Libraries”.

The ANA (analytic) link We enter one item for the “main” biblographic record, 67355, and no LKR field No volume

The ANA (analytic) link We enter no item for record 67356, and we add the following LKR field LKR L $$a ANA $$b 67355 (number of the linked document record) $$l USM01 (bibliographic library) $$k 23-67 (pages) $$n Academic libraries: a collection of papers (text for UP link) $$m Academic libraries in North America (text for DWN link) It is customary to also put the pages of the article as part of the bibliographic record

The ANA (analytic) link We enter no item for record 67357, and we add the following LKR field LKR L $$a ANA $$b 67355 (number of the linked document record) $$l USM01 (bibliographic library) $$k 68-97 (pages) $$n Academic libraries: a collection of papers (text for UP link) $$m History of Academic Libraries (text for DWN link) It is customary to also put the pages of the article as part of the bibliographic record

The ANA (analytic) link We enter web OPAC and view record 67355. It has a down link to both articles, and a link to the item.

The ANA (analytic) link We enter web OPAC and view record 67356. It has an up link to the main record, as well as the item of the main record

The ANA (analytic) link We enter web OPAC and view record 67357. It also has an up link to the main record, as well as the item of the main record