Use Macros

Basics: Use Macros

Judy Barnes
Last revised 2008

Introduction to OCLC Macro Language for Connexion client

Macros are short programs you write to automate routine tasks. Macros are built from commands. Each command does one step in the procedure you want to run automatically. Creating and using macros is optional and requires some understanding of BASIC programming language. The client supports macros written using OCLC Macro Language (OML), which provides:

• Standard BASIC functions and statements
• Macro commands developed specifically for the client

Why use macros?

Using macros can help to:

• Reduce the number of keystrokes and mouse clicks by running repetitive processing steps automatically
• Standardize procedures to reduce errors and inconsistencies
• Decrease staff time required for routine tasks

OCLC-supplied object class and variables

• OCLC supplies the object class Connex.Client. Commands in OML macros automate Connexion client actions by accessing a subset of client functionality through this object class, which is the interface between the client functionality and OML.
• To gain access to the functions provided by Connex.Client, an OML macro contains two lines that do the following:
  • Define the object variable CS by which to reference Connex.Client:
    Dim CS as Object.
  • Set CS to reference an instance of the object class Connex.Client:
    Set CS = CreateObject("Connex.Client").

Why use an object?

The only way to create a macro that automates Connexion client operations is to use the variable CS as an instance of the class Connex.Client. You can then use the capabilities of that class of object to make the macro work. By using the appropriate object, you can, for example, write a macro to log on to Connexion, automate a search, modify a record, display a record from a list, or take an action on a record.

How to use a client object

The tasks an object can do are called methods or member functions of the object. OML Help uses the term commands for the methods of the client object class.

For a list of commands for use in client macros, see "List of Connexion client macro commands."

Syntax for client macro commands

• Command syntax links client commands to the Connex.Client object.
• At the beginning of a macro, define the object variable CS to represent the object.
• For each macro command, add the prefix CS. to the command name to reference the required object through its predefined object variable, CS.
  Example:

  dim CS as Object

  set CS = CreateObject("Connex.Client")

  CS.WindowCount
  (Returns the number of open record and list windows)
• At the beginning of a macro, name and declare data types for variables to represent the values you supply as arguments (for example, line numbers and text strings) for carrying out the commands.
  Example:

  dim CS as Object

  dim sData as String

  dim n as integer

  set CS = CreateObject("Connex.Client")
  (Sets sData as a string of characters and n as an integer)

Return values from client macro commands

• Many client macro commands are functions that return a value of TRUE (if the command executes successfully) or FALSE (if the command fails).
• For these commands to work correctly, you must assign a variable to store the return values. As each command executes, the stored value is updated.
• Optional. You can include If . . Then . . Else statements or other code that checks the value of this variable and, based on the result, displays messages or branches to different sections of the macro.

  If...Then...Else executes alternative blocks of program code based on one or more expressions.
  

  Syntax A

  If condition Then then_statement [Else else_statement]
  [bracketed parameter is optional]
  

  Syntax B (block version)

  If condition Then

  statement_block

  [ElseIf expression Then

  statement_block]

  [Else

  statement_block]

  End If

  Where:

  -condition is any expression that evaluates to TRUE (non-zero) or FALSE (zero)

  -then_statement is any valid single expression

  -else_statement is any valid single expression

  -expression is any expression that evaluates to TRUE (non-zero) or FALSE (zero)

  -statement_block is 0 or more valid expressions, separated by colons (:) or entered on separate lines

  Note: When multiple statements are required in either the Then or Else clauses, use the block version (Syntax B) of the If statement.

• Use the following syntax to specify the variable BOOL to store the return value of each command:
  BOOL = CS.[command]

Note: Standard OML commands do not use the CS. prefix.

OCLC-supplied macros

OCLC supplies several widely used macros:

• FourFig and Sanborn in a macro book file named Dewey.mbk for adding a Cutter number to a Dewey classification number. See instructions for using the Cutter macro in Cataloging, Print Labels and Accessions Lists, "Print labels."
• GenerateAuthorityRecord named OCLC.mbk for generating an authority record from a name heading in a bibliograhic record. You can run the macros from Tools > Macros > Manage.

