Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
marcit_record_loads [2013/04/09 21:47] ldegozzaldi |
marcit_record_loads [2019/01/07 17:20] 127.0.0.1 external edit |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| The following is the general process for adding bibliographic records generated by the SFX/MARCIt! service to the catalog. These are approximately half CONSER records for serials offered by the library through individual or package subscriptions where available, brief records for non-CONSER journals supplied by the SFX system, database aggregators, or open access. | The following is the general process for adding bibliographic records generated by the SFX/MARCIt! service to the catalog. These are approximately half CONSER records for serials offered by the library through individual or package subscriptions where available, brief records for non-CONSER journals supplied by the SFX system, database aggregators, or open access. | ||
| - | * On an approximate bi-monthly basis, Lucy deGozzaldi generates MARCIt! records using the MARCIt! Tool within the SFX Admin Center. | + | * Upon request from someone in Acquisitions, Lucy deGozzaldi generates MARCIt! records using the MARCIt! Tool within the SFX Admin Center. |
| - | * Several changes are applied to the bib records through a script, in preparation for loading and management in our catalog through Aleph services. | + | * Several changes are applied to the bib records through a script, in preparation for loading and management in our catalog through Aleph Services. |
| * The following files are created through Aleph Services/Load Records/Check Input File Against Database (manage-36): | * The following files are created through Aleph Services/Load Records/Check Input File Against Database (manage-36): | ||
| - **New** - MARCIt! records being added to our database for the first time. | - **New** - MARCIt! records being added to our database for the first time. | ||
| - | - **Updated** - MARCIt! records already existing in the Aleph database which have been revised, and need to be overlaid. (Normally the largest file we receive.) ??This report also notes which records have multiple 856 fields in the holdings record.??[need to check with Mike] | + | - **Updated** - MARCIt! records already existing in the Aleph database which have been revised, and need to be overlaid. (Normally the largest file we receive.) |
| - **Duplicates** - multiple MARCIt records in Aleph with the same SFX ID in the 035-9 field. These are now rare, as they have been "cleaned up." If any are found, they need to be reviewed and resolved by eleres. | - **Duplicates** - multiple MARCIt records in Aleph with the same SFX ID in the 035-9 field. These are now rare, as they have been "cleaned up." If any are found, they need to be reviewed and resolved by eleres. | ||
| //NOTE: Bibs earmarked for deletion will have "umzzz" in a 035-9 field. These can occur in both the **new** or **updated** files.// | //NOTE: Bibs earmarked for deletion will have "umzzz" in a 035-9 field. These can occur in both the **new** or **updated** files.// | ||
| - | * After all preparatory steps are done, the files of new and updated records are loaded into the Aleph database. For the **new** records, items and HOL records are created (through Aleph Services manage-50, which adds the 856 to the HOL and the proper coding into the items) and the 856 removed from the bibs. For the **updated** records, the urls are compared and differences resolved (through downloading machine-readable data into Excel) and the 856 removed from the bibs after overlaying. | + | * After all preparatory steps are done, the files of new and updated records are loaded into the Aleph database. For the **new** records, items and HOL records are created (through Aleph Services manage-50, which adds the 856 to the HOL and the proper coding into the items) and the 856 removed from the bibs. For the **updated** records, the urls are compared and differences resolved (through downloading machine-readable data into Excel) and the 856 removed from the bibs after overlaying. |
| + | |||
| + | //NOTE: Records with more than one 856 in their HOL, including those marked for deletion, will be reported to eleres.// | ||
| * The "umzzz" records (deletes) are pulled into a list through a CCL search, and run through a test delete (Aleph Services manage-33). Lucy will generate a spreadsheet listing all bibs with ERROR reports (mostly due to attached order records), add titles and save it on the R: drive (Coll-Management)\Acquisitions\MARCIt, and send a notification to eleres. Once the ERROR bibs have been removed from the list, the rest of the umzzz bibs can be deleted without further review. | * The "umzzz" records (deletes) are pulled into a list through a CCL search, and run through a test delete (Aleph Services manage-33). Lucy will generate a spreadsheet listing all bibs with ERROR reports (mostly due to attached order records), add titles and save it on the R: drive (Coll-Management)\Acquisitions\MARCIt, and send a notification to eleres. Once the ERROR bibs have been removed from the list, the rest of the umzzz bibs can be deleted without further review. | ||
| + | * Following Lucy's notification of MARCIt! record load to eleres, e-resources staff will note date of load on eleres Google calendar. | ||
| * E-Resources will review bibs with ERROR reports which have order records attached. Four possible scenarios with these records: | * E-Resources will review bibs with ERROR reports which have order records attached. Four possible scenarios with these records: | ||
| - Bib is being replaced with "better" record: Staff will move the order record(s) to the better bib. | - Bib is being replaced with "better" record: Staff will move the order record(s) to the better bib. | ||
| Line 28: | Line 31: | ||
| //NOTE: The process for generating bibliographic records for new e-journals is described in [[EJournals - Adding New Titles (MARCIt)]].// | //NOTE: The process for generating bibliographic records for new e-journals is described in [[EJournals - Adding New Titles (MARCIt)]].// | ||
| + | |||
| + | **MARCIt Records and SFX Object Types.** | ||
| + | * SFX object types that generate MARCIt records: Journal, Conference, Newspaper, Series, Transcript, Wire. Database? (SFX says databases do generate MARCit records but is this always true?) | ||
| + | * SFX object types that DO NOT generate MARCIt records. Book, CD, Dissertation, Document, Manuscript, Proceeding, Report. | ||
| + | |||
