Відмінності між версіями «Auth / 104 Кодовані дані: Основні дати»
Dubyk (обговорення • внесок) (→Індикатори) |
Dubyk (обговорення • внесок) (→Індикатори) |
||
| Рядок 18: | Рядок 18: | ||
==Індикатори== | ==Індикатори== | ||
| − | + | ||
Indicator Value Description | Indicator Value Description | ||
1 # blank (not defined) | 1 # blank (not defined) | ||
2 # blank (not defined) | 2 # blank (not defined) | ||
| + | |||
Subfields Description | Subfields Description | ||
$a Date of Beginning or Unique Date | $a Date of Beginning or Unique Date | ||
Версія за 15:22, 29 квітня 2026
Зміст
104 Кодовані дані: Основні дати
Тег: 104
Назва поля: Кодовані дані: Основні дати
Інші назви: Coded data field: Main dates of entity (англ.)
Визначення поля
Основна дата або період часу служить для характеристики авторизованої точки доступу в полях 2XX. Це поле можна використовувати для будь-якої сутності, яка відповідає IFLA LRM.
Наявність
Обовʼязкове.
Не повторюється.
Індикатори
Indicator Value Description 1 # blank (not defined) 2 # blank (not defined)
Subfields Description $a Date of Beginning or Unique Date The first or unique date that is associated with the entity described in the 2XX field. This date includes: - a person's date of birth or the earliest date in a period of activity; - the year a corporate body was established, a date on which a conference was held, or the earliest date in a period of activity of a corporate body; - the earliest date associated with a work or expression (e.g. the date the work was created or first published or released or the date of the earliest known manifestation of the expression). The type of date and level of detail chosen in this subfield depend on the type of entity and the practices of individual cataloguing rules. Not repeatable. List of fixed length data elements for subfield $a: Name of Data Element Number of Characters Character Position Era 1 0 Date 8 1-8 Date Reliability 1 9 The data element Era is mandatory if the subfield is used. $b Final Date The latest date in the period that is associated with the entity described in the 2XX field. This date includes: - a person's date of death or the latest date in a period of activity; - the year a corporate body was terminated or the latest date in a period of activity of a corporate body; - the ending date of the date range associated with a work or expression. 104 CODED DATA FIELD: MAIN DATES OF ENTITY UNIMARC Authorities Format Manual (online ed., 1.2.0, 2025) 2/5 The type of date and level of detail chosen in this subfield depend on the type of entity and the practices of individual cataloguing rules. Not repeatable. List of fixed length data elements for subfield $b: Name of Data Element Number of Characters Character Position Era 1 0 Date 8 1-8 Date Reliability 1 9 The data element Era is mandatory if the subfield is used. Notes on Field Contents $a/0 Era 1-character code indicates the era associated with the entity described. c date falls before the year 1 in the Gregorian calendar, i.e. B.C. d date falls after the year 1 in the Gregorian calendar, i.e. A.D. $a/1-8 Date 8-numeric characters in ISO standard form (ISO 8601) for dates: YYYYMMDD where YYYY represents the year, MM the month with leading 0 if necessary, and DD the day of the month with leading 0 if necessary. If any digit in a year, month, or day is unknown or not needed, the character position should be left blank. $a/9 Date Reliability 1-character code indicates the reliability of the date.
- certain date
? uncertain date $b/0 Era 1-character code indicates the era associated with the entity described. c date falls before the year 1 in the Gregorian calendar, i.e. B.C. d date falls after the year 1 in the Gregorian calendar, i.e. A.D. $b/1-8 Date 8-numeric characters in ISO standard form (ISO 8601) for dates: YYYYMMDD where YYYY represents the year, MM the month with leading 0 if necessary, and DD the day of the month with leading 0 if necessary. If any digit in a year, month, or day is unknown or not needed, the character position should be left blank. $b/9 Date Reliability 1-character code indicates the reliability of the date.
- certain date
? uncertain date Related Fields 122 CODED DATA FIELD - TIME PERIOD OF WORK CONTENT Used for information on the date or time period covered by the content of a work. 104 CODED DATA FIELD: MAIN DATES OF ENTITY UNIMARC Authorities Format Manual (online ed., 1.2.0, 2025) 3/5 340 BIOGRAPHY AND ACTIVITY NOTE Use for additional information regarding the dates contained in field 104. 341 ACTIVITY NOTE PERTAINING TO PRINTER/PUBLISHER Use for additional information regarding the dates contained in field 104. 640 PLACES AND DATES ASSOCIATED WITH THE ENTITY Field 104 contains the dates chosen by the cataloguer as the dates to be used in the authorized access point. For recording other dates or periods, use field 640. Examples EX 1 104 ##$a#1803#####$b#1869##### 200 #1$aBerlioz$bHector$f1803-1869 340 ##$cCompositeur$cChef d'orchestre 640 1#$aFR$cIsère$dLa Côte-Saint-André$f#18031211# 640 2#$aFR$dParis$f#18690308# According to the cataloguing rules, the year of birth and death is needed to distinguish between authorized access points. Dates of birth and death that include the month and day associated with the places are entered in field 640. EX 2 104 ##$a#1637#####$b#1714##### 200 #1$aLeclerc$bSébastien$f1637-1714 340 ##$aMembre de l'Académie royale de peinture et de sculpture (à partir du 16 août 1672)$aGraveur du roi (à partir de 1688 ?)$cDessinateur$cGraveur 640 1#$aFR$dMetz$f#16370926# 640 2#$aFR$dParis$f#17141025# 640 4#$aFR$dParis$f#1665#####$i#17141025# The dates of birth and death, following the cataloguing rules, are entered in field 104 while the precise dates of birth and death associated with the places and the residence period in Paris are entered in repeated fields 640. The date of birth may also include the month and day of the person’s birth. EX 3 104 ##$a#1946#####$b#1958##### 210 01$aFrance$bAssemblée nationale$f1946-1958 340 ##$aUne des deux chambres parlementaires sous la Quatrième République en France instituée par la Constitution française du 27 octobre 1946 640 1#$aFR$f#19461128# 640 2#$aFR$f#19581208# EX 4 104 ##$a#19911107# 231 ##$8frefre$aConvention sur la protection des Alpes$d1991-11-07 370 ##$aTraité multilatéral qui a pour objectif à long terme la sauvegarde de l'écosystème naturel des Alpes et leur développement durable.$cAdoptée le 7 novembre 1991 à Salzbourg, la Convention sur la protection des Alpes (ou Convention alpine) a été signée par les huit pays alpins : l'Autriche, la France, l’Allemagne, l’Italie, la Suisse, le Liechtenstein, la Slovénie et Monaco ainsi que l’Union européenne, et est entrée en vigueur le 6 mars 1995$cRatifiée par la France (loi n° 95-1270 du 06-12-1995) et publiée par le décret n° 96-437 du 20 mai 1996 640 0#$0Adoption$aAT$dSalzbourg$f19911107 640 0#$0Entrée en vigueur$f19950306 640 0#$0Signature par la France$f19911107 104 CODED DATA FIELD: MAIN DATES OF ENTITY UNIMARC Authorities Format Manual (online ed., 1.2.0, 2025) 4/5 640 0#$0Ratification par la France$f199400610 731 ##$8freger$aÜbereinkommen zum Schutz der Alpen$d1991-11-07 731 ##$8freita$aConvenzione per la protezione delle Alpi$d1991-11-07 731 ##$8freslv$aKonvencija o varstvu Alp$d1991-11-07 According to the cataloguing rules, the adoption date of the treaty is chosen as the main date for the entity. Other dates (e.g., the ratification date, date of signature, etc.), are entered in fields 640. EX 5 104 ##$a#1862##### 241 ##$1001$1FRBNF13891412$1200#1$aBerlioz$bHector$f1803-1869$1231##$aLes Troyens$sH 133A 370 ##$aOpéra en 5 actes et 9 tableaux, en deux parties : “La Prise de Troie” (actes I et II), “Les Troyens à Carthage” (actes III, IV et V)$cDates de composition : avril 1856-1858$cDates de révision : nos 33 et 40 (1859), no 44 (1859 ou 1860), no 52 (janvier 1860)$c1re éd. privée (chant et piano) : Paris : imprimé par Thierry frères, [1862]$a1re représentation (“La Prise de Troie”) : Karlsruhe, Hoftheater, 6 décembre 1890. 1re représentation (“Les Troyens à Carthage”) : Paris, Théâtre-Lyrique, 4 novembre 1863 640 5#$f#185604###$i#1858##### 640 0#$0Révision$f#1859#####$i#1860##### 640 0#$0Première édition$f#1862##### 640 6#$dKarlsruhe$eHoftheater$f#18901206# 640 6#$dParis$eThéâtre Lyrique$f#18631104# Depending on the cataloguing rules, the main date of work can either be the date of the earliest public presentation, the publication date (as is the case in this example), or the date of the earliest execution or representation. In this case, the main date of the entity (field 104) is not used in the access points because the title, author, and reference number of the work in a thematic catalogue (241 $s) are more relevant for the identification of the work. EX 6 104 ##$a#1929##### 242 ##$3FRBNF13917708$aRavel, Maurice (1875-1937)$tBoléro$sO 81$lArrangement$vPiano (4 mains) 300 ##$aArrangement pour piano à 4 mains par Maurice Ravel de sa musique de ballet, “Boléro” 640 5#$0Arrangement$f#1929### 640 0#$0Première édition$f#1929##### The main date of the entity (field 104) is not needed in the access points for this expression of a musical work. EX 7 104 ## $a#1990##### 242 ##$3FRBNF13917708$aRavel, Maurice (1875-1937)$tBoléro$sO 81$lArrangement $vPiano (4 mains)$nMusique exécutée$wAchatz ; Nagai 300 ##$aInterprétation de l’arrangement pour piano à 4 mains de Maurice Ravel par les pianistes Dag Achatz et Yukie Nagai, enregistrée le 29 juillet 1990 à Danderyd (Suède), Grammar school 640 5#$0Interprétation/exécution$aSE$dDanderyd$eGrammar school$f#19900729# 640 7#$aSE$dDanderyd$eGrammar school$f#19900729# The main date of the entity (field 104) is not used in the access points, since this interpretation of the arrangement for piano in four hands by pianists Dag Achatz and Yukie Nagai was recorded only on July 29, 1990, in Danderyd (Sweden). According to cataloguing rules, the main date of the entity (field 104) is used in the access points for an expression of a musical work when the same work (or arrangement of work) is performed by the same performers on different dates.
History
2021 New field. 2022 Text errata. 2025 Text edit