|
| 1 | +--- |
| 2 | +parent: Glossary |
| 3 | +--- |
| 4 | + |
| 5 | +# Catalogue |
| 6 | + |
| 7 | +**Synonyms:** Online library, Literature database, Reference source, Data provider |
| 8 | + |
| 9 | +## Meaning |
| 10 | + |
| 11 | +A **catalogue** is an online bibliographic data source that allows searching, retrieving, and importing metadata for scholarly works such as journal articles, conference papers, and books. |
| 12 | +In JabRef, a catalogue refers to an **external service or repository** — for example, ACM Digital Library, IEEE Xplore, Google Scholar, CrossRef, or arXiv — from which bibliographic entries can be fetched. |
| 13 | + |
| 14 | +Catalogues provide structured metadata (author, title, DOI, year, etc.) that JabRef imports to enrich or create local entries in a user’s library. |
| 15 | + |
| 16 | +## Delimitation (Scope and Exclusions) |
| 17 | + |
| 18 | +* **Not the same as a library:** |
| 19 | + A *[library](library.md)* is the local `.bib` file managed in JabRef; a *catalogue* is an external source from which data is imported. |
| 20 | +* **Not the same as a bibliography:** |
| 21 | + A *[bibliography](bibliography.md)* is a conceptual collection of works; a *catalogue* is a retrieval system that provides access to such works. |
| 22 | +* **Not the same as references:** |
| 23 | + *[References](references.md)* are selected works cited in a publication, possibly originating from multiple catalogues. |
| 24 | +* **Not a search engine in general:** |
| 25 | + Although some catalogues expose web search interfaces, their primary function is structured metadata access. |
| 26 | + |
| 27 | +## Validity |
| 28 | + |
| 29 | +A catalogue is valid as long as its public interface (API or HTML interface) is operational and accessible. |
| 30 | + |
| 31 | +Different catalogues may use: |
| 32 | + |
| 33 | +* standard interfaces (e.g., **DOI**, **OAI-PMH**, **OpenSearch**), |
| 34 | +* custom APIs (e.g., **CrossRef REST API**), |
| 35 | +* or web-scraping-based access (e.g., Google Scholar). |
| 36 | + |
| 37 | +## Naming and Uniqueness |
| 38 | + |
| 39 | +Each catalogue is identified by: |
| 40 | + |
| 41 | +* its **provider name** (e.g., “ACM Digital Library”), and |
| 42 | +* its **base URL** or **API endpoint**. |
| 43 | + |
| 44 | +In JabRef’s internal configuration, catalogues correspond to **[fetchers](../code-howtos/fetchers.md)**, each implementing a standardized interface for metadata retrieval. |
| 45 | + |
| 46 | +## Open Issues / Uncertainties |
| 47 | + |
| 48 | +* Availability and licensing of catalogue APIs may change without notice. |
| 49 | +* Metadata quality and completeness vary by provider. |
| 50 | +* Rate limits or CAPTCHA systems can restrict automated access. |
| 51 | +* The term “catalogue” is JabRef-specific; other reference managers use “online database” or “data source.” |
| 52 | + |
| 53 | +## Related Terms (Cross-References) |
| 54 | + |
| 55 | +[Library](library.md), [Bibliography](bibliography.md), [Citation](citation.md) |
0 commit comments