In general, there are two basic tasks to be performed: 1. Creation of a shared folder on a server, containing the files described below 2. Modification of each user's marcreport.ini file to refer to the folder created in step #1

IMPORTANT NOTE The first time each user runs MARC Report, a file called marcreport.ini is created and written to their My Documents folder. This file tracks all of the checkbox changes made in the Program Options. The program's options are not initialized until the first time the user runs the program. Therefore, any customizations made to marcreport.ini depend upon the program having been previously started at least once.

The top of the marcreport.ini (located in the user's My Documents\MarcReport folder) file looks like this:

[Files and Directories] ROOTDIR=c:\program files\tmq\marc report\ OPTIONSPATH=c:\program files\tmq\marc report\options\ OPTIONSPATH2=c:\program files\tmq\marc report\options\

The second options path, 'OPTIONSPATH2', which defaults to the same location as the main options path ('OPTIONSPATH'), determines where the program will look for the following 'set' files:

Cataloging Check sets Mandatory Field Sets Local Subject sets Cancelled Messages sets Local Validation sets

After installation and initialization, you may change OPTIONSPATH2 to another folder that will contain the customized set files that you want centrally controlled and shared. For example

OPTIONSPATH2=Z:\my shared sets\

Be sure to terminate the folder name with a trailing backslash. Also, for best results, use a mapped drive ( Z:\serverpath\ )instead of a UNC path ( \\servername\serverpath\ ). If mutliple users are going to use these set files, then the folder in question should be read-only. The user will be able to select any sets in the folder, however they will not be able to make changes to them. Any attempts to make changes to the sets, including cancelling messages, will generate an informative error message.

The program installs a 'default' template in the Options folder for each of the above sets; if OPTIONSPATH2 is set to a non-default value, then the following files must be copied to the OPTIONSPATH2:

default.ccs		// cataloging checks
default.mnd		// mandatory fields
default.lsb		// local subjects
default.can		// cancelled messages
default.lvt		// local validation

The presence of these default files is required for the program to operate correctly (even tho the user will not be able to change them).

There is one exception to the above. Local validation uses two compiled files at runtime, instead of the set deposited in the Options folder. These compiled local validation files are generated whenever the Options are saved, and they are written to the program installation folder, by default:

c:\program files\tmq\marc report\

The two files required for local validation support are: valdata.usr – validation data msgs_usr.tmq – user messages

Both of these files must be copied to the shared folder specified in OPTIONSPATH2. If these local validation files are present in the shared folder, they will override any copies in the user's program folder. Also, local validation will work without the second file (msgs_usr.tmq); however, any custom notes which were defined will not display (a generic note will appear instead).


If the user should open the program options and save them, this action will generate new copies of the local validation files in the user's program folder (which may be exactly the same as those in the shared folder). Again, if these local validation files are present in the shared folder, they will override any copies in the user's program folder.

If changes are made to the local validation table by the head cataloger, the options should be saved, and new copies of these two files copied from the head cataloger's installation folder to OPTIONSPATH2.


If it is necessary to limit the changes that an individual user can make to their options, an overlay of the user's marcreport.ini file by another version of this file in OPTIONSPATH2 is possible.

If OPTIONSPATH2 is set to a non-default value, and if a file called marcreport.ini is present in OPTIONSPATH2, then the OPTIONSPATH2 settings in marcreport.ini will have precedence, regardless of the user's own settings. Whenever the program reads the options (when it starts up, and whenever the Options are selected from the main menu), the user's marcreport.ini is read first (from their My Documents folder), and then the marcreport.ini from OPTIONSPATH2 is read. Any values in the latter thus overlay the corresponding values from the former.

IMPORTANT: marcreport.ini contains some settings that are relevant only to a user's system, and which could potentially cause bizarre behavior if changed. Because of this, only two sections of marcreport.ini should be used when customizing this file: [Cataloging Checks] and [Validation]. These two sections contain all of the settings needed to centrally manage cataloging activity.

The option name, default value, and brief description follows for each option in the two sections mentioned above. Please note that the option name must be given _exactly_ as it is below (in uppercase), followed by an equal sign (no spaces), followed by the option value. Set names must include the file extension, but exclude the path name (which will be taken from OPTIONSPATH2).

[Cataloging Checks]
ENABLECATCHECKS=Y	// a master switch for disabling all cataloging checks
CHECKCOMMONPROBS=Y	// a switch for disabling all checks performed by the cataloging check set
CHECKFILINGINDS=Y	// a switch for disabling all checks for filing indicator problems
RUNISBDPUNCCHECK=Y	// a switch for disabling all ISBD punctuation checks
CHECKENDPUNC=Y		// a switch for disabling all end-of-field punctuation checks
CHECKENDBLANKS=N	// a switch for disabling all checks for blank spaces at the end-of-field
LOADMAND=Y		// a switch for disabling the user of the Mandatory Fields table
LOCALSUBJECTS=Y		// a switch for disabling the use of the Local Subjects table
CATCHECKNAME=default.ccs	// the name of the cataloging check set to be used
MANDATORYNAME=my mad mands.mnd	// the name of the mandatory fields set to be used
SUBJECTSFNAME=my local subs.lsb	// the name of the local subjects set to be used
CHECKFICTION=Y		// whether fiction records should be considered when running the local subjects checks
CHECKNONPRINT=Y		// whether non-print records should be considered when running the local subjects checks
CHECKUTF8=N		// whether the program will assume all records are UTF-8 encoded
CHECKLEADER09=Y		// whether the program will consult Leader/09 to determine whether a record is UTF-8 encoded
CANCELNAME=my cancels.can	// the name of the cancelled message set to be used
RESTRICTCANCELS=Y	// whether the program should block attempts to cancel serious errors (eg. empty fields)
REPORTCHECKDIGIT=N	// whether the ISBN-13 check digit value should be reported in brief messages.
ALLOWLOCALCANCELS=Y	// whether the user will be allowed to use the cancelled message feature
LOCALDATANAME=my local vals.lvt	// the name of the local validation set to be used
LOADLOC=Y		// whether the DLC bibliographic format validation table should be loaded
LOADOCL=Y		// whether the OCLC validation extensions should be loaded 
LOADAUT=Y		// whether the DLC authority format validation table should be loaded
LOADCIF=N		// whether the DLC community information format validation table should be loaded
LOADHLD=N		// whether the DLC holdings format validation table should be loaded
LOADUSR=N		// a switch for disabling the Local Validation table
FILTERRULE=Y		// whether the switches that follow should be applied to Validation as well as to Cataloging Checks
IGNORECTRLCHARS=N	// whether unusual characters at the end of the leader should be considered errors
IGNORE09XTAGS=N		// whether 09X tags should be ignored
IGNORE59XTAGS=N		// whether 59X tags should be ignored
IGNORE69XTAGS=N		// whether 69X tags should be ignored
IGNOREXX9TAGS=N		// whether tags that end in '9' should be ignored
IGNOREX9XTAGS=Y		// whether tags with a middle digit of '9' should be ignored
IGNORE9XXTAGS=Y		// whether tags that begin with '9' should be ignored
IGNORESUBF9=Y		// whether subfield $9 should be ignored
IGNORELOCALHOLDINGS=Y	// whether tags 049 and 852 should be ignored
IGNOREOBS=N		// whether messages about obsolete coding should be ignored during validation
IGNOREOLD=N		// whether messages about 'old coding' (OCLC) should be ignored during validation


If the user changes one of the options above, and the overlay feature is being used, that change will be silently ignored.

The program's cancelled messages feature contains options that allow cataloging messages to be cancelled using an in-memory table, circumventing a shared cancelled message set, if defined. The end-effect is that the user may cancel any additional cataloging messages they want. If this is not desirable, then the [Cataloging Checks] section option called 'ALLOWLOCALCANCELS' should be changed from 'Y' to 'N'. If this option is set to 'Y', the default, then the user will be able to cancel cataloging messages during a validation session, even those these cancellations will be discarded once the program is closed.

In a nutshell: set up a shared folder on the server, copy the 5 default sets, and your customized sets, to the shared folder, and change the OPTIONSPATH2 parameter in your marcreport.ini (the one mentioned above) to point to the shared folder; then copy your marcreport.ini to the shared folder, and delete all sections from it but [Cataloging Checks] and [Validation]. Test that it works. Try changing some parameters in the marcreport.ini on the shared folder, and see if they kick in when you run the program.

phelp/helpsharedsets.txt · Last modified: 2018/12/20 11:29 (external edit)
Back to top
CC Attribution-Noncommercial-Share Alike 3.0 Unported
Driven by DokuWiki Recent changes RSS feed