Material types



Download 350.14 Kb.
Page8/8
Date30.04.2017
Size350.14 Kb.
#16750
1   2   3   4   5   6   7   8

formats.lng
The formats.lng table defines the material types codes (2 characters).

  • marc_country_codes
    The marc_country_codes table in the alephe/tab directory is used to define the list of valid marc country codes. This table is used by the check_val_country that verifies that the position range of a given fixed-length field forms a valid country code (e.g. positions 15-17 of the 008 MARC21 field).

  • marc_exp.dat
    The marc_exp.dat table is used to define default subfields. The subfields defined are displayed in the following circumstances:

      • When a field is selected from the list of valid fields.

      • When the Open form option from the Edit menu is chosen for a field for which no form is available.



    1. marc_language_codes
      The marc_language_codes table in the alephe/tab directory is used to define the list of valid marc language codes. This table is used by the check_val_language that verifies that the position range of a given fixed-length field forms a valid language code (for example, positions 35-37 of the 008 MARC21 field).

    2. permission.dat
      The permission.dat table defines allowed and denied tags for different catalogers.

    3. scancode.dat
      The scancode.dat table defines the heading lists that are used when the cataloger chooses one of the Search Headings functions.

    4. tab00.lng
      The tab00.lng table defines the system index files. There should be one such table for each language defined.

    5. tab01.lng
      The tab01.lng table contains the tag codes and names of MARC and ALEPH fields.

    6. tab02
      The tab02 table defines text that is used by the fix_doc_non_filing_ind program. The program sets the value of a field's non-filing indicator. Fix programs are defined in the tab_fix table.

    7. tab04
      The tab04 table converts one set of cataloging tags to another. Different conversion routines can be defined and linked to the fix_doc_tab04_(01_99) program. This can be used when importing records from a database with a different cataloging system. All tags not defined in this table are deleted from the record when activating the fix routine.

    8. tab05.lng
      The tab05.lng table defines captions for links between records using subfields in the LKR field.

      In the LKR tag, the MARC tag defining the reason for linking two records is registered in subfield 'r'. tab05.lng defines the caption to display in the OPAC before subfields $$n and $$m.



    9. tab11_acc
      The tab11_acc table is used to assign fields to headings indexes.

    10. tab11_aut
      The tab11_aut table is used to define the headings files that the system uses to create hypertext links to FIND and BROWSE from the authority record. This allows the user to navigate the bibliographic database using the authority record fields.

    11. tab11_ind
      The tab11_ind table is used to assign fields to direct indexes.

    12. tab11_word
      The tab11_word table is used to assign fields to word indexes.

    13. tab_aut
      The tab_aut table establishes which headings indexes in the bibliographic database should be subject to authority control. This table also designates per ACC index which authority database should be checked for a match.

    14. tab_expand
      The tab_expand table defines three aspects:



      1. The expand program that defines which data from the record can be expanded.

      2. The system function in which the expand program works.

      3. If required, additional parameters for the expand program.



    1. tab_expand_extract
      The tab_expand_extract table defines extraction of subfields (in a virtual manner) for indexing. This allows separate indexing of every occurrence of a subfield.

    2. tab_expand_join
      The tab_expand_join table creates a single virtual field out of two MARC fields. The table determines: which fields (and which of its subfields) are joined; in which order fields and subfields are joined; and what name the resulting field should be called. The new virtual field can be used for indexing and display.

    3. tab_expand_join_simple
      The tab_expand_join_simple table creates a virtual field taking specific occurrences of another field. The table determines which fields and which of its subfields should be joined, in which order, and what the resulting field should be called.

    4. tab_expand_split
      The tab_expand_split table is used to cut the contents of a tag into separate virtual tags on each occurrence of a subfield, taking all the subfields from one subfield to the next. For example, if subfield $a is set in the table, then $a$b$c$a$a$c splits into:



    5. $a$b$c

    6. $a

    7. $ac

    8. tab_fix
      Fix routines are standard library-defined procedures that automatically "fix" or make changes to cataloging records. The tab_fix table defines three aspects:

      1. The fix program that defines the type of "change" performed on the cataloging record.

      2. The fix routine in which the fix program runs.

      3. If required, additional parameters for the fix program.



    1. tab_locate
      The tab_locate table defines the locate routine to be used when searching for a similar record in other databases. Multiple lines can be set up for one library, in which case ALL lines are taken with an AND condition between them. The tab_locate table must include both the source and the target library.

    2. tab_match This table is used to specify the match routines performed by the Check Input File Against Database (manage-36) service and by the check_doc_match checking routine.

    3. tab_match_acc The tab_match_acc table is a sample table used to define the fields in the records to be checked against the headings index when the match_doc_acc program is used in the tab_match table.

    4. tab_merge
      The tab_merge table lists the merge routines which can be used by the fix_doc_merge program to merge or overlay cataloging records. Column 3 of the tab_fix table is used to define the merging routine that matches the relevant section in the tab_merge table.

    5. tab_merge_overlay
      The tab_merge_overlay table defines the fields to be retained, when overlaying cataloging records.

    6. tab_subfield_punctuation
      The tab_subfield_punctuation in the library's tab directory is used to define the punctuation that is added to the headings in the catalog draft and to the headings for display in the Web OPAC and GUI applications. The table is required to add punctuation to headings from which punctuation has been stripped in order to normalize them.

    7. tab_z103
      The tab_z103 table defines which program runs for the building of links between records.

    8. tab_z105
      The tab_z105 table defines messaging between libraries. For example, the update of an authority record should cause an update of a z01 (heading) in the bibliographic library.

    9. tag_text.dat
      The tag_text.dat table defines fixed values for specific subfields.

    10. taginfo.lng
      The taginfo.lng table defines the help screen that is displayed in the Cataloging GUI for each tag. The display is activated by F2 or from the Edit menu by, the Help on Field option, or by the Help on Field button on the form.

    11. tagonnew.dat
      The tagonnew.dat table defines the default fields when a new record is created.





    Download 350.14 Kb.

    Share with your friends:
  • 1   2   3   4   5   6   7   8




    The database is protected by copyright ©ininet.org 2024
    send message

        Main page