OCLC provides additional macros. The following table lists all OCLC-supplied macros supplied in OCLC.mbk, describes the purpose of each, and gives details for using them:

OCLC may supply additional macros or modify existing macros in the OCLC.mbk book file in future versions of the client.

Caution for retaining your own macros when upgrading to the next client version:

• When OCLC adds or modifies macros in Dewey.mbk and/or OCLC.mbk, these files are overwritten when you upgrade to a new version of the client.
• You will lose your customized macros if you store them in either of these files when you upgrade. Copy any of your own macros to another macro book that you create or rename the macro book before upgrading to prevent this loss.

OCLC macro book files and macro book files you create are stored in X:\Program Files\OCLC\Connexion\Program\Macros (X = the letter of your hard drive). See more about user file locations in Getting Started with OCLC Connexion Client.

To view the OCLC macros:

Help for using client macros

Caution for Windows Vista users:

• Older Help files (*.hlp) linked from the main Connexion client Help file (*.chm) are unavailable under Windows Vista unless you download the discontinued Help engine WinHlp32.exe from the Microsoft Web site at:
  
  http://go.microsoft.com/fwlink?LinkID=82148 http://support.microsoft.com/kb/917607.
• Only the Standard BASIC guide and Macro Editor and Debugger Help topics are affected. These topics are in two help files, osbl5x.hlp and osbi5x.hlp.
• Client macro command-specific Help is in the main help file (clienthelp.chm) and is not affected .
• For complete information, see Windows Help program (WinHlp32.exe) is no longer included with Windows [Vista] on the Microsoft Web site at:
  
  http://support.microsoft.com/kb/917607.

The client provides separate but interlinked Help systems that cover macros

• OML and Basics Help (osbl5x.hlp)
• Macro Editor and Debugger Help (osbi5x.hlp)
• Client-specific macro commands in the main client Help (clienthelp.chm)
• The Help files are located in D:\Program Files\OCLC\Connexion\Program.

To open OML Help on standard BASIC:

• Click the Client Help button in any client Help topic on macros. Then, in the OCLC Macro Language Help window, click the link OML Standard BASIC Reference.
  Or
  In the Macro Editor and Debugger Help window, click , and then click the link BASICS.
  Or
  In the text of a macro in the Macro Editor, right-click any BASIC language keyword (such as sub) to open a topic describing the keyword.
  
  OML Help provides information on:
  • Syntax, usage tips, and examples for standard OML statements and functions
  • Overview topics that describe how to use features in OML
  • Program examples that illustrate OML functions and statements

To open the Macro Editor and Debugger Help:

• On the toolbar in the Macro Editor and Debugger window, click .
  
  Note: You open the Macro Editor and Debugger when you create or edit macros.

To open Connexion Client Help topics on using client-specific macros:

• On the Help menu, click Client Help, or click , or press <F1>. In the Help Contents tab, expand Basics/Use Macros.

Reference table: For diacritics and special characters in data used with macro commands such as CS.GetField or CS.SetField, see a list of codes, "ASCII and hexadecimal codes for diacritics and special characters."

Use Connexion client macros

Client macro tools

The client provides the following tools for working with macros:

Notes for Windows Vista users:

• Macro (*.mbk) files. See information on the location of Connexion client macro files with Windows Vista.
• Macro Help files. Older (legacy) Help files (*.hlp) for the Standard BASIC guide and Macro Editor and Debugger Help that are linked from the main Connexion client Help file (*.chm) are unavailable under Windows Vista. To use these Help files, you must download the discontinued WinHlp32.exe Help engine from the Microsoft Web site at: http://go.microsoft.com/fwlink?LinkID=82148. For more information, see Windows Help program (WinHlp32.exe) is no longer included with Windows [Vista] at: http://support.microsoft.com/kb/917607. See also Basics, Get Help and Information, "Use client Help" for more details.

How to create macros

There are two ways to create macros for the client. You can:

• Write your own macros in the macro editor, or copy and paste from an existing macro to a new one and then edit the new macro as needed (see "Write macros" immediately following).
  Or
