When a library in Chennai catalogues a new book and an abstracting service in Geneva indexes the same journal article, they create records that look nothing alike. Each system uses its own internal structure, its own field codes, and its own rules. So how does the bibliographic information move between them without getting lost in translation? The answer, for decades, has been the Common Communication Format (CCF). Developed by UNESCO, CCF is a standardised way of recording and exchanging bibliographic data so that records created in one system can be read and processed by another. This post explains what CCF is, how a CCF record is built, and why it remains a foundational idea in information processing and retrieval.

Table of Contents

What is the Common Communication Format?

CCF is a structured format for creating bibliographic records and for exchanging those records between libraries, abstracting and indexing services, and other information agencies. The core problem it solves is incompatibility. Libraries traditionally used cataloguing formats like MARC, while secondary services such as abstracting and indexing agencies used their own formats designed for journal articles and reports. These two communities described materials differently, and their records could not be shared easily.

To bridge this gap, UNESCO sponsored an International Symposium on Bibliographic Exchange Formats in Taormina, Sicily, in April 1978. Following the symposium’s recommendations, UNESCO’s General Information Programme (PGI) set up an ad-hoc group to establish a Common Communication Format. The first edition was published in 1984 under the editorship of Peter Simmons and Alan Hopkinson. A second edition appeared in 1988, eventually split into two volumes: CCF/B for bibliographic information and CCF/F for factual information. The CCF/B for bibliographic information remains documented in UNESCO’s records.

The purpose behind CCF

The designers of CCF had a few clear objectives in mind. The format was built to do the following:

  • Enable exchange: To permit the exchange of bibliographic records between libraries and abstracting and indexing services.
  • Allow shared software: To let a single agency use one set of computer programs to handle records received from both libraries and secondary services, regardless of how those records were originally created.
  • Provide a database template: To serve as a model for an agency building its own bibliographic database, by offering a ready list of useful data elements.

Notice what is missing from this list. CCF was never meant to replace MARC or any other format. As the UNESCO experts framed it, the goal was a “switching format” that acts as a bridge between existing systems rather than a substitute for them. This distinction matters for understanding everything else about CCF.

How a CCF record is structured

The record structure of CCF is a specific implementation of the international standard ISO 2709, the standard that defines the format for bibliographic information interchange. Because CCF follows ISO 2709, every CCF record is built from four major parts: the record label, the directory, the data fields, and a record separator.

The record label

Every CCF record begins with a fixed-length label of 24 characters. This is the only part of the record with a fixed length. The label carries information that the receiving system needs before it can process anything else. This includes the total length of the record, the record status (for example, whether it is a new record or a correction), the bibliographic level of the item, and the base address of data, which tells the system the exact character position where the data fields begin.

The label also indicates how many characters are used for indicators and subfield identifiers in the rest of the record. In effect, the label acts as a map. The receiving system reads these 24 characters first and learns how to interpret everything that follows.

The directory

After the label comes the directory, which works as an index to the data fields in the record. The directory is a table made up of a variable number of entries, with each entry pointing to one data field. The directory ends with a field separator character.

Each directory entry tells the system three essential things about a data field: the tag (a three-character code identifying what the field contains), the length of that field, and the starting character position where the field begins. In CCF, the directory entry is extended further with an additional segment, so an entry includes elements such as an occurrence identifier that helps manage repeated fields. If a particular field appears more than once in a record, it gets a separate directory entry for each appearance.

This design is clever because the tags themselves are stored in the directory, not inside the bibliographic fields. The data fields hold only the content, while the directory holds the addressing information. A system can therefore scan the directory and jump straight to any field it needs without reading the entire record sequentially.

The data fields

The data fields contain the actual bibliographic information. This is where you find the title, the author or authors, the publication date, the publisher, the ISBN, and other descriptive details. Each field corresponds to a directory entry, and within a field the information can be broken down further into subfields. A subfield is a subfield identifier followed by a string of data, terminated either by the next subfield identifier or by a field separator.

One distinctive feature of CCF is its use of record segments. Groups of fields can be organised into segments that allow relationships between fields and between records to be expressed. This is what lets CCF represent complex situations, such as an article within a journal issue, or a chapter within a book, by linking records at different bibliographic levels. The format does this without forcing a rigid set of cataloguing rules, which gives it considerable flexibility.

The record separator

The fourth part is the record separator, a single character that marks the end of one complete record. In ISO 2709 terms this is a defined control character. It tells the receiving system that one record has finished and the next one is about to begin, which is essential when many records are transmitted together in a single file or on a single storage medium.

Mandatory and optional data elements

A key design principle of CCF is minimalism. Rather than demanding a long list of compulsory fields, the format defines only a small core of mandatory data elements considered essential for bibliographic description. These mandatory elements are then augmented by a well-identified set of optional elements that an agency can use as needed.

This two-tier approach has a practical consequence. An institution with limited staff and resources can create a valid CCF record using only the essential fields, while a larger agency can enrich its records with many optional elements. Unlike MARC, which prescribes detailed rules for description, CCF specifies no rules for description and permits minimal records. This made CCF especially attractive to information agencies in developing countries, where the resources for full MARC cataloguing were often not available.

