14 SETUP (CLIENT)

For cataloging can be made adjustments without changing the generation of data base. The following files are for order.

Files on server../etc/client/pc_XXX.pck (XXX stands for master file. If you change this field, you have to change the date in the first line of the file, so that the Catalog Tab will be reloaded.

files on the Client: ../catalog/tab/catalog.ini

Server codes.<lng> Editable fields (15.0)
Server formats.<lng> Material Types (14.2)
Server <nnn>_<xx>.<lng> Forms for for particular fields (14.3)
Server <Name>.mrc Templates (14.4)
Server marc_exp.dat Which Sub-fields Should Open (14.5)
Server Help Help on Field (14.6)
Server scancode.dat Search Headings (14.7)
Server tag_text.dat Tables (14.8)
Server tagonnew.dat Default Values for "New Record" (14.9)
Client [DuplicateRecord] Duplicate Record(15.00)
Client [Package] Import tables (15.01)
Client Colours Colours (15.02)

15.0 EDITABLE FIELDS

The codes.lng file defines the valid category number and field name This list can be displayed in the catalog mudule by using the shortcut key F5. The Client can be set to display only the category number or the category number and the library deposited description (z.B. 331-Title proper or 245-Title proper). The option to display the field name is initialised

You can determine which fields can be edited by the cataloger. Other options can be determined: e.g. Field name

Following is an example from the table:

PKC_FILE_BEGIN codes.ger
!1  2 3 4 5 6        7        8       9
!!!-!-!-!-!-!-!!!!!!!!!!!!!!!-!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

LDR   N Y Y L Leader          L Leader
001   Y Y Y L Control No.     L Control Number
002   N Y Y L Entry date      L Original date of entry / Takeover of external data
003   Y N Y L Control No. ID  L Control Number Identifier
005   Y N Y L Date and Time   L Date and Time of Last Transaction
006   Y Y Y L Mater. charac.  L Material characteristics
007   Y Y Y L Phys. Descrip.  L Physical Description Fixed Field
008   Y Y Y L Fixed Data      L Fixed Length Data Elements
010   Y N N L LoC Control No. L Library of Congress Control Number
013   Y N N L Patent Inform.  L Patent Control Information
015   Y N N L Nat.Bib. No.    L National Bibliography Number
016   Y N N L Nat.Bib.Ag. No. L National Bibliographic Agency Control No.
017   Y N N L Copyright No.   L Copyright or Legal Deposit No.
018   Y N N L Copyr. Fee Code L Copyright Article-Fee Code
020   Y N N L ISBN            L International Standard Book Number
022   Y N N L ISSN            L International Standard Serial Number
024   Y N N L Other ID        L Other Standard Identifier
025   Y N N L Overseas No.    L Overseas Acquisition Number
026   Y N N L Fingerprint     L Fingerprint identifier
...

Key to table:

top

14.2 MATERIAL TYPES

You may define material types by editing the "formats" table. You may create a template for each material type.

Example:

PKC_FILE_BEGIN formats.ger
!1 2     3
!!-!-!!!!!!!!!!!!!
MH L MAB2 Hauptsatz
MU L MAB2 Untersatz

Key to table:

top

14.3 FORMS

You may define the forms that catalogers may use to enter data for a field.

The filenames are in the format nnn_xx.lng

Sample 1:

Following is a sample form for fixed-length field 006 (MARC):

PKC_FILE_BEGIN 006_a.eng

   ^1^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

 ^2^^^^^^^^^ $1               ^3^^^^^^^^^ _1 _1 _1 _1
 ^4^^^^^^^^^ _1               ^5^^^^^^^^^ _1
 ^6^^^^^^^^^ _1 _1 _1 _1      ^7^^^^^^^^^ _1
 ^8^^^^^^^^^ _1               ^9^^^^^^^^^ _1
 ^10^^^^^^^^ _1               ^11^^^^^^^^ _1
 ^12^^^^^^^^ _1               ^13^^^^^^^^ _1

###
D a^^^^^^^^^^^000^0^
V

^1=006 Fixed length data elements - Additional material (BOOKS - Language materials)

^2=Form of Material (00)
^3=Illustration codes (01-04)
^4=Target audience (05)
^5=Form of item (06)
^6=Nature of contents (07-10)
^7=Govt.publication (11)
^8=Conference publication (12)
^9=Festschrift (13)
^10=Index (14)
^11=Undefined (15)
^12=Literary Form (16)
^13=Biography (17)

top

14.4 TEMPLATES

Templates will have with an *.mrc extension. The template name can user-defined. e.g issue.mrc oder serie.mrc.

Following is a sample template for series:

PKC_FILE_BEGIN serie.mrc
DB    L LOCAL
SYSID L 0
FMT   L MH
LDR   L -----nM2.01200024------h
030   L z|1dar|z||||7
036a  L DE
037b  L ger
050   L a|a|||||||||||
052   L
078   L serial
082   L
100   L $$a$$b$$9
200   L $$a$$9
331   L
333   L
335   L
359   L
360   L
403   L
410   L
412   L
425   L
433   L
540   L $$a$$b

Key to template:

top

14.5 DEFINE SUB-FIELDS

The "marc_exp" table defines which sub-fields will be displayed as defaults in the catalog record if no form is available for editing the field, use UTIL M/2 to edit . (Assuming there is no form, the sub-fields will be displayed when the cataloger chooses the Open Form function from the Edit Menu.) The marc_exp.dat file displays the subfields, which are used, when a field is selected from a list (F5) in the catalog. The tables have only to contain fields, for which form window was not created. Please note that ALL fields must not be defined - only the fields used frequently.

Following is an example from the table:

PKC_FILE_BEGIN marc_exp.dat
!1  2  3             4
!!!-!!-!!-!!!!!!!!!!!!!!!!!!!!!!!!
...
100 #  XX ab9
101 #  XX
102 #  XX
103 #  XX
104 #  XX ab9
105 #  XX
106 #  XX
107 #  XX
108 #  XX ab9
109 #  XX
110 #  XX
111 #  XX
112 #  XX ab9
...

Key to table:

top

14.6 HELP ON FIELDS

You can find the help on fields in the help field tab (GUI). The Help files are in HTML-Format with a .html. extension.

Example:



top

14.7 SEARCH HEADINGS

You can define the headings file that should be used when the cataloger chooses one of the Search Headings functions by editing the scancode.dat table located in the library's pc_tab/catalog directory. The scancode.dat file determines, which authority data files can be used. This can done from the field code level or the subfield code level. The cataloger can search in index entries (which you have defined), when he selects the "Search" menu in the menu function. The following is a sample of the table:

PKC_FILE_BEGIN scancode.dat
!!!!!!-!!!----!!!----!!!----!!!----!!!----!!!----!!!----!!!----!!!----!!!!!!!!!!!!!!!!!!!
LOCAL  M-TIT  M-AUT  M-SUB  M-THS

!-----------------------------
050##  LCN$
082##  DDC$
086##  GDC$
100##  PER    PER
110##  COP    COP
111##  MEE    MEE
130##  TIP$   TIT$   TIT$
...
or (MAB-Version)
!11112  3      4      5      6      7      8      9     10     11        12
!!!!!!-!!!----!!!----!!!----!!!----!!!----!!!----!!!----!!!----!!!----!!!!!!!!!!!!!!!!!!!
LOCAL  B-TIT  B-AUT  B-KOR  B-SWT  B-NOT  B-ESB  B-BIS  B-TKR  B-THS

!-----------------------------
100##  AUT    AUT
104##  AUT    AUT
412##  VLP_
711##  SWT                  SWP
...

Key to table:

top

14.8 TABLE

The"tag_text.dat" file defines You may define the menu options that are displayed when the cataloger chooses Search Table by editing the table. The tag_text.dat file describes field codes/subfiels values used whereas the cataloging You can define the menu option, when you select the "Table" function Following is a sample of the table:

PKC_FILE_BEGIN tag_text.dat
!1  2  3 4      5
!!!-!!-!-!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!>
041 ## L a mis //  Miscellaneous
041 ## L a ger //  German
041 ## L a spa //  Espanhol
041 ## L a fin //  Finnish
041 ## L a dut //  Dutch
041 ## L a fre //  French
041 ## L a gre //  Greek
041 ## L a heb //  Hebrew
041 ## L a hun //  Hungarian
041 ## L a eng //  English
041 ## L a ita //  Italian
041 ## L a lat //  Latin
...

Key to table:

top

14.9 DEFAULT FIELDS FOR NEW RECORD

You may define the fields that will appear automatically in a new record when the cataloger chooses "Open New Record" from the "File" menu.

To do so, open the tagonnew.dat file. Enter each desired field on a separate line, in the order in which you want the fields to appear. Enter the script in the first colunm and the content of a field will be displayed in this script in GUI.

Sample:

PKC_FILE_BEGIN tagonnew.dat
!22222
!!!!!!
L030
L050

For each field, which should be opened as form, you must define a form. When the cataloger creates a new record, the formular will be automatically displayed an must be filled in. In this case, a default is not possible.

top

15.00 DUPLICATE RECORD FUNCTION

The "Duplicate Record" function enables you to copy the currently displayed record and then edit the copy. The new record will be located on your local drive.

It is up to you, the Setup (Client), to determine whether the new record should be saved automatically in the Home Library (the library to which the user is currently connected); saved automatically in another specific library; or saved in the library of the cataloger's choice (in which case, a list of all available libraries will be displayed for the cataloger to choose from).

In order to determine which of the above will be in effect, open the CATALOG.INI file (found in the client's CATALOG/TAB directory). Go to the [DuplicateRecord] section. Following is an example of what you may find there:

[DuplicateRecord]
Library=HOME

If you want the new record to be saved automatically in the Home library, type HOME to the right side of the equal (=) sign. If you want a different library, type the code for the library, e.g., B-TIT. If you want the cataloger to choose from a list of all available libraries (that is, all libraries listed in the per_lib.ini file in the CATALOG/TAB directory), type ALL. If you want to define the list of libraries that the cataloger can choose from, type the list of libraries, e.g.,

Library=B-TIT,D-TIT

15.01 IMPORTING UPDATED TABLES

You may determine whether or not the system will automatically import updated Catalog tables when the Cataloger opens the Catalog module. To do so, go to the Client's CATALOG/TAB directory and open the CATALOG.INI file. Go to the section labelled [Package].
Following is an example of the relevant section:

[Package]
AlwaysImport=Y

Enter Y to the right of the equal sign if you want the system to import updated tables automatically.

Enter N to the right of the equal sign if you want the system to ask the Cataloger whether or not he wants to import the updated tables.

top

15.02 Color

Choose the color for the Back Color and the script

[RecordBar]
FgColorDescript=000,000,255
With FgColorDescript With FgColorDescript the script color will be determined. [RecordTree]

[RecordTree]
BkColor=255,255,255
2=370
You can determine with BkColor the back color on the left, in the navigation tree.