• Record macros automatically using the macro recorder: You start the recorder, do a series of actions in a procedure you want to automate (using the mouse or the keyboard), and the recorder writes a macro that captures the procedure. See section titled "Record macros (create automatically)" below.

Note: See a list of client commands that are not available for use in macros you write or record below. The following commands are available for use in macros you write but cannot be recorded: View the next or previous 100 records from a list (View > Previous 100 Records or Next 100 Records).

Write macros

	Action
1	On the Tools menu click Macros > Manage, or press <Ctrl><Alt><Shift><G>.
2	In the Macro window under the Macros list, select the macro book in which you want to create the new macro. You must use macro books to contain macros. Or Create a new macro book in which to store the new macro: In the Macro window box, click New Book. Type a descriptive name over the highlighted default name New Book. Press <Enter>. You can also use the macro organizer to create a new macro book.
3	Click New Macro.
4	In the Macro Description window, type a unique description of the macro's purpose. Then click OK or press <Enter>.
5	In the text box with NewMacro highlighted, type an appropriate name for the new macro. Press <Enter>.
6	Click Edit. The OCLC Connexion Macro Editor and Debugger opens. Its title bar gives the names of the macro book and macro. In the work area, the start and end text of a macro are provided: MacroName:[name you typed] 'MacroDescription:[description you typed] Sub Main() End Sub
7	Between Sub Main and End Sub, type commands and appropriate comments to create the macro. To create a specific instance of the client object class, macros that use client commands must begin with the lines: Dim CS as Object Set CS = CreateObject("Connex.Client") In macros that use variables (numbers, strings), include lines to declare the data type of each variable to be used in the macro. Example: The first part of a macro using the GetField command declares the variable sData as a string to store the text of the specified field: Dim CS as Object Dim sData as String Set CS = CreateObject("Connex.Client")
8	Press <Enter> at the end of each line. Make sure End Sub remains as the last line of the macro.
9	On the Macro Editor toolbar, click (Check) to check macro syntax. (See the "Check macro syntax" section below for details.)
10	Click (Execute), (Animate), (Step Into), and (Run to Cursor) to test and debug the macro. For more information, open the OML Macro Editor Help: Click (Help) on the Macro Editor toolbar.
11	Click (Save).
12	When finished editing, on the File menu click Exit, or press <Ctrl><F4>. See a detailed macro example below.

Tips for using the Macro Editor

