1. 1 Purpose and Scope of unimarc 7 2 Format Maintenance 7


Occurrence Optional. Repeatable. Indicators



Download 5.17 Mb.
Page118/148
Date29.01.2017
Size5.17 Mb.
#11653
1   ...   114   115   116   117   118   119   120   121   ...   148

Occurrence


Optional. Repeatable.

Indicators


Indicators are as for field 720.

Subfields


Subfields are as for field 720.

Notes on Field Contents


The same guidelines apply as for field 720.

Related Fields


200$f TITLE AND STATEMENT OF RESPONSIBILITY, First Statement of Responsibility

Data in field 200 is recorded as it appears on the item. If there are two or three names in the first statement of responsibility, subsequent names after the first will often be names with alternative responsibility.

720 FAMILY NAME – PRIMARY RESPONSIBILITY

If field 721 is used for names of families of alternative responsibility, field 720 (or rarely 710 or 700) must be present. If field 721 is used because the cataloguing rules do not recognise the concept of main entry, or the source format does not distinguish it, then field 720 will not be present.

722 FAMILY NAME – SECONDARY RESPONSIBILITY

If there are families considered to have less responsibility than persons or entities in fields 700, 701, 710, 711, 720, 721, they should be entered in field 722.


Examples


The form of the data in the examples under field 720 applies equally here.



722   FAMILY NAME – SECONDARY RESPONSIBILITY

Field Definition


This field contains the name of a family considered to have secondary responsibility for a work, in a form suitable for an access point.

Occurrence


Optional. Repeatable.

Indicators


Indicators are as for field 720.

Subfields


Subfields are as for field 720 with the following addition:

$5 Institution to which the Field Applies

Name of institution to which field applies in coded form. Codes should be entered in accordance with the provisions of International Standard Identifier for Libraries and Related Organizations (ISIL), ISO 15511. (Existing records may contain codes from MARC Code List for Organizations, the full name of the agency or a national code). If the institution holds more than one copy the shelfmark of the item should be added after a colon; however, it is strongly recommended that this be done even if the copy is the only one held at the time of cataloguing. Mandatory. Not repeatable.

Notes on Field Contents


The same guidelines apply as for field 720.

Subfield $5, Institution to which the Field Applies, is used only when the added entry/ies are peculiar to an individual copy. It is generally used for older monographic publications (antiquarian).


Related Fields


200 $f, $g TITLE AND STATEMENT OF RESPONSIBILITY, First Statement of Responsibility, and Subsequent Statement of Responsibility

Data in field 200 is recorded as it appears on the item. The name of the family mentioned in $f or in $g to whom is attributed secondary responsibility for the item (if any) will be entered in field 722 in access point form.

720 FAMILY NAME – PRIMARY RESPONSIBILITY

The name of the first family mentioned in the title page with primary responsibility should be entered in field 720. Names of families with secondary responsibility are entered in 722.

721 FAMILY NAME – ALTERNATIVE RESPONSIBILITY

Alternative means a second or further instance of primary responsibility. However, if the record is catalogued according to rules which do not recognise the concept of main entry, or the source format does not separately identify it, all family names should be entered in field 721.



Examples

The form of the data in the examples under field 720 applies equally here.




730   NAME – ENTITY RESPONSIBLE

Field Definition


This field contains in unstructured form the name of an entity considered to have responsibility for a work. The name does not follow cataloguing rules.

Occurrence


This field should be used only when other 7-- fields are unsuitable. Repeatable.

Indicators


 Indicator 1:  Form of Name Indicator

This indicator specifies whether the type of name has been detemined or not.

0  Type of name cannot be determined

1  Personal name

2  Not a personal name

 Indicator 2:  blank (not defined)


Subfields


$a Entry Element

The name used as the entry element in the heading. Not repeatable.

$4 Relator Code

The code used to designate the relationship between the entity named in the field and the bibliographic item to which the record refers. The list of codes is to be found in Appendix C. Repeatable.


Examples


EX 1: 730 0#$aDerek Weselak$4070

Dublin Core:

The record was converted from a Dublin Core entry which makes no distinction between personal authors and others. "Creator" has the sense of primary responsibility for the item so the relator code for "author" is added.

EX 2: 730 2#$aInformation Systems, British Library$4070

Dublin Core:

EX 3: 730 1#$Weselak$bDerek

Dublin Core:

CONTENT takes the form "term comma term" and the NAME is "Creator.Personal". The name could with some confidence be assigned to a more specific 7-- field by the use of computer algorithms.

EX 4: 730 0#$aDerek Weselak

Dublin Core:

The record was converted from a Dublin Core entry which makes no distinction between personal authors and others. "Contributor" has the sense of any responsibility for the item other than primary responsibility, e.g. illustrator, sponsor, so no relator code can be added.


Download 5.17 Mb.

Share with your friends:
1   ...   114   115   116   117   118   119   120   121   ...   148




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

    Main page