International
Tables for
Crystallography
Volume G
Definition and exchange of crystallographic data
Edited by J. R. Hester and B. McMahon

International Tables for Crystallography (2026). Vol. G. Early view chapter

Section 1.1.5. The database manager

James R. Hestera and Brian McMahonb

aAustralian Nuclear Science and Technology Organisation, Locked Bag 2001, Kirrawee DC, NSW 2232, Australia, and bInternational Union of Crystallography, 5 Abbey Square, Chester CH1 2HU, UK.

1.1.5. The database manager

| top | pdf |

Databases may be required to ingest CIF data from a variety of sources, and so must be able to handle input conformant with any format specification they support (Chapters 2.2[link] , 2.3[link] ). They may wish to incorporate existing filter programs into their workflow (Chapter 5.4[link] ), but they may also need to write a complete system to handle ingest, validation and database loading. In such a case, they may wish to build their own application programming interface, perhaps informed by the approach of the reference CIF API (Chapter 5.2[link] ) or by some of the design decisions of existing CIF libraries (Chapter 5.3[link] ).

Validation programs may be built to check all the constraints and relations expressed in dictionaries through the DDL (Chapter 2.4[link] ) and dREL (Chapter 2.5[link] ) languages. For correct interpretation of the ingested data, the definitions presented in all the relevant dictionaries (Part 4) must be studied. Data for a complex structure or system may be spread across several data blocks within the same file, and Chapters 3.3[link] and 4.3[link] provide guidance on how this might be presented.

Approaches to validation and, indeed, overall design and control of workflows of existing databases are discussed in depth in the chapters of Part 7.








































to end of page
to top of page