• Description. Provide an informative description for each macro you create.
• Comments. Include comments in the macro to document what each part of the macro does. Comment lines begin with a single quotation mark (').
  Example:
  ' Get the first item from the first list

  If CS.Search("WC", "gon,wi,th,w") > 0 Then

  CS.CloseList

  End If
• Open and work with multiple macros:
  • To open another Connexion client macro, with the Macro Editor open:
    
    On the client Tools menu, click Macros. The Macros window reopens. Select another macro in the list or create a new one and select it, and then click Edit. The macro opens in a separate window.
  • To help navigate among multiple open macros in the Editor:
    
    On the Macro Editor Window menu, click Cascade or Tile, or make a different macro window current (bring it to the top and set focus) by selecting its name in the windows list.
• Help for BASIC keywords. To get a specific Help topic on any BASIC language keyword (such as sub) in a macro in the Editor, right-click the keyword in the macro text.
  
  Reference table: For diacritics and special characters in data used with macro commands such as CS.GetField or CS.SetField, see a list, "ASCII and hexadecimal codes for diacritics and special characters" in "Connexion client macro commands: Edit records."

View or edit macros

Check macro syntax

When you create or edit a macro, you must check the macro syntax (click the

Check button on the toolbar. The Macro Editor displays a message on the status bar of the Editor window.

• If the macro contains no syntax errors, the message is: Successfully compiled [macrobook]![macroname].sbl
• If the macro contains syntax errors, the message is: _Error(s) in [macrobook]![macroname].sbl. Lines containing syntax errors are highlighted in red.

To review errors:

Action
On the Macro Editor toolbar, click the Next Error button and Previous Error button to move between error lines in the macro.

To view details of syntax errors:

	Action
1	On the Macro Editor toolbar, click the Console button . A new window opens at the bottom of the Editor window, just above the gray message bar. The window displays output from the syntax checker.
2	Drag the separator up to expand the console window. Maximize the Editor window to provide more space if needed.
3	On the Macro Editor toolbar, click the Check button again. In the console window, the Editor displays messages that give the line number containing each syntax error (in parentheses following the macro name) and identify the general type of error.

Macro example

Sub Main()

End Sub

This example:

• Logs on to Connexion if not already logged on, using the default authorization and password you selected in Tools > Options > Authorizations tab (leaves logon values blank).
• Searches WorldCat for record number 1.
• Adds a new field 300 in the tenth line of the record (inserted as the tenth variable field) with no indicators (two spaces between the tag number 300 and the text of the field). Adds the text Line 10 test to the field. (No confirmation message.)
• Adds a second instance of repeatable field 500 (that is, adds a new field 500 below the first existing field 500) with no indicators and the text Another test. If the action is successful, returns the confirmation message 500 field successfully added.

See a complete list of client commands in "List of Connexion client macro commands." See detailed descriptions and examples for each command in sections organized by function.

Include macros in another macro

Including macros in a macro lets you:

• Reuse macros you developed and tested as building blocks for more complex macros
• Insert standardized elements in multiple macros (for example, declarations of variables, frequently used subroutines, or a function library)
• Avoid the errors and repetitive debugging that result from recreating existing code

You can:

• Run a macro from another macro:
  • The RunMacro command executes a specified macro from within another macro. When the called macro finishes running, execution of the calling macro resumes with the next statement
  • Syntax:BOOL = CS.RunMacro("macrobook!macroname")
    Tip: For faster execution, locate macro(s) you run using the RunMacro command in the same macro book that contains the calling macro(s).

    Limitation:RunMacro does not include code from the specified macro in the compile process. The called macro is treated as an external "black box."
• Include code from another macro in compile:
  • The $Include metacommand tells the OML compiler to merge code from another macro at compile time. Included code becomes part of the macro that contains the $Include command. Functions, subroutines, and variables in the included code become available for use at any time during the main macro's execution.
  • Syntax:'$Include: "macrobook!macroname"
  • Correct OML syntax: The topic describing $Include in OML Standard Basic Language Reference Help gives the syntax for including a file by specifying path (drive and folder) and file name. This syntax does not work in client macros. You must specify the macro to include as "macrobook!macroname".
    Tip: Place the $Include metacommand before the main procedure (Sub Main() ... End Sub) of the macro if the code to be included contains global components such as declared variables, functions, or subroutines.

Run macros

Stop macros

Delete macros

Organize macros and macro books

• You create macros only within a macro book. Macro book files use the extension *.mbk.

Caution: OCLC-supplied macro books may be overwritten at upgrade

Do not store customized macros in OCLC-supplied macro books

OCLC-supplied macro book files OCLC.mbk and Dewey.mbk may be overwritten when you upgrade the software to provide you with the most currently available OCLC macros.

If you store customized macros in either of these books, you must rename the existing macro book before upgrading to be sure that the installation does not overwrite it and cause you to lose your own macros.

OCLC recommends that you: Create different macro book file(s) to store macros you create, copy, or record.

Actions not available for macros

You cannot use the following actions in macros you write or record:

• Attach digital files to WorldCat records (Edit menu) (available only to those who have an OCLC logon authorization that includes CONTENTdm, a license to use CONTENTdm, and an established CONTENTdm collection and who use the CONTENTdm hosting service)
• Authorities history records searching and browsing (Authorities > Search menu) and showing distributed vs. superseded versions (Authorities > Show menu)
• Batch set or delete holdings by OCLC number (Batch menu)
• Cancel the last edit in a record (Edit > Undo)
• Check spelling (Tools menu)
• Control a single heading in a record (Edit > Control Headings > Single)
• Convert characters to MARC-8 CJK (Edit > MARC-8 Characters menu)
• Copy data as text (Edit > Copy as Text)
• Copy the OCLC control number by selecting it manually and copying (to record, you must use the Copy Control Number command on the Edit menu)
• Create constant data (Cataloging > Create > Constant Data)
• Create records for electronic resources by extracting metadata (Cataloging > Create > Extract Metadata)
• Customize the toolbar (Tools > Toolbar Editor)
• Delete selected text
• Derive a new constant data record (Edit > Derive > New Constant Data)
• Edit or create 006, 541, or 583 fields using guided entry (Edit > Guided Entry > Edit [or Insert 006, 541, 583)
  
  Note: Existing macro commands can be used, such as SetFieldLine to insert a field and specify data.
• Import records (File > Import Records)
• Insert field 760 - 787 data automatically from a cited record (Edit > Insert from Cited Record)
• Launch local holdings maintenance (Tools menu)
• Launch WebDewey (Cataloging menu)
• Link/unlink non-Latin script fields with equivalent Latin script fields (Edit > Linking Fields)
• Lock linked authority record (Action menu)
• Move the cursor from one record area to another (Edit > Previous Record Area or Next Record Area)
• Open the CJK E-Dictionary (Tools menu)
• Paste Unformatted (Edit menu)
• Print accessions lists (File menu)
• Set a constant data record as the default (Edit > Constant Data > Online > Set as Default)
• Set options in Tools > Options
  
  Note: You can, however, assign keystroke shortcuts to run macros, either by writing a macro using the command AssignMacroToKey or recording a macro while you assign a keystroke from Tools > Keymaps.
• Show default constant data (Cataloging > Show > Default Constant Data; same command on the Authorities menu)
• Show numbers of online save file records by individual statuses (Cataloging > Show > By Online Save File Status; same command on the Authorities menu)
• Transliterate Arabic or Persian (Edit menu)
• Use assigned User Tools (Tools menu)
• Use text strings (Tools menu)
• Verify MARC-8 characters (Edit menu)

Note: You can use the following commands in macros you write, but you cannot record them:

• GetNext100Records (View menu)
• GetPrevious100Records (View menu

Record macros (create automatically)

Record a macro

The client provides a macro recorder that records the actions in a procedure as you do them, whether you use the mouse to click commands or toolbar buttons, or press shortcut keystrokes, or use a combination of mouse and keyboard.

The recorder writes the macro automatically in the OML macro recorder.

To record a macro:

	Action
1	On the Tools menu, click Manage, or press <Ctrl><Alt><Shift><G>.
2	In the Macro window, click the name of the macro book where you want to store the new macro and then click Record.
3	In the Record a New Macro window, enter a unique name and description for the macro. The description displays in: The Description box of the Macro window, when you select the name of the macro, to help you remember what the macro does At the top of the macro text when you open the macro in the macro editor
4	Click OK to start recording, or click Cancel to close the window without startingrecording. Result if you click OK: The client displays a macro recording toolbar under the client toolbar: . The toolbar contains buttons for (left to right): Pause Recording, Resume Recording, and Stop Recording. These commands are also available as commands under Tools > Macros.
5	Carry out the procedure(s) you want to capture in a macro. The client records all actions except those listed in "Non-recordable actions" below.
6	Optional: To pause and then resume recording the current new macro: On the Tools menu, click Macros > Pause Recording. Or On the macro recording toolbar, click . Or Press <Alt><T><M><P>. To resume recording the same macro at the point where you paused: On the Tools menu, click Macros > Resume Recording. Or On the macro recording toolbar, click . Or Press <Alt><T><M><E>.
7	When you are finished, to stop recording and end the macro: On the Tools menu, click Macros > Stop Recording Or On the macro recording toolbar, click . Or Press <Alt><T><M><R>. Results: The macro is saved automatically. You can open the macro to check or edit it. In the Macro window (Tools > Options > Macros > Manage), click the name of the macro you recorded, and then click Edit. The macro opens in the Macro Editor. The macro recording toolbar closes. Note: If you exit the client before you stop recording a macro, the program stops recording for you. You may want to check the macro later for completeness.
8	To view, check, or edit the macro, see "View or edit macros" and other sections about checking and editing macros in the topic, "Use Connexion client macros."

Tips for using the macro recorder

• To copy from field 245, use Find/Replace to find field 245. Then close the box to locate the cursor in field 245.
• You cannot record manually selecting and copying the OCLC number in a record. You must use Edit > Copy Control Number.
• When recording taking an action on a bibliographic record, the macro recorder does not record replacing text by manually selecting and overwriting the text.

List of Connexion client macro commands

See:

• Commands listed by function
• Commands listed in alphabetical order

List of client macro commands by function

See also "ASCII and hexadecimal codes for diacritics and special characters."

Note on macros and non-Latin script data: You can incorporate Unicode character data into macros using GetFieldUnicode and GetFieldLineUnicode. The Unicode characters are converted to Numeric Character Reference (NCR) form.

Note: See more about bibliographic institution records in Cataloging, Bibliographic Institution Records.

Alphabetical list of macro commands

Connexion client macro commands: Log on and off

Logon

Logoff

IsOnline

Connexion client macro commands: Search

Search

Search guidelines, indexes, examples

WorldCat searches (database identifier WC)

The search string for the Search macro command should follow the same format for a keyword/numeric or derived search that you would enter in the Command Line Search of the Search WorldCat window, except:

Guidelines:

• Omit the Find command (fin) from a derived or keyword search.
• Include index labels in a keyword search.
• When you use index labels, include the following punctuation:
  • Colon (:) for single words
  • Equal sign (=) for phrases and whole phrases
  • Enclose whole phrases in a double set of quotation marks ("" "")
  • Do not use spaces before or after the punctuation
• Index labels are optional for a derived search if it is the first or only search; if you combine searches, index labels are required.
• Enter an OCLC Control Number search with the index label (no:) or precede the number with an asterisk (*) or number sign (#).
• If you include qualifiers, begin each qualifier with a slash or an index label followed by a colon (:).
  
  Use slashes or index labels with the following four types of qualifiers: type of material, years, microform, or source (/dlc).
  
  Use index labels only to qualify a search by Internet/non-Internet or a language.
• For slash qualifiers, you can include only one qualifier of each type and the qualifiers must be in the last position of the search statement.
• Combine searches using Boolean operators (and, or, not).
• In a keyword search, you can specify proximity and order of terms with proximity operators with (w) or near (n).
• To expand a term in a keyword or numeric search, replace characters or endings with symbols for wildcards (# or ?), truncation (*), and plural stemming (+). See Use wildcards, truncation, and plural stemming in searches for details.
  
  Caution: Wildcard and truncation symbols must be preceded by at least three characters.

For more information and for lists of selected indexes and examples, see Cataloging, Search WorldCat, "Search WorldCat interactively."

See Searching WorldCat Indexes at < http://www.oclc.org/support/documentation/worldcat/searching/searchworldcatindexes > for comprehensive descriptions of indexes, guidelines, and examples.

Online bibliographic save file searches (database identifier BS)

Guidelines:

• Enter an index label (see list below), a colon, and then the search term.
• You can combine searches using Boolean operators. To distinguish the words and, or, or not when they are part of your search term (not used as Boolean operators), you must enclose in single quotation marks (').
  Example:
  "ti:red 'and' the black"
• The search is not case-sensitive: you can enter the search string in upper- or lowercase.
• To retrieve all records in the save file, leave the search string parameter empty: CS.Search "BS", "".

Indexes and labels:

Note: If you record rather than write a macro, statuses are recorded with no spaces between words. When you write macros, you can retain the spaces. Values you enter are not case-sensitive.

Online bibliographic constant data searches (database identifier BD)

Search examples:

Indexes and labels:

• Constant Data Name (nm) (default)
• My Status (ms)

Local bibliographic save file searches (database identifier BL)

Follow the same guidelines as for online bibliographic save file searches (except use the database identifier BL).

Indexes and labels:

Note: If you record rather than write a macro, statuses are recorded with no spaces between words. When you write macros, you can retain the spaces. Values you enter are not case-sensitive.

Local bibliographic constant data searches (database identifier BC)

See examples for online bibliographic constant data searches (except use the database idenfifier BC).

Indexes and labels:

• Constant data name (nm:) (default)
• My Status (ms:)

Online bibliographic review records (database identifier BR)

Use to find bibliographic records sent to your library for review by another library you specify by institution symbol. (Same as selecting Review File Records for Institution check box and entering institution symbol in the Search Online Bibliographic Save File window via Cataloging > Search > Online Save File).

Index and label:

Authority File searches (database identifier AF)

Guidelines:

• Enter an index label (see list below), a colon, and then the search term.
  Example:
  CS.Search "AF", "pn:mitchell"
• You can combine searches using Boolean operators. To distinguish the words and, or, or not when they are part of your search term, you must enclose them in single quotation marks (').
  Example:
  CS.Search "AF", "ti:war 'and' peace"
• The search is not case-sensitive: you can enter the search string in upper- or lowercase.

Indexes and labels:

Online authority save file searches (database identifier AS)

Guidelines:

• Enter an index label (see list below), a colon, and then the search term.
• You can combine searches using Boolean operators. To distinguish the words and, or,or not when they are part of your search term (not used as Boolean operators), you must enclose in single quotation marks.
  Example:
  CS.Search "AS", "ti:red 'and' the black"
• The search is not case-sensitive: you can enter the search string in upper- or lowercase.
• To retrieve all records in the save file, leave the search string parameter empty: CS.Search "AS", "".

Indexes and labels:

Note: If you record rather than write a macro, statuses are recorded with no spaces between words. When you write macros, you can retain the spaces. Values you enter are not case-sensitive.

Online authority constant data searches (database identifier AD)

Search examples:

Index and label:

Local authority save file (database identifier AL)

Follow the same guidelines as for online authority save file searches (except use the database identifier AL).

Note: If you record rather than write a macro, statuses are recorded with no spaces between words. When you write macros, you can retain the spaces. Values you enter are not case-sensitive.

Local authority constant data searches (database identifier AC)

See examples of online authority constant data searches (except use the database identifier AC).

Indexes and labels:

• Constant data (nm:) (default)
• My Status (ms:)

Online authority review records (database identifier AR)

Use to find authority records sent to your library for review by another library you specify by institution symbol. (Same as selecting Review File Records for Institution check box and entering institution symbol in the Search Online Authority Save File window via Authorities > Search > Online Save File).

Index and label:

• Records sent for review (sm:).
  Enter a valid institution symbol (in uppercase) for a library whose records you want to retrieve for review.
  Example:
  num = CS.Search("AR", "sm:OCL")
  MsgBox("Found " & num & "records")

Chinese name authority file searches (database indicator CN)

Search for Chinese name authority records using Latin script search terms only. You cannot use non-Latin scripts with macros. Access to the records is read-only.

Indexes and labels:

Hand Press Book database searches (database indicator HP)

Hand Press Book (HPB) is available by contract with OCLC to members of the Consortium of European Research Libraries (CERL).

For indexes and labels, in the client, open the client Help, click the Index tab, enter keyword Hand Press Book and double-click search indexes for the HPB database to see a list of Hand Press Book-specific indexes and a list of standard WorldCat indexes that can also be used for Hand Press Book searches.

Online Hand Press Book save file searches (database indicator HO)

Hand Press Book is available by contract with OCLC to members of the Consortium of European Research Libraries (CERL).

Indexes and labels:

Note: If you record rather than write a macro, statuses are recorded with no spaces between words. When you write macros, you can retain the spaces. Values you enter are not case-sensitive.

Local Hand Press Book save file searches (database indicator HL)

Hand Press Book is available by contract with OCLC to members of the Consortium of European Research Libraries (CERL).

Indexes and labels:

Note: If you record rather than write a macro, statuses are recorded with no spaces between words. When you write macros, you can retain the spaces. Values you enter are not case-sensitive.

Browse