CHAPTER: 3
Study of MARC21 Elements for Codification and Transliteration
Introduction History of MARCH MARC Format MARC: Record Structure Study of MARC21 for Data Encoding Record Translation Methodology for Data Codification Analysis of MARC21 Fields Conclusion Chapter 3: Study of MARCH elements 82
3.1 INTRODUCTION
The holding of a library is displayed in the form of catalogue. There are many forms of catalogue: > Book catalogue > Sheaf catalogue > Card Catalogue > Computer Catalogue (Machine Readable Catalogue)
So far, the widely used form of catalogue is Card Catalogue but a gradual shift is seen towards having Machine Readable Catalogue.
Computer Catalogue or Machine Readable Catalogue (MARC) was developed to print card catalogue and to facilitate bibliographic data exchange. MARC, was initiated by Library of Congress (LC) as pilot project in 1965. In 1963 a study conducted by LOC recommended automation of cataloguing, searching, indexing and document retrieval (1). MARC is for identification and arrangement of bibliographic data for computer processsing and fiirther distribution of catalogue (2).
MARC format is a standardized approach to describe bibliographic data so that computers can understand the data irrespective of the language and script of the data. To cut across the language barrier MARC used numeric tags but still English has its own impact on MARC , for example the use of sub-field identifiers (3).
3.2 HISTORY OF MARC21
The pilot project known as MARC-I began in the year 1965 with the main aim of creation and distribution of machine readable cataloging data to other libraries with Library of Congress (LC) as the distributing point. MARC-I only dealt with books. The development of MARC-II started in 1968. It was Chapter 3: Study ofMARC2I elements 83 planned to cover all types of materials including books and monographs. During 1970-1973 documentation was issued for other materials i.e. in 1972 films records were issued, 1973 for serials, maps and French books and by 1975 records for German, Spanish, and Portuguese material. (4)
In the year 1999 USMARC and CAN/MARC were harmonized and named as MARC21 (5). The MARC21 bibliographic format, as well as all official MARC 21 documentation, is maintained by the Library of Congress and by Canadian National Library (6) and the Library of Congress maintains the MARC21 website. Recently UKMARC is also being merged with MARC21 and British Library is shifting fi-om UKMARC to MARC21.
The Library of Congress and the National Library of Canada serve as the maintenance agency for the MARC21 formats for bibliographic, authority, holdings, classification, and community information data. Proposals for changes to the format may originate from any MARC21 users. The proposals for change in formats can be expressed by MARC users at open meetings or via email and the listserv (7).
3.3 MARC FORMAT
A MARC record involves three elements: the record structure, the content designation, and the data content of the record (8): > Structure: MARC records is typical of Information Interchange Format (ANSI Z39.2) and Format for Information Exchange (ISO 2709). > Content designators: By definition "the codes and conventions established to identify explicitly and characterize further the data elements within a record and to support the manipulation of those data". Anything which establishes the kind of data is a Content Designator, for example, there are three kinds of content designators ~ tags, indicators, and subfield codes. Chapter 3: Study ofMARC21 elements 84
> Content: This is the actual data which we store in the data fields. Often most of the data elements are defined by standards outside the formats in for example, Anglo-American Cataloguing Rules, Library of Congress Subject Headings, National Library of Medicine Classification. The current research follows hypothesis that much of the content can be codified or transliterated which facilitates cross lingual information retrieval in Indian languages.
In MARC21, formats are defined for five types of data: bibliographic, holdings, authority, classification, and community information. The current study is only oriented to Bibliographic data. The elements which are essential for bibliographic description are taken in the account.
3.3.1 MARC: Record Structure
A typical MARC record consists of three main sections (8): the leader, the directory, and the variable fields. > The leader consists of data elements that contain coded values and are identified by relative character position. It is also called as Record label in CCF and UNIMARC. Data elements in this section define parameters for processing the record. It is fixed in length (24 characters) and occurs at the beginning of each MARC record. > The directory contains the tag, starting location, and length of each field within the record. The length of the directory entry is defined in the entry map elements in Leader/20-23. In the MARC 21 format, the length of a directory entry is 12 characters, while in CCF it is 14 characters where character 13* and 14"" are Segment Identifier and Occurrence Identifier. The directory ends with a field terminator character. > The data content of a record is divided into variable fields. The MARC 21 format distinguishes two types of variable fields: variable control fields and variable data fields. Chapter 3: Study of MARCH elements. 85
RECORD LENGTH LABEL 5 characters 24 characters RECORD STATUS DIRECTORY 1 character variable length TYPE OF RECORD DATA FIELDS 1 character variable length BIBLIOGRAPHIC LEVEL RECORD SEPARATOR 1 character 1 character TYPE OF CONTROL 1 character
Directory Structure CHARACTER CODING ENTRY SCHEME 12 characters 1 character INDICATOR COUNT E>rrRY 1 character 12 characters
ENTRY SUBFIELD CODE COUNT 12 characters 1 character ENTRY BASE ADDRESS OF DATA 12 characters 5 character
ENCODING LEVEL 1 character FIELD SEPARATOR 1 character DESCRIPTIVE CATALOGUING FORM 1 character LINKED RECORD ^ REQUIREMENT Directory 3 character LENGTH OF THE LENGTH OF FIELD STARTING LENGTH OF I character TAG CHARACTER DATAFIELD LENGTH OF THE 3 characters POSITION 4 characters STARTING CHARACTER 3 characters POSITION • LENGHT OF THE IMPLEMENTATION DEFINED 1 character UNDEFINED Datafleld Structure 1 character
SUBFIELD SUBFIELD FIELD INDICATORS SUBFIELD SUBFIELD IDENTIFIER IDENTIFIER SEPARATOR 2 characters variable variable 2 characters 2 characters 1 character
Fig. 3.1: Diagrammatic Representation of MARC Record Chapter 3: Study ofMARCll elements. 86
3.4 STUDY OF MARC21 FOR DATA ENCODING
Listing of content designators in MARCH Manual is done in nine blocks. The '0th block' is for control data and codified data. Control data are basically different types of numbers given by different agencies or by libraries for unique identification of number for example, ISBN, ISSN, Library of Congress Class Number and so on. The codified data represents country of publication, date of publication and so on.
Block MARC21 Area 0 Control Data and Coded Data 1 Main Entry Fields 2 Title, Edition, Imprint etc. 3 Physical Description, etc. Fields 4 Series Statement Fields 5 Note Fields: Part 1 and Part 2 6 Subject Access Fields 7 Name, etc. Added Entries or Series; Linking Entry Fields 8 Series Added Entry Fields, Holding and Location 9 Reserved for Local Implementation
Table 3.1: MARC21 Blocks
3.4.1 Multilingual MARC
One of the objectives of the present work is to display the records in different Indian language scripts. There are two aspects of multilingual display, transliteration and translation.
Some of the data fields require transliteration from one script to other. For example, Name of a person will be always same in all the language only script should be changed. Chapter 3: Study ofMARCll elements 87
Much of the data in a catalogue requires translation. There are three ways of achieving Machine Translation, > Data codification > Multilingual Thesaurus > Machine translation
If data is codified it is easy to translate it from one language to other using a kind of table lookup where rows contain words in different languages. That is why the current project has taken the approach to identify the fields which can be codified and allot numeric value to the standardized terms and at the end with help of machine readable multilingual lookup table, one can translate the data into any other language.
Similarly, multi-lingual thesauri can be developed to handle subject headings. In other words, if we can develop a lookup table for multi-lingual thesauri, one can replace any keyword into a keyword in another language using the lookup table. In the present work, this aspect is less emphasized for the lack of the availability of multi-lingual thesauri of subject keywords for Indian languages. However, the approach taken in the case of replacing the codes by translated words can be easily adopted in the case of subject key terms.
There are several subfields which require machine translation. But Machine translation (MT) is still a hard task with current Natural Language Processing (NLP) technology.
In this regard a study is made to identify the fields which should be transliterated and translated using codification in MARC21 bibliographic standard. Chapter 3: Study ofMARCll elements.
Broadly, field/subfields can be classified in following classes, > Translated field/subfield o Codified field/subfield o Data translation > Transliterated field/subfield > Non-processed
3.4.1.1 Translated field/subfield
There are number of fields which need to be translated for mulfilingual access. Since, Machine Translation (MT) is a difficult task to achieve attempt has been made to identify the fields which could be codified and which must require translation.
3.4.1.1.1 Codified field/subfield
The fields which use standard data elements for description are codified. For example. Relator Term (100 - MAIN ENTRY PERSONAL NAME, subfield $e) demonstrates the role or relation of the person with the document. It is not very tough to conclude to a list of such relation. Similarly, there are many instances in the MARC where there is no existing code but one can arrive at code for example. Edition of document, if an analytical study is conducted on large set of data, one can arrive on standard terms which can explain different editions. Similar, study has been done in the present work and standard has been generated.
3.4.1.1.2 Translated field/subfield
These are the field which require human translation and cannot be codified. Often such fields are found in Note Area. These fields contain free text. For example, 500 - General Note, subfield $a. Chapter 3: Study ofMARC21 elements 89
3.4.1.2 Transliteratedfield/subfield
These fields are basically, name of place, person or thing (for example, subfield $2 Source). The in these subfield can be easily transliterated. For example, 245 - Title statement, subfield $a Title, should always been transliterated as it represents the name of the document.
3.4.1.3 Non-processed field/subfield
There are several fields which carry some kind of number for example, ISBN or ISSN, which should be adopted as such in the display. Such data need not be processed. Dates also fall in the same category only the difference is the data entered in the system should be in accordance to ISO standard 8601. Data is adopted unprocessed often in the case of URI (Uniform Resource Identifier), URN (Uniform Resource Name), Login name, ISBN, ISSN etc.
3.4.2 Methodology for Data Codification
In the following text each of the MARC21 content designators, i.e. tags and subfields are studied in order to decided whether the data contained in each of the subfields required to translated or transliterated or left unchanged. Information about the availability of the code is indicated, if no code is available, information about the coded developed is given and the relevant appendix, where the code tables is presented is indicated.
3.4.2.1 Use MARC21 Defined Codes
MARC21 has developed several codes for recording different characteristics of an item, for example, type of storage device, polarity, coloration etc. But unfortunately the given codes are in Roman alphabets, which really do not Chapter 3: Study ofMARCll elements. 90 cut across the language barrier. For such kind of pre-existing codes numeric designators has been re-allotted. As far as possible the numeric values are kept simple starting from 1, 2, 3, 4, ... and so on except in some cases. Like in the field, '300 Physical description' where many aspects have to be taken into account within the same subfield. For example, '$a Extent' covers the number of pages, volumes, cassettes, total playing time, etc. of all types of items, without distinction about types of item. In such cases, 3 to 4 character length numeric values are allotted and each digit carries some meaning. For example, value 303 represents CD-ROM for computer files where first digit '3' represents item type 'Computer files' and 03 (2"*^ and 3'^'' digits) represents 'CD-ROM'.
3.4.2.2 Use of Existing International Code
If MARC21 has not developed code for a particular characteristic an attempt has been made to identify equivalent standard code preferably numeric, for example, 'ISO 4217 Code for Currency' — Numeric code for currency. If numeric code is not available, but any standard code already exists, numeric value is given to elements of code, for example. Appendix 2.2 'Code for Patent Status' which is maintained by European Patent Office (EPO) has been used but elements are given numeric codes. A part of the code is as follows,
Numeric Value Value 1 Deemed to be withdrawn 2 Refused 3 Withdrawn 4 Lapsed in a contracting state 5 Expired 6 Opposition filed 7 Revoked Chapter 3: Study ofMARC21 elements. 91
3.4.2.3 Methodology for Code Generation
If there is no standard code available either in MARC21 or elsewhere, an attempt has been made to codify particular characteristic. A database of 116745 records has been created in WINISIS. These records are downloaded from OCLC database. An index has been generated on the each subfield which holds the data of that characteristic and index is dumped in a text file. Unique terms are extracted from index and numeric code is given to each term in alphabetical sequence. The 'Appendix 3.16 Code for Edition' is developed with this methodology. A part of code is as follows,
Numeric Value Code 1 Abridged 2 Advance Reader's 3 Advance Uncorrected Proof 4 Anniversary 5 Annotated 6 Annual 7 Answers Edition.
3.4.2.4 Illustrative Codes
In many places it is felt that a particular characteristic contained in a subfield can be codified but there are no standards available. Also no data is available for analyzing and generating codes. In these cases an illustrative code of a few elements is prepared and display has been shown with the help of these codes. For example, in the field '366 - Trade Availability Information', the subfield '$c - Availability Status Code' is represented as follows,
Numeric Value Value 1 Reprint
2 Not in Print /,'• 3 In Print //^r-. 4 Out of stock Chapter 3: Study ofMARCIl elements 92
3.4.3 Analysis of MARC21 Fields
The following information details each of the MARC21 content designators.
001 - Control Number
The control number is assigned by the organization creating, using, or distributing the record.
This field can be taken as it is, no processing has to be done.
003 - Control Number Identifier
This field contains the MARC code for the organization whose control number is contained in field 001 (Control Number). MARC21 uses MARC Code List for Organizations that is maintained by the Library of Congress. The code consists of roman characters sometime dashes (-). The code can be lower and upper case and should not exceed more than eight characters.
There are four parts to the code. (9) > The first unit represents the country. The code is taken from MARC Code List for Countries. If it is U.S. the first part presents the state or territory. For example, li stands for India. Ca stands for Canada.
> The second unit represents city or town. For example, liCa represents Kolkata in India. Chapter 3: Study ofMARC21 elements 93
> The third unit represents the name of the institute. For example, liCaNL represents National Library of India (Kolkata, India)
> The any subdivision of the institute is mentioned in the last unit. For example, Oxford University Press is represented by Uk-OxUP.
It is very difficult to generate the code for individual organization. Rendering the name of organization is the best way to represent the name of organization. This data can be transliterated as and when it is required for display purpose in other script. For example, 003 ^5T^^^^BC»R #1^ ^<^ S^g^^ -^^
003 cr'&»^Sood*;6 6S5d>, S)w §;Dort ^oto6
003 5TcF5Jc^?TH 1^^ WZ t^^ ^te^
005 - Date and Time of Latest Transaction (NR) According to MARC21, this sixteen character length data, indicates the date and time of the latest record transaction and serve as a version identifier for the record.
Date and time are recorded according to Representation of Dates and Times (ISO 8601). The date requires 8 numeric characters in the pattern yyyymmdd. The time requires 8 numeric characters in the in the pattern hhmmss.f, expressed in terms of the 24-hour (00-23) clock. Neither translation nor transliteration is required for the data in this field. Chapter 3: Study ofMARC21 elements 94
Examples 005 200040423151047.0 [April 23, 2004, 3:10:47 P.M.]
006 - Fixed-Length Data Elements—Additional Material Characteristics- General Information (R)
This field stores codified data. It has fixed length of 18 characters. It is used for special aspects particularly when the item has multiple characteristics which can't be catalogued in field 008 - Fixed - Length Data Element. It covers books, computer files/electronic resources, maps, music, continuing resources, visual materials, and mixed materials. Since the field is already codified so it should be maintained as it is.
007- Physical Description Fixed Field—General Information (R)
This is again a coded field. This field contains special information about the physical characteristics. The information may represent the whole item or parts of an item such as accompanying material.
Materials described in the field 007 are; map, electronic resource, globe, tactile material, projected graphic, microform, non-projected graphic, motion picture, kit, notated music, remote-sensing image, sound recording, text, video-recording, and unspecified. Since the field is already codified so it should be maintained as it is.
008 - Fixed-Length Data Elements—General Information (NR)
This is also coded field. This field is of 40 characters. This field is designed for data retrieval point of view. In this field, important bibliographic aspects are codified. Chapter 3: Study of MARCH elements 95
This field deals with Books, Computer files. Maps, Music, Continuing resources, Visual materials and Mixed materials. Character position 0-17 and 35-39 are same across all the types of materials. Rest is material specific. Since the field is already codified so it should be maintained as it is.
010 - Library of Congress Control Number (NR)
Subfield Codes
$a - LC control number (NR)
This subfield contains Library of Congress control number which is a numeric value for identification of document in LC collection, so it should be maintained as it is.
$b - NUCMC control number (R)
This subfield contains National Union Catalog of Manuscript Collections (NUCMC) which is codified number for identification of document so it should be maintained as it is.
$z - Canceled/invalid LC control number (R)
This is also control number so it should be taken as it is and so it should be maintained as it is. Chapter 3: Study ofMARC21 elements 96
013 - Patent Control Information (R)
Subfield Codes
$a - Number (NR)
This is control number so it should be maintained as it is.
$b - Country (NR)
MARC21 takes the value for subfield from MARC Code List for Countries. It is good to adopt the ISO 3166 Numeric-3 code for identifying the place. (10) ISO 3166 is not a priced document, so for practical purpose, numeric value is given to 'MARC code list for Countries'. The code is given in Appendix 3.1. Ultimately, this data has to be transliterated for Indie language display.
$c - Type of number (NR)
It provides designation to the type of patent document identifier. This field should be translated.
$d - Date (R) The date assigned by a competent authority i.e. a patent office reflects when a patent or similar certificate was granted. Other dates, such as effective dates, exhibition dates, etc., are also recorded. Multiple dates are recorded in separate occurrences of subfield $d if they all relate to the same patent document. Qualifying information is recorded in subfield $e. Date is recorded in the yyyymmdd format, for example, 19990911. As explained earlier the ISO 8601 should be followed to record data. Chapter 3: Study ofMARCll elements 97
$e - Status (R)
This indicates the status of the patent document identified by the number in the field. There are codes for the status of patent documents but they use mixed notation. World Intellectual Property Organization (WIPO) code (11) and European Patent Office (EPO) code can be used to create an authority file, otherwise, these codes can also be used as it is. (12). The standard is given in Appendix 3.2.
The data in the subfield can be codified which can in turn generate translated text at the time of display.
$f- Party to document (R)
The data in this subfield represents the organization which is responsible for patent. Name of the organization can be entered in the prescribed script which can be transliterated at the time of retrieval.
015 - National Bibliography Number (R)
This field contains the National Bibliography Number.
Subfield Codes
$a - National bibliography number (R)
This subfield contains the value of National Bibliography Number so it should be maintained as it is.
$2 - Source (NR)
The name of the source from which national bibliography number in subfield Sa is taken. MARC21 maintains a list of codes for identifying Chapter 3: Study ofMARC21 elements 98 different national bibliographies which can be found at www.loc.gov/marc/relators/relaothr.html#rela015b (\y). The code is of two or three character length and rendered in roman characters. Numeric version of code is given in Appendix 3.3.
016- National Bibliographic Agency Control Number (R)
Indicators
First - National bibliographic agency
# - National Library of Canada 7 - Source specified in subfield $2 Second - Undefined # - Undefined
The use of # in the first indicator represents the National bibliographic agency is National Library of Canada. It is because the National Library of Canada is involved in the designing of MARC21 such biasness is seen. For others first indicator 7 is used where as Name of other agencies should be mentioned in S2 Source.
Subfield Codes
$a - Record control number (NR)
This subfield contains Record control number assigned by national bibliographic agency so it should be maintained as it is. Chapter 3: Study ofMARC21 elements 99
$z - Canceled or invalid record control number (R)
This subfield contains a canceled or invalid number assigned by a national bibliographic agency.
$2 - Source (NR)
The name of national bibliographic agency is contained in this subfield. MARC21 suggests the use of MARC Code List for Organizations. Alternatively, transliteration of the data is good enough for retrieval in other languages.
017 - Copyright or Legal Deposit Number (R)
Subfield Code
$a - Copyright registration number (R)
Data is registration number so it should be maintained as it is.
$b - Assigning agency (NR)
Name of the body assigned copyright registration number. This data needs to be transliterated.
$2 - Source (NR)
The subfield contains source of the national bibliography number in subfield $a. MARC21 has so far not defined the code so data should be transliterated. Chapter 3: Study of MARCH elements 100
018 - Copyright Article-Fee Code (Nr)
Subfield Code
$a - Copyright article-fee code (NR)
The data in this field has numeric value. Data should be taken for display as it is.
020 - International Standard Book Number (R)
Subfield Codes
$a - International Standard Book Number (NR)
This subfield contains numeric data separated by hyphens and parenthetical qualifying informafion about the binding.
MARC21 recommends ISBN should be entered without hyphens. MARC21 further advocates for an algorithm for print program to generate hyphens while printing.
In fact, there is no harm entering the data as it is in database with hyphens so nothing needs to be done.
$c - Terms of availability (NR)
This subfield contains price information. For example, the following examples are taken from MARC21 manual. 020 ##$cRsl5.76 ($5.60 U.S.) 020 ##$cRental material 020 ##$cFor sale ($200.00 for 3/4 in.; $150.00 for 1/2 in.) Chapter 3: Study ofMARC21 elements. 101
The Currency code, ISO 4217 should be adopted for display in other scripts, which is maintained by Business Information (14). The code is given in Appendix 3.4. This facilitates the translation of Currency in different language. At the time of data entry Currency should be separated by a period (.). For example, if the numeric codes are given as,
Numeric Code Value 1 Rs. 2 $ 3 Pound Sterling
And the data entry can done with numeric code as, 020 ##1.200
Multilingual display can be achieved in different language scripts. ^.200 cb. 200
There are two types of data in one subfield first part is currency code and second part is value to currency. In such circumstances, differentiating data becomes difficult. So for practical approach field should be transliterated, but this true only for Indie languages.
$z - Canceled/invalid ISBN (R)
This should be treated in the same way as subfield $a. Chapter 3: Study ofMARCIl elements 102
022 - International Standard Serial Number (R)
Indicators
First - Level of international interest
# - No level specified 0 - Continuing resource of international interest 1 - Continuing resource not of international interest
Second - Undefined
#- Undefined
Subfield Codes
$a - International Standard Serial Number (NR)
This subfield contains numeric data separated by hyphens so it should be maintained as it is.
$y - Incorrect ISSN (R)
This subfield contains numeric data. Data can be taken as it is for display.
$z - Canceled ISSN (R)
This subfield contains numeric data. Data can be taken as it is for display.
$2 - Source (NR)
The source of document is a recent addition in MARC21 manual. The Source codes are not defined in the 'MARC Code Lists for Relators, Chapter 3: Study ofMARC21 elements 103
Sources, Description Conventions'. The name of source should be entered as text which should be transliterated at the time of display.
024 - Other Standard Identifier (R)
A standard number or code published on an item which cannot be accommodated in another field (e.g., field 020 (International Standard Book Number), 022 (International Standard Serial Number), and 027 (Standard Technical Report Number)). The type of standard number or code is identified in the first indicator position or in subfield $2 (Source of number or code).
Indicators
First - Type of standard number or code
0 - International Standard Recording Code (ISRC) 1 - Universal Product Code (UPC) 2 - International Standard Music Number (ISMN) 3 - International Article Number (EAN) 4 - Serial Item and Contribution Identifier (SICI) 7 - Source specified in subfield $2 8 - Unspecified type of standard number or code
Second - Difference indicator
# - No information provided 0 - No difference 1 - Difference Chapter 3: Study ofMARC21 elements. 104
Subfield Codes
$a - Standard number or code (NR)
This is codified data so it should be maintained as it is,
$c - Terms of availability (NR)
Same as subfield 20$c of ISBN.
$d - Additional codes following the standard number or code (NR)
This is codified data so it should be maintained as it is.
$z - Canceled/invalid standard number or code (R)
This is codified data so it should be maintained as it is.
$2 - Source of number or code (NR)
A code is maintained in 'MARC Code Lists for Relators, Sources, Description Conventions' to identify the source. But alternatively library can use numeric values for codification.
Numeric code MARC21 code Value 1 doi Digital object identifier 2 isan International standard audiovisual number 3 Istc International standard text code 4 Iswc International standard musical work code
Table 3.2: Standard Identifiers
Example, 024 7# $ahttp://hdl.handle.net/1849/166$cl Chapter 3: Study ofMARC21 elements 105
The output in Hindi could be achieved as, http://hdl.handle.net/1849/166 (fef^TSct 025 - Overseas Acquisition Number (R) Subfieid Code $a - Overseas acquisition number (R) This is codified data so it should be maintained as it is. 026 - Fingerprint Identifier (R) Subfieid Code 5a - First and second groups of characters (R) This is codified data so it should be maintained as it is. $b - Third and fourth groups of characters (R) This is codified data so it should be maintained as it is. $c - Date (NR) This is codified data so it should be maintained as it is. $d - Number of volume or part (R) This is codified data so it should be maintained as it is. Chapter 3: Study ofMARC21 elements. 106 $e - Unparsed fingerprint (NR) This is codified data so it should be maintained as it is. $2 - Source (NR) A code is maintained in 'MARC Code Lists for Relators, Sources, Description Conventions' to identify the source. But alternatively library can use numeric values for codification. (15) Numeric code MARC21 code Value 1 fei Fingerprints = Empreintes = Impronte (Paris: Institut de recherche et d'histoire des textes) 2 stcnf Vriesma, P.C.A. The STCN [Short title catalogue Netherlands] fingerprint (in 'Studies in bibliography, v. 39, 1986, p. 93-100) (s'- Gravenhage: Koninklijke Bibliotheek) Table 3.3: Code for Finger Print Identifier $5 - Institution to which field applies (R) This subfield holds the code of the institution or organization that holds the copy to which the field applies. The name of the institute should be entered in full text and for the purpose of retrieval data can be transliterated as shown in the example, 026 ##$5'^5T^^^°5l»R #r^ *a<^ ^^M'^ -^^ 027 - Standard Technical Report Number (R) The technical report number is usually the primary means of identifying a specific technical report. Chapter 3: Study ofMARCll elements 107 The STRN is formulated according to Standard Technical Report Number (STRN), Format and Creation, ANSI Z39.23-1983. (16) Subfield Codes $a - Standard technical report number (NR) This is codified data so it should be maintained as it is. $z - Canceled/invalid number (R) This is codified data so it should be maintained as it is. 028 - Publisher Number (R) Indicators First - Type of publisher number 0 - Issue number 1 - Matrix number 2 - Plate number 3 - Other music number 4 - Video recording number 5 - Other publisher number Second - Note/added entry controller 0 - No note, no added entry 1 - Note, added entry 2 - Note, no added entry 3 - No note, added entry Chapter 3: Study of MARCH elements 108 Subfield Codes $a - Publisher number (NR) This is codified data so it should be maintained as it is. $b - Source (NR) Name of the source from which publisher number is taken. The data of this subfield should be transliterated. 030 - CODEN Designation (R) This field contains the CODEN designation assigned to a periodical title by the Chemical Abstracts Service. Each CODEN consists of four mnemonic letters and a fifth letter, A, B, C, or D. The sixth character, a check character, is alphabetic or numeric. The sixth character of a CODEN is a calculated check character, either numeric, 2-9, or alphabetic, A-Z. It is used to identify and eliminate typographical errors. (17) Subfield Codes $a - CODEN (NR) This subfield contains valid CODEN for the title. This is codified data so it should be maintained as it is. $z - Canceled/invalid CODEN (R) This is codified data so it should be maintained as it is. Chapter 3: Study of MARCH elements 109 032 - Postal Registration Number (R) The number assigned to a publication for which the specified postal service permits the use of a special mailing class privilege. Subfield Codes Sa - Postal registration number (NR) The six numeric characters are right justified and each unused position contains a zero. MARC21 recommends that the hyphen at third character position should be generated by the system. (18) Example 032 ##$a221 001 There is no harm in entering data with hyphens or any other punctuation and it also does not put load on the display program to process and bring corresponding display. $b - Source (agency assigning number) (NR) This subfield contains the name of the agency. This data should be translated as shown in the example of field 003. 033 - Date/Time and Place of an Event (R) Indicators First - Type of date in subfield $a # - No date information 0 - Single date Chapter 3: Study ofMARC21 elements 110 1 - Multiple single dates 2 - Range of dates Second - Type of event # - No information provided 0 - Capture 1 - Broadcast 2 - Finding Subfield Codes $a - Formatted date/time (R) The data and time represented in the following format yyyymmddhhmm+- hmm. > yyyymmdd represents the date. > hhmm represents the time > +-hmm represents Time Differential Factor $b - Geographic classification area code (R) This is codified data. The source of the code is Library of Congress Classification Class G (dropping the letter G) that is maintained by the Library of Congress so it should be maintained as it is. $c - Geographic classification subarea code (R) This is codified data. An alphanumeric Cutter number, derived fi-om Class G or expanded Cutter lists, that represents a subarea of the geographic area coded in subfield $b. Cutter numbers for places in the U.S. are published in Geographic Cutters. Class G, Geographic Cutters, and the expanded Cutter Chapter 3: Study ofMARCll elements Ill lists are maintained by the Library of Congress so it should be maintained as it is. 034 - Coded Cartographic Mathematical Data (R) Field contains the coded form of the mathematical data of the bibliographic record. Indicators First - Type of scale 0 - Scale indeterminable/No scale recorded 1 - Single scale 3 - Range of scales Second - Type of ring # - Not applicable 0 - Outer ring 1 - Exclusion ring Subfield Codes $a - Category of scale (NR) One-character code that indicates the type of scale of the item. Numeric code Value 1 Linear scale 2 Angular scale 3 Other type of scale Table 3.4: Scale Code Chapter 3: Study ofMARC21 elements 112 $b - Constant ratio linear horizontal scale (R) $c - Constant ratio linear vertical scale (R) $d - Coordinates—westernmost longitude (NR) $e - Coordinates—easternmost longitude (NR) $f- Coordinates—northernmost latitude (NR) $g - Coordinates—southernmost latitude (NR) $h - Angular scale (R) $j - Declination—northern limit (NR) $k - Declination—southern limit (NR) $m - Right ascension—eastern limit (NR) $n - Right ascension—western limit (NR) $p - Equinox (NR) $s - G-ring latitude (R) $t - G-ring longitude (R) All the subfields carry numeric value which should be used as it is while printing. No further processing is required on data. 035 - System Control Number (R) Subfield Codes $a - System control number (NR) $z - Canceled/invalid control number (R) This code has two parts. Part one is organization code which MARC21 recommends to take from 'MARC Code List for Organizations' enclosed in parenthesis. The second part is a number outside the parenthesis. Since the system control number is constructed in two parts, this subfield should be split in two parts. The part one should store the name of Chapter 3: Study ofMARC21 elements 113 organization which in tum at the time of display can be transliterated. The second part should have been the number which should be printed as such at the time of display. 036 - Original Study Number for Computer Data Files (NR) Subfield Codes $a - Original study number (NR) This is codified data so it should be used as it is. $b - Source (agency assigning number) (NR) It contains name of the agency which assigned the number. This data should be transliterated. 037 - Source of Acquisition (R) Subfield Codes $a - Stock number (NR) Numbers such as distributor and publisher numbers are codified data so it should be maintained as it is. $b - Source of stock number/acquisition (NR) This subfield contains name of the source which provides stock number. This data should be transliterated. Chapter 3: Study of MARCH elements 114 $c - Terms of availability (R) This subfield should be treated according to 20$c. $f- Form of issue (R) Format or binding in which item is available. Code can be developed for different form of item which can be used. MARC21 defines format and binding in field 008 which is numerically codified as shown in Appendix 3.5. $g - Additional format characteristics (R) The names of formats, format version numbers, and/or format version dates in which the data is available for transfer. (19) Data is stored in fi-ee text which is difficult to codify. For display in other language and script data needs to be translated. $n - Note (R) Subfield contains textual notes pertaining to the acquisition of the item. This is free text which needs to be translated. 038 - Record Content Licensor (NR) MARC21 recommends the use of 'MARC Code List for Organizations' for organization code for this field. Chapter 3: Study ofMARC21 elements 115 Subfleld Codes $a - Record content licensor (NR) Name of the organization should be entered which should be transliterated at the time of print. 040 - Cataloging Source (NR) Subfleld Codes $a - Original cataloging agency (NR) This subfield stores the name of the cataloguing agency. OCLC recommends the use of code for this subfield developed by OCLC. But if there is no code it good to enter the fiill name of the organization. This data should be transliterated at the time of display. $b - Language of cataloging (NR) Library of congress maintains the code for languages called as 'ISO 639-2 Codes for the Representation of Names of Languages Part 2: Alpha-3 Code'. LC is official body recognized by International Organization for Standardization (ISO) to maintain and register a new language. This code list uses roman alphabets. There are two types of language code ISO 639-1 which is two character language code while ISO 639-2 is three character language code. 'MARC code List for Languages' is derived fi'om this standard. Numeric version of this code is not available. (20) Chapter 3: Study ofMARCll elements 116 There is a numeric code list of scripts maintained by Unicode Consortium. (21). Appendix 3.6 contains numeric version of 'MARC code List of Languages'. $c - Transcribing agency (NR) This subfield stores the name of the institution that input the record. This data should be transliterated. $d - Modifying agency (R) This subfield stores the name of the institution that altered the record. This data should be transliterated. $e - Description conventions (NR) The MARC maintains code for 'MARC Code Lists for Relators, Sources, Description Conventions'. This code can be converted to numeric code for cutting the language barrier. The numeric value uses less characters. Appendix 3.7 is the altered form of code for numeric code, (22). 041 - Language Code (R) The sources of the codes are: MARC Code List for Languages or other code lists such as ISO 639-1 (Codes for the representation of names of languages - Part 1 : alpha-2 code). (23). Appendix 3.6 is the 'MARC Code List of Languages'. Chapter 3: Study ofMARCll elements 117 Indicators First - Translation indication 0 - Item not a translation/does not include a translation 1 - Item is or includes a translation Second - Source of code # - MARC language code 7 - Source specified in subfield $2 Subfield Codes $a - Language code of text/sound track or separate title (R) This is codified data so it should be maintained as it is. Numeric code for languages can be adopted which is maintained in Appendix 3.6. $b - Language code of summary or abstract/overprinted title or subtitle (R) This is codified data so it should be maintained as it is. Numeric code for languages can be adopted which is maintained in Appendix 3.6. $d - Language code of sung or spoken text (R) This is codified data so it should be maintained as it is. Numeric code for languages can be adopted which is maintained in Appendix 3.6. $e - Language code of librettos (R) This is codified data so it should be maintained as it is. Numeric code for languages can be adopted which is maintained in Appendix 3.6. Chapter 3: Study ofMARC21 elements 118 $f- Language code of table of contents (R) This is codified data so it should be maintained as it is. Numeric code for languages can be adopted which is maintained in Appendix 3.6. $g - Language code of accompanying material other than librettos (R) This is codified data so it should be maintained as it is. Numeric code for languages can be adopted which is maintained in Appendix 3.6. $h - Language code of original and/or intermediate translations of text (R) This is codified data so it should be maintained as it is. Numeric code for languages can be adopted which is maintained in Appendix 3.6. $2 - Source of code (NR) This field contains the name of the source which is used for language code, if any. This data should be transliterated. 042 - Authentication Code (NR) Subfield Code $a - Authentication code (R) MARC21 defines Authentication code. The numeric translation of the code is given in Appendix 3.8. Chapter 3: Study ofMARCll elements 119 043 - Geographic Area Code (NR) Subfield Code $a - Geographic area code (R) MARC21 maintains 'Geographical Area code'. There are many sections and subsection and it uses roman character. Numeric codes can be allotted to this code and then it can be used. For the practical purpose 'Appendix 3.1 Country' code has been used. Classification scheme like Colon classification of Dewy Decimal Classification can be used to identify geographical area. Using these numbers Subject headings can also generated which is useful for subject access. This approach has not been adopted in the system. This is codified data so it should be maintained as it is. $b - Local GAC code (R) A local expansion of a Geographic Area Code. Use a separate subfield $b for each local GAC code. The source of the code is indicated in subfield $2. This is codified data so it should be maintained as it is. $c - ISO code (R) This is codified data according to ISO 3166 so it should be maintained as it is. Chapter 3: Study of MARCH elements 120 $2 - Source of local code (R) This subfield identifies the source from which $b is taken. This data should be transliterated. 044 - Country of Publishing/Producing Entity Code (NR) This field contains country of publishing/producing entity codes if more than one country or producer is associated with an item. Subfield Code $a - MARC country code (R) MARC21 recommends use of 'MARC Code List for Countries'. This is codified data so it should be maintained as it is. Appendix 3.1 contains 'MARC List of Country Codes'. $b - Local subentity code (R) This is codified data so it should be maintained as it is. $c - ISO country code (R) This is codified data according to ISO 3166 so it should be maintained as it is. $2 - Source of local subentity code (R) This subfield identifies the source fi-om which $b is taken. This data should be transliterated. Chapter 3: Study ofMARC2I elements 121 045 - Time Period of Content (NR) Indicators First - Type of time period in subfield $b or $c # - Subfield $b or $c not present 0 - Single date/time 1 - Multiple single dates/times 2 - Range of dates/times Second - Undefined # - Undefined Subfield Codes $a - Time period code (R) This subfield contains four-character time period code. The first two characters represent the earliest period covered. The last two represent the latest period. (24) The code uses alphanumeric characters for time period codification which does not cut across the language barrier so numeric version of the codes should be prepared and used. This is a codified subfield so nothing should be done. Examples, taken from OCLC Manual (24) 122 Numeric code Period covered Time period code 1 423 B.C.-390 B.C. d5d6 2 to 300 B.C. a0d6 3 42 B.C.-A.D. 37 d9e3 4 1066-1328 o6r2 5 12-14th centuries p-r- 6 1740-1840 v4w4 7 1828-1859 w2w5 8 20th century x-x- 9 Compare 1 st century A.D. and 20th e-e- Ja x-x- century 10 Collected scores of George Gershwin's musical comedies Table 3.5: Time Period Code $b - Formatted 9999 B.C. through C.E. time period (R) The subfield contains a time period recorded in the pattern yyyymmddhh and preceded by a code for the era (c for B.C.; d for C.E.). Dates should be taken as it is for display. Example, 045 l#$bdl972 $bdl975 $c - Formatted pre-9999 B.C. time period (R) A time period that consists of as many numeric characters as are needed to represent the number of pre-9999 years B.C. Dates should be taken as it is for display. Example, 045 2#$c225000000 $c70000000 Chapter 3: Study ofMARCll elements 123 046 - Special Coded Dates (R) All dates should follow yyyymmddhh pattern. Subfield Codes $a - Type of date code (NR) Numeric Code Value 1 Inclusive dates of collection 2 Bulk of collection 3 Multiple dates 4 Unknown dates 5 Distribution/release/issue and production/recording session dates 6 Questionable date 7 Reissue and original dates 8 Single known/probable date 9 Publication and copyright dates 10 Incorrect dates Table 3.6: Type of Date Code The data of the following subfield should be recorded in yyyymmdd format. $b - Date I (B.C. date) (NR) $c - Date 1 (C.E. date) (NR) $d - Date 2 (B.C. date) (NR) $e - Date 2 (C.E. date) (NR) $j - Date resource modified (NR) $k - Beginning or single date created (NR) $1 - Ending date created (NR) $m - Beginning of date valid (NR) $n - End of date valid (NR) $2 - Source of date (NR) MARC21 recommends the use of 'MARC Code Lists for Relators, Sources, Description Conventions' for the source but no code is defined in the Chapter 3: Study of MARCH elements 124 MARC21 Manual. In fact, the name of the source can be taken as it is and transliterated at the time of display. 047 - Form of Musical Composition Code (NR) Subfield Codes $a - Form of musical composition code (R) MARC21 recommends the use of code '/MM' for this field. The uses roman characters for codification based on mnemonics which can be converted to numeric. Appendix 3.9 is 'MARC Code List for Musical Composition'. Example, Input: 047 ##$a36 Output: 048 - Number of Musical Instruments or Voices Code (R) This field contains a two-character, alphabetic code that indicates the medium of performance for a musical group. Each code may be followed by a two-digit number (01-99) that indicates the number of parts or performers (e.g., va02, a two-part composition for Voices - Soprano). The number of parts may be omitted if not applicable. (25) Subfield Codes $a - Performer or ensemble (R) The subfield contains a two-character alphabetic code for a performer or ensemble. This is codified subfield so nothing should be done. Numeric codification of MARC21 code is given in Appendix 3.9. Chapter 3: Study of MARCH elements 125 $b' Soloist (R) The subfield contains a two-character alphabetic code for a soloist. Numeric codification should be followed as given Appendix 3.9. Example, 048 ##$b3901 $a3540 $b cH^-lf^--^^ (i7cPH)01 $a cIT?I-?i?^-^H3^ 40 Here 01 in $b and 40 in $a represents the number of performers. 050 - Library of Congress Call Number (R) Indicators First - Existence in LC collection # - No information provided 0 - Item is in LC 1 - Item is not in LC Second - Source of call number 0 - Assigned by LC 4 - Assigned by agency other than LC Subfield Codes $a - Classification number (R) Field should be used as it is. Chapter 3: Study ofMARC21 elements 126 $b - Item number (NR) Field should be used as it is. $3 - Materials specified (NR) Data of this subfield should be translated. 051 - Library of Congress Copy, Issue, Offprint Statement (R) Subfield Codes $a - Classification number (R) Field should be used as it is. $b - Item number (NR) Field should be used as it is. $c - Copy information (NR) The data in this subfield can be codified to some extent but often use of free text makes it complex for codification so this field should be translated. 052 - Geographic Classification (R) Indicators First - Code source # - Library of Congress Classification 1 - U.S. Dept. of Defense Classification 7 - Source specified in subfield $2 Chapter S: Study of MARCH elements 127 Second - Undefined # - Undefined Subfleld Codes $a - Geographic classification area code (NR) A four- to six-character numeric code for the main geographic area associated with the item. The code is derived from the LC class G schedule by dropping the letter G. Data is codified so it should be maintained as it is. $b - Geographic classification subarea code (R) An alphanumeric code, assigned from expanded Cutter lists, that represents a subarea of the geographic area coded in subfield $a. Cutter numbers for places in the U.S. are published in Geographic Cutters that is maintained by the Library of Congress. Data is codified so nothing should be done. $d - Populated place name (R) The subfield contains the name of the geographic area. This data should be transliterated. $2 - Code source (NR) The subfield contains the name of the source which is used for Geographical classification. This data should be transliterated. Chapter 3: Study ofMARCll elements 128 055 - Classification Numbers Assigned in Canada (R) Indicators First - Existence in NLC collection # - Information not provided 0 - Work held by NLC 1 - Work not held by NLC Second - Type, completeness, source of class/call number 0 - LC-based call number assigned by NLC 1 - Complete LC class number assigned by NLC 2 - Incomplete LC class number assigned by NLC 3 - LC-based call number assigned by the contributing library 4 - Complete LC class number assigned by the contributing library 5 - Incomplete LC class number assigned by the contributing library 6 - Other call number assigned by NLC 7 - Other class number assigned by NLC 8 - Other call number assigned by the contributing library 9 - Other class number assigned by the contributing library Subfield Codes $a - Classification number (NR) Data is codified so it should be maintained as it is. $b - Item number (NR) Data is codified so it should be maintained as it is. Chapter 3: Study ofMARC21 elements. 129 $2 - Source of call/class number (NR) MARC 'Code Lists for Relators, Sources, Description Conventions', identifies the classification scheme used to assign the call/class number where the second indicator position contains value 6, 7, 8, or 9. Numeric codification of the code is as follows, Numeric Value code 1 Class FC: a classification for Canadian history and Class PS8000: a classification for Canadian literature. (Ottawa: National Library of Canada) 2 KF classification, modified for use in Canadian law libraries. (Downsview, Ont.: York University Law Library) 3 Los Angeles County Law Library, class K-Law. (Los Angeles: County Law Library) 4 Moys, Elizabeth M. Moys classification and thesaurus for legal materials. (London: Bowker-Saur) Table 3.7: Sources of Call/Class Number Code 060 - National Library of Medicine Call Number (R) Indicators First - Existence in NLM collection # - No information provided 0 - Item is in NLM 1 - Item is not in NLM Second - Source of call number 0 - Assigned by NLM 4 - Assigned by agency other than NLM Chapter 3: Study ofMARCll elements 130 Subfield Codes $a - Classification number (R) Data is codified so it should be maintained as it is. $b - Item number (NR) Data is codified so it should be maintained as it is. 061 - National Library of Medicine Copy Statement (R) Subfield Codes $a - Classification number (R) Data is codified so it should be maintained as it is. $b - Item number (NR) Data is codified so it should be maintained as it is. $c - Copy information (NR) This data should be translated. 066 - Character Sets Present (NR) This subfield contains the information that indicates that the character set present in a record is other than ISO 10646 (or Unicode). Use of the Universal Coded Character Set (UCS or ISO/IEC 10646) and its industry subset Unicode have been approved for standard interchange of MARC21 records according to the specifications 'MARC 21 Specifications for Record Chapter 3: Study ofMARCll elements 131 Structure, Character Sets, and Exchange Media, CHARACTER SETS: Part 2 UCS/Unicode Environment'. (26) Subfleld Codes $a - Primary GO character set (NR) This is codified data so it should be maintained as it is. $b - Primary Gl character set (NR) This is codified data so it should be maintained as it is. $c - Alternate GO or Gl character set (R) Subfield Sc contains a code identifying the alternative character set used in the record. The subfield is repeated for each additional character set present. OCLC maintains a code for this subfield. This is codified data so it should be maintained as it is. 070 - National Agricultural Library Call Number (R) Indicators First - Existence in NAL collection 0 - Item is in NAL 1 - Item is not in NAL Second - Undefined # - Undefined Chapter 3: Study of MARCH elements 132 Subfteld Codes $a - Classification number (R) This is codified data so it should be maintained as it is. $b - Item number (NR) This is codified data so it should be maintained as it is. 071 - National Agricultural Library Copy Statement (R) Subfleld Codes $a - Classification number (R) This is codified data so it should be maintained as it is. $b - Item number (NR) This is codified data so it should be maintained as it is. $c - Copy information (NR) This subfield should be translated. 072 - Subject Category Code (R) Indicators First - Undefined # - Undefined Chapter 3: Study ofMARC2] elements 133 Second - Source specified in subfield $2 0 - NAL subject category code list 7 - Source specified in subfield $2 Subfleld Codes Sa - Subject category code (NR) This is codified data so it should be maintained as it is. $x - Subject category code subdivision (R) This is codified data so it should be maintained as it is. $2 - Source (NR) A MARC code that identifies the thesaurus used to assign the subject category code when the second indicator position contains value 7. Code firom: MARC Code Lists for Relators, Sources, Description Conventions. Numeric codes is given in Appendix 3.11 'MARC Code List for Thesaurus'. 074 - GPO Item Number (R) Subfield Codes $a - GPO item number (NR) The number is assigned from List of Classes of United States Government Publications Available for Selection by Depository Libraries that is maintained by GPO. This is codified field so it should be maintained as it is. Chapter 3: Study of MARCH elements 134 $z - Canceled/invalid GPO item number (R) This is codified field so it should be maintained as it is. 080 - Universal Decimal Classification Number (R) Subfleld Code $a - Universal Decimal Classification number (NR) This is codified field so it should be maintained as it is. $b - Item number (NR) This is codified field so it should be maintained as it is. $x - Common auxiliary subdivision (R) This is codified field so it should be maintained as it is. $2 - Edition identifier (NR) This is codified field so it should be maintained as it is. 082 - Dewey Decimal Classification Number (R) Indicators First - Type of edition 0 - Full edition 1 - Abridged edition Chapter 3: Study ofMARCll elements 135 Second - Source of classification number # - No information provided 0 - Assigned by LC 4 - Assigned by agency other than LC Subfield Codes $a - Classification number (R) This is codified field so it should be maintained as it is. $b - Item number (NR) This is codified field so it should be maintained as it is. $2 - Edition number (NR) This is codified field so it should be maintained as it is. 084 - Other Classification Number (R) Subfield Codes $a - Classification number (R) This is codified field so it should be maintained as it is. $b - Item number (NR) This is codified field so it should be maintained as it is. Chapter i: Study ofMARCll elements 136 $2 - Source of number (NR) MARC21 maintains a code of classification sources in 'MARC Code Lists for Relators, Sources, Description Conventions'. The numeric version of the code is given in Appendix 3.12 'MARC Code List for Classification Systems'. 086 - Government Document Classification Number (R) Indicators First - Number source # - Source specified in subfield $2 0 - Superintendent of Documents Classification System 1 - Government of Canada Publications: Outline of Classification Second - Undefined # - Undefined Subfield Codes $a - Classification number (NR) This is codified field so it should be maintained as it is. $: - Canceled/invalid classification number (R) This is codified field so it should be maintained as it is. Chapter 3: Study of MARCH elements 137 $2 - Number source (NR) 'Code from: MARC Code Lists for Relators, Sources, Description Conventions' should be used when the first indicator position contains value #. This code list is made only for US and Canada. The Number source can be any scheme from any country. Notification of all the world schemes is difficult and since the idea of MARC is internationalization so in the present system codification of this field is avoided. It is good to use the name of the Number source in case of any other country which can be transliterated at the time of display. 088 - Report Number (R) Subfield Codes $a - Report number (NR) It should be maintained as it is. $z - Canceled/invalid report number (R) It should be maintained as it is. 100 - Main Entry—Personal Name (NR) Indicators First - Type of personal name entry element 0 - Forename 1 - Surname 3 - Family name Chapter 3: Study of MARCH elements 138 Second - Undefined # - Undefined Subfield Codes $a - Personal name (NR) A surname and/or forename; letters, initials, abbreviations, phrases, or numbers should be transliterated. $b - Numeration (NR) In Europe or west numeration related to the name of person is always in Roman capital so Roman numeral should used as it is but when dealing with India names for example, Vikramaaditya II is always written in Hindi as rci9h«Hlicir^ fIfctrzT. Hence, the numeration should be done in the native language of data entry. $c - Titles and other words associated with a name (R) Titles and other words should be transliterated. $d - Dates associated with a name (NR) Dates of birth, death, or flourishing, or any other date associated should be used in yyyymmdd format and used as it is. $e - Relator term (R) Chapter 3: Study ofMARCll elements 139 This subfield describes the relationship between a name and a work. This subfield is present in only 12 records out of 116745 records downloaded from OCLC. Same data is entered in $4 Relator Code of same field. MARC21 identifies the Relator code (27). Numeric conversion of the code is given in Appendix 3.13: 'MARC Code List for Relator Code'. $f- Date of a work (NR) Data should be entered as yyyymmdd and taken as it is for display. $g - Miscellaneous information (NR) A data element not more appropriately contained in another defined subfield. This data should be translated. $j - Attribution qualifier (R) Attribution information for names when the responsibility is unknown, uncertain, fictitious or pseudonymous. $k - Form subheading (R) AACR2 defines following Form subdivisions in Rule 25.8 - 25.17. The numeric code of Form subdivision is derived from AACR2. Appendix 3.14: 'MARC Code List for Form Subdivision'. Though codification has been done but it is difficult to give codes to values as values do not fall in finite set. Chapter 3: Study of MARCH elements 140 $1 - Language of a work (NR) Use language code given in Appendix 3.6 'MARC Code List for Languages'. $n - Number of part/section of a work (R) A number designation for a part or section of a work used with a title in a name/title field. Numerals should be used to identify the part or section. Often roman alphabets or language alphabets are used for number. In such cases number should be rendered as it is. For example, a. b. c. ... A. B.C. ... «P ^ ^ ... $p - Name of part/section of a work (R) This data should be transliterated. $q - Fuller form of name (NR) A more complete form of the name contained in subfield $a. This data should be transliterated. $t - Title of a work (NR) The data in this subfield should be transliterated. Chapter 3: Study ofMARCll elements 141 $u - Affiliation (NR) An affiliation or address of the name. The data in this subfield should be transliterated. $4 - Relator code (R) This subfield is already codified. The data of this subfield is already entered in Se Relator Term. So this subfield can be removed 110 - Main Entry—Corporate Name (NR) Indicators First - Type of corporate name entry element 0 - Inverted name 1 - Jurisdiction name 2 - Name in direct order Second - Undefined # - Undefined Subfleld Codes $a - Corporate name or jurisdiction name as entry element (NR) Data of this subfield should be transliterated. $b - Subordinate unit (R) Data of this subfield should be transliterated. Chapter 3: Study of MARCH elements 142 $c - Location of meeting (NR) Data of this subfield should be transliterated. $d - Date of meeting or treaty signing (R) Data in this subfield should follow yyyymmdd. $e - Relator term (R) Same as 100 $e. $f- Date of a work (NR) Data in this subfield should follow yyyymmdd. $g - Miscellaneous information (NR) The data in this subfield should be translated. $k - Form subheading (R) Same as 100 $k $1 - Language of a work (NR) Same as 100 $1. $n - Number of part/section/meeting (R) Same as 100$n. Chapter 3: Study ofMARCll elements 143 $p - Name of part/section of a work (R) Data of this subfield should be transliterated. $t - Title of a work (NR) Data of this subfield should be transliterated. $u - Affiliation (NR) Data of this subfield should be transliterated. $4 - Relator code (R) Same as 100 $4 111 - Main Entry—Meeting Name (NR) Indicators First - Type of meeting name entry element 0 - Inverted name 1 - Jurisdiction name 2 - Name in direct order Second - Undefined # - Undefined Chapter 3: Study of MARCH elements 144 Subfield Codes $a - Meeting name or jurisdiction name as entry element (NR) Data of this subfield should be transliterated. $c - Location of meeting (NR) Data of this subfield should be transliterated. $d - Date of meeting (NR) Data in this subfield should follow yyyymmdd. $e - Subordinate unit (R) Data of this subfield should be transliterated. $f- Date of a work (NR) Data in this subfield should follow yyyymmdd. $g - Miscellaneous information (NR) A data element not more appropriately contained in another defined subfield. This data should be translated. $k - Form subheading (R) Same as 100 $k. Chapter 3: Study of MARCH elements 145 $1 - Language of a work (NR) Same as 100 $1. $n - Number of part/section/meeting (R) Number should be used for representation. $p - Name of part/section of a work (R) Data of this subfield should be transliterated. $q - Name of meeting following jurisdiction name entry element (NR) Data of this subfield should be transliterated. $t - Title of a work (NR) Data of this subfield should be transliterated. $u - Affiliation (NR) Data of this subfield should be transliterated. $4 - Relator code (R) Same as 100 $4. Chapter 3: Study ofMARC21 elements 146 130 - Main Entry-Uniform Title (NR) Indicators First - Nonfiling characters 0-9 - Number of nonfiling characters Second - Undefined # - Undefined Subfield Codes $a - Uniform title (NR) Uniform title should be transliterated. $d - Date of treaty signing (R) Data of this subfield should follow yyyymmdd though MARC21 does not advocate any specific format but it is better to follow ISO 8601. Data entered in this format should be taken as it is. $f- Date of a work (NR) Data of this subfield should follow yyyymmdd though MARC21 does not advocate any specific format but it is better to follow ISO 8601. Data entered in this format should be taken as it is. $g - Miscellaneous information (NR) A data element not more appropriately contained in another defined subfield. This data should be translated. Chapter 3: Study of MARCH elements 147 $h - Medium (NR) Different media can be codified. A numeric code for medium should be developed. MARC21 defines mediums in field 007 which can be used as medium. The numeric code is in given in Appendix 3.15: 'MARC Code List for Medium'. $k - Form subheading (R) Same as 100 $k. $1 - Language of a work (NR) Same as 100 $1. $m - Medium of performance for music (R) This data should be transliterated. $n - Number of part/section of a work (R) Number should be used for representation. $0 - Arranged statement for music (NR) The abbreviation arr. used in a uniform title field. For example, 130 0 $aGod save the king; $o arr. $f 1982. $p - Name of part/section of a work (R) Data of this subfield should be transliterated. Chapter 3: Study of MARCH elements 148 $r - Key for music (NR) OCLC defines uses of 'Code for music compositions'. The code provided in field 008 for music composition can be used. Numeric code is given in Appendix 3.9; MARC Code List for Musical Composition'. $s - Version (NR) Data should be transliterated. $t - Title of a work (NR) Data should be transliterated. 210 - Abbreviated Title (R) Indicators First - Title added entry 0 - No added entry 1 - Added entry Second - Type # - Abbreviated key title 0 - Other abbreviated title Subfield Codes $a - Abbreviated title (NR) Data in this field should be taken as it is because the abbreviated title is given by ISSN centres. Chapter 3: Study ofMARCll elements 149 Examples from OCLC manual, 210 0 SaManage. improve, cost redact, goals $b - Qualifying information (NR) When qualifying information is present in the key title, the same information is added to field 210 in the appropriate abbreviated form. The qualifiers are always enclosed in parentheses. 210 0 SaPlant prot. bull. $b (Faridabad) Data of this field should be transliterated. $2 - Source (R) MARC21 follows Code from: MARC Code Lists for Relators, Sources, Description Conventions for abbreviated title. Numeric codification of the code is as follows, Code Value 1 National Library of Medicine Locatorplus (Bethesda, MD: National Library of Medicine) 2 HLAS journal abbreviations (Washington, DC: Library of Congress, Hispanic Division, Handbook of Latin American Studies) fhttp://lcweb2.loc.gov/hlas/journals.html] Table 3.8: Abbreviated Title code 222 - Key Title (R) Indicators First - Undefined # - Undefined Chapter 3: Study ofMARCll elements 150 Second - Nonfiling characters 0-9 - Number of nonfiling characters Subfield Codes $a - Key title (NR) Data of this subfield field should be transliterated. $b - Qualifying information (NR) Data of this subfield field should be transliterated. 240 - Uniform Title (NR) Indicators First - Uniform title printed or displayed 0 - Not printed or displayed 1 - Printed or displayed Second - Nonfiling characters 0-9 - Number of nonfiling characters Subfield Codes Following subfields should be treated same as 130 Main Entry - Uniform Title. $a - Uniform title (NR) $d - Date of treaty signing (R) $f- Date of a work (NR) Chapter 3: Study of MARCH elements 151 $g - Miscellaneous information (NR) $h - Medium (NR) $k - Form subheading (R) SI - Language of a work (NR) $m - Medium of performance for music (R) $n - Number of part/section of a work (R) $o - Arranged statement for music (NR) $p - Name of part/section of a work (R) $r - Key for music (NR) $s - Version (NR) 242 - Translation of Title by Cataloging Agency (R) Indicators First - Title added entry 0 - No added entry 1 - Added entry Second - Nonfiling characters 0-9 - Number of nonfiling characters Subfield Codes $a - Title (NR) This subfield contains data of the title proper and alternative title, excluding the designation of the number or name of a part. The data of this subfield should be transliterated. Chapter 3: Study of MARCH elements 152 $b - Remainder of title (NR) The data of this subfield includes parallel, alternative, and other title information. The data of this subfield should be transliterated. $c - Statement of responsibility, etc. (NR) The statement of responsibility and/or any remaining title statement data contained in this subfield should be transliterated. $h - Medium (NR) The code table for Medium given 130$h can be adopted for defining medium. $n - Number of part/section of a work (R) Number should be used for representation. $p - Name of part/section of a work (R) Data of this subfield should be transliterated. $y - Language code of translated title (NR) MARC21 recommends use of language code. Chapter 3: Study ofMARC2I elements 153 243 ' Collective Uniform Title (NR) Indicators First - Uniform title printed or displayed 0 - Not printed or displayed 1 - Printed or displayed Second - Nonfding characters 0-9 - Number of nonfiling characters Subfleld Codes Following subfields should be treated same as 130 Main Entry - Uniform Title. $a - Uniform title (NR) $d - Date of treaty signing (R) $f- Date of a work (NR) $g - Miscellaneous information (NR) $h - Medium (NR) $k - Form subheading (R) $1 - Language of a work (NR) $m - Medium of performance for music (R) $n - Number of part/section of a work (R) $o - Arranged statement for music (NR) $p - Name of part/section of a work (R) $r - Key for music (NR) $s - Version (NR) Chapter i: Study ofMARCll elements 154 245 - Title Statement (NR) Indicators First - Title added entry 0 - No added entry 1 - Added entry 0-9 - Number of nonfiling characters Subfield Codes $a - Title (NR) Title of the document is same in all the language so the data in this subfield should be transliterated. $b - Remainder of title (NR) The data in this subfield should be transliterated. $c - Statement of responsibility, etc. (NR) The name of the person is same in all the language so the data in this subfield should be transliterated but often the role of the person is also associated with the name. SaHow to play chess / $c Kevin Wicker ; with a foreword by David Pritchard Combination of role and name can be render as Role # Name; Role # Name ... Chapter 3: Study ofMARC21 elements 155 Code for role can be adopted from Role code table of 130$e. So the above mentioned example can be rendered as, SaHow to play chess / $c 18 # Kevin Wicker; 3 # David Pritachard $f- Inclusive dates (NR) and $g - Bulk dates (NR) The time during which the entirety of the contents of the described record unit were created. Use for archival materials. This subfield often contains the range of dates or years. It is often seen in data entry that text is entered for date. Example, 245 00 $aShort-Harrison-Symmesfamilypapers,$f 1760-1878. 245 00 $k Letter, $f 1901 March 6, $b Dublin, to Henrik Ibsen, Kristiana [Oslo]. 245 10 $k Employment applications $gJan.-Dec. 1985 The date should not be entered as mentioned $f of second example $g of third example. It is non-standardized form of data entry. It requires a separate algorithm for data processing. With standardized input one algorithm is good enough for data processing whereever it appears and data can be used for input as it is. $h - Medium (NR) This subfield should be treated same as I30$h. $k - Form (R) This subfield should be treated same as 130$k. Chapter 3: Study ofMARC21 elements 156 $n - Number of part/section of a work (R) This subfield should be treated same as 130$n. $p - Name of part/section of a work (R) This subfield should be treated same as 130$p. $s - Version (NR) This subfield should be treated same as 130$s. 246 - Varying Form of Title (R) Indicators First - Note/added entry controller 0 - Note, no added entry 1 - Note, added entry 2 - No note, no title added entry 3 - No note, added entry Second - Type of title # - No type specified 0 - Portion of title 1 - Parallel title 2 - Distinctive title 3 - Other title 4 - Cover title 5 - Added title page title 6 - Caption title 7 - Running title 8 - Spine title Chapter 3: Study ofMARC21 elements 157 Subfield Codes $a - Title proper/short title (NR) Data of this field should be transliterated. $b - Remainder of title (NR) Data of this field should be transliterated. $f- Date or sequential designation (NR) Same as 245$f and $g. $g - Miscellaneous information (NR) Data of this subfield needs to be translated. $h - Medium (NR) Should be treated as 130$h $i - Display text (NR) The data of this subfield should be translated. $n - Number of part/section of a work (R) Same as 130$n. $p - Name of part/section of a work (R) Same as 130$p. Chapter 3: Study ofMARCll elements 158 $5 - Institution to which field applies (NR) MARC21 defines the use of Control Subfield code to identify the name of the institute but it is easy to write the name of the institute and apply the transliteration algorithm of multilingual display. 247 - Former Title (R) Indicators First - Title added entry 0 - No added entry 1 - Added entry Second - Note controller 0 - Display note 1 - Do not display note Subfields $a - Title (NR) Same as 245$a. $b - Remainder of title (NR) Same as 245$b. $f- Date or sequential designation (NR) Same as 245$f Chapter 3: Study ofMARC21 elements 159 $g - Miscellaneous information (NR) Same as 245$g. $h - Medium (NR) Same as 245$h. $n - Number of part/section of a work (R) Same as 245Sn. $p - Name of part/section of a work (R) Same as 245$p. $x - International Standard Serial Number (NR) ISSN is itself a codified data. 250 - Edition Statement (NR) Subfield Codes $a - Edition statement (NR) Most of the time a number represents the edition of the document. But in many instances terms are also used for representing the edition of the document and much of these terms can be can be codified. If a number is used to represent the edition it can be directly used for display in any language but if a term is used that term needs to be translated in corresponding language and then displayed. For example, Rev. ed. Updated ed. Chapter 3: Study of MARCH elements 160 A study of 116745 records form OCLC demonstrates 18522 occurrences of the subfield. Out of 18522 occurrences 72 commonly used terms are extracted. The individual or combination of these terms used to define edition of the document. Numeric codes have been assigned to these terms and code is translated to Hindi, Kannada, Telugu and Bengali for multilingual display. The code is given in Appendix 3.16: 'MARC Code List for Edition Statement'. Individually or combination of them terms can be used to represent a particular edition. For example. Final Draft Paperback Edition, should be represented as, {Final (32) + Draft (27) + Paperback (49)} (32 + (27) + (49) If there is a number associated with the edition statement should be represented with number and | symbol. Number can be numeric or a word. For example, 1| 58+61 represents, 'First Revised Students. In the case of Indian languages, the word 'Edition' varies from one language to other. For example, In Hindi it is Samskaran (-ti-W'<"!), in Telugu it is Prati (SbLO), in Kannada Mudrana (rfDCJiW) and so on. The system should add corresponding word for edition according to the language at the end. The format for codified data entry in field 250$a should be Edition number (word or numeral) | codified terms | •M'MI zixiXijZi etc. Chapter 3: Study ofMARC21 elements 161 If the edition statement does not follow the code it should be transliterated. For example, 'Bell Tower Edition' $b - Remainder of edition statement (NR) Reminder of edition statement stores information like, statement of responsibility, parallel edition statement, roles etc. In case of statement of responsibility and parallel edition statement data needs to be transliterated where as roles should be translated using role codes. The format of rendering role and name should be same as suggested in 245$c. If the data is not codified that means it is either name of a person or parallel title, in this case data should be codified. 254 - Musical Presentation Statement (NR) Subfield Codes $a - Musical presentation statement (NR) This data can be codified. MARC21 field 008 for Music gives a list of code which can be adopted in this subfield. It has been translated to a three digit numeric code the first digit shows that the code is for musical item. Listing of the code is given in Appendix 3.21. 255 - Cartographic Mathematical Data (R) Subfleld Codes Sa - Statement of scale (NR) Following code should be followed in case of scales. More over this code is just illustrative which can be extended further. Chapter 3: Study ofMARCll elements. 162 Numeric Value Code 1 Scale 2 Scales differ or vary 3 Scale not given 4 Scale ca. For example, SaScale [1:6,336,000], 1" = 100 miles. Vertical scale [1:192,000]. 1/16" = approx. 1000'. SaScale vary can be rendered as Sal # [1:6,336,000]. 1" = 100 miles. Vertical scale [1:192,000]. 1/16" = approx. 1000'. Sa2 respectively. # is used as delimiter between scale code and data. Rest of the data should be transliterated. $b - Statement of projection (NR) Data should be taken as it is. Sc - Statement of coordinates (NR) Data should be taken as it is. $d - Statement of zone (NR) Data should be taken as it is. Chapter 3: Study ofMARC21 elements 163 $e - Statement of equinox (NR) Data should be taken as it is. $f- Outer G-ring coordinate pairs (NR) Data should be taken as it is. $g - Exclusion G-ring coordinate pairs (NR) Data should be taken as it is. 256 - Computer File Characteristics (NR) Characteristics of a computer file, such as the type of file, the number of records or statements. Subfleld Codes $a - Computer file characteristics (NR) Basically, there are two parts of the data. Part one is the data outside the circular brackets. This data represents the Type of computer file. Example, Computer data (2 files : 876,000, 775,000 records) Computer programs (2 files : 4300, 1250 bytes) MARC21 provides in field 008 Computer files a code for Type of computer file. Chapter 3: Study ofMARC21 elements. 164 Numeric value of the code is as follows, Numeric Code Value I Numeric data 2 Computer program 3 Representational 4 Document 5 Bibliographic data 6 Font 7 Game 8 Sound 9 Interactive multimedia 10 Online system or service 11 Combination 12 Unknown 13 Other 14 No attempt to code Table 3.9: Codes for Typed of Computer file The data inside the circular bracket should be transliterated. Thus the above mentioned example can be mentioned as, 1 (2 files : 876,000, 775,000 records) 2 (2 files : 4300, 1250 bytes) 257 - Country of Producing Entity For Archival Films (NR) Subfield Codes $a - Country of producing entity (NR) The code for name of the country can be taken from MARC country code numeric version. The subfield may contain the abbreviation [S.I.] when the country is unknown. For example, Saltaly ; France Chapter 3: Study ofMARC21 elements 165 Should be represented as $al36;96 260 - Publication, Distribution, Etc. (Imprint) (R) Indicators First - Sequence of publishing statements # - Not applicable/No information provided/Earliest available publisher 2 - Intervening publisher 3 - Cuaent/latest publisher Second - Undefined # - Undefined Subfield Codes $a - Place of publication, distribution, etc. (R) The name of the place is rendered same in all the languages so data of this field should be transliterated. $b - Name of publisher, distributor, etc. (R) The name of the publisher or distributor is rendered same in all the languages so data of this field should be transliterated. $c - Date of publication, distribution, etc. (R) Date format of ISO 8601 (yyyymmdd) should be followed. Chapter 3: Study ofMARCll elements 166 $e - Place of manufacture (NR) Same as $a. $f- Manufacturer (NR) Same as $b. $g - Date of manufacture (NR) Same as $c. 263 - Projected Publication Date (NR) Subfield Code $a - Projected publication date (NR) MARC21 recommends a six-digit date recorded in the pattern yyyymm. A hyphen (-) is used for an unknown portion of the date. So overall this data can be taken as it is. $al99412 $al998- $a200102 270 - ADDRESS (R) Indicators First - Level # - No level specified 1 - Primary 2 - Secondary Chapter 3: Study ofMARC21 elements 167 Second - Type of address # - No type specified 0 - Mailing 7 - Type specified in subfield $i Subfield Codes $a - Address (R) Data of this subfield should be transliterated. $b - City (NR) Name of the city should be transliterated. $c - State or province (NR) Name of state or province should be transliterated. $d - Country (NR) Country code should be adopted. For use of country code Appendix 3.1 should be referred. $e - Postal code (NR) Postal code is a numeric code for a particular place. This data should be taken as it is for display. $f- Terms preceding attention name (NR) Chapter 3: Study ofMARC21 elements. 168 The title associated with the attention name (e.g.. General, Dr. or Reverend) when the title precedes the name. The data should be transliterated. $g - Attention name (NR) The name of the person should be transliterated. $h - Attention position (NR) The name of the position can be codified. But if the code is not found data can be transliterated. $i - Type of address (NR) The type of address can be codified. For example, an illustrative code list can be, Numeric code Value 1 Billing 2 Mailing 3 Official 4 Residential $j - Specialized telephone number (R) The subfield stores phone number and specificity of the number. The specialty of the telephone is entered in circular bracket. For example, 270 10 $aP.O. Box 50007 Jb Pasadena IcCAJe 91115 Jj 1-213-681-2626 (24 hour hotline) Chapter 3: Study ofMARC2J elements 169 OCLC recommends following format of entering telephone number in a record, (28) [country code]-[area/city code]-[line number] Telephone number should picked up as it is and data inside circular bracket should be transliterated. $k - Telephone number (R) Same as $j but specificity of phone number is not recorded in this subfield. $1 - Fax number (R) Same as $k. $m - Electronic mail address (R) Data should be taken as it is. $n - TDD or TTY number (R) Data should be taken as it is. $p - Contact person (R) Name of the contact person should be transliterated. $q - Title of contact person (R) Same as $f Chapter 3: Study ofMARC21 elements 170 $r - Hours (R) The time should be recorded as hh.mm format where hh should be represented in terms of 24 hours. $z - Public note (R) A note data should be translated. $4 - Relator code (R) Numeric code of Role code should be used. 300 - Physical Description (R) Subfield Codes $a - Extent (R) In this subfield data consists of number of pages, volumes, cassettes, total playing time, etc., of the described item. The subfield covers Book, Computer files. Manuscripts, Non- projected graphic, Projected graphic, Music, Map, Motion pictures. Serials and Video recording. Each type of item has its own characteristics to describe. Often codes are defined within the MARC21 manual which is in turn converted to numeric. For identifying the type of item and the value of the extent characteristics three characters numeric code is used. The first character of the code represents type of item. Chapter 3: Study of MARCH elements. 171 For example, Numeric code Value 1 Book 2 Serials 3 Computer files 4 Music 5 Projected Graphics 6 Motion Pictures 7 Video recording 8 Map Table 3.10: Code for type of documents The second and third characters of code represent the corresponding extent value of the item. For example, 303 - represents CDROM of item type Computer files. Codes are given in Appendix 3.20. But the data in this subfield has two parts, first the extent (number) and second the characteristic of the item type. It difficult to differentiate between part one and part two of data so for the practical purposes this subfield is transliterated. $b - Other physical details (NR) This subfield contains data regarding physical characteristics such as illustrative matter, coloration, playing speed, groove characteristics, presence and kind of sound, number of channels, and motion picture presentation format. Chapter 3: Study ofMARCll elements. 172 Again like $a there are variety of characteristics which should be codified. MARC21 has codified much of the data and corresponding numeric value is given for demonstration. Rather four digits code is followed here. Since there can be many characteristics so the first two characters are used to represents the type of characteristics. It is not implemented in the system. For example, Numeric code Value 01 Material code 02 Coloration 03 Polarity 04 Sound 05 Speed 06 Channels 07 Groove 08 Illustration 09 Storage technique Table 3.11: Characteristic code of Document Second and third character represents the value for the characteristics. For example, 0508 -represents 160 rpm. The subfield Sb should be read always in the context of $a of the field. This subfield also has same difficulty as $a so for practical purposes this subfield has been transliterated. $c - Dimensions (R) Data of this subfield should be taken as it is. Scales can be transliterated. Chapter 3: Study of MARCH elements 173 $e - Accompanying material (NR) There are two parts to this subfield. The first part which is outside the parenthesis represents the type of material. The code used in $a can be used to represent the kind of accompanying material. For example, 801 - represents Atlas The value inside the parenthesis represents the other characteristics of accompanying material. A combination of codes from $a and $b should be used to represent the elements inside the parenthesis and the last element which is dimension should be transliterated. Example, 801(200 123, 19 115+126: 37 0203+803; 21 cm x 26 cm) This data should be interpreted as atlas( 200 pages, 19 leaves plate: 37 multi-coloured maps; 21 cm x 26 cm) 123 pages 115 leaves 126 plates 0203 multi-coloured 803 map Punctuations can be used as delimiters. $f- Type of unit (R) Data of this subfield should be transliterated. Chapter 3: Study ofMARCll elements 174 $g - Size of unit (R) Data of this subfield can be taken as it is. $3 - Materials specified (NR) This subfield should be translated. 306 - Playing Time (NR) Subfield Code $a - Playing time (R) Data is in format of hhmmss so nothing should be done where hh represents hours, mm represents minutes and ss represents seconds. 307 - Hours, Etc. (R) Indicators First - Display constant controller # - Hours 8 - No display constant generated Second - Undefined # - Undefined Subfleld Codes Sa - Hours (NR) Data in this subfield should be transliterated for multilingual display. Chapter 3: Study ofMARCll elements 175 $b - Additional information (NR) Data of this field should be translated. 310 - Current Publication Frequency (NR) Subfield Codes $a - Current publication frequency (NR) This subfield contains the frequency of the serials besides it also contains the information about the regularity of publication. MARC21 defines the code in 008 18 and 19 position for frequency and regularity. Both codes can be merged and numeric value is given to each element alone or combination of the codes can be used to display the frequency. Appendix 3.36: contains 'MARC Code List of Frequency'. Sometimes text is used with the code. Often the coded data is separated by a comma (,). Thus the data beyond comma can be transliterated. For example, Monthly, including annual cumulation Can be represented as 13, including annual comulation $b - Date of current publication frequency (NR) Data in this subfield is range of dates which can be entered as yyyymmdd format. Chapter 3: Study ofMARC21 elements 176 321 - Former Publication Frequency (R) The date is similar to the field 310 Current Publication Frequency and the field should be treated same as 310. Subfleld Codes $a - Former publication frequency (NR) $b - Dates of former publication frequency (NR) 340 - Physical Medium (R) Subfield Codes $a - Material base and configuration (R) This subfield contains data about physical material and the storage material in case of computer files. The code for physical material for the item is defined 300$b which can be used. Similarly 300$a codes are defined for storage medium for different kinds of electronic media. Like Motion pictures, video recording, sound recording etc. $b - Dimensions (R) This data should be transliterated. $c - Materials applied to surface (R) This data can be codified so that multilingual retrieval can be made possible, Chapter 3: Study ofMARC21 elements 177 $d - Information recording technique (R) The technique used to record the data in or on the material base (e.g., punched, molded, x-ray). This data can be codified so that multilingual retrieval is possible. $e - Support (R) The physical material on or on which records are mounted, bound, or otherwise supported. The material code specified in 300$b can be used for data codification. $f- Production rate/ratio (R) The normal rate or ratio at which the material must be used for the information to be meaningful (e.g., revolutions per minute for recordings). Data of this sub field should be transliterated. $h - Location within medium (R) The location of the described materials within the material base and configuration (e.g., baud, frame number). This data needs to be translated. $i - Technical specifications of medium (R) This subfield contains the name of the equipment required to read or access the information from the item. Chapter 3: Study ofMARC21 elements 178 The data of this subfield should be transliterated. $3 - Materials specified (NR) The data in this subfield can be translated. 342 - Geospatial Reference Data (R) Indicators First - Geospatial reference dimension 0 - Horizontal coordinate system 1 - Vertical coordinate system Second - Geospatial reference method 0 - Geographic 1 - Map projection 2 - Grid coordinate system 3 - Local planar 4 - Local 5 - Geodetic model 6 - Altitude 7 - Method specified in $2 8 - Depth Subfield Codes $a - Name (NR) The data of this subfield should be transliterated. Chapter 3: Study ofMARCll elements 179 Following subfields are numeric. Values should be taken as it is. $b - Coordinate or distance units (NR) $c - Latitude resolution (NR) $d - Longitude resolution (NR) $e - Standard parallel or oblique line latitude (R) $f- Oblique line longitude (R) $g - Longitude of central meridian or projection center (NR) $h - Latitude of projection origin or projection center (NR) Si - False easting (NR) $j - False northing (NR) $k - Scale factor (NR) $1 - Height of perspective point above surface (NR) $m - Azimuthal angle (NR) $n - Azimuth measure point longitude or straight vertical longitude from pole (NR) $o - Landsat number and path number (NR) $p - Zone identifier (NR) $r - Semi-major axis (NR) St - Vertical resolution (NR) Sq - Ellipsoid name (NR) The name of this subfield should be transliterated. Ss - Denominator of flattening ratio (NR) Textual as well as numeric both kind of data is stored in this subfield. Thus based on data field needs to be transliterated. Chapter 3: Study ofMARCll elements 180 Sw - Local planar or local georeference information (NR) Textual as well as numeric both kind of data is stored in this subfield. Thus based on data field needs to be transliterated. $u - Vertical encoding method (NR) The data of this subfield should be translated. $v - Local planar, local, or other projection or grid description (NR) and The data of these subfields should be transliterated. $2 - Reference method used (NR) The data of these subfields should be transliterated. 343 - Planar Coordinate Data (R) Subfield Codes $a - Planar coordinate encoding method (NR) Data of this subfield should be transliterated. $b - Planar distance units (NR) Measures should be transliterated. $c - Abscissa resolution (NR) Since the data is numeric in this subfield so it should be taken as it is. Chapter 3: Study ofMARC21 elements. 181 $d - Ordinate resolution (NR) The data is numeric in this subfield so it should be taken as it is. $e - Distance resolution (NR) The data is numeric in this subfield so it should be taken as it is. Sf- Bearing resolution (NR) The data is numeric in this subfield so it should be taken as it is. $g ' Bearing units (NR) This subfield contains measuring unit which should be transliterated. $h - Bearing reference direction (NR) A code can be used for direction, Numeric code Value 1 East 2 West 3 North 4 South Table 3.12: Direction code A combination of the these codes with plus (+) can be used for defining other directions like North-East, South-East etc. $i - Bearing reference meridian (NR) The data of this subfield should be translated. Chapter 3: Study ofMARCIl elements 182 351 - Organization and Arrangement of Materials (R) Subfield Codes $a - Organization (R) The data of this subfield should be translated. $b - Arrangement (R) A code can be developed about different types of arrangement. A good example can be sited from library classification. The principles of helpful sequence can be adopted for codification of arrangement. The numeric code for arrangement is listed in Appendix 3.37: 'MARC Code List for Arrangement'. A combination of codes values can also be used for arrangement. $c - Hierarchical level (NR) The hierarchical level can be codified. A code can be built for representation of hierarchical level. Numeric code Value 1 Series 2 Group 3 Subgroup 4 Packaging unit Table 3.13: Hierarchy Code $3 - Materials specified (NR) Data of this subfield should be translated. Chapter 3: Study ofMARCll elements. 183 352 - Digital Graphic Representation (R) Subfield Codes $a - Direct reference method (NR) Basically this subfield contains the data about the type of graphics used vector, raster or point. The data of this subfield can be easily codified. An illustrative code is as follows, Numeric code Value I Point 2 Vector 3 Raster Table 3.14: Graphic code $b - Object type (R) The specific type of point vector or raster graphic objects used to locate geometric locations in a data set. This field can be codified. $c - Object count (R) Data is numeric. It can be taken as it is. $d - Row count (NR) Value is numeric. It can be taken as it is. $e - Column count (NR) Value is numeric. It can be taken as it is. Chapter 3: Study of MARCH elements. 184 $f- Vertical count (NR) Value is numeric. It can be taken as it is. $g - VPF topology level (NR) OCLC manual defines, "The level of completeness of the topology carried by the data set. Use levels defined in Department of Defense 1992, Vector Product Format (MIL-STD-600006; Philadelphia PA/Department of Defense/Defense Printing/Service Detachment Office)." (29). The data for this subfield is already codified which can be used but unfortunately there are no examples for this subfield in MARC21 manual and OCLC manual. $i - Indirect reference description (NR) The data of this subfield should be translated. $q - Format of the digital image (R) A code of different format of graphic files can be developed. An illustrative example is, Numeric Code Value 1 Bitmap 2 Jpeg 3 Gif 4 Png Chapter 3: Study ofMARC21 elements 185 355 - Security Classification Control (R) Indicators First - Controlled element 0 - Document 1 - Title 2 - Abstract 3 - Contents note 4 - Author 5 - Record 8 - Other element Subfield Codes $a - Security classification (NR) A code of terms for security classification can be developed. As follows, Numeric code Value 1 Unclassified 2 Secret 3 Top secret 4 Confidential Table 3.15: Security classification code This code list is only illustrative and can be further expanded. $b - Handling instructions (R) The data in this subfield can be free text which needs to be translated. Moreover this subfield is localized that means the handling information may Chapter 3: Study ofMARCll elements 186 defer from organization to organization. If required, localized codes can be developed for this subfield. $c - External dissemination information (R) The data in this subfield can be free text which needs to be translated. $d - Downgrading or declassification event (NR) Often after a certain period document lose its importance (phenomena of obsolescent) in term of meaning, use and so on and then it is required to change its class or grade. The data regarding this is stored in this field. Often this subfield contains name or the person or organization who gives consent on change of grading of the item. The data needs to be transliterated. $e - Classification system (NR) The name of the scheme should be transliterated. $f- Country of origin code (NR) Numeric code of countries can be used. Code in 'Appendix 3.1 country code' should be used. $g - Downgrading date (NR) Date should be mentioned in yyyymmdd format. $h - Declassification date (NR) Date should be mentioned in yyyymmdd format. Chapter 3: Study of MARCH elements 187 $j - Authorization (R) The name of the organization should be transliterated. 357 - Onginator Dissemination Control (NR) Specifications pertaining to originator (i.e., author, producer) control of dissemination of the material in hand. Subfield $a contains a specific term denoting that the originator has control over the material. Subfields $a - Originator control term (NR) This field is codified and this codification is done by the originating agency. $b - Originating agency (R) This subfield contains the name of originating agency. MARC21 uses the organization code but it is better using the full name of the agency and transliterating. $c - Authorized recipients of material (R) This subfield contains name of the authorized recipient of material which should be transliterated for the display in other languages. $g - Other restrictions (R) The data of this subfield is free text which requires translation. Chapter 3: Study of MARCH elements 188 362 - Dates of Publication and/or Sequential Designation (R) Indicators First - Format of date 0 - Formatted style 1 - Unformatted note Second - Undefined # - Undefined Subfield Codes $a - Dates of publication and/or sequential designation (NR) If the data entry in this subfield is done in a particular format, this formatted data can be used. MARC21 gives few examples of data entry, $aVol. l,no. 1 (Apr. 1981)- $al968- $aVol. 1, no. 1 (Apr. 1983)-v. 1, no. 3 (June 1983) SaBegan with 1930 issue.$zCf Letter from Ak. State Highway Dept., Aug. 6, 1975. $aCeasedwith2(1964) $aVol. 77, num. 1 (enero-abr. 1981)- In the above mentioned data example 4 and 5 shows the use of free text 'Began with' and 'Ceased with'. The use of this kind of free text creates problem in standardization. AACR2 Rule 12.3C to 12.3G avoids using any kind of free text. That means, if free text could be avoided the elements used in subfield could be machine processed (30). If numerals are used to represent volume, issue and part, rest of the data of the subfield can be transliterated or else date can also be written according to ISO 8601. Chapter 3: Study ofMARClI elements 189 Numeric code Value 1 Volume 2 Number 3 Issue 4 Part Table 3.16: Code for Level of Item Now the data can be represented as $all,21 (April 1981)- $z - Source of information (NR) Name of the source should be transliterated. 365 - Trade Price (R) Subfield Codes $a - Price type code (NR) Data is codified numeric data which can be used. $b - Price aniount (NR) Price of the item is always mentioned in numerals. Hence, it can be used as it is. $c - Currency code (NR) ISO 4217, which is maintained by Business Information, is numeric code for currency which can be adopted in subfield as it is. (14) Chapter 3: Study nj MARC2I elements 190 $d - Unit of pricing (NR) The data is numeric hence it can be used as it is. $e - Price note (NR) The data in this subfield is textual note about the pricing which requires translation. $f- Price effective from (NR) Date format of ISO 8601 can be adopted. $g - Price effective until (NR) Date format of ISO 8601 can be adopted. $h - Tax rate ] (NR) The data is numeric hence it can be used as it is. $i - Tax rate 2 (NR) The data is numeric hence it can be used as it is. $j - ISO country code (NR) The data of this field itself is codified. Hence, it can be used as it is. Chapter 3: Study of MARCH elements 191 $k - MARC country code (NR) Numeric country code of MARC which is developed for the purpose of this research should be used, which can be found in Appendix 3.1 $m - Identification of pricing entity (NR) The name of the pricing entity should be transliterated. $2 - Source of price type code (NR) The name of the source should be transliterated. 366 - Trade Availability Information (R) Subfield Codes $a - Publishers' compressed title identification (NR) Data requires transliteration. $b - Detailed date of publication (NR) Date should follow yyyymmdd format of ISO 8601. $c - Availability status code (NR) A code for availability can be developed. Following is an illustration, which can be further extended. Numeric code Value 1 Reprint 2 Not in Print 3 In Print 4 Out of stock Chapter 3: Study ofMARC21 elements 192 Often it is seen that data is followed by date. The date can be recorded according to ISO 8601 format. $d - Expected next availability date (NR) Date should follow yyyymmdd format of ISO 8601. $e - Note (NR) The data of note should be translated. $f- Publishers' discount category (NR) This code depends on the organization so individual organization needs to create their own code. $g - Date made out of print (NR) Date should follow yyyymmdd format of ISO 8601. $j - ISO country code (NR) Same as 365 $j. $k - MARC country code (NR) Same as 365$k. $m - Identification of agency (NR) Name of the agency should be transliterated. Chapter 3: Study ofMARC21 elements 193 $2 - Source of availability status code (NR) Name of the source should be transliterated. 440 - Series Statement/Added Entry-Title (R) Indicators First - Undefined # - Undefined Second - Nonfiling characters 0-9 - Number of nonfiling characters Subfield Codes Sa - Title (NR) Title of the document will be same in all the languages so the data of this subfield should be transliterated. $n - Number of part/section of a work (R) Number should be recorded with numerals but in case if section is mentioned by an alphabet or other script character it should be transliterated. $p - Name of part/section of a work (R) The data of this subfield should be transliterated. Chapter 3: Study ofMARC21 elements 194 $v - Volume number/sequential designation (NR) Numerals should be used to record the number or sequence. $x - International Standard Serial Number (NR) Record ISSN as it is. 490 - Series Statement (R) Indicators First - Specifies whether series is traced A value that indicates whether the record contains a corresponding 800-830 series added entry field. 0 - Series not traced 1 - Series traced differently Second- Undefined # - Undefined Subfield Codes $a - Series statement (R) The series statement should be transliterated. $1 - Library of Congress call number (NR) This subfield holds LC call number so it should be maintained as it is. Chapter 3: Study ofMARC21 elements 195 $v - Volume number/sequential designation (R) Numerals should be used to record volume number or sequence. $x - International Standard Serial Number (NR) Record ISSN as it is. 500 - General Note (R) Subfield Codes $a - General note (NR) The data of this subfield should be translated. $3 - Materials specified (NR) The data of this subfield should be translated. $5 - Institution to which field applies (NR) Name of the institute should be transliterated. 501 - With Note (R) Subfield Codes $a - With note (NR) The data of this subfield should be translated. Chapter 3: Study ofMARC21 elements 196 $5 - Institution to which field applies (NR) Name of the institute should be transliterated. 502 - Dissertation Note (R) Subfield Codes 5a - Dissertation note (NR) The data of this subfield should be translated. 504 - Bibliography, Etc. Note (R) Subfield Codes $a - Bibliography, etc. note (NR) The data of this subfield should be translated. $b - Number of references (NR) Numbers are used to record the references. Hence, it can be used as it is. 505 - Formatted Contents Note (R) Indicators First - Display constant controller 0 - Contents 1 - Incomplete contents 2 - Partial contents 8 - No display constant generated Chapter 3: Study of MARCH elements 197 Second - Level of content designation # - Basic 0 - Enhanced Subfield Codes $a - Formatted contents note (NR) The data of this subfield should be translated. $g - Miscellaneous information (R) The data of this subfield should be translated. $r - Statement of responsibility (R) The data of this subfield should be transliterated. $t - Title (R) The data of this subfield should be transliterated. $u - Uniform Resource Identifier (R) This subfield records URI of the document so it should be maintained as it is. 506 - Restrictions on Access Note (R) Subfield Codes $a - Terms governing access (NR) The data of this subfield should be translated. Chapter 3: Study of MARCH elements 198 $b - Jurisdiction (R) The data of this subfield should be translated. $c - Physical access provisions (R) The data of this subfield should be translated. $d - Authorized users (R) The data of this subfield should be translated. $e - Authorization (R) The data of this subfield should be translated. $u - Uniform Resource Identifier (R) This subfield records URI of the document, so it should be maintained as it is. $3 - Materials specified (NR) This subfield should be translated. $5 - Institution to which field applies (NR) The data of this subfield should be transliterated. Chapter 3: Study ofMARC21 elements 199 507 - Scale Note for Graphic Material (NR) Subfield Codes $a - Representative fraction of scale note (NR) The data of this subfield should be translated. There are scales in Indian languages for measurement but unfortunately there is no interoperability among different language scales. So it is very difficult to standardized scale for Indie languages. In the note field often scale data entered are free text so that is why we cannot look for data codification. $b - Remainder of scale note (NR) The data of this subfield should be translated. 508 - Creation/Production Credits Note (R) Subfield Codes $a - Creation/production credits note The data of this subfield should be translated. 510 - Citation/References Note (R) Indicators First - Coverage/location in source 0 - Coverage unknown 1 - Coverage complete Chapter 3: Study ofMARCll elements 200 2 - Coverage is selective 3 - Location in source not given 4 - Location in source given Second - Undefined # - Undefined Subfield Codes $a - Name of source (NR) The data of this subfield should be translated. $b - Coverage of source (NR) The data of this subfield should be translated. $c - Location within source (NR) The data of this subfield should be transliterated. $x - International Standard Serial Number (NR) This subfield records ISSN in this subfield which should be maintained as it is. $3 - Materials specified (NR) This subfield should be translated. Chapter 3: Study ofMARCll elements 201 511 - Participant or Performer Note (R) Indicators First - Display constant controller 0 - No display constant generated 1 - Cast Second - Undefined # - Undefined Subfield Codes $a - Participant or performer note (NR) The data of this subfield should be translated. 513 - Type of Report and Period Covered Note (R) Subfield Codes $a - Type of report (NR) The data of this subfield should be translated. $b - Period covered (NR) Formatted dates should be used. Chapter 3: Study ofMARCll elements 202 514 - Data Quality Note (NR) Subfleld Codes $a - Attribute accuracy report (NR) Data of this subfield should be translated. $b - Attribute accuracy value (R) Data of this subfield should be translated. $c - Attribute accuracy explanation (R) Data of this subfield should be translated. $d - Logical consistency report (NR) Data of this subfield should be translated. $e - Completeness report (NR) The report can be complete or not complete which can be codified numerically. $f- Horizontal position accuracy report (NR) Data of this subfield should be translated. $g - Horizontal position accuracy value (R) Data of this subfield should be translated. Chapter 3: Study of MARCH elements 203 $h - Horizontal position accuracy explanation (R) Data of this subfield should be translated. $i - Vertical positional accuracy report (NR) Data of this subfield should be translated. $j - Vertical positional accuracy value (R) Data of this subfield should be translated. $k - Vertical positional accuracy explanation (R) Data of this subfield should be translated. $m - Cloud cover (NR) Data of this subfield should be translated. $u - Uniform Resource Identifier (R) Records URI of the document so it should be maintained as it is. $z - Display note (R) Data of this subfield should be translated. Chapter 3: Study ofMARCll elements 204 515 - Numbering Peculiarities Note (R) Subfield Codes $a - Numbering peculiarities note (NR) Data of this subfield should be translated. 516- Type of Computer File or Data Note (R) Indicators First - Display constant controller # - Type of file 8 - No display constant generated Second - Undefined # - Undefined Subfield Codes $a - Type of computer file or data note (NR) Data of this subfield should be translated. 518 - Date/Time and Place of an Event Note (R) Subfield Codes $a - Date/time and place of an event note (NR) Data of this subfield should be translated. Chapter 3: Study ofMARC21 elements 205 $3 - Materials specified (NR) This subfield should be translated. 520 - Summary, Etc. (R) Indicators First - Display constant controller # - Summary 0 - Subject 1 - Review 2 - Scope and content 3 - Abstract 8 - No display constant generated Second - Undefined # - Undefined Subfield Codes $a - Summary, etc. note (NR) Data of this subfield should be translated. $b - Expansion of summary note (NR) Data of this subfield should be translated. $u - Uniform Resource Identifier (R) Record URI of the document so it should be maintained as it is. Chapter 3: Study ofMARCIl elements 206 $3 - Materials specified (NR) This subfield should be translated. 521 - Target Audience Note (R) Indicators First - Display constant controller # - Audience 0 - Reading grade level 1 - Interest age level 2 - Interest grade level 3 - Special audience characteristics 4 - Motivation interest level 8 - No display constant generated Second - Undefined # - Undefined Subfield Codes $a - Target audience note (R) Data of this subfield should be translated. $b - Source (NR) Data of this subfield should be transliterated. Chapter 3: Study ofMARC21 elements 207 $3 - Materials specified (NR) This subfield should be translated. 522 - Geographic Coverage Note (R) Indicators First - Display constant controller # - Geographic coverage 8 - No display constant generated Second - Undefined # - Undefined Subfield Codes $a - Geographic coverage note (NR) Data of this subfield should be translated. 524 - Preferred Citation of Described Materials Note (R) Indicators First - Display constant controller # - Cite as 8 - No display constant generated Second - Undefined # - Undefined Chapter 3: Study ofMARC21 elements 208 Subfield Codes $a - Preferred citation of described materials note (NR) Data of this subfield should be translated. $2 - Source of schema used (NR) Data of this subfield should be transliterated. $3 - Materials specified (NR) This subfield should be translated. 525 - Supplement Note (R) Subfield Codes $a - Supplement note (NR) Data of this subfield should be translated. 526 - Study Program Information Note (R) Indicators First - Display constant controller 0 - Reading program 8 - No display constant generated Second - Undefined # - Undefined Chapter 3: Study ofMARC21 elements 209 Subfield Codes $a - Program name (NR) Data of this subfield should be translated. $b - Interest level (NR) Data of this subfield should be translated. $c - Reading level (NR) Data of this subfield should be translated. $d - Title point value (NR) Data of this subfield should be translated. $i - Display text (NR) Data of this subfield should be translated. $x - Nonpublic note (R) Data of this subfield should be translated. $z - Public note (R) Data of this subfield should be translated. $5 - Institution to which field applies (NR) Data of this subfield should be transliterated. Chapter 3: Study ofMARC21 elements 210 530 - Additional Physical Form Available Note (R) Subfield Codes $a - Additional physical form available note (NR) Data of this subfield should be translated. $b - Availability source (NR) Data of this subfield should be translated. $c - Availability conditions (NR) Data of this subfield should be translated. $d - Order number (NR) Data is a specific number so nothing has to be done. $u - Uniform Resource Identifier (R) This subfield records URI of the document so nothing should be done. $3 - Materials specified (NR) This subfield should be translated. 533 - Reproduction Note (R) Subfield Codes $a - Type of reproduction (NR) Data of this subfield should be translated. Chapter 3: Study ofMARC21 elements 211 $b - Place of reproduction (R) Data of this subfield should be transliterated. $c - Agency responsible for reproduction (R) Data of this subfield should be transliterated. $d - Date of reproduction (NR) Date should be recorded in the format of yyyymmdd. $e - Physical description of reproduction (NR) Data of this subfield should be translated. $f' Series statement of reproduction (R) Data of this subfield should be translated. $m - Dates and/or sequential designation of issues reproduced (R) Data of this subfield should be translated. $n - Note about reproduction (R) Data of this subfield should be translated. $3 - Materials specified (NR) This subfield should be translated. Chapter 3: Study ofMARCll elements 212 534 - Original Version Note (R) Subfield Codes $a - Main entry of original (NR) Data of this subfield should be translated. $b - Edition statement of original (NR) Data of this subfield should be translated. $c - Publication, distribution, etc. of original (NR) Data of this subfield should be translated. $e - Physical description, etc. of original (NR) Data of this subfield should be translated. $f- Series statement of original (R) Data of this subfield should be translated. $k - Key title of original (R) Data of this subfield should be transliterated. $1 - Location of original (NR) Data of this subfield should be transliterated. Chapter 3: Study ofMARC21 elements 213 $m - Material specific details (NR) This field should be translated. $n - Note about original (R) Data of this subfield should be translated. $p - Introductory phrase (NR) Data of this subfield should be translated. $t - Title statement of original (NR) Data of this subfield should be translated. $x - International Standard Serial Number (R) Record ISBN of the document in this subfield. $z - International Standard Book Number (R) Record ISSN of the document in this subfield. 535 - Location of Originals/Duplicates Note (R) Indicators First - Additional information about custodian 1 - Holder of originals 2 - Holder of duplicates Chapter 3: Study ofMARC2J elements 214 Second - Undefined # - Undefined Subfleld Codes $a - Custodian (NR) Data of this subfield should be transliteration. $b - Postal address (R) Postal address as such can be entered in any language. But for practical purpose entering postal address in other script which is unknown to other has no meaning. Hence, it is good to enter postal address in English but for databases one can enter postal address in any language/script which can be transliterated on the fly at time of printing. So, data of this subfield should be transliterated. $c - Country (R) Data of this subfield should be transliterated. $d - Telecommunications address (R) Data of this subfield should be transliterated. $g - Repository location code (NR) Data of this subfield should be transliterated. $2 - Materials specified (NR) This subfield should be translated. Chapter 3: Study ofMARC21 elements 215 556 - Funding Information Note (R) Subfield Codes $a - Text of note (NR) Data of this subfield should be translated. $b - Contract number (R) Data is an identification number which is numeric data so it should be maintained as it is. $c - Grant number (R) Data is an identification number which is numeric data so it should be maintained as it is. $d - Undifferentiated number (R) Data is an identification number which is numeric data so it should be maintained as it is. $e - Program element number (R) Data is an identification number which is numeric data so it should be maintained as it is. $f- Project number (R) Data is an identification number which is numeric data so it should be maintained as it is. Chapter 3: Study ofMARCll elements 216 $g - Task number (R) Data is an identification number which is numeric data so it should be maintained as it is. $h - Work unit number (R) Data is an identification number which is numeric data so it should be maintained as it is. 538 - System Details Note (R) Subfleld Codes $a - System details note (NR) Data of this subfield should be translated. $i - Display text (NR) Data of this subfield should be translated. Su - Uniform Resource Identifier (R) Record URI of the document so it should be maintained as it is. $3 - Materials specified (NR) This subfield should be translated. Chapter 3: Study ofMARC21 elements 217 540 - Terms Governing use and Reproduction Note (R) Subfield Codes $a - Terms governing use and reproduction (NR) Data of this subfield should be translated. $b - Jurisdiction (NR) Data of this subfield should be translated. $c - Authorization (NR) Data of this subfield should be translated. $d - Authorized users (NR) Data of this subfield should be translated. $u - Uniform Resource Identifier (R) Record URI of the document so it should be maintained as it is. $3 - Materials specified (NR) This subfield should be translated. $5 - Institution to which field applies (NR) Data of this subfield should be transliterated. Chapter 3: Study ofMARC21 elements 218 541 - Immediate Source of Acquisition Note (R) Subfield Codes $a - Source of acquisition (NR) Data of this subfield should be transliterated. Sometimes one or two words in the data needs to be translated for understanding the full meaning. For example, $cGift;$aLeavitt Hunt's daughter, Mrs. William E. Patterson;$dl947 Much of the meaning can be conveyed using transliteration because source will be name of a person or organization. $b - Address (NR) Data of this subfield should be transliterated. $c - Method of acquisition (NR) Data of this subfield should be translated. $d - Date of acquisition (NR) Date should be recorded in the format of yyyymmdd. $e - Accession number (NR) Data is identification number so it should be maintained as it is. $f- Owner (NR) Data of this subfield should be transliteration. Chapter 3: Study ofMARCll elements 219 $h - Purchase price (NR) Price is always mentioned in terms of currency. This subfield contains data about type of currency as well as numeric value to state the amount. Though numeric currency code can be used as mentioned in 'Appendix 3.4 Currency code', it is very difficult to separate the type of currency from amount. So, it is good to transliterate the subfield for display purpose in Indian languages. $n - Extent (R) The subfield contains number of items required so it should be maintained as it is. $0 - Type of unit (R) The name of the unit should be transliterated. $3 - Materials specified (NR) This subfield should be translated. $5 - Institution to which field applies (NR) Data of this subfield should be transliterated. 544 - Location of Other Archival Materials Note (R) Indicators First - Relationship # - No information provided 0 - Associated materials Chapter 3: Study ofMARC21 elements 220 1 - Related materials Second - Undefined # - Undefined Subfield Codes $a - Custodian (R) Data of this subfield should be transliterated. $b - Address (R) Data of this subfield should be transliterated. $c - Country (R) Country code should be used. Appendix 3.1 can be used for country codes. $d - Title (R) Data of this subfield should be transliterated. $e - Provenance (R) The subfield contains information about history of custody of the described materials since their creation, including any changes that successive custodians have made to them so the field should be translated. $n - Note (R) Data of this subfield should be translated. Chapter 3: Study of MARCH elements 221 $S ' Materials specified (NR) This subfield should be translated. 545 - Biographical or Historical Data (R) Indicators First - Type of data # - No information provided 0 - Biographical sketch 1 - Administrative history Second - Undefined # - Undefined Subfield Codes $a - Biographical or historical note (NR) i • Data of this subfield should be translated. $h - Expansion (NR) Data of this subfield should be translated. $u - Uniform Resource Identifier (R) Record URI of the document so it should be maintained as it is. Chapter 3: Study ofMARCll elements. 222 546 - Language Note (R) Subfield Codes $a - Language note (NR) Data of this subfield should be translated. $b - Information code or alphabet (R) This field should be codified. An illustration of code is as follows which can be expanded further, Numeric Code Value 1 Arabic alphabet 2 Arabic numerals 3 Braille 4 Ciphers 5 Cyrillic alphabet 6 Greek alphabet 7 Hebrew alphabet 8 Hieroglyphics 9 Musical notation systems 10 Pictograms n Roman alphabet 12 Roman numerals $3 - Materials specified (NR) Data of this subfield should be translated. 547 - Former Title Complexity Note (R) Subfield Codes $a - Former title complexity note (NR) Data of this subfield should be translated. Chapter 3: Study ofMARC21 elements 223 550 - Issuing Body Note (R) Subfield Codes $a - Issuing body note (NR) Data of this subfield should be translated. 552 - Entity and Attribute Information Note (R) Subfield Codes $a - Entity type label(NR) Data of this subfield should be translated. $b - Entity type definition and source(NR) Data of this subfield should be translated. $c - Attribute label(NR) Data of this subfield should be translated. $d - Attribute definition and source (NR) Data of this subfield should be translated. $e - Enumerated domain value (R) Data of this subfield should be translated. Chapter 3: Study ofMARC21 elements 224 $f- Enumerated domain value definition and source(R) Data of this subfield should be translated. $g - Range domain minimum and maximum(NR) Data are numbers so it should be maintained as it is. $h - Codeset name and source(NR) Data of this subfield should be transliterated. $i - Unrepresentable domain(NR) Data of this subfield should be transliterated. $j - Attribute units of measurement and resolution(NR) Data of this subfield should be codified according to some standards. $k' Beginning date and ending date of attribute values(NR) Date should be recorded in the format of yyyymmdd. $1 - Attribute value accuracy(NR) Data of this subfield should be codified. For example 1 Tested 2 Untested and, so on. Chapter 3: Study of MARCH elements 225 $m - Attribute value accuracy explanation (NR) Data of this subfield should be translated. $n - Attribute measurement frequency (NR) Data is number so it should be maintained as it is. $o - Entity and attribute overview (R) Data of this subfield should be translated. $p - Entity and attribute detail citation (R) Data of this subfield should be translated. $u - Uniform Resource Identifier (R) Record URI of the document so it should be maintained as it is. $z - Display note(R) Data of this subfield should be translated. 555 - Cumulative Index/Finding Aids Note (R) Indicators First - Display constant controller #- Indexes 0 - Finding aids 8 - No display constant generated Chapter 3: Study ofMARCll elements 226 Second- Undefined # - Undefined Subfield Codes $a - Cumulative index/finding aids note (NR) Data of this subfield should be translated. $b - Availability source (R) The subfield contains data about the organizational unit or vendor from which finding aids or other documentation may be obtained. So this subfield should be translated. But if they are names of person or place it can be translated. $c - Degree of control (NR) The subfield contains data about the extent of administrative, bibliographic, or physical control available over the described materials. So this subfield should be translated. $d - Bibliographic reference (NR) The subfield contains data about a citation to a published or unpublished index or finding aid when it is not cataloged with the described item. So this subfield should be translated. $u - Uniform Resource Identifier (R) Record URI of the document so it should be maintained as it is. Chapter 3: Study ofMARC21 elements 227 $3 - Materials specified (NR) Data of this subfield should be translated. 556 - Information About Documentation Note (R) Indicators First' Display constant controller # - Documentation 8 - No display constant generated Second - Undefined # - Undefined Subfield Codes $a - Information about documentation note (NR) Data of this subfield should be translated. $z - International Standard Book Number (R) Data is ISBN so it should be maintained as it is. 561 - Ownership and Custodial History (R) Subfield Codes Sa - History (NR) Data of this subfield should be translated. Chapter 3: Study of MARCH elements 228 $3 - Materials specified (NR) Data of this subfield should be translated. $5 - Institution to which field applies (NR) Data of this subfield should be transliterated. 562 - Copy and Version Identification Note (R) Subfield Codes $a - Identifying markings (R) Data of this subfield should be translated. $b - Copy identification (R) Data of this subfield should be translated. $c - Version identification (R) Data of this subfield should be translated. $d - Presentation format (R) Data of this subfield should be translated. $e - Number of copies (R) Data is numeric so it should be maintained as it is. Chapter 3: Study ofMARCll elements 229 $3 - Materials specified (NR) Data of this subfield should be translated. $5 - Institution to which field applies (NR) Data of this subfield should be transliterated. 563 - Binding Information (R) Subfield Codes $a - Binding note (NR) Data of this subfield should be translated. Su - Uniform Resource Identifier (R) Record URI of the document so it should be maintained as it is. $3 - Materials specified (NR) Data of this subfield should be translated. $5 - Institution to which field applies (NR) Data of this subfield should be transliterated. 565 - Case File Characteristics Note (R) Indicators First - Display constant controller # - File size Chapter 3: Study ofMARC21 elements 230 0 - Case file characteristics 8 - No display constant generated Second - Undefined # - Undefined Subfield Codes $a - Number of cases/variables (NR) Data is identification number so it should be maintained as it is. $b - Name of variable (R) Data of this subfield should be transliterated. $c - Unit of analysis (R) Data of this subfield should be translated. $d - Universe of data (R) Data of this subfield should be translated. $e - Filing scheme or code (R) Data of this subfield should be translated. $3 - Materials specified (NR) Data of this subfield should be translated. Chapter 3: Study ofMARC21 elements 231 567- Methodology Note (R) Indicators First - Display constant controller # - Methodology 8 - No display constant generated Second - Undefined # - Undefined Subfield Codes $a - Methodology note (NR) Data of this subfield should be translated. 580 - Linking Entry Complexity Note (R) Subfield Codes $a - Linking entry complexity note (NR) Data of this subfield should be translated. 581 - Publications About Described Materials Note (R) Indicators First - Display constant controller # - Publications 8 - No display constant generated Chapter 3: Study ofMARC21 elements 232 Second - Undefined # - Undefined Subfield Codes $a - Publications about described materials note (NR) Data of this subfield should be translated. $z - International Standard Book Number (R) This subfield records ISBN of the item so it should be maintained as it is. $3 - Materials specified (NR) Data of this subfield should be translated. 583 - Action Note (R) Subfield Codes $a - Action (NR) Data of this subfield should be translated. $b - Action identification (R) Data of this subfield should be translated. Chapter 3: Study ofMARC21 elements 233 $c - Time/date of action (R) Date and time should be recorded according to ISO 8601 format i.e. yyyymmddhhmm. $d - Action interval (R) Data of this subfield should be translated. $e - Contingency for action (R) Data of this subfield should be translated. $f- Authorization (R) Data of this subfield should be translated. $h - Jurisdiction (R) Data of this subfield should be translated. $i - Method of action (R) Data of this subfield should be translated. $j - Site of action (R) Data of this subfield should be translated. $k - Action agent (R) Data of this subfield should be translated. Chapter 3: Study ofMARC21 elements. 234 $1 - Status (R) The data of this subfield can be codified. An illustration is as follows which can extend further, Numeric Code Value 1 Filmed 2 ' Digitized 3 Microfilmed $n - Extent (R) This subfield contains numbers for this data can be used as it is. $o - Type of unit (R) Data of this subfield should be transliterated. $u - Uniform Resource Identifier (R) Record URI of the document so it should be maintained as it is. $x - Nonpublic note (R) Data of this subfield should be translated. $z - Public note (R) Data of this subfield should be translated. $2 - Source of term (NR) Data of this subfield should be transliterated. Chapter 3: Study ofMARCll elements 235 $3 - Materials specified (NR) Data of this subfield should be translated. $5 - Institution to which field applies (NR) Data of this subfield should be transliterated. 584 - Accumulation and Frequency of Use Note (R) Subfield Codes $a - Accumulation (R) Data is unit of measurement. Unit needs to be transliterated. $b - Frequency of use (R) Data of this subfield should be translated. $3 - Materials specified (NR) Data of this subfield should be translated. $5 - Institution to which field applies (NR) Data of this subfield should be transliterated. Chapter 3: Study of MARCH elements 236 585 - Exhibitions Note (R) Subfield Codes $a - Exhibitions note (NR) Data of this subfield should be translated. $3 - Materials specified (NR) Data of this subfield should be translated. $5 - Institution to which field applies (NR) Data of this subfield should be transliterated. 586 - Awards Note (R) Indicators First - Display constant controller # - Awards 8 - No display constant generated Second - Undefined # - Undefined Subfield Codes $a - Awards note (NR) Data of this subfield should be translated. Chapter 3: Study ofMARCU elements 237 $3 - Materials specified (NR) Data of this subfield should be translated. 600 - Subject Added Entry-Personal Name (R) Indicators First - Type of personal name entry element 0 - Forename 1 - Surname 3 - Family name Second - Thesaurus 0 - Library of Congress Subject Headings 1 - LC subject headings for children's literature 2 - Medical Subject Headings 3 - National Agricultural Library subject authority file 4 - Source not specified 5 - Canadian Subject Headings 6 - Repertoire de vedettes-matiere 7 - Source specified in subfield $2 Subfield Codes All the subfields are same as field '100 - Main Entry -Personnel Name' except the follows, Chapter 3: Study ofMARCll elements 238 $h - Medium (NR) Different media can be codified. A numeric code for medium should be developed. Appendix '3.15: MARC Code List for Medium' should be followed. $m - Medium of performance for music (R) This data should be transliterated. $o - Arranged statement for music (NR) The abbreviation arr. should be used with uniform title to demonstrate the arrangement of the document is done according to Uniform title. AACR2R recommends use of literal arr. (31) Hence, arr. should be transliterated. $r - Key for music (NR) OCLC defines uses of 'Code for music compositions'. The code provided in field 008 for music composition can be used. The numeric value of the code list is defined in 130$r. $s - Version (NR) Data should be transliterated. $v - Form subdivision (R) The data of this subfield should be translated. Chapter 3: Study ofMARCll elements 239 Sx - General subdivision (R) Basically, this subdivision is based on the subject. A numeric list of codes can be developed which can be used for this subfield. But sometimes it may not be subject subdivision. In such instances, data should be transliterated. $y - Chronological subdivision (R) The data in this subfield can be entered according to ISO 8601 format. $z - Geographic subdivision (R) Place name should be transliterated. $2 - Source of heading or term (NR) MARC21 defines the code for this subfield. Numeric version of the code is given in Appendix 3.38: 'MARC Code List for Subject Headings'. $3 - Materials specified (NR) If present this subfield should be translated. 610 - Subject Added Entry—Corporate Name (R) Indicators First - Type of corporate name entry element 0 - Inverted name 1 - Jurisdiction name 2 - Name in direct order Chapter 3: Study ofMARC21 elements 240 Second - Thesaurus 0 - Library of Congress Subject Headings 1 - LC subject headings for children's literature 2 - Medical Subject Headings 3 - National Agricultural Library subject authority file 4 - Source not specified 5 - Canadian Subject Headings 6 - Repertoire de vedettes-matiere 7 - Source specified in subfield $2 Subfield Codes Subfield $a,$b,$c and $d should be treated as 110$a,$b$c and $d respectively, rest of the subfields should be treated same as field 600. $a - Corporate name or jurisdiction name as entry element (NR) $b - Subordinate unit (R) $c - Location of meeting (NR) $d - Date of meeting or treaty signing (R) $e - Relator term (R) $f- Date of a work (NR) $g - Miscellaneous information (NR) $h - Medium (NR) $k - Form subheading (R) SI - Language of a work (NR) $m - Medium of performance for music (R) $n - Number of part/section/meeting (R) So - Arranged statement for music (NR) Sp - Name of part/section of a work (R) Sr - Key for music (NR) Chapter 3: Study ofMARC21 elements 241 $s - Version (NR) $t - Title of a work (NR) $u - Affiliation (NR) $v - Form subdivision (R) $x - General subdivision (R) $y - Chronological subdivision (R) $z - Geographic subdivision (R) $2 - Source of heading or term (NR) S3 - Materials specified (NR) $4 - Relator code (R) 611 - Subject Added Entry—Meeting Name (R) Indicators First - Type of meeting name entry element 0 - Inverted name 1 - Jurisdiction name 2 - Name in direct order Second - Thesaurus 0 - Library of Congress Subject Headings 1 - LC subject headings for children's literature 2 - Medical Subject Headings 3 - National Agricultural Library subject authority file 4 - Source not specified 5 - Canadian Subject Headings 6 - Repertoire de vedettes-matiere 7 - Source specified in subfield $2 Chapter 3: Study ofMARC21 elements 242 Subfleld Codes The following subfield should be treated according to 111 - Main Entry - Uniform Title. $a - Meeting name or jurisdiction name as entry element (NR) $c - Location of meeting (NR) $d - Date of meeting (NR) $e - Subordinate unit (R) $f- Date of a work (NR) $g - Miscellaneous information (NR) $h - Medium (NR) $k - Form subheading (R) $1 - Language of a work (NR) $n - Number of part/section/meeting (R) $p - Name of part/section of a work (R) $q - Name of meeting following jurisdiction name entry element (NR) $t - Title of a work (NR) $u - Affiliation (NR) The following subfields should be treated according to '600 - Subject Added Entry - Personnel Name', $s - Version (NR) $v - Form subdivision (R) $x - General subdivision (R) $y - Chronological subdivision (R) $z - Geographic subdivision (R) $2 - Source of heading or term (NR) $3 ' Materials specified (NR) $4 - Relator code (R) Chapter 3: Study ofMARCll elements 243 630 - Subject Added Entry-Uniform Title (R) Indicators First - Nonfiling characters 0-9 - Number of nonfiling characters Second - Thesaurus 0 - Library of Congress Subject Headings 1 - LC subject headings for children's literature 2 - Medical Subject Headings 3 - National Agricultural Library subject authority file 4 - Source not specified 5 - Canadian Subject Headings 6 - Repertoire de vedettes-matiere 7 - Source specified in subfield $2 Subfield Codes Following subfields should be treated according to '130 - Main Entry - Uniform Title', $a - Uniform title (NR) $d - Date of treaty signing (R) $f- Date of a work (NR) $g - Miscellaneous information (NR) $h - Medium (NR) $k - Form subheading (R) $1 - Language of a work (NR) $m - Medium of performance for music (R) $n - Number of part/section of a work (R) $o - Arranged statement for music (NR) Chapter 3: Study of MARCH elements 244 $p - Name of part/section of a work (R) $r - Key for music (NR) $s - Version (NR) St - Title of a work (NR) Following subfields should be treated according to '600 - Subject Added Entry - Personnel Name', $v - Form subdivision (R) $x - General subdivision (R) $y - Chronological subdivision (R) $z - Geographic subdivision (R) $2 - Source of heading or term (NR) $3 - Materials specified (NR) 648 - Subject Added Entry—Chronological Term (R) Indicators First - Undefined # - Undefined Second - Thesaurus 0 - Library of Congress Subject Headings 1 - LC subject headings for children's literature 2 - Medical Subject Headings 3 - National Agricultural Library subject authority file 4 - Source not specified 5 - Canadian Subject Headings 6 - Repertoire de vedettes-matiere 7 - Source specified in subfield $2 Chapter 3: Study of MARCH elements 245 Subfield Codes $a - Chronological term (NR) Data should be entered according to ISO 8601 format. Following subfields should be treated according to '600 - Subject Added Entry - Personnel Name', $v - Form subdivision (R) $x - General subdivision (R) $y - Chronological subdivision (R) $z - Geographic subdivision (R) $2 - Source of heading or term (NR) $3 - Materials specified (NR) 650 - Subject Added Entry-Topical Term (R) Indicators First - Level of subject # - No information provided 0 - No level specified 1 - Primary 2 - Secondary Second - Thesaurus 0 - Library of Congress Subject Headings 1 - LC subject headings for children's literature 2 - Medical Subject Headings 3 - National Agricultural Library subject authority file 4 - Source not specified 5 - Canadian Subject Headings Chapter 3: Study of MARCH elements 246 6 - Repertoire de vedettes-matiere 7 - Source specified in subfield $2 Subfleld Codes $a - Topical term or geographic name entry element (NR) This field needs to be translated. There are thesauri mentioned in second indicator which should be used for subject heading. Classuarus can be very well adopted for the subfield with numeric notations. $b - Topical term following geographic name entry element (NR) This field needs to be translated though geographical name can be transliterated. For example, 'Wilting disease of potato in Himalayan region', though the title has geographical name it but it is a part of subject. So such kinds of subjects are difficult to codify then to translate. $c - Location of event (NR) Location of the event should be transliterated. $d - Active dates (NR) Dates should be entered in yyyymmdd format. X:--/.',•• •, /. ,;. A-:^ The code should be picked up from the Relator code list. Chapter 3: Study ofMARC21 elements 247 Following subfields should be treated according to '600 - Subject Added Entry - Personnel Name', $v - Form subdivision (R) $x - General subdivision (R) $y - Chronological subdivision (R) $z - Geographic subdivision (R) $2 - Source of heading or term (NR) $3 - Materials specified (NR) 651 - Subject Added Entry—Geographic Name (R) Indicators First - Undefined # - Undefined Second - Thesaurus 0 - Library of Congress Subject Headings 1 - LC subject headings for children's literature 2 - Medical Subject Headings 3 - National Agricultural Library subject authority file 4 - Source not specified 5 - Canadian Subject Headings 6 - Repertoire de vedettes-matiere 7 - Source specified in subfield $2 Subfield Codes $a - Geographic name (NR) Name of a place should be transliterated. Chapter 3: Study ofMARCll elements 248 Following subfields should be treated according to '600 - Subject Added Entry - Personnel Name', $v - Form subdivision (R) $x - General subdivision (R) $y - Chronological subdivision (R) $z - Geographic subdivision (R) $2 - Source of heading or term (NR) $3 - Materials specified (NR) 653 - Index Term—Uncontrolled (R) Indicators First - Level of index term # - No information provided 0 - No level specified 1 - Primary 2 - Secondary Second - Undefined # - Undefined Subfield Codes $a - Uncontrolled term (R) The data of this field may range from any domain of knowledge so it should be translated. Chapter 3: Study ofMARCll elements 249 654 - Subject Added Entry—Faceted Topical Terms (R) Indicators First - Level of subject # - No information provided 0 - No level specified 1 - Primary 2 - Secondary Second - Undefined #- Undefined Subfleld Codes $a - Focus term (R) The data of this field may range from any domain of knowledge so it should be translated. Basically, this term is controlled term according to some Vocabulary controlled device (VCD). The term 'focus term' means 'the term which has to be indexed'. For example, 'brown horse' Here the term 'horse' is the focus term and 'brown' is qualifier to focus term. This subfield should be translated. $b - Non-focus term (R) Any qualifier element is non-focus term. This data also requires translation. Chapter 3: Study of MARCH elements 250 $c - Facet/hierarchy designation (R) This subfield records the hierarchy of the focus term in the VCD. Numerical designation to the hierarchy designation can also be used. Following subfields should be treated according to '600 - Subject Added Entry - Personnel Name', 5v - Form subdivision (R) $y - Chronological subdivision (R) $z - Geographic subdivision (R) $3 - Materials specified (NR) $2 - Source of heading or term (NR) MARC21 has defined the code for this subfield. Numeric Code Value 1 Art & architecture thesaurus (Los Angeles, CA: Getty Research Institute, Getty Vocabulary Program) 2 Faceted application of subject terminology (Dublin, Ohio: OCLC) 3 Locally assigned term. Table 3.17: Faceted Topical Term Thesauri Codes 655 - Index Term—Genre/Form (R) Indicators First - Type of heading # - Basic 0 - Faceted Second - Thesaurus 0 - Library of Congress Subject Headings Chapter 3: Study of MARCH elements 251 1 - LC subject headings for children's literature 2 - Medical Subject Headings 3 - National Agricultural Library subject authority file 4 - Source not specified 5 - Canadian Subject Headings 6 - Repertoire de vedettes-matiere 7 - Source specified in subfield $2 Subfleld Codes $a - Genre/form data or focus term (NR) Term should be translated. $b - Non-focus term (R) Term should be translated. $c - Facet/hierarchy designation (R) This subfield records the hierarchy of the focus term in the VCD. Numerical designation to the hierarchy designation can also be used. Following subfields should be treated according to '600 - Subject Added Entry - Personnel Name', $v - Form subdivision (R) $x - General subdivision (R) rv-Chn:vn]..nlca!suhd-::.i3n(R) $z - Geographic subdivision (R) $3 - Materials specified (NR) Chapter 3: Study ofMARC21 elements. 252 $2 - Source of term (NR) MARC21 has defined the code for this subfield. Numeric Code Value 1 Art & architecture thesaurus (Los Angeles, CA: Getty Research Institute, Getty Vocabulary Program) Svenska amnesord for bam (Stockholm: Svensk biblioteksforening) Canadian subject headings (Ottawa, ON: National Library of Canada) Dictionary of occupational titles. (Washington: United States Dept. of Labor, Employment and Training Administration, United States Employment Service) Gale Group subject thesaurus and named entity vocabulary (Farmington Hills, ML Gale Group) HAPI thesaurus and name authority, 1970-2000 (Los Angeles, CA: UCLC Latin America Center Pubs.) Index of Christian art (Princeton, NJ: Princeton University) Library of Congress subject headings. (Washington: Library of Congress) Library of Congress subject headings: Annotated Card Program, AC Subject headings (Washington, DC: Library of Congress, Cataloging Distribution Service) 10 Llista d'encapfalaments de materia en catala (Barcelona: Biblioteca de Catalunya, Servei de Normalitzacio Bibliografica) [use only after Dec. 29, 2003] 11 Locally assigned term. [See the explanation in the Introduction] 12 Madakhil al-asma' al-'arabiyah al-qadimah (Cairo: Maktabah al- Akadimiyah) 13 National Agricultural Library subject headings (Beltsville, MD: National Agricultural Library) 14 New Zealand national bibliographic (Wellington: National Library of New Zealand) 15 Opetusministerion asiasanasto (Helsinki: Opetusministerion) 16 Qa'imat ru'us al-mawdu'at al-'Arabiyah al-qiyasiyah al-maktabat wa- marakaz al-ma'lumat wa-qawa'id al-bayanat (al-Qahirah: Dar Shuruq) 17 REVEAL: fiction indexing and genre headings (Bath: UKOLN) Natsional'nyi normativnyi fail geograficheskikh nazvanii Rossiiskoi Federatsii (Moskva: Rossiiska i^ gosudarstvennaia biblioteka) [use only after Dec. 29, 2003] 19 Repertoire de vedettes-matifere (Ottawa, ON, Canada: Bibliothe que nationale du Canada) 20 SIPRl library thesaurus (Stockholm; Stockholm International Peace Research Institute) [use only after May 11, 2003] Vedettes-matiere jeunesse (Montreal, QC: Services documentaires multimedia) [use only after Dec. 29, 2003] Table 3.18: Subject Heading Code Chapter 3: Study ofMARCIl elements 253 656 - Index Term—Occupation (R) Indicators First - Undefined # - Undefined Second - Source of term 7 - Source specified in subfield $2 Subfleld Codes $a - Occupation (NR) Occupational term should be translated. Alternatively, US Department of Labor has developed numeric classification scheme called as 'Standard Occupational Standard' which can also be adopted. (33 - 31) In any, case subfield $2 records the code followed for Occupational classification. $k - Form (NR) Data for this subfield should be translated. Following subfields should be treated according to '600 - Subject Added Entry - Personnel Name', $v - Form subdivision (R) $x - General subdivision (R) $y - Chronological subdivision (R) $z - Geographic subdivision (R) $3 - Materials specified (NR) Chapter 3: Study ofMARC21 elements. 254 $2 - Source of term (NR) MARC21 has defined the code for this subfield. Code Value Numeric I Art & architecture thesaurus (Los Angeles, CA; Getty Research Institute, Getty Vocabulary Program) 2 Svenska amnesord for bam (Stockholm: Svensk biblioteksforening) 3 Canadian subject headings (Ottawa, ON: National Library of Canada) 4 Dictionary of occupational titles. (Washington: United States Dept. of Labor, Employment and Training Administration, United States Employment Service) 5 Gale Group subject thesaurus and named entity vocabulary (Farmington Hills, MI: Gale Group) 6 HAPI thesaurus and name authority, 1970-2000 (Los Angeles, CA: UCLC Latin America Center Pubs.) 7 Index of Christian art (Princeton, NJ: Princeton University) 8 Library of Congress subject headings. (Washington: Library of Congress) 9 Library of Congress subject headings: Annotated Card Program, AC Subject headings (Washington, DC: Library of Congress, Cataloging Distribution Service) 10 Llista d'encapipalaments de materia en catala (Barcelona: Biblioteca de Catalunya, Servei de Normalitzacio Bibliografica) [use only after Dec. 29, 20031 11 Locally assigned term. [See the explanation in the Introduction] 12 Madakhil al-asma' al-'arabtyah al-qadimah (Cairo: Maktabah al-Akadtmtyah) 13 National Agricultural Library subject headings (Beltsville, MD: National Agricultural Library) 14 New Zealand national bibliographic (Wellington: National Library of New Zealand) 15 Opetusministerion asiasanasto (Helsinki: Opetusministerion) 16 Qa'imat ru'us al-mawdu'at al-'Arabiyah al-qiyastyah al-maktabat wa-marakaz al- ma'lumat wa-qawa'id al-bayanat (al-Qahirah: Dar Shuruq) 17 REVEAL: fiction indexing and genre headings (Bath: UKOLN) 18 Natsional'nyi normativnyi fail geograficheskikh nazvanii Rossiiskoi Federatsii (Moskva: Rossiiska ia gosudarstvennaia biblioteka) [use only after Dec. 29, 2003] 19 Repertoire de vedettes-matiere (Ottawa, ON, Canada: Biblioth^ que nationale du Canada) 20 SIPRI library thesaurus (Stockholm: Stockholm International Peace Research Institute) [use only after May 11, 2003] 21 Vedettes-matiere jeunesse (Montreal, QC: Services documentaires multimedia) [use only after Dec. 29, 2003] labieS.i'si: IViAkC2i COvJ, li.ii oi Ocupiiiiunal CUL Chapter 3: Study ofMARC2J elements 255 657 - Index Term—Function (R) Indicators First - Undefined # - Undefined Second - Source of term 7 - Source specified in subfield $2 Subfield Codes $a - Function (NR) This subfield should be translated or codified according to some standardized code mentioned in $2. Following subfields should be treated according to '600 - Subject Added Entry - Personnel Name', $v - Form subdivision (R) $x - General subdivision (R) $y - Chronological subdivision (R) $z - Geographic subdivision (R) $3 - Materials specified (NR) $2 - Source of term (NR) MARC21 has defined the code for this subfield. Chapter 3: Study of MARCH elements. 256 Numeric Value Code 1 Art & architecture thesaurus (Los Angeles, CA: Getty Research Institute, Getty Vocabulary Program) 2 Svenska amnesord f6r bam (Stockholm; Svensk biblioteksfi&rening) 3 Canadian subject headings (Ottawa, ON: National Library of Canada) 4 Dictionary of occupational titles. (Washington: United States Dept. of Labor, Employment and Training Administration, United States Employment Service) 5 Gale Group subject thesaurus and named entity vocabulary (Farmington Hills, MI: Gale Group) 6 HAPI thesaurus and name authority, 1970-2000 (Los Angeles, CA: UCLC Latin America Center Pubs.) 7 Index of Christian art (Princeton, NJ: Princeton University) 8 Library of Congress subject headings. (Washington:Library of Congress) 9 Library of Congress subject headings: Annotated Card Program, AC Subject headings (Washington, DC: Library of Congress, Cataloging Distribution Service) 10 Llista d'encap9alaments de materia en catala (Barcelona: Biblioteca de Catalunya, Servei de Normalitzacio Bibliografica) [use only after Dec. 29, 2003] 11 Locally assigned term, [See the explanation in the Introduction] 12 Madakhil al-asma' al-'arabiyah al-qadimah (Cairo: Maktabah al-Akadimiyah) 13 National Agricultural Library subject headings (Beltsville, MD: National Agricultural Library) 14 New Zealand national bibliographic (Wellington: National Library of New Zealand) 15 Opetusministerion asiasanasto (Helsinki: Opetusministerion) 16 Qa'imat ru'ijs al-mawdu'at al-'Arabiyah al-qiyasiyah al-maktabat wa-marakaz al- ma'lumat wa-qawa'id al-bayanat (al-Qahirah: Dar Shuruq) 17 REVEAL: fiction indexing and genre headings (Bath: UKOLN) 18 Natsionarnyi normativnyi fail geograficheskikh nazvanii Rossiiskoi Federatsii (Moskva: Rossiiska ia gosudarstvennaia biblioteka) [use only after Dec. 29, 2003] 19 Repertoire de vedeties-matiere (Ottawa, ON, Canada: Bibliothe que nationale du Canada) 20 SIPRI library thesaurus (Stockholm: Stockholm International Peace Research Institute) [use only after May 11, 2003] 21 Vedettes-matifere jeunesse (Montreal, QC: Services documentaires multimedia) [use only after Dec. 29, 2003] Table 3.20: MARC21 Code List of Index Term Codes Chapter 3: Study of MARCH elements 257 658 - Index Term—Curriculum Objective (R) Subfleld Codes $a - Main curriculum objective (NR) This subfield should be translated. Though, the data can be codified and the scheme can be mentioned in subfield $2. $b - Subordinate curriculum objective (R) This subfield should be translated. $c ' Curriculum code (NR) The data in this subfield is codified so it should be maintained as it is. $d - Correlation factor (NR) The most common correlation factors recorded are, and their corresponding numeric code is as follows, Numeric Code Value 1 Slightly correlated 2 Moderately correlated 3 Highly correlated Table 3.21: Correlation Code $2 - Source of term or code (NR) MARC21 has defined the code for this subfield. Chapter 3: Study of MARC21 elements. 258 Numeric Value Code 1 ABLEDATA thesaurus (Silver Spring, MD: National Rehabilitation Information Center) 2 ACCS subject directory. (West Lafayette, IN: Kappa Delta Pi) 3 Svenska amnesord for bam (Stockholm: Svensk biblioteksforening) 4 Canadian subject headings (Ottawa, ON: National Library of Canada) 5 Thesaurus of ERIC descriptors (Washington: Educational Resources Information Center, National Institute of Education, U.S. Dept. of Education) 6 Gale Group subject thesaurus and named entity vocabulary (Farmington Hills, MI: Gale Group) 7 HAPI thesaurus and name authority, 1970-2000 (Los Angeles, CA: UCLC Latin America Center Pubs.) 8 HyperAble Data special ed terms list. (Madison, WI: Trace Research and Development) 9 Index of Christian art (Princeton, NJ: Princeton University) 10 Llista d'encap9alaments de materia en catala (Barcelona: Biblioteca de Catalunya, Servei de Normalitzacio Bibliografica) [use only after Dec. 29, 20031 U Locally assigned term. [See the explanation in the Introduction] 12 Madakhil al-asma' al-'arabtyah al-qadimah (Cairo: Maktabah al-Akadimiyah) 13 Missouri show-me standards (Jefferson City, MO: Dept. of Elementary and Secondary Education 14 National Agricultural Library subject headings (Beltsville, MD: National Agricultural Library) 15 New Zealand national bibliographic (Wellington: National Library of New Zealand) 16 Ohio curriculum objectives (Columbus, OH: Department of Education) 17 Opetusministerion asiasanasto (Helsinki: Opetusministerion) 18 Qa'imat ru'iis al-mawdu'at al-'Arabiyah al-qiyasiyah al-maktabat wa-marakaz al- ma'lumat wa-qawa'id al-bayanat (al-Qahirah: Dar ShurOq) 19 REHABDAT thesaurus (Silver Spring, MD: National Rehabilitation Information Center) 20 REVEAL: fiction indexing and genre headings (Bath: UKOLN) 21 Natsional'nyi normativnyi fail geograficheskikh nazvanii Rossiiskoi Federatsii (Moskva: Rossiiska ia gosudarstvennai'a biblioteka) [use only after Dec. 29, 2003] 22 Repertoire de vedettes-matiere (Ottawa, ON, Canada: Bibliothe que nationale du Canada) 23 SIPRI library thesaurus (Stockholm: Stockholm International Peace Research Institute) fuse only after May 11, 2003] 24 Texas essential knowledge and skills (TEKS) (Austin, TX : Texas Education Agency, Office of Curriculum and Professional Development) 25 Texas administrative code. Volume 11, chapter 75. Curriculum (Austin, TX: Texas Education Agency, Policy Planning and Evaluation) 26 Vedettes-matiere jeunesse (Montreal, QC: Services documentaires multimedia) [use onh-after Dec. Tl 200;'^ Table 3.22: Code for Curriculum Objectives Chapter 3: Study of MARCH elements 259 700 - Added Entry—Personal Name (R) Indicators First - Type of personal name entry element 0 - Forename 1 - Surname 3 - Family name Second - Type of added entry # - No information provided 2 - Analytical entry Subfield Codes Following subfields should be treated according to '600 - Subject added entry - personnel name', $a - Personal name (NR) $b - Numeration (NR) $c - Titles and other words associated with a name (R) $d - Dates associated with a name (NR) $e - Relator term (R) $f- Date of a work (NR) $g - Miscellaneous information (NR) $h - Medium (NR) $j - Attribution qualifier (R) Tk - Form subheading (R) i>i - Language of a work (NR) $m - Medium of performance for music (R) $n - Number of part/section of a work (R) $o - Arranged statement for music (NR) Chapter 3: Study of MARCH elements 260 $p - Name of part/section of a work (R) $q - Fuller form of name (NR) $r - Key for music (NR) $s - Version (NR) $t - Title of a work (NR) $u - Affiliation (NR) $3 - Materials specified (NR) $4 - Relator code (R) $x - International Standard Serial Number (NR) This subfield should record the ISSN of the serials. $5 - Institution to which field applies (NR) The name of the institute/organization should be transliterated. 710 - Added Entry-Corporate Name (R) Indicators First - Type of corporate name entry element 0 - Inverted name 1 - Jurisdiction name 2 - Name in direct order •' .''',-," •• 'j j',':is of added enliy # - No information provided 2 - Analytical entry Chapter 3: Study ofMARClI elements 261 Subfield Codes Following subfields should be treated according to '610 - Subject Added Entry - Corporate Name (R)', $a - Corporate name or jurisdiction name as entry element (NR) $b ' Subordinate unit (R) $c - Location of meeting (NR) $d - Date of meeting or treaty signing (R) $e - Relator term (R) $f- Date of a work (NR) $g - Miscellaneous information (NR) $h - Medium (NR) $k - Form subheading (R) $1 - Language of a work (NR) $m - Medium of performance for music (R) $n - Number of part/section/meeting (R) $0 - Arranged statement for music (NR) $p - Name of part/section of a work (R) $r - Key for music (NR) $s - Version (NR) $t - Title of a work (NR) $u - Affiliation (NR) $3 - Materials specified (NR) $4 - Relator code (R) $x - Internatiofial SUi'ulard Serial Number (NR) ": '-.ii.:...;;.;;^i., ] a:;, i-!,! ... :: j \xx Ljh! > of the serials. $5 - Institution to which field applies (NR) The name of the institute/organization should be transliterated. Chapter 3: Study ofMARC21 elements 262 711 - Added Entry-Meeting Name (R) Indicators First - Type of meeting name entry element 0 - Inverted name 1 - Jurisdiction name 2 - Name in direct order Second - Type of added entry # - No information provided 2 - Analytical entry Subfleld Codes Following subfields should be treated according to '611 - Subject Added Entry - Meeting Name (R)', $a - Meeting name or jurisdiction name as entry element (NR) $c - Location of meeting (NR) $d - Date of meeting (NR) $e - Subordinate unit (R) $f- Date of a work (NR) $g - Miscellaneous information (NR) $h - Medium (NR) $k - Form subheading (R) $1 - Language of a work (NR) '^; - N "n'y- o-^pn^i/'y'rtfnij/meeting (R) $q - Name of meeting following jurisdiction name entry element (NR) $s - Version (NR) St - Title of a work (NR) Chapter 3: Study ofMARCl 1 elements 263 $u - Affiliation (NR) $3 - Materials specified (NR) $4 - Relator code (R) $x - International Standard Serial Number (NR) This subfield should record the ISSN of the serials. $5 - Institution to which field applies (NR) The name of the institute/organization should be transliterated. 720 - Added Entry-Uncontrolled Name (R) Subfleld Codes $a - Name (NR) The name of the person, corporate body or meeting should be transliterated. $e - Relator term (R) The role code mentioned in field '100 - Main Entry - Personnel Name' should be adopted. $4 - Relator code (R) r c.\:-:v-- Cf^d;l;-!-(• . .; ;• <: Chapter 3: Study ofMARCll elements 264 730 - Added Entry-Uniform Title (R) Indicators First - Nonfding characters 0-9 - Number of nonfiling characters Second - Type of added entry # - No information provided 2 - Analytical entry Subfield Codes Following subfields should be treated according to '630 - Subject Added Entry - Uniform Title (R)', $a - Uniform title (NR) $d - Date of treaty signing (R) $f- Date of a work (NR) $g - Miscellaneous information (NR) $h - Medium (NR) $k - Form subheading (R) $1 - Language of a work (NR) $m - Medium of performance for music (R) $n - Number of part/section of a work (R) $o - Arranged statement for music (NR) $p - Name of part/section of a work (R) Sr •• /r."v for music (NR) $t - Tide of a work (NR) $3 - Materials specified (NR) Chapter 3: Study ofMARC21 elements 265 $x - International Standard Serial Number (NR) This subfield should record the ISSN of the serials. $5 - Institution to which/ield applies (NR) The name of the institute/organization should be transliterated. 740 - Added Entry-Uncontrolled Related/Analytical Title (R) Indicators First - Nonfiling characters 0-9 - Number of nonfiling characters Second - Type of added entry # - No information provided 2 - Analytical entry Subfield Codes $a - Uncontrolled related/analytical title (NR) The data of this subfield requires translation. Following subfields should be treated according to '700 - Added Entry - Personnel Name (R)', $h - Medium (NR) $n - Number of part/section of a work (R) $p - Name of part/section of a work (R) $5 - Institution to which field applies (NR) Chapter 3: Study ofMARC21 elements 266 752 - Added Entry—Hierarchical Place Name (R) Subfield Codes $a - Country (NR) The name of the country should be transliterated or MARC21 defines the list of countries which is given in 'Appendix 3.1 MARC Code List for Country Codes'. $b - State, province, territory (NR) The name of the stated, province or territory should be transliterated or else if there is any standard that can be adopted. $c - County, region, islands area (NR) The name of the county, region or islands area should be transliterated. Appendix 3.1 Country code can be used but otherwise region, island etc. can be transliterated or else if there is any standard that can be adopted. $d - City (NR) The name of the city should be transliterated or else if there is any standard that can be adopted. 753 - System Details Access to Computer Files (R) Subfield Codes $a - Make and model of machine (NR) The name of the machine and its model should be transliterated. Chapter 3: Study ofMARC21 elements 267 $b - Programming language (NR) The name of the programming language should be transliterated. $c - Operating system (NR) The name of the operating system should be transliterated. 754 - Added Entry—Taxonomic Identification (R) This fields deals with the taxonomic classification to identify an individual species. Subfield Codes $a - Taxonomic name (R) The taxonomic name of the species should be transliterated. $c - Taxonomic category (R) The taxonomic category of the species should be transliterated. $d - Common or alternative name (R) The common or alternative name of a species differs in different languages so this subfield should be translated. $x - Non-public note (R) The data of this subfield should be translated. Chapter 3: Study ofMARCll elements 268 $z - Public note (R) The data of this subfield should be translated. $2 - Source of taxonomic identification (NR) MARC21 defines a code list of taxonomic data but it is good to enter the full name of the source which can be transliterated. 800 - Series Added Entry-Personal Name (R) Indicators First - Type of personal name entry element 0 - Forename 1 - Surname 3 - Family name Second - Undefined # - Undefined Subfield Codes Following subfields should be treated according to '600 - Subject Added Entry — Personnel Name (R)' except $v, $a - Personal name (NR) $h - Numeration (NR) $c - Titles and other words associated with a name (R) $d - Dates associated with a name (NR) $e - Relator term (R) Sf- Date of a work (NR) $g - Miscellaneous information (NR) Chapter 3: Study ofMARCll elements 269 $h - Medium (NR) $j - Attribution qualifier (R) $k - Form subheading (R) $1 - Language of a work (NR) $m - Medium of performance for music (R) $n - Number of part/section of a work (R) $o - Arranged statement for music (NR) $p - Name of part/section of a work (R) $q - Fuller form of name (NR) $r - Key for music (NR) Ss - Version (NR) $t - Title of a work (NR) $u - Affiliation (NR) $4 - Relator code (R) $v - Volume/sequential designation (NR) The data of this subfield is either numeric or alphabetic in a language which should not be altered. 810 - Series Added Entry—Corporate Name (R) Indicators First - Type of corporate name entry element 0 - Inverted name 1 - Jurisdiction name 2 - Name in direct order Second- Undefined # - Undefined Chapter 3: Study ofMARCll elements 270 Subfield Codes Following subfields should be treated according to '610 - Subject Added Entry — Corporate Name (R)' except $v, $a - Corporate name or jurisdiction name as entry element (NR) $b - Subordinate unit (R) $c ' Location of meeting (NR) $d - Date of meeting or treaty signing (R) $e - Relator term (R) $f- Date of a work (NR) $g - Miscellaneous information (NR) $h - Medium (NR) $k - Form subheading (R) $1 - Language of a work (NR) $m - Medium of performance for music (R) $n - Number of part/section/meeting (R) $o - Arranged statement for music (NR) $p - Name of part/section of a work (R) $r - Key for music (NR) $s - Version (NR) $t - Title of a work (NR) $u - Affiliation (NR) $4 - Relator code (R) $v - Volume/sequential designation (NR) The data of this subfield is either numeric or alphabetic in a language which should not be altered. Chapter 3: Study ofMARC2I elements 271 811 - Series Added Entry—Meeting Name (R) Indicators First - Type of meeting name entry element 0 - Inverted name 1 - Jurisdiction name 2 - Name in direct order Second - Undefined # - Undefined Subfield Codes Following subfields should be treated according to '611 - Subject Added Entry — Meeting Name (R)' except $v, $a - Meeting name or jurisdiction name as entry element (NR) $c - Location of meeting (NR) $d - Date of meeting (NR) $e - Subordinate unit (R) $f- Date of a work (NR) $g - Miscellaneous information (NR) $h - Medium (NR) $k - Form subheading (R) $1 - Language of a work (NR) $n - Number of part/section/meeting (R) $p - Name of part/section of a work (R) $q - Name of meeting following jurisdiction name entry element (NR) $s - Version (NR) $t - Title of a work (NR) $u - Affiliation (NR) $4 - Relator code (R) Chapter 3: Study of MARC21 elements 272 $v - Volume/sequential designation (NR) The data of this subfield is either numeric or alphabetic in a language which should not be altered. 830 - Series Added Entry-Uniform Title (R) Indicators First - Undefined # - Undefined Second - Nonfiling characters 0-9 - Number of nonfiling characters Subfield Codes Following subfields should be treated according to '630 - Subject Added Entry ~ Uniform Title (R)' except $v, $a - Uniform title (NR) $d - Date of treaty signing (R) $f- Date of a work (NR) $g - Miscellaneous information (NR) $h - Medium (NR) $k - Form subheading (R) $1 - Language of a work (NR) $m - Medium of performance for music (R) $n - Number of part/section of a work (R) $o - Arranged statement for music (NR) $p - Name of part/section of a work (R) $r - Key for music (NR) Chapter 3: Study ofMARC21 elements 273 $s - Version (NR) $t - Title of a work (NR) $v - Volume/sequential designation (NR) The data of this subfield is either numeric or alphabetic in a language which should not be altered. 850 - Holding Institution (R) Subfield Codes $a - Holding institution (R) The data of this subfield should be transliterated. 852 - Location (R) Indicators First - Shelving scheme # - No information provided 0 - Library of Congress classification 1 - Dewey Decimal classification 2 - National Library of Medicine classification 3 - Superintendent of Documents classification 4 - Shelving control number 5 - Title 6 - Shelved separately 7 - Source specified in subfield $2 8 - Other scheme Chapter 3: Study of MARCH elements 274 Second - Shelving order # - No information provided 0 - Not enumeration 1 - Primary enumeration 2 - Alternative enumeration Subfield Codes $a - Location (NR) The name of the organization should be transliterated. $b - Sublocation or collection (R) The sublocation data should be transliterated but sometimes data needs to be translated when the collection is divided into main collection and subsidiary collection. For example, 852 0 $a[location identifier] $b Manuscript Division $c - Shelving location (R) The data of this subfield should be transliterated. $e - Address (R) The address should be transliterated. $f- Coded location qualifier (R) Qualifier type 1 - Latest Chapter 3: Study of MARCH elements 275 p - Previous 1-9 - Number of units Unit type: Time m - Month(s) w - Week(s) y - Year(s) Part e - Edition(s) i - Issue(s) s - Supplement(s) Whole subfield is coded but numerals could have been preferred for storing Qualifier type, Unit type and Part. $g - Non-coded location qualifier (R) This subfield should be transliterated though there are no examples given in MARC21 manual. $h - Classification part (NR) From this subfield data should be taken as it is. $i - Item part (R) Number of item should be recorded or else if part is named by some text it should be transliterated. Chapter 3: Study ofMARC21 elements 2 76 $j - Shelving control number (NR) From this subfield data should be taken as it is. $k - Call number prefix (R) From this subfield data should be taken as it is. $1 - Shelving form of title (NR) Data of this subfield should be transliterated. $m - Call number suffix (R) From this subfield data should be taken as it is. $n - Country code (NR) Appendix 3.1 Country code can be used. $p - Piece designation (NR) From this subfield data should be taken as it is. $q - Piece physical condition (NR) Data of this subfield should be translated. $s - Copyright article-fee code (R) From this subfield data should be taken as it is. Chapter 3: Study of MARCH elements 277 $t - Copy number (NR) From this subfield data should be taken as it is. $x - Nonpublic note (R) Data of this subfield should be translated. $z - Public note (R) Data of this subfield should be translated. $2 - Source of classification or shelving scheme (NR) Though MARC21 defines the code, it is good to transliterate the data. $3 - Materials specified (NR) Data of this subfield should be translated. 856 - Electronic Location and Access (R) Indicators First - Access method # - No information provided 0 - Email 1 -FTP 2 - Remote login (Telnet) 3 - Dial-up 4 - HTTP 7 - Method specified in subfield $2 Chapter 3: Study ofMARC21 elements 278 Second - Relationship # - No information provided 0 - Resource 1 - Version of resource 2 - Related resource 8 - No display constant generated Subfield Codes $a - Host name (R) The name of the host should be transliterated. $b - Access number (R) If numeric data should be used as it is. Else it should be transliterated. $c - Compression information (R) As such, data of this subfield should be translated if data is in following format, 856 l#$amaine.maine.edu$cMust be decompressed with PKUNZIPSfi-esource.zip It will be good to give only program name which is required for decompression. In that case data should be only transliterated. Sd - Path (R) Path information should be taken as it is. Chapter 3: Study ofMARC2J elements 279 $f- Electronic name (R) The data in this subfield contains the name of the file which should be transliterated. $h - Processor of request (NR) The name of the user or processor should often is the name of person, so this data should be transliterated. $i - Instruction (R) The data of this subfield should be used as it is. $j - Bits per second (NR) This is numerical data so it should be maintained as it is. $k - Password (NR) No processing is needed on password so it should be used as it is. $1 - Logon (NR) The login name should be used as it is. $0 - Operating system (NR) Name of the Operating system should be transliterated. Chapter 3: Study of MARCH elements 280 $p - Port (NR) Port number is a numeric value so it should be maintained as it is. $q - Electronic format type (NR) The electronic format type should be used as it is. $r - Settings (NR) The data is codified so can be adapted as it is. $s - File size (R) File size is a numeric value so it should be maintained as it is. $t - Terminal emulation (R) Terminal emulation should be transliterated. $u - Uniform Resource Identifier (R) URI is unique identifier for the resource so this data should be used as it is. $v - Hours access method available (R) The data of this subfield should be transliterated. $w - Record control number (R) Record control number should be taken as it is. Chapter 3: Study of MARCH elements 281 $x - Nonpublic note (R) The data of this subfield should be translated. $y - Link text (R) Link text should be used as it is. $z - Public note (R) The data of this subfield should be translated. $2 - Access method (NR) This field contains the method of access to information if the first indicator value is 7. There are different access methods and data should be taken as it is. $3 - Materials specified (NR) The data of this subfield should be translated. ; 3.5 CONCLUSION A total of 1033 subfields are analyzed. Linking fields i.e. 760 - 787 are ignored as these fields are used for record linking and some times used for generation of notes. These fields are not that important from the point of view of describing an item. Similarly, in 8''' bUock field 841 - 850, 854 - 855 and 863 - 887 are basically holding information fields and few others are less important. These fields don't have much importance from the point of view of bibliographic materials. Chapter 3: Study ofMARCll elements. 282 Out of 1079 analyzed subfields, only 235 subfields require translation which is about 22% of the total. There are about 304 subfields which require transliteration, 283 subfields which do not require any kind of processing, 169 subfields which can be codified, 56 subfields which should use formatted data and 32 subfields which use number counts. However, it should be noted that some subfields use partial codification and translation or numbers. Type of Processing No. of Fields Percentage Translation 235 21.78 Transliteration 304 28.17 No processing 283 26.22 Codification 169 15.66 Formatted data 56 5.19 Numbers 32 2.97 Total 1079 100 Table 3.23: Percentage table of processing type 3.6 REFERENCES 1. KHAN (M.A,). Cataloguing in Library Science. New Delhi: Samp & Sons, 1997 p.l09 2. GREDLEY (Ellen) and HOPKINSON (Alan). Exchanging bibliographic data: MARC and other inemational formats. Ottawa: Canadian Library Association, 1990. p. 10 3. THE MARC 21 Formats: Background and Principles. MARBI (American Library Association's ALCTS/LITA/RUSA Machine- Readable Bibliographic Information Committee) in conjunction with Network Development and MARC Standards Office Library of Congress. Revised November 1996.http://Mrww.loc.sov/marc/96principl.htmlik>ne Browsed on 14"^ July, 2004. Chapter 3: Study ofMARCll elements 283 4. MORTAZA (Kokabi). The internationalization of MARC. Part II: some MARC formats based on USMARC. In: Library Review 12 (1), 1996 pp. 21-31,38-45. 5. MARC 21: Harmonized USMARC and CAN/MARC. http://lcweb.loc.eov/marc/annmarc21.html Browsed on 14'*^ July, 2004. 6. UNDERSTANDING MARC Bibliographic: Parts 1 to 6. http://www.loc.eov/marc/umb/um01to06.html Browsed on 14'*^ July, 2004. 7. MARC Development Overview (Library of Congress). http://www. loc.gov/marc/overview. html Browsed on 14' July, 2004. 8. THE MARC 21 Formats: Background and Principles. MARBI (American Library Association's ALCTS/LITA/RUSA Machine- Readable Bibliographic Information Committee) in conjunction with Network Development and MARC Standards Office Library of Congress. Revised November 1996. http://www.loc.eov/marc/96principl.htmlik>neBrovjsed on 14' July, 2004. 9. MARC21 ListofOrganizaitions. http://www.loc.eov/marc/oreanizations/BTOwsed on 14'*' July, 2004. 10. ISO 3166 Maintenance agency (ISO 3166/MA) - ISO's focal point for country codes. http://www. iso.ch/iso/en/prods- services/iso3166ma/index.html Browsed on 14'*' July, 2004. 11. LEGAL status codes for World Intellectual Property Organization (WIPO) (WO). http://www.delphion.com/help/leealcodes? cn2= WO&name=World% 20Intellectual%20ProDertv%20Oreanization%20{WIPO) Browsed on 14"^ July, 2004. Chapter 3: Study of MARCH elements 284 12. LEGAL status codes for European Patent Office (EPO (EP). http://www.delphion.com/help/legalcodes? cn2=EP&name=Europea n%20Patent%20Omce%20(EPO) Browsed on 14''^ July, 2004. 13. FIELD 015 (National Bibliography Number). http://www.loc.sov/marc/relators/relaothr.html#rela015b Browsed on 14'^ July, 2004. 14. BSI Currency Code Service (ISO 4217 Maintenance Agency). http://www.bsi- global.com/Technical+Information/Publications/_Publications/tis90. xalter Browsed on 14* July, 2004. 15. 026 Fingerprint Identifier (R). www.oclc.ors\bibformats\en\0xx\026.shtm Browsed on 14"^ July, 2004. 16. 027 STANDARD Technical Report Number (R). www.oclc.ors\bibformats\en\0xx\027.shtm Browsed on 14"^ July, 2004. 17. 030 CODEN Designation (R). www.oclc.ors\bibformats\en\0xx\030.shtm Browsed on 14' July, 2004. 18. 032 - POSTAL Registration Number (R) www.loc.gov/marc/bibliographic/ecbdnumb.html#mrcbO32 Browsed on 14* July, 2004. 19. SOURCE of Acquisition (R). www.oclc.org\bibformats\en\0xx\037.shtm Browsed on 14' July, 2004. 20. ISO 639-2. httD://www.he.sov/standards/iso639-2/ Browsed on 14* July, 2004. Chapter 3: Study of MARCH elements 285 21. CODES for the representation of names of scripts. http://www.unicode.org/isol5924/isol5924-num.html Browsed on H'*' July, 2004. 22. MARC Code List: PART VI: Description Conventions. http://www.loc.sov/marc/relators/reladesc.html Browsed on 14* July, 2004. 23. 041 - LANGUAGE Code (R). http ://www. loc. gov/marc/bibliographic/ecbdnumb. html#mrcb04I Browsed on 14* July, 2004. 24. TIME Period of Content (NR). http://www.oclc.org/bibformats/en/0xx/045.shtm Browsed on 14* July, 2004. 25. 048 - NUMBER of Musical Instruments or Voices Code (R). http://www, loc. gov/marc/bibliographic/ecbdnumb. html#mrcb048 Browsed on 14* July, 2004. 26. MARCH Specifications for Record Structure, Character Sets, and Exchange Media, CHARACTER SETS: Part 2, UCS/Unicode Environment, http://www.loc.gov/marc/specifications/speccharucs.html Browsed on 14* July, 2004. 27. MARC Code List: Relator Codes ~ Code Sequence. www.loc.gov\marc\relators\relacode.html Browsed on 14' July, 2004. 28. 270 ADDRESS (R). www.oclc.ore\bibformats\en\2xx\270.html Browsed on 14* July, 2004. 29. 352 DIGITAL Graphic Representation (R) www.oclc.org\bibformats\en\Sxx\352.html Browsed on 14* July, 2004. Chapter 3: Study of MARCH elements 286 30. ANGLO-AMERICAN Cataloguing Rules / Prepared under the direction of the Joint Steering Committee for the Revision of AACR; edited by Michael Gorman and Paul W. Winkler. 2nd. ed. 1988 revision. Chicago: American Library Association, 1988, pp. 286-288. 31. ANGLO-AMERICAN Cataloguing Rules / Prepared under the direction of the Joint Steering Committee for the Revision of AACR; edited by Michael Gorman and Paul W. Winkler. 2nd. ed. 1988 revision. Chicago: American Library Association, 1988, Rule 25.35 pp. 536-537. 32. US department of labor Bureau of Statistics. http://MWW.bls.sov/soc/soc maio.htm Browsed on 14' July, 2004.