Imagine a library in Delhi trying to share its catalogue records with an abstracting service in Paris, while both use completely different in-house systems. Without a shared language for bibliographic data, this exchange would collapse into endless manual conversion. The Common Communication Format (CCF) was created to solve exactly this problem. Developed under the guidance of UNESCO, CCF is an exchange format that lets libraries, documentation centres, and information agencies share machine-readable bibliographic records without forcing everyone to abandon their own systems. This post explains where CCF came from, how its records are built, and why it remains a useful model for understanding data interoperability.
Table of Contents
- Origins of CCF
- From idea to published standard
- Why it was developed
- Structure of CCF records
- The record label
- The directory
- The data fields and record separator
- Record segments and bibliographic levels
- Advantages of using CCF
- True interoperability across systems
- Standardisation with built-in flexibility
- Support for cooperation and access
- A foundation that still informs practice
Origins of CCF
The story of CCF begins in the late 1970s, a period when several bibliographic exchange formats already existed but none could talk to each other easily. The well-known ISO 2709 structure for recording bibliographic information on magnetic tape was in use, yet different agencies built incompatible formats on top of it. This lack of compatibility made record sharing between libraries and other information services slow and error-prone.
To address this, UNESCO’s General Information Programme organised the International Symposium on Bibliographic Exchange Formats in Taormina, Sicily, in April 1978. The symposium was held in collaboration with the International Council of Scientific Unions Abstracting Board (ICSU-AB), the International Federation of Library Associations and Institutions (IFLA), and the International Organization for Standardization (ISO). On its recommendations, UNESCO formed an ad-hoc group to establish a common format that could serve everyone.
From idea to published standard
The first edition of CCF was published in 1984 under the editorship of Peter Simmons and Alan Hopkinson. A second edition followed in 1988, released in two volumes: CCF/B for bibliographic information and CCF/F for factual information. A third edition appeared in 1992. According to a UNESCO-linked account of the format’s development, CCF emerged from a “marriage” of ideas drawn from the UNISIST Reference Manual and UNIMARC, both of which trace back to the original MARC format created by the Library of Congress in 1967.
Why it was developed
CCF had clear, practical goals. As documented in standard library science teaching material from IGNOU’s eGyankosh, exchange formats like CCF exist so that systems can pass records to one another regardless of the internal processing format each one uses. The format was designed to:
Permit record exchange: CCF allows bibliographic records to move between groups of libraries and abstracting and indexing services that previously could not share data directly.
Enable shared computer programs: A single set of programs can manipulate records received from different agencies, even when those agencies created the records using very different methods.
Provide a database framework: CCF offers a list of useful data elements that an agency can adopt as the basis for its own bibliographic or factual database.
A defining feature was its focus on developing nations. Unlike MARC, which prescribed detailed cataloguing rules, CCF specified no rules for description and permitted minimal records. This made it accessible for institutions with limited resources, including many libraries in India, where rigid and expensive cataloguing infrastructure was not always available.
Structure of CCF records
To understand how CCF achieves interoperability, you need to look at how a single record is built. The record structure of CCF is a specific implementation of the ISO 2709 standard, which provides a generalised container for bibliographic data. The ISO standard does not dictate what content goes into a record; it only defines the technical frame, which gives CCF the flexibility to carry different kinds of data.
A CCF bibliographic record consists of four major parts: the record label, the directory, the data fields, and a record separator. Each part has a defined role, and together they let a receiving system decode the record accurately.
The record label
Every CCF record begins with a record label, also called the leader. It is a fixed-length field of exactly 24 characters and is the only part of the record whose length never changes. The label does not contain bibliographic data itself. Instead, it carries information the system needs to process the record, such as the total record length and the base address of data, which marks where the first data field begins. As the Library of Congress record structure specification explains, the label also indicates how many characters are used for indicators and subfield identifiers. In effect, the label acts as a map that tells the receiving computer how to read everything that follows.
The directory
Following the label is the directory, which works like an index to the data fields. The directory contains one entry for each data field in the record. Each entry records the field tag, the length of the field, and the starting character position of that field within the data area. If a field appears more than once, it gets a separate directory entry for each occurrence.
This is where CCF differs from MARC in a small but important way. In MARC 21, a directory entry is 12 characters long. In CCF, each directory entry is 14 characters, because the 13th and 14th characters are reserved for a Segment Identifier and an Occurrence Identifier. These extra characters are not cosmetic. They allow CCF to group related fields and to link different records together, a capability discussed in the next section.
The data fields and record separator
The data fields hold the actual bibliographic information, such as the title, author, publication year, and ISBN. Each field is identified by a three-character tag and is located using the position and length values stored in the directory. Because the tags live in the directory rather than inside the fields themselves, the data area remains a clean string of content that the system reads according to the directory’s map.
Finally, a single record separator character marks the end of the record. This tells the system where one complete record finishes and the next one begins when records are stored or transmitted in sequence.
Record segments and bibliographic levels
One of CCF’s most distinctive design choices is the use of record segments: groups of fields that permit relationships between fields and between whole records. Because of the Segment and Occurrence Identifiers in the directory, CCF can represent hierarchical relationships, such as an article within a journal issue, or a chapter within a book, without applying strict cataloguing rules. This flexible linking of records at different bibliographic levels was a deliberate part of CCF’s philosophy, allowing rich relationships to be captured in a lightweight way.
Advantages of using CCF
The structural choices described above translate into real benefits for institutions that need to share data. CCF was never meant to replace internal systems; it was meant to sit between them as a neutral bridge.
True interoperability across systems
The central advantage of CCF is interoperability. An agency can keep its own internal processing format, structured however its software demands, and still convert records into CCF for exchange. This conversion can be handled by computer programs, so a library retains its preferred internal setup while staying compatible with national and international partners. Whether one institution uses MARC and another uses UNIMARC, CCF provides a shared destination format that both can read and write.
Standardisation with built-in flexibility
CCF promotes standardisation by specifying a small number of mandatory data elements that every sector of the information community recognises as essential for identifying an item. At the same time, it offers many optional elements that an agency can use to describe materials according to its own practices. Each field and subfield carries a note indicating whether its use is mandatory or optional. This combination of a small mandatory core and a large optional set is what makes CCF approachable for institutions of very different sizes and capacities.
Support for cooperation and access
By making records portable, CCF supports interlibrary cooperation, union catalogues, and the building of comprehensive bibliographies that span multiple languages and regions. A newly catalogued resource can be exported in CCF and shared with other libraries or consortia, reducing duplicated cataloguing effort. In the Indian context, work has been done on crosswalks linking CCF and the metadata used by the Information and Library Network (INFLIBNET) to standards such as Dublin Core, showing how the format connects to wider metadata ecosystems.
A foundation that still informs practice
While many modern systems now rely on MARC 21, XML, or linked data approaches, CCF established a clear model for how bibliographic data can be standardised and exchanged across very different environments. Its emphasis on a neutral, ISO 2709-based container, a minimal mandatory core, and flexible record linking remains a useful reference point for anyone studying how information systems achieve compatibility. For a generation of libraries that could not afford heavy cataloguing infrastructure, CCF demonstrated that participation in global bibliographic exchange did not require abandoning local practice.
What do you think? If most large library networks today rely on MARC 21 and emerging linked data standards, does a lightweight format like CCF still have a role to play in resource-limited institutions? And how much should an exchange format dictate cataloguing rules versus simply providing a neutral container for whatever data an agency chooses to share?

Leave a Reply