How CCF bridges different bibliographic formats

The real value of CCF lies in interoperability, the ability of different systems to work with the same data. Bibliographic data exchange faces a fundamental obstacle: every system tends to develop its own internal structure suited to its own needs. A university library, a national documentation centre, and an international abstracting service each have valid reasons for organising data differently. Without a shared format, exchanging records means writing custom conversion programs for every pair of systems, which quickly becomes unmanageable.

CCF addresses this by acting as a neutral intermediary. A record created in one internal format can be converted into CCF, transmitted, and then converted into the receiving system’s internal format. Because CCF rests on the widely adopted ISO 2709 structure, systems that already understand MARC, UNIMARC, or similar formats can be adapted to read and write CCF with manageable effort. This is what makes CCF a switching format rather than a competing one.

Connecting libraries and secondary services

The most important bridge CCF builds is between two communities that historically did not talk to each other easily: traditional libraries and secondary services like abstracting and indexing agencies. Libraries describe whole documents such as books and journals. Secondary services describe the analytical contents of those documents, such as individual journal articles. CCF’s segment and linking structure allows both kinds of description to coexist in a compatible framework, so a record can express the relationship between a journal and the articles inside it.

Relevance in the Indian information network

CCF has had a documented role in the development of library networks here. During the late 1980s, the National Information System for Science and Technology (NISSAT) organised a tripartite meeting involving CALIBNET, DELNET, and INFLIBNET to resolve the choice between CCF and UNIMARC. The eventual decision allowed database producers to use either format, as recorded in IGNOU’s course material on machine formats. The flexibility and lower entry barrier of CCF made it a practical option for many institutions building databases with modest resources.

The lasting idea behind CCF

Even as MARC 21 and newer metadata standards have become dominant in large-scale cataloguing, the principle that CCF demonstrated remains influential. The Library of Congress’s MARC 21 record structure still uses the same ISO 2709 foundation of a leader, a directory, and variable fields. CCF proved that bibliographic systems built for different purposes could share a common transmission structure while keeping their own internal practices. That separation of structure from content is the conceptual ancestor of how modern systems exchange data through agreed-upon formats.

CCF at a glance

To pull the pieces together, here is what defines CCF as a format. It was created by UNESCO to enable bibliographic record exchange across libraries and secondary services. It implements the ISO 2709 structure, so each record has a 24-character label, a directory, data fields, and a record separator. It uses a small core of mandatory elements supported by optional ones, keeping records flexible and accessible. And it functions as a switching format, bridging incompatible systems rather than replacing them. These features explain why CCF earned a place in the study of bibliographic record formats and why it continues to appear in information processing and retrieval syllabi.

What do you think? If CCF was designed as a bridge between formats rather than a replacement, do you think a single universal bibliographic format would ever truly serve the diverse needs of libraries and secondary services? And as discovery increasingly moves to linked data and the web, how relevant is a fixed record structure like ISO 2709 to the future of bibliographic exchange?

How useful was this post?

Click on a star to rate it!

Average rating 0 / 5. Vote count: 0

No votes so far! Be the first to rate this post.

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

References
  1. https://eric.ed.gov/?id=EJ347605
  2. https://digitallibrary.un.org/record/131419?ln=en
  3. https://www.researchgate.net/publication/51995146_Converting_bibliographic_records_into_ISO_2709_format_Access_Presentation
  4. https://www.learntechlib.org/p/169971/
  5. https://egyankosh.ac.in/bitstream/123456789/33106/1/Unit-9.pdf
  6. https://www.loc.gov/marc/specifications/specrecstruc.html

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

Information Processing & Retrieval

1 Intellectual Organisation of Information

  1. Intellectual Organisation of Information
  2. Meaning of Intellectual Organisation of Information
  3. Why IOI is Necessary?
  4. IOI in Indexing Systems
  5. IOI and Indexing Languages
  6. IOI in User Services
  7. IOI and Content Analysis
  8. Information Retrieval Systems – Changing Environment
  9. Future Trends

2 Indexing Languages–Part I – Concepts and Types, Subject Headings Lists and Thesauri

  1. Indexing and its Types
  2. Indexing Language
  3. Vocabulary Control
  4. Classification Schemes
  5. Subject Headings Lists
  6. Thesaurus
  7. Thesaurofacet
  8. Classaurus
  9. Sears List of Subject Headings
  10. Library of Congress List of Subject Headings

3 Indexing Languages–Part II- Classification Schemes

  1. Dewey Decimal Classification (DDC) Scheme
  2. Universal Decimal Classification (UDC) Scheme
  3. Library of Congress Classification (LCC) Scheme
  4. Colon Classification (CC) Scheme
  5. Bibliographic Classification (BC) Scheme
  6. Library Bibliographical Classification (BBK) Scheme
  7. Broad System of Ordering (BSO) Scheme
  8. Special Classification Systems

4 Indexing Systems and Techniques

  1. Indexing Principles and Process
  2. Pre-Coordinate Indexing Systems
  3. Post-Coordinate Indexing Systems
  4. Automatic Indexing
  5. Non-Conventional Indexing: Citation Indexing
  6. Web Indexing

5 Evaluation of Indexing Systems

  1. Purpose of Evaluation
  2. Levels of Evaluation
  3. Evaluation Criteria
  4. Recall and Precision
  5. Other Performance Measures
  6. Relevance
  7. Evaluation Methodology
  8. Evaluation Experiments

6 Principles and Evolution of Bibliographic Description

  1. Bibliographic Description: An Overview
  2. Scope and Objectives of Bibliographic Description
  3. Evolution of Bibliographic Description
  4. Ranganathan’s Principles
  5. ISBDs
  6. Bibliographic Formats
  7. Electronic Resource Description
  8. Models of Bibliographic Description
  9. Bibliographic Description: Entities, Attributes and Relationships

7 Rules for Bibliographic Description

  1. Bibliographic Description: Its Origin
  2. Development of Anglo-American Code
  3. The International Standard Bibliographic Description (ISBD)
  4. Impact of ISBD on Catalogue Codes
  5. Bibliographic Description for Non-Print Materials
  6. Guidelines for Bibliographic Description of Electronic Resources
  7. Guidelines for Bibliographic Description of Internet Resources
  8. Rules for Description of Electronic Resources in AACR2 Revision 2002

8 Standards for Bibliographic Record Format

  1. International Standard Bibliographic Description (ISBD)
  2. MARC Format
  3. UNIMARC
  4. Common Communication Format (CCF)
  5. Indian Standard

9 Metadata- MARC21-856 Field, Dublin Core, TEI

  1. MARC21 – 856 Field
  2. Dublin Core Metadata Initiative (DCMI)
  3. Text Encoding Initiative (TEI)
  4. Procedure of Electronic Resource Description

10 Norms and Guidelines for Content Development

  1. Introduction
  2. Needs and Guidelines
  3. Standards Related to Electronic Content
  4. W3C Recommendations
  5. Electronic Text Encoding and Interchange
  6. Dynamic Content

11 Introduction to HTML and XML

  1. World Wide Web and Markup Languages
  2. Standard Generalized Markup Language (SGML)
  3. HyperText Markup Language (HTML)
  4. Basic HTML Tags
  5. Linking
  6. URLs
  7. HTML and the Browser
  8. eXtensible Markup Language (XML)
  9. XML Syntax and Semantic Tags
  10. Document Type Definition (DTD)
  11. Implications of XML in Library and Information Activities

12 Web-based Content Development

  1. What can be done with World Wide Web?
  2. Hypertext, Hyperlink, and Hypermedia
  3. Hypertext Markup Language (HTML)
  4. Introduction to Dynamic HTML
  5. Web Interface to Database Linking
  6. Introduction to XML
  7. XML Document Design
  8. Multimedia Web Resources
  9. Web Servers
  10. Website Hosting
  11. Tools for Web Page Designing

13 Multilingual Content Development (Using Unicode)

  1. Character Representation in Computer
  2. American Standard Code for Information Interchange (ASCII)
  3. Indian Scenario and Indian Standard Code for Information Interchange (ISCII)
  4. UNICODE
  5. Web Content Development Through UNICODE
  6. Applications of UNICODE
  7. Applying UNICODE to the Libraries
  8. Problems Associated with UNICODE

14 ISAR Systems- Objectives, Types, Operations and Design

  1. Users and Their Information Needs
  2. Objectives of ISAR Systems
  3. Types of ISAR Systems
  4. Design of ISAR Systems
  5. Evaluation of ISAR Systems

15 Compatibility of ISAR Systems

  1. Need for Compatibility Among ISAR Systems
  2. Scope of Compatibility in ISAR Systems
  3. Areas of Compatibilities in ISAR Systems
  4. Principal Issues of Compatibility in ISAR Systems
  5. Compatibility of Online IR Systems
  6. Approaches Towards Compatibility in ISAR
  7. Quality Control and Compatibility

16 Intelligent Information Retrieval Systems

  1. Introduction
  2. Expert Systems
  3. Expert Systems for Information Processing and Retrieval
  4. Components of Expert Systems
  5. Knowledge Representation
  6. Knowledge Engineering
  7. Artificial Intelligence Based Decision Support Systems (DSS)
  8. Pattern Recognition

17 Information Retrieval Processes and Techniques

  1. Information Retrieval Systems
  2. Databases
  3. Information Retrieval Systems: Purpose, Components, and Functions
  4. Indexing and Information Representation
  5. Vocabulary Control
  6. Searching
  7. Information Seeking and User Interfaces
  8. Web Information Retrieval Systems
  9. Intelligent Information Retrieval

18 Information Retrieval Models and Their Applications

  1. Information Retrieval
  2. Information Retrieval Techniques
  3. Models Based on Input/Output
  4. Models Based on Theories and Tools

19 Search Strategies, Processes and Techinques

  1. Search File – An Essential Component
  2. Search Strategies and Pre-requisites
  3. Search Techniques
  4. The Information Search Process
  5. Online Searching
  6. How the Search Engines Work
  7. Common Search and Retrieval Features of Web Search Engines