Aleph Cataloguing/Authorities Conversion Work Group s1

Aleph Cataloguing/Authorities Conversion Work Group s1

<p>Aleph Cataloguing/Authorities Conversion Work Group</p><p>Recognition of deleted NOTIS records</p><p>Authority records with deleted status: If the NOTIS STAT 2nd position (leader/05) is D: the authority record is deleted. Do not migrate deleted authority records.</p><p><<js 06feb2000 We will do this. Probably in next load.</p><p>Bibliographic records with deleted status: If the NOTIS STAT 2nd position (leader/05) is D, C, F, M, N (in CAPS): the bibliographic record is deleted. (Codes C, F, M, N mean that the record has, or once had, a closed order record attached to it.) Do not migrate deleted bibliographic records without associated order records to Aleph. No BIB ADM HOL or ITM records should be created based on them. Ex. AEL9023, AGF3895 in the sample base are deleted records</p><p>However, if the bibliographic record is linked to a closed order record, migrate it as a logically deleted record in Aleph using the STA::$$aDELETED field. </p><p><<js 06feb2000 With this bib spec we would need to wait until we have read the copy holdings record (to check the order linkage). This would be too much trouble. We can delete them all (everything with "D") or convert them all as "STA $ $aDELETED. (Sorry about this. I'm thinking that your best option might be running the NOTIS bib purge --which *is* already set up to check for order linkage, before conversion. I assume that in time we'll have more sophisticated purges in ALEPH500 --but couldn't say when....)</p><p>Copy statements with deleted status: A copy statement with classification type Z represents a deleted copy. Do not migrate such a statement unless there is an order record associated with it. Do not create an ADM 852 for these statements, nor create any HOL records for them. Ex. ABK8053 statements 1 and 3 are to be deleted BEA6964 statement 2 is to be deleted ACA9343 statement 2 is to be deleted</p><p>Any NOTIS MHLD records linked to them should be discarded regardless of status, any NOTIS ITEM records linked to them should be discarded regardless of status. Ex. AAF2019 statement 2 has an MHLD attached to a Z copy statement </p><p>06/08/18 - 1 - However, if a copy statement with Z classification type is linked to an order record (open or closed), create/migrate a HOL record for it which is suppressed in Aleph using the STA::$$aSUPPRESSED field. (See: Acquisitions Conversion Report for ExLibris -- Jan. 11, 2000, Item #7)</p><p><<js 06feb2000 Basically the same issue as the bib. (If you run the NOTIS purge, you will get the copy holdings purged too....)</p><p>MHLD records with deleted status: An MHLD record with STAT (leader/05) d (lower case) is deleted. If an MHLD record attached to an active copy statement is coded d, the fields in that MHLD should not be added to the HOL record for that copy statement during migration. Instead, a default HOL record should be created based on the copy statement.</p><p><<js 06feb2000 We will do this (but if you're doing the NOTIS bib purge you will want to do the NOTIS MHLD purge first anyway).</p><p>ITEM records with deleted status: If the item status (C00 item leader field, position 17) is d (deleted), o (orphaned), w (withdrawn) the item record should not be migrated. Migrate only active item records.</p><p><<js 06feb2000 We are already doing this.</p><p>06/08/18 - 2 -</p>

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    2 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us