How a reference library turns sources into reusable references

The CiteKit Reference Library stores and organizes reusable references. A reference represents a source through structured reference metadata such as its title, authors, publication information, URL, or identifier. A reference set groups references into a named collection. A citation style can then transform the stored metadata into formatted citations or bibliography entries.

Those are separate layers. The source is the work or resource being described. The reference is the structured record that represents it. The reference set organizes records. The citation style determines how selected metadata is displayed. The bibliography is formatted output rather than a replacement for the underlying reference data.

That distinction is what makes a reference reusable. CiteKit stores Reference Library data in the user's browser and allows the same underlying reference-set data to be used by the Reference Library, Citation Generator, Bibliography Generator, and Citation Schema Generator. A source entered for one operation can therefore remain structured reference data available to another operation instead of ending as an isolated citation string.

Concept relationships

• Reference → represents → Source
• Reference → contains → Reference metadata
• Reference set → groups → References
• Citation style → formats → Reference metadata
• Bibliography → presents → Formatted references

From source to reference set to bibliography

Reference management begins with information about a source, not with the punctuation of its final citation.

A journal article might have authors, a title, journal information, a publication date, volume and issue data, page numbers, and a DOI. A book may instead have an ISBN, publisher, edition, and other book-specific metadata. A webpage may have a URL, title, author, publisher or website name, and publication date.

CiteKit can receive source information from a URL or YouTube URL, DOI, ISBN, PubMed ID, title or keyword search, AI/LLM source entry, or manual entry. Identifier and search lookups can turn available source information into a structured reference. Crossref, for example, exposes bibliographic metadata through its REST API and provides DOI-specific retrieval for individual metadata records.

The conceptual path is:

Source → source metadata → reference → reference set → citation-style formatting → bibliography

Each stage performs a different job.

The source is the underlying work. Source metadata describes that work. A reference stores that description as a structured record. A reference set organizes one or more references. A citation style applies formatting rules to the metadata. A bibliography presents the resulting formatted entries.

The underlying source does not change when its citation style changes. Formatting the same reference as APA, MLA, Chicago, Harvard, IEEE, or another style changes its presentation, not the identity of the source it represents.

A reference set also remains distinct from its bibliography. CiteKit users can create, rename, and delete reference sets, remove references from sets, and choose a citation style for a set. CiteKit can then format the references in that set as a bibliography that can be copied as plain text or HTML or downloaded as a .txt file.

The reference set is the organized collection. The bibliography is one output generated from it.

Source, reference, citation, and bibliography are different things

The terms source, reference, citation, and bibliography describe related concepts, but they are not interchangeable.

Source

A source is the underlying work or resource. A journal article, book, webpage, report, video, dataset, or AI output can all function as sources when they are being referenced.

Reference

A reference is a structured record that represents a source. Citation Style Language documentation describes bibliographic information about an item as item metadata. That metadata can include names, titles, dates, identifiers, URLs, publishers, container information, volume and issue data, page ranges, and other fields appropriate to the source type.

A reference is therefore more than the text of a formatted citation. It preserves individual pieces of information that a formatting system can use later.

Citation

A citation represents a reference in a particular citation context. Depending on the citation style, that representation might appear as an author and year, a number, a footnote, an endnote, or another formatted marker.

Citation Style Language distinguishes the metadata that describes an item from information about the context in which that item is cited. Citation context can include matters such as citation order, grouped citations, and locators such as page numbers.

Bibliography

A bibliography presents formatted references. Citation Style Language styles can define separate rules for citations and bibliographies, allowing the same underlying metadata to produce an inline citation in one context and a full bibliography entry in another.

This distinction matters in a reference library. Storing only a completed citation string loses much of the structure that made the citation possible. A formatted APA entry is useful as output, but its individual metadata fields are more useful when the same source later needs to be formatted differently, placed in another reference set, or used by another tool.

Why structured reference data can be reformatted

The CiteKit Reference Library stores CSL-JSON-shaped data inside reference sets. CSL-JSON is a JSON representation commonly used to provide bibliographic item data to Citation Style Language processors.

The CSL schema distinguishes bibliographic item metadata from information about a particular citation context. Its csl-data.json schema describes bibliographic items, while csl-citation.json adds contextual information about how those items are cited.

This separation is central to reference management because data and presentation perform different jobs.

A structured reference might preserve fields such as:

• source type;
• title;
• author or authors;
• publication date;
• container or publication title;
• publisher;
• volume and issue;
• page range;
• DOI;
• ISBN;
• PMID;
• URL.

The citation style supplies a separate set of rules that determines which of those values appear and how they are arranged. Citation Style Language is an XML-based language for describing the formatting of citations and bibliographies. A CSL processor combines reference metadata with those style rules to produce formatted output.

Consider a simplified reference record:

{
  "id": "example-reference",
  "type": "article-journal",
  "title": "Example Article",
  "author": [
    {
      "family": "Rivera",
      "given": "Alex"
    }
  ],
  "issued": {
    "date-parts": [[2026]]
  },
  "container-title": "Example Journal"
}

The record preserves the source information as separate values. APA can transform those values according to APA rules. MLA can transform the same values according to MLA rules. Chicago can apply another set of rules.

The formatting changes. The reference continues to represent the same source.

There is also an important technical limitation. CSL-JSON is widely used across citation software, but the CSL project's schema documentation notes that CSL-JSON is not yet fully normative. Two systems using CSL-JSON-shaped data should therefore not be assumed to have perfect field-for-field interoperability without examining how each system maps its data.

Structured reference data makes reformatting and reuse possible. It does not remove the need for accurate metadata or compatible data mappings.

One reference record, multiple CiteKit tools

The Reference Library is part of a shared CiteKit free-tool workflow rather than an isolated storage screen. The current interface exposes Library, All References, and Reference Sets as separate views over the stored reference data.

A reference set created in the Bibliography Generator appears in the Reference Library, and a reference set created in the Reference Library can be used by the Bibliography Generator. The Citation Generator can create references that enter the shared reference store instead of existing only as one-off formatted citation strings.

The Citation Schema Generator can also operate on the same underlying reference-set data. This allows structured references to move between different operations without requiring the source metadata to be entered again for every tool.

The resulting workflow is:

Look up or enter a source → preserve the reference → organize it in a reference set → format or reuse it where needed.

The bibliography is one possible output from that workflow. The reusable asset is the structured reference data underneath it.

The free Reference Library keeps its reference data in the user's browser, and bibliography formatting runs in the browser. No account is required for that browser-local workflow. Browser storage describes where these free-tool records are kept; it should not be confused with account-based storage or synchronization between devices.

For publishers who need reference management directly inside WordPress, see the CiteKit Reference Manager for WordPress.

Related glossary terms

• Reference Management
• Reference Library
• Source
• Reference
• Reference Metadata
• Reference Set
• Citation
• Bibliography

4 Sources

1. 1. Citation Style Language, “Primer — An Introduction to CSL,” https://docs.citationstyles.org/en/master/primer.html

2. 2. Citation Style Language, “CSL 1.0.2 Specification,” https://docs.citationstyles.org/en/v1.0.2/specification.html

3. 3. Citation Style Language, “Schemas describing the Citation Style Language,” https://github.com/citation-style-language/schema

4. 4. Crossref, “REST API,” https://www.crossref.org/documentation/retrieve-metadata/rest-api/