949 fields and order records – the selector/requestor fields

Fair warning: seriously arcane cataloging topic discussed.

It took – literally – months to work through this, but kudos to Monica Brady, Principal Data Analyst at Innovative Interfaces Inc., for sticking with me and going the extra several miles to track this down.

Okay, here’s the thing:

To export a record from OCLC Connexion to our Sierra catalog, we add a 949 field which sets up the codes in the bibliographic record and creates an order record with information filled in.

Example for a book:

949  *recs=bo;ov= ; b1=a;b2=a;b3=o;bn=order;at=p;br=order;cp=1;c4=-;fm=a;st=o;vd=gobi;ep=00;
ep=1.00;

(this actually shows as one line, perhaps with a wrap-around)

The value of recs= is the load table extension so the records are loading through m2btab.bo, a load table programmed to load bibliographic and order records. This causes the system to create a bib record b and an order record o and fill in codes for them. From about the at= field, this sets up the order record and fills in codes, clear down to the estimated price ep=

Problem: We need to have the selecting (we call them liaison) librarian’s name in each order record, as we assign funds to each liaison librarian for their program areas.

We’ve been having to do it manually. While Sierra’s order records have special fields for s selector and r requestor (meaning faculty), the instruction in the Webhelp didn’t actually work — it was received (I think from OCLC) but wasn’t actually compatible with Sierra. III is going to or has changed that information.

So began a long process of researching by III and trial-and-error at my end.

Now we have the answer:

949  *recs=bo;ov= ;b1=a;b2=a;b3=o;bn=order;at=p;br=order;cp=1;c4=-;fm=a;st=o;vd=gobi;ep=00;
ep=1.00; ǂs selector ǂr requestor

(note the space and then ǂs selector ǂr requestor with no more semi-colons – use s and/or r as shown)

That’s it.  Following the last semi-colon, add a space, the standard double-dagger, the field code, another space and the name, with no semi-colon on the end — all different from the way all the other data is provided. The example shows how to do both in the same 949 but either works alone.

Our procedure provides the selector name when I get it, but now I can add that name in the order record without going back in later. Efficient!

Advertisements

Size is relative in video files

So, I have a video file from a presentation by one of our faculty. It’s a video recording in the Apple Quicktime .mov format. Quicktime is not always available on Windows PCs unless the user goes out and gets it.

And it’s big. Over 14 GB.

So, I can’t get it to save to a catalog record for downloading in Sierra, and it’s too big to burn to a DVD. Yes, I tried both, even though I didn’t have much hope. It’s only 17 minutes long, but MOV makes for a big file.

So, I tried VLC player to convert it to .avi format which would work on Windows Media Player and on VLC, but VLC is erratic in conversion results – I kept getting the video with no sound with various settings.

Next, I checked the web, and the free websites that convert wouldn’t do a file that large for free.

So, I tried VideoGrabber. Had to download a piece of software, but that got a file that is still too large to save to the catalog record (485,427 KB) but would burn to a DVD. I threw in the PowerPoint presentation with it on the disc and burned it.

I don’t expect much use off campus, so I didn’t catalog it on OCLC. It’s an interesting presentation, though, and gives some original insight into Beethoven’s work. We are glad to be able to keep material like this in the library.

I also make a point of saving such files to our network drive so they will be backed up elsewhere. Just in case.