throbber
Sirsi-Batch loading
`
`Loading record batches to Unicorn
`
`While this methodology does not make sense for the small numbers of records one usually works with in copy cataloging operations, when
`loading larger sets such as YBP approval books, NetLibrary titles, GPO Shipping List records, or batches of original records from OCLC, it is
`much simpler to use MARC Import and the
` report then to bring the records in one at a time through SmartPort. Unicorn can load MARCbibload
`
`records in both communication format and as formatted text files.
`
`MARC communication format loads
`
`1.
`2.
`3.
`4.
`
`5.
`
`6.
`
`7.
`8.
`
`MARCIMPORT
` wizard.
`With desired upload file on your PC or network, select the
`From the
` box, accept the default values and click OK.MarcImport : Properties
`
`From the
` box, click on
`MarcImport Utility : Main
`Bibliographic data and Import
`.
` box and identify the MARC file awaiting upload using the
`From the
`MarcImport Utility : Import Bibliographic Data
`OTHER
` box, click on the
`Source gadget (diamond-shaped button to right of Source window). Make sure that the
`MARC
` radio button has been selected.
`Provide a filename you can remember in place of OTHER.MARC. This could be your initials and date (cp031117.marc) or a name
`indicating the content or purpose of the load (YBP1125.marc, GPOUrl0312.marc, NetLibraryMay.marc). Media should read pcdiskette
`even when you are working with a networked file.
`No
` to the question on more files to upload or they will be appended to the
`Click
`OK
` and answer
`Yes
` to "Is diskette ready?". Answer
`present file. A text file, listing the number of records loaded, will pop up. The top section refers to bibliographic records loaded while the
`bottom is for authorities.
`MarcImport Utility : File
`Go back into WorkFlows and you should see your uploaded file listed in the
` list
`Cancel and
`Exit
` your way out of
`MARCIMPORT
` and you are ready to run
`bibload
`, instructions for which are in a separate section below.
`
`Loading database output and flat ASCII formatted text
`
`Follow the instructions above, but at step 4 select the
`
`SIRSI
`
` file type and click on the
`
`Flat ASCII
`
` radio button.
`
`Sirsi specifies the following format for ASCII text input:
`
`.[MARC tag]. Ind1Ind2|aText|bText
`
`Each bibliographic record in the input file must begin with a document boundary statement and the name of the FORMAT being used (MARC,
`SERIAL, MANUSCRIPT, MAP, MRDF, MUSIC, VM):
`
`*** DOCUMENT BOUNDARY ***
`FORM=MARC
`
`The following illustrates a typical MARC record presented as ASCII text to MARCIMPORT:
`
`Page 1 of 4
`
`GOOGLE EXHIBIT 1036
`
`

`

`*** DOCUMENT BOUNDARY ***
`FORM=MARC
`.007. |acr an---------
`.008. |a030622s2003 ncuab m 000 eng d
`.040. |aNRC|cNRC
`.100. 1 |aByrd, Erick T.|q(Erick Tilghman),|d1973-
`.245. 13|aAn analysis of variables that influence stakeholder participation
`and support for sustainable tourism development in rural North
`Carolina|helectronic resource /|cby Erick T. Byrd.
`.260. |c2003.
`.300. |axxi, 272 p. :|bill., map.
`.502. |aThesis (Ph.D.)--North Carolina State University.
`.504. |aIncludes bibliographical references (p. 140-146).
`.500. |aIncludes vita.
`.520. |aKeywords: stakeholders, development, tourism, sustainable
`tourism.
`.650. 4|aNorth Carolina State University|xTheses|xParks, Recreation and
`Tourism Management.
`.856. 4|yFull text
`(pdf)|uhttp://www.lib.ncsu.edu/theses/available/etd-11122003-102451/unrest
`ricted/etd.pdf
`.948. |c5/11/2003
`.949. |wETD|mONLINE|lNET|tDISSERTN|zNCSUTHESIS
`
`Bibload report
`
`While MARCIMPORT prepares MARC or text data for use by the system, it takes a second report from the MARC Import group to actually load
`the data into the database. There are reports which do pretty much the same thing,
`bibload
` and
`. The latter is intended for far largerbibloadbatch
`
`batches in the range of several thousands.
`
` tab.
`
`1.
`2.
`3.
`
`4.
`5.
`
`6.
`7.
`
`8.
`9.
`10.
`11.
`
`12.
`
`13.
`
`14.
`
`Basic Information
`
` tab provide a Report name you will
`
`MARC Import
` wizard and, within that, the Schedule new report
`
`Select the
`Select
`Load Bibliographic Records
` and click the
` button.Schedule
`
`On the
`Schedule New Reports : Create bibload
` box you will find three tabs. On the
`remember when looking at the finished reports later on.
`On the
`Selection Criteria
` tab, first identify the file you imported above, specifying whether it was a MARC or FLAT (ASCII text) file.
`Under
`Title control processing
` select the appropriate sources for incoming flexkeys using the gadget to the right of the data entry window.
`For OCLC original records this will be OCLC number (001); for other records this could be ISBN (020), OCLC number (035), or another
`appropriate source.
`A
`Title control number matching rule
` table is provided below. Select the rule appropriate to the overlay/new record outcome you desire
`You may select to use
` under TODAY
`
` or you could set this to the previous month if you desire to prevent the file fromDate cataloged
`
`going to Marcive for authority processing and OCLC for holdings setting.
`Default record format can be set to anything, allowing MARC leader to set the format.
`Under
`Update title control information
` enter 948.
`.Remove junktags
`Under
` check
`Bibliographic record processing
` and Update bibliographic record
`
`
` to either create or
`Under
`Call number and copy processing
` leave
` set to Holdings entry preprocessing
`
`NONE
`. Set
`Copy processing
`update holdings. If you are loading new records with holdings information imbedded in 949, choose Create and update copies using
`holdings statement _and put the holdings tag (usually 949) in the _Entry ID
`
` window. Call number load rules
` are set in the format used for
`SmartPort (Class scheme, MARC tag, subfields, occurence).
`With
` you can set all records to load particular values for library, location, item type, and item categories according toDefault holding code
`
`the
`Holding code table
`.
`Once
`. If you are worried about causing
`Click on
`
` to schedule the load. For files of less than several hundred, go ahead and use Schedule
`other reports to queue up, you can schedule the load to occur after hours. Click on
`OK
` and the report is off and running.
`To check the status of your report, click on the
`Finished reports
` wizard. If your report is done it will show up on the list. If not you can click
`the middle icon at the upper left of the
`Finished report
`Display report scheduler status
`. Single click on your report name and
` box to
`choose
`View
` to see your report.
`
`Title control number matching rules
`
`Rule
`
`IF record new IF record match\ DATE CAT=NEVER IF record match\& DATE CAT=nn/nn/nnnn
`
`Page 2 of 4
`
`

`

`1
`
`2
`
`3
`
`4
`
`5
`
`Create
`
`Create
`
`Error
`
`Create
`
`Error
`
`Error
`
`Overlay
`
`Overlay
`
`Overlay
`
`Overlay
`
`Error
`
`Error
`
`Error
`
`Overlay
`
`Overlay
`
`External use of MARC 949 to generate holdings
`
`If you are cataloging a number of titles on OCLC or need to batch load records from a vendor like Marcive, NetLibrary, or Yankee Book Peddler, it
`may be faster to key holdings information into a MARC 949 field and then to use MARCIMPORT and the bibload report to create both title AND
`call/item records in Unicorn. This is the methodology that UNC-CH and Duke have used for all of their current DRA cataloging since 1993. It is
`also the method we currently use for batch loading GPO MARC record sets from Marcive, NetLibrary e-book titles, and large microform sets such
`as the Evans Collection.
`
`For loading into Unicorn, a 949 needs to be created for each call number record associated with a title. Thus, for each volume of a multi-volume
`set, for each additional library holding the title, and for each accompanying material type, a new 949 is created. The following table illustrates the
`subfields that map to various fields in the call number and item records in Unicorn.
`
`Subfield
`
`Contents
`
`Default
`
`a
`
`w
`
`v
`
`c
`
`d
`
`e
`
`f
`
`g
`
`h
`
`i
`
`j
`
`k
`
`l
`
`m
`
`n
`
`o
`
`p
`
`q
`
`r
`
`s
`
`t
`
`u
`
`x
`
`z
`
`Call number
`
`Class scheme
`
`Volume number
`
`Copy number
`
`Last activity
`
`Call # specified in load statement
`
`LC
`
`None
`
`1
`
`MM/DD/YYYY
`
`Date last charged
`
`MM/DD/YYYY
`
`Date inventoried
`
`MM/DD/YYYY
`
`Times inventoried
`
`Holding code
`In place of separate
`Library, Location, Item type
`
`0
`
`None
`
`Barcode
`
`Auto barcode
`
`Number of pieces
`
`0
`
`Current location
`
`Home location
`
`Home location
`
`Library
`
`Total charges
`
`None
`
`None
`
`0
`
`Item notes or comments
`
`None
`
`Price
`
`In-house charges
`
`Circulate flag
`
`Permanent flag
`
`Item type
`
`0
`
`0
`
`Yes
`
`Yes
`
`None
`
`Acquisitions date
`
`MM/DD/YYYY
`
`Item cat1
`
`Item cat2
`
`None
`
`None
`
`Note that while new volumes require a new 949, you can use a single 949 to create multiple copies with the same call number. Defaults in the
`table above refer to values automatically created when that subfield is not coded. Thus, leaving out the barcode subfield will cause an AUTO
`barcode to be generated. Leaving out the |w class scheme will result in a default to LC. Note also that one can use |h Holding codes in place of
`separate |m Library |t Location |l Item type |x Item cat1 |z Item cat2 combinations. Call number spacing here should be identical to what is used in
`manually created call records. A number of examples follow.
`
`949 B2430 .B344 C36 2003|iS01869427.|hHIL-STACKS
`949 PK2200 .A13 Z37 2000|c1|iS02251186P|mDHHILL|tBOOK|lSTACKS|xBOOK|c2|iS02261961R
`
`Page 3 of 4
`
`

`

`949 MF 875|wALPHANUM|tMICROFICHE|lMICROFORMS|xMICROFORM|mDHHILL
`
`949 TT685 .V35 2000|mTEXTILES|tVID-CASS|lMEDIA|xVIDEO
`949 TT685 .V35 2000 Brochures|mTEXTILES|tBOOK|lMEDIA|xBOOK
`
`949 |wEBOOK|hNCLIVENETL
`949 |wETD|mONLINE|tDISSERTN|lNET|xNCSUTHESIS
`
`External use of MARC 948 to generate time stamps
`
`Setting date stamps for DATE CREATED, DATE MODIFIED and DATE CATALOGED must be done in 948, much as call number information is
`set in 949. Format should be MM/DD/YYYY, as in WorkFlows.
`
`Subfield
`
`Contents
`
`Default
`
`a
`
`b
`
`c
`
`Date title created
`
`Date of load
`
`Date title modified
`
`Date of load
`
`Date title cataloged NEVER
`
`Page 4 of 4
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket