Serials Solutions Marc Records overview

 

Serials Solutions will provide Marc record updates each month.  The files will be divided into three categories:  new, changed and delete.  In order to take full advantage of the service we have purchased, the best way to handle these records is to allow electronic journals to have bib records that are separate from their print counterparts.

 

New files:  This file will contain Marc records for the initial load.  In future, it will contain Marc records for recently subscribed to ejournals.  Records will not overlay existing records.  Appropriate item records will be generated to facilitate scoping.

 

Changed files:  This file will contain updated Marc records.  Any field in the Marc record may be updated.  These records will overlay existing Serials Solutions records.  The overlay point is the unique Serials Solutions control number, present in the 016. 

 

Delete files:  This file will contain Marc records for cancelled ejournals.  These records will not be deleted, but automatically suppressed.  In the shared environment, I envision the process working like this:

 

IF . . .several libraries subscribe to an ejournal and one cancels . . .

THEN . . .the change file will reflect that one library has cancelled.  Canceling library must suppress its’ item record.

 

IF . . .all libraries subscribing to an ejournal cancel

THEN . . .the delete file will reflect that all libraries have cancelled and the entire record will be suppressed at the bib level.

 

Some notes:

All records will contain accurate OCLC 001s.

Whenever possible, we have chosen to get the best CONSER records available. 

Serials Solutions bib records should not be edited.

Libraries are responsible for their own item records, which may be suppressed by using an “n” in the ICODE2 field.

Mat type will be S, item type will be 51

Appropriate branch and item locs will be generated by the III load profile.

 

Some questions:

  1. Should libraries be expected to migrate to the serial solutions records order records for their electronic subscriptions that are attached to print titles?
  2. Records suppressed by a delete file load should eventually be deleted for real.  How do we decide the criteria and frequency of this deletion process?
  3. Authority – should these records be run through the control process?
  4. How do we keep these records out of the duplicate reports?
  5. Other comments and questions.