My Content International Standard Bibliographic Description (ISBD) (1969 UNESCO) Outline of the ISBD (G) 8 ElementsCommon Communication Format (CCF) Scope and use of CCF Structure of CCF Record Label DirectoryMARC - 21MARC - 21Important Field of MARC-21MARC (lis link)Structure of MARC TapesAdvantages of Using MARCMachine Readable Cataloguing-21 (MARC-21)Necessity of MARC 21Standard used in MARC 21MARC Tags and SubfieldMARC 21 structureGeneral Record structure of MARC 21 Leader Directory Variable Fields ConclusionResources Description and Access (RDA) Underlying Principles of RDAFRBRFRADStatement of International Cataloguing PrinciplesStructure of RDAFunctional Requirements for Bibliographic Records. (FRBR) Entities expression Manifestation FRBR Relationships Work-to-work User tasksBIBFRAME 2016 BIBFRAME "The Project" The BIBFRAME model
Standards of Bibliographic Record Formats and Description ISBD, MARC-21, CCF, RDA, FRBR, Bibframe
International Standard Bibliographic Description (ISBD) (1969 UNESCO)
The next step towards international agreement after the paris conference was taken at the International Meeting of Cataloguing Experts (IMCE) held in Copenhagen in 1969. As a result of this meeting, International standard Bibliographic Description (ISBD) was formulated and issued in 1971.
The first of the ISBDs was the International Standard Bibliographic Description for Monographic Publication (ISBD-M), which appeared in 1971.
In 1975, the General International Standard Bibliographic Description (ISBD-G) was developed and The ISBD (G), published in 1977. The primary aim of this code was to prescribe the order of bibliagraphic elements and punctuation marks on a record so that uniformity could be maintained in the cataloguing.
Outline of the ISBD (G) 8 Elements
1. Title and statement of responsibility area
2. Edition area
3. Meterial (or type of Publication) Specific area.
4. Publication, distribution, etc. area
5. Physical description area.
6. Series area.
7. Note area.
8. Standard number (or alternative) and terms of availability area.
Common Communication Format (CCF)
UNESCO held in Taormina, sisily.
1st ed. 1984
2nd ed. 1988
3rd ed. 1992
The Common Communication Format (CCF) was developed under the auspices of United Nations Educational, Scientific and Cultural Organization (UNESCO) in order to facilitate the exchange of bibliographic data between organization. These had begun in earnest with the project known as UNISIST (Refers to UNESCO's Intergovermental Programme for cooperation in scientific and Technological Information) which involved cooperation between UNESCO and ICSU - AB ( the International Council of Scientific Unions Abstracting Board). The first edition of the format was published in 1984, Second Edition was published in 1988 and third edition was published in 1992. It has been developed as an ISO-2709 exchange format and has adapted the second revised edition of the Anglo American Cataloguing Rules (AACR) as a standard for data entering. Visit the following link and search for "CCF".
First Published under the editorship of Peter Simmons and Hopkins.
Scope and use of CCF
Following are the scope and use of CCF.
i. To permit the exchange of records between groups of information agencies, including libraries, abstracking and indexing services, referral systems and other kinds of information agencies.
ii. To permit the use of a single set of computer programs to manipulate records received from various informations agencies regardless of their internal record-creation practices.
iii. To serve as the basis of format for an agency's own bibliographic or factual database, by providing a list of useful data elements. To assist the development of individual systems, unesco has published implementation notes for users of the Common Communication Formats (CCF).
Structure of CCF
The record structure of the CCF constitutes a specific implementation of the international standard ISO-2709: Each CCF record consists of four major parts :
Record label (24 character)
Directory (14 character)
Data fields
Record Separators (1 character)
Record Label
Each CCF record begins with a fixed length label of 24 characters, the contents are as given below :
Character Position. Content
0-4 Record length. The length of the recon includes the table, directory, data fields and record separator.
5 Record status, using the following code.
a = New Record
b = Replace record
c = Deleting record
6 Blank, this character position is not used.
7 Bibliographical level of the target item i.e.
s = Serial
a = component Part
e = Made-up Collection
8 Blank, this character Position is not used.
9 Blank, this character Position is not used.
10 "2" The Subfield identifier length. This shows the number of indicator characters in each subfield identifier.
11. "2" the Subfield identifier length. This should the number of indicator characters in each subfield identifier.
12-16 Base address of data. The location within the record at which the first data field being begins, relative to the first characters used as the subfield identifier.
17-19 Blank, these character Positions are not used
20 "4" the length of data field in the directory.
21 5' the length of starting character content.
22 "2" "The length of Implementation defined section of each entry in the directory. One is used for segment identifier and other is used for occurrence identifier.
23 Blank, this character position is not used.
Directory
The directory is a table containing a variable number of fourteen character entries; a f ield separator character terminate the table. Each directory entry compesponds to an occurrence of a data field in the record and is divided in five parts.
TAG LENGTH OF STARTING SEGMENT OCCURRENCE
3 character DATA FIELD CHARACTER IDENTIFIER IDENTIFIER
4 character POSITION 1 character 1 character
5 character
Data fields
A datafields consists of
• Indicator
• One or more subfields each of which is preceded by a subfield identifier.
• A data field separator.
A datafield, which has a single subfield will be organised as follows:
INDICATORS. SUBFIELD SUBFIELD FIELD SEPARATOR IDENTIFIER Variable
2 character 2 character 1 character
A data field, which has a single subfield will be organised as follows.
INDICATOR First sub field FIRST subfield Second subfield Second subfield Field separator
IDENtifier variable identifier variable
character 2 character 2 character 2 character 1
MARC - 21
The MARC pilots project was an experiment conducted by the Library of Congress, in cooperation with 16 participating cataloging data into machine-readable from for distribution of magnetic tapes. MARC (Machine Readable Cataloging) records were distributed for some 16,000 titles in the pilot phase from November 1966. MARC - 1 format entirely based on LC Catalogue Card BNB (with active participation with LC) Makes some operational changes to make it interchangeable format. As a result MARC - II was developed in 1968. MARC was first developed by Henriette Avram.
US MARC becomes US national standard in 1971 (ANSI Z39.2) and international standard in 1973 (ISO2709)
UNIMARC, IFLA 1st verson of UNIMARC was developed in 1977, only for monographs and serial, UNIMARC follows the ISO communication format ISO - 2709 (1981) .
MARC - 21
MARC 21 formats are standards for the representation and communication of bibliographic and related information in machine-readable form MARC-21, is a result of the combination of the united states and canadian MARC formats (USMARC and CANMARC) was developed in 1999. The MARC 21 formats are maintained by the Library of Congress in consultation with various user communities. The development of the MARC-21 formats is an international effort with avenues for all MARC 21 user to substantially contribute to it. The library of congress and the library and archives canada serve as the maintenance agency for the MARC-21 formats for bibliographic, authority, holdings, classification, and community information data for the MARC 21 user community.
Important Field of MARC-21
010 tag - Library of Congress Control Number (LCCN)
020 tag - International Standard Book Number (ISBN)
100 tag - Personal name main entry (author)
245 tag - Title information (which includes the title, other title information, and the statement of responsibility
250 tag - Edition 260 dag - Publication information
300 tag - Physical description (often referred to as the "collation" when describing books)
490 tag - series statement
520 tag - Annotation or Summary note.
650 tag - Topical Subject heading.
700 tag - Personal name add entry (joint author, editors or illustrator)
Bibliographic format blacks
oxx control information numbers, codes.
1xx Main Entry.
2xx Titles, edition, imprint
3xx Physical description, etc.
4xx series statements.
5xx Notes. 6xx Subject access fields
7xx Name, etc. added entries or series. linking.
8xx series added entries, holdings and locations.
9xx Reserved for local implementation
lis link
Machine Readable cataloguing (MARC) MARC format has become a generic term to all MARC formats including UKMARC, CANMARC, Inter MARC, etc. which are used for the identification and arrangement of bibliographical data for handling by computer.
The first conference on Machin Readable Cataloguing was sponsored by the library of congress. The committee on Automation of the Association of Research Libraries (ARL) and Council of Library Resources (CLR) was met at the Library of Congress. This conference recommended that.
i. MARC records should include additional information to be used as multipurpose records, in addition to information available on printed card.
ii. The element of MARC data should be standardized.
iii. MARC records should be produced and distributed to libraries which have automated system.
In the second conference held at the Library of Congress in November 1965, Library of Congress sought funds form CLR and in December 1965 in received a grant to conduct a pilot project.
In early January 1966 the planning for the pilot project began. The third conference was held in February 1966 at the library of congresso which was considered the official opening of the pilot project for machine readable cataloguing data. The Pilot Project was called MARC - I. In this way the MARC - I format was set up in April 1966 which was restricted to books only. The distribution of regular weekly service of MARC tapes started from now 1966. The MARC - I format was based entirely on the structure of the Library of Congress Catalogue Card. So, BNB (with active collaboration with Library of Congress) made some operational changes to make it interchangeable record format. As a result, MARC - Ii was developed. It is capable of containing bibliographic data of all forms of library material such as books, monographs, serial, map, music, etc. By subscribing to this service a library can acquire magnetic tapes in machine readable form.
Due to the differences between the British Library and the Library of Congress MARC - II was later split into two formats-BNB MARC (later UK MARC) and US MARC format becomes the US National standard in 1971 (ANSI Z39.2) and an International standard in 1973 (ISO 2709) The MARC - II also influenced the other countries to develop their own standard format which followed the same structure but the tags were slightly different. As a result, certain amount of incompatibility exists among the different countries. To solve this problem IFLA, launched a programme known as UNIMARC (1977), but eventually it failed.
Structure of MARC Tapes
a. Leader : It provides information about ensuring such records as total length of the record, the type of record, etc. It is 24 characters (00-23) lang.
b. Record Directory It shows what variable fields are in the record and what their locations in the record are. It is of 12 characters long.
c. Variable Field The variable fields are of two types- variable control field (001-009) and variable data field.
Advantages of Using MARC
a. MARC tapes can be used by individual libraries for producing their conventional card catalogue / book form of catalogue, etc.
b. It helps in the creation of centrally prepared catalogue.
c. Distribution of MARC tapes to the receiving libraries avoid duplication of effort.
d. Uses of MARC taped make different library software compatible to one another.
e. MARC tapes can be used computerized SDI service.
f. MARC tapes perform sharing of bibliographical information.
Machine Readable Cataloguing-21 (MARC-21)
MARC-21 is a standard format for the make up or representation and communication of bibliographic data and related information in machine readable form. It is a representation and communication of bibliographic and related information in machine - readable form. It provides a framework for catalogue record. It is widely used to enter the records for the online catalogue so that the bibliographic information can be exchanged among automated library systems by way of copy cataloguing and other means. However, not everything in MARC is captured on OPAC display of a record MARC 21 is a result of the harmonization of USMARC and Canadian MARC (CANMARC). The MARC-21 standards include formats for authority records, holding records, classification schedules and community information in addition to the format for bibliographic record.
ISO 2709 defines how the marked up record in formatted so that it can be read by computer programs and can be transferred among computer ISO 2709 is usually referred to as the MARC communications format.
It was developed by Henriette Avram at the us library of congress during the 1960s to create records that can be used by computers and to share those records among libraries.
The Network Development and MARC standards office is a center for library and information network standards and planning in the library of congress. Established in 1976 to provide focus for networking activities in the library of congress, the office was expanded in 1984 to include MARC standards responsibilities. In 1987, the Library of congress issued the first edition of the document MARC-21 subsequent editions were published in 1990, 1994 and 2000.
The library of congress and the National library of Canada serve as the maintenance agency for MARC-21. The MARC-21 format, documention and reviewing and revision are done by the Machine Readable Bibliographic Information Committee (MARBI). MARBI is a committee of the ALA. MARBI meets in conjunction with MARC advisory committee at each American Library Association (ALA) conference.
Necessity of MARC 21 : Mark 21 is necessary because of the following factors
i. Lack of standardization among different national MARC formats.
ii. Lack of internationally accepted cataloguing code to MARC record.
iii. Diverse functions of bibliographic agencies.
iv. Lack of agreement among different biblingraphic communities.
Standard used in MARC 21 : The following standards are used in the MARC-21 format
i. Cataloguing code : AACR-II
ii. Subject Heading : LCSH
iii. Classification scheme: DDC
iv. ISO 2709 and ANSI/NISO Z39.2
Till now, MARC 21 remains the standard one which is widely accepted in different library softwares and also in different countries.
MARC Tags and Subfield : The data in a MARC 21 recond is organized into fields, each identified by a three-character tag. Although ANSI Z39.2 and ISO 2709 allow both alphabetic and numeric Characters, MARC 21 formats use only numeric tags.
oxx - Control information, numbers, and codes
1xx - Main entry
2xx - Titles and title paragraph (title, edition, imprimt)
3xx - Physical description etc.
4xx - Series Statements.
5xx - Notes
6xx - Subject access fields
7xx - Added entries other than Subject or series; linking fields
8xx - Series addes entries; location, and alternate graphics.
9xx - Reserved for local implementation
oxx : The leader (000), Control number (001), MARC code for organization (003) and date and time of last transaction (005) are computer generated fixed fields and the cataloguer has no control over it. 001 field is generated by the OCLC, LC or the library management system that is used to create the record. The coded general information (800) is partially computer generated fixed fields.
1xx - The main entry fields are not repeatable.
MARC 21 structure
The structure of MARC record is divided into three elements record structure, content designation and data content of the record.
a. Record structure The record structure is an implementation of the international standard format for Information Exchange (ISO 2709) and its American counterpart, Bibligraphic. Information Interchange (ANSI/NISO Z39.2). It is the overall framework for the record.
b. Content Designation Content designation is set of symbols by which data in the record are identified and manipulated. The codes and conventions established explicitly to identify and further characterize the data elements within a record and to support the manipulation of that data.
c. Content of the Data Content of the data are record specific information f ield by field. Content of the data elements is usually defined by standards outside the formats. Examples are the International Standard Bibliographic Description (ISBD). Anglo-American Cataloguing Rulers, Library of Congress Subject Headings (LCSH), or other cataloging rules, subject thesauri and classification schedules (DDC, UDC, etc.) used by the organization that creates a record. The content of certain coded data elements is defined in the MARC formats (eg. the leader, field 007, field 008).
General Record structure of MARC 21
The general structure of a record is represented schematically below.
LEADER DIRECTORY FT CONTROL NUMBER FIELD FT
CONTROL FIELD 1 FT CONTROL FIELD n FT
DATA FIELD 1 FT DATA FIELD n FT RT
a. Leader
Each record begins with a leader, which is fixed field containing information for the processing of the record. The leader is the first field in the record and has a fixed length of 24 octets (character positions 0-23). Only ASCII graphic characters are allowed in the leader. This is something the cataloguer do not have much control. Only a fee coded data are needed to be determined by the cataloguer i.e. type of record, bibliographic level.
b. Directory
The directory begins immediately after the leader. The directory is generated by the computer for locating data fields with the help of their address. The address mechanism comprises there components f ield tag, field longth and starting position, which are place consecutively without any space in between. Each directory entry is 12 characters in length. The directory begins in character position 24 of the record. The first three digit of each entry contains tag, following each tag the next four positions show the length of the field and the next five positions tell the starting point for the f ield. The directory ends with a field terminator (FT), ASCII control character IE (hex).
c. Variable Fields
The variable fields follow the leader and the directory in the record and consist of control fields and data fields. Control fields precede data f ields in the record. The data content has the related bibliographic data as data fields. Two kinds of content designations are used within variable data f ields indicators and subfield codes. The indicators are two one-character. positions that contain values that interpret the data found in the field. Every field does not have the indicator. Each subfields code is preceded by a character called delimiter and is followed by an alphabetic or numeric character.
Conclusion
Machine-readable cataloguing for assigning labels to various parts of a bibliographic record is a convenient method in which information can be identified and used by computers. The structure of a machine readable record is known as format MARC 21 is a general format for representing bibliographic information and is a standard for the representation and communication of data in machine-readable form MARC format has become a generic term to all MARC formats including UKMARC, CANMARC, Inter MARC and is used for the identification arrangement of bibliographical data for handling by computer. The USMARC format became the US National Standard in 1971 (ANSI Z39.2) and an international standard in 1973 (ISO 2709). To solve the problem of incompatible nature among different countries, IFLA launched a programme known as UNIMARC. UNIMARC followed the ISO communication format ISO-2709 (1981), but it failed. The UNESCO also came up with CCF, which is the implementation of ISO-2709 to solve the problem of incompatibility. Several countries have adopted this standard for exchange and creation of bibliographic record at national level. The MARC 21 is a new name of harmonization of CANMARC and USMARC in a single edition. It uses the standard AACR-II, LCSH, DDC, ISO-2709 and ANSI/NISO Z39.2. Till now, MARC -21 remains the standard one which is widely accepted in different library software and also in different countries.
Resources Description and Access (RDA)
In 1997, the joint steeping committee for rivision of AACR (JSC) organized the International Conference on the priciple and Future Development of AACR in Toronto to book at future directions for the Anglo--American Cataloguing Rules. The JSC decided to develop a new cataloguing code called AACR3.
In December 2004, JSC distributed. a full first draft of part-1 of the code. The public reaction and comments on the draft were suprising. Many of the cataloguers did not like to change the rules. On the othey hand, many people were expecting a greater change in the cataloguing.
They decided that a new standard designed for the digital environment was more appropriate. In April 2005, the agreed to abandon the title Anglo American Cataloguing Rulers and took a new working title for the code i.e. RDA, Resource Description and Access.
Underlying Principles of RDA
RDA is based on :
• Functional Requirements for Bibliographic Records (FRBR)
• Functional Requirements for Authority Data (FRAD)
• Statement of International Cataloguing Principles
FRBR
• FRBR includes a conceptual model of entities and relationships and attributes.
• Identifies specific user tasks that bibliographic records are intended to fulfill.
• Find, identify, select, obtain; and
• Recommends a set of elements for including in national bibliographic records.
FRAD
FRAD is a conceptual model to provide an analytical framework for the analysis of functional requirements for the kind of authority data that is required to support authority control and for the international sharing of authority data. The model focuses on data, regardless of how it may be packaged (e.g. in authority records).
Statement of International Cataloguing Principles
RDA is being developed in line with a set of objectives and principles which are based on the statement of International cataloguing principles, developed by the IFLA meetings of experts on an International cataloguing code (IME ICC).
• The statement of International Cataloguing Principles sets the objectives and Functions of the catalogue in the following terms.
• The catalogue should be an effective and efficient instrument that enables a user :
1. to find bibliographic resource in a collection as the result of a search using attributes or relationships of the resources.
1.1 to Find a single resource.
1.2. To find a single resource
• All resources belonging to the some work
• All resources embodying the same expression
• All resources exemplifying the same manifestation
• All resources associated with a given person, family, on corpostate body.
• All resources on a given subject.
• All resources defined by other criteria
(language, place of publication, publication date, content type, carrier type, etc.), usually as a secondary limiting of a search result.
2. to identify a bibliographic resource or agent (that is, to confirm that the described entity corresponds to the entity sought or to distinguish between two or more entities with similar characteristics)
3. to select a bibliographic resource that is appropriate to the user's needs (that is to choose a resource that meets the user's requirements with respect to medium, content, carrier, etc, or to reject a resource as being inappropriate to the user's needs)
4. to acquire or obtain access to an item described (that is, to provide information that will enable the user to acquire an item through purchase, loan, etc. or access an item electronically through an online connection to a remote source); or to access, acquire, or obtain authority data or bibliographic data.
5. to navigate within a catalogue and beyond (that is, through the logical arrangement of bibliographic and authority data and presentation of clear ways to move about, including presentation of relationships among works, expressions manifestations, items, persons, families corporate bodies, concepts, objects, events and places).
Structure of RDA
There are two main parts of RDA :
• A series of sections defining the attributes that may be used to describe each of the FRBR entities (sections 1-4)
• A series of sections defining the relationships that may be made among these entities (sections 5-10)
• Each section begins with a chapter of general instruction, followed by chapters for specific entities.
•RDA consist of:
• 10 sections with 37 chapters.
• And 12 appendices
• Glossary
• Index
Section - 1 : Recording attributes of manifestation and item.
Chapter - 1 : General, guidelines on recording attributes of manifestation and item
Chapter - 2: Idendifiying manifestation and item
Chapter - 3 : Describing Carriers
Chapter - 4 : Providing acquisition and access information
Section 2 : Recording attributes of work and expression
Chapter - 5 : General guidelines on recording attributes of works and expression
Chapter - 6 : Identifysing work and expression
Chapter - 7 : Describing additional attributes of works and expression.
Section - 3 : Recording attributes of person family and corporate body.
Chapter 8 : General guidelines on recording attributes of persons, families, and corporate bodies.
Chapter 9 : Identifying person.
Chapter 10 : Identifying families.
Chapter 11 : identifying corportate bodies.
Section 4 : Recording attributes of concept object, event and place
Chapter 12 : General guidelines on recording attributers of concepts, objects, event and place.
Chapter 13 : Identifying concepts.
Chapter 14 : Identifying objects.
Chapter 15: Identifying events. (Chapter 13-15 to be developed after the initial release of RDA)
Chapter 16 : Identifying Places.
Section 5: Recording Primary relationships between work, expression, manifestation and item.
Chapter 17: General guidelines on recording primary relationships between a work, expression, manifestation and item.
Section 6 : Recording relationships to persons families, and corporate bodies associated with a resource.
Chapter 18 : General guidelines on recording relationships to persons, families and corporate bodies associated with a resource.
Chapter 19 : Persons, families, and corporate bodies associated with a work.
Chapter 20 : Persons, families and comporate bodies associated with a expression.
Chapter 21: Persons, families and corporate bodies associated with a manifestation.
Chapter 22 : Person, families and corporate bodies associated with an item.
Section 7 : Recording Subject relationships
Chapter 28 : General guidelines the subject of a work (To be developed after the initial release of RDA.)
Section - 8 : Recording relationship between works, expression, manifestations and items
Chapter 24 : General guideline on recording relationship between work, expressions, manifestation and items
Chapter 25 : Related works.
Chapter 26 : Related manifestation
Chapter 27 : Related pilession
Chapter 28 : Related items.
Section 9 : Recording relationships between persons, families and corporate bodies.
Chapter 29 : General guidelines on recording relationships between persons families, and corporate bodies,
Chapter 30 : Related Persons.
Chapter 31 : Related families.
Chapter 32 : Related corporate bodies.
Section 10 : Recording relationship between concepts, objects, events and places
Chapter 33 : General Guidelines or recording relationships between concepts. objects, events, and places.
Chapter 34 : Related concepts.
Chapter 35 : Related objects.
Chapter 36 : Related events.
Chapter 37: Related places.
Appendices
A. Capitalization
B. Abbreviation
C. Initial articles.
D. Record syntaxes for descriptive data.
E. Record syntaxes for access point control data
F. Additional instructions on names of persons.
G. Titles of nobility, terms of ranks, etc.
H. Converson of datas to the Gregorian calendar
J. Relationship designators : Relationships between a resource and persons, families and corporate bodies associated with the resource.
K. Relationship designators : Relationships between works, expression, menifestations and items.
L. Relationship designators: Relationship between persons, families and corporates bodies.
M. Relationship designators : Relationship between concepts, objects, events and places.
Functional Requirements for Bibliographic Records. (FRBR)
conceptual entity relationship model.
anthor Name 'Ferber'
FRBR a conceptual model. Based on the entity attribute relationship model of analysis.
• Entities of interest to users of bibliographic systems are identified.
• Attributes of interest of users are identified for each entity.
• Relationships that operate between entities are specified
• 1992-1992 IFLA FRBR working Group
• 1997 IFLA FRBR Final Report
Entities
Three groups of Entities
Group 1 : The products of intellectual or artistic endeavor that are named or described in bibliographic records (work, expression, manifestation and item) WEMI Ex-Book
Group 2 : entities that are responsible for intellectual or artistic content, physical production and dissemination or custodianship of such products (person and corporate body) Ex-Author's.
Group 3 : entities in addition to those in Group / and 2 that may serve as the subjects of intellectual or artistic endeavor (concept, object, event and place)
Group I entities,
work, expression, Manifestation, item
Work
• distinct intellectual or artistic creation
• abstract entity with an single materia object one can point to
• recognized through individual expression of the work.
e.g. Saratchandra Chattopadhyay's "Devdas" the movie "Devdas"
expression
• realization of a work in alpha-numeric, musical or choreographic notation, sound, image, object, movement etc, or any combination of such forms.
• A new expression excludes aspects of physical form (eg. typeface) that do not change intellectual or artistic realisation of the work.
e.g. for Sarakchandra Chattopadhyay's "Devdas"
e.g. e1 - 1348 | Bengali Calender edition Published by Mitra o Ghosh.
e2 - 2006 edition illustrated with scenes from the movie.
e3 - version translated in Tamil.
Manifestation
• physical embodiment of an expression of a work; when production involves changes in the physical from (or format) it results in a new manifestation.
e.g. Saratchandra Chattopadhyay's "devdas"
e1 - original text document.
m1 - 1348 Publication
m2 - photocopy of my
e.g. The Telegraph
e1 - Paper version.
m1 - Print-on-Paper format
m2 - microfilm format.
item 'Concrete'
• A single exemplar of a manifestation.
• normally the same as the manifestation itself.
• however, variations external to the intent of the producer of the manifestation can occur in different items. eg.damaged copy; Copy' autographed by author; Coply bound by a library, etc.
Group 2 entities Person,
Person
• an individual, living or deceased. corporate body
• an organization or group of individuals and/or organizations acting as a unit.
A Person and on a corporate dody is a FRBR entity only is involved in the creation or realization of a work, or its the subject of a work.
Group B entities
object, event, place. concept
object
A material thing, including animate and inanimate objects occurring in nature; fixed, movable, and moving objects that are products of human creation; objects that no longer exist.
event
an action on occurrence (e.g. historical event, epoch, period of time)
Place
• A location from one of a comprehensive range of locations : terrestrial and extra-terrestrial; historical and contemporary, geographic features and geo-political jurisdictions.
A concept, an object, an event, or a place is treated as a FRBR entity only if it is the subject of a work.
Any group 1 or 2 entities may be the subject of any group 1 entity.
There are 4 additional group 3 entities :
• Concept
• an abstract notion or idea encompasses a comprehensive range of abstractions, and may be broad in nature or narrowly defined and precise
Attributes of entities
• Serve as means for users to formulate queries and to interpret responses. • FRBR contains detailed lists of attributes for each entity and definitions of each attribute.
• Some attribute may appear to be the same as entities, but they really are different (e.g. the attribute "statement of responsibility" pertains to the labeling information, while the entity person is a representation of a creation relationship- even though the words for each may be identical : "Edna Ferber," Perhaps.)
Attributes in Common
It is instructive to observe some attributes that work and expression have in common :
title
form
date
other distinguishing characteristic
However, these would not necessarily have identical character strings (e.g. Show boat for the work, but showboat for an expression; symphony for form of work, but musical notation on sound for forms of expression).
FRBR Relationships
In the model, relationships serve to show the link between on entity and another .
The following 3 slides, reproduced from the FRBR document, show the high level
WORK
is realized through EXPRESSION
is embodied in MANIFASTATION
is exemplified by ITEM
Work-to-work
Relationship types for Work-to-work
• Succesor (Sequel, Succeeding work)
• Supplement (index, concordance, teacher's guide, gloss, supplement, appendix)
• complement (cadenza, libretto, choreography, ending for unfinished work, incidental music)
• Summarization (digest, abstract)
• adaptation (adaptation, Paraphrase free translation, musical, variation, harmonization, musical fantasy).
• transformation (dramatization, novellzation, versification, Screenplay).
• Imitation (Parody, Imitation, travesty).
• whole / part (chapter, section, part, volume/issue illustration for a text, sound aspect of a f lim, monograph in a series, journal article)
Expression-to-expression
Relationship typers for expressions:
• abridgement
• revision.
• translation.
• arrangement (music).
• Successor [and the rest of the same list under "work-to-work relationships"]
Barbara Tillett and Richard Smiraglia have done much work on bibliographic relationships. Tilletts diagram of Smiraglia's "bibliographic family" concept follows.
User tasks
Finally, FRBR maps the attributes and relationships to user talks :
• to find entities that correspond to the user's stated search criteria.
• to identify an entity
• to select an entity that is appropriate to the user's needs
• to acquire or obtain access to the entity described
BIBFRAME 2016
Initiated by the library of Congress, BIBFRAME provides a foundation for the future of Bibliographic description, both on the web, and in the broader networked world that is grounded in Linked Data techniques. A major focus of the initiative is to determine a transition path for the MARC 21 formats while preserving a robust data exchange that has supported resource sharing and cataloging cost savings in recent decades. The MARC standards was developed by Henriette Avram at the US Library of Congress during the 1960s. In a provocatively titled article (2002), Library technologist roy Tennant argued that "MARC Must Die", noting that the standard was old; used only within the library community; and designed to be a display. rather than a storage or retrieval format. The library of congress released version 2.0 of BIBFRAME in 2016
BIBFRAME "The Project"
• Library of Congress contracted with zepheira (2012 through early 2014)
• To develop the model and model description that kick started the BIBFRAME project.
• Produced a model for profiles and use cases.
• opted to pursure active hands on experiments.
• Library of Congress, National library of Medicine, George Washington university. British National Library, Princeton university, Deutsche National Bibliothek, OCLC, zepheira.
All parties continue to experiment and more forward the evolution.
The BIBFRAME model
The BIBFRAME model consists of the following main classes :
• creative work : a resource reflecting a conceptual essence of the cataloging item.
• Instance : a resource reflecting an individual, material embodiment of the work.
• Authority : a resource reflecking key authority concepts that have defined relationships reflected in the work and Instance Examples of Authority Resource include People, Places, Topics, Organizatio etc.
Annotation : A resource that decorates other BIBFRAME resources with additional information. Example of such annotations include library Holdings information, cover out and reviews.
No comments:
Post a Comment