The 2016 MARC21 core set for e-resources, updated

DataMercs’ core set for MARC records, brought up to current practice and widened to e-journals and databases. One table, three markets: DNB and the German-language union catalogues, LC/PCC, and OCLC. Draft.

The 2016 core set is my core field set for e-book MARC records: which fields a publisher’s record has to carry so that libraries in Germany and the US can load it without rework. Its last revision dates from December 2016. This page brings it up to date and widens it to e-journals and databases.

It is a delivery core, not a cataloguing manual. Each column says what one document asks for, in its own layer. Where a document does not mention a field, the cell says so and nothing more.

MARC 21 Bibliographic · LoC DACH: AG KVA e-book requirements · RDA DACH US: PCC PN · BSR · CSR OCLC: BFAS Full / Minimal

How to read the tables

Requirement levels. M mandatory · A mandatory if applicable (OCLC: required if applicable) · O optional · X not used · — not stated in that document. OCLC cells read Full/Minimal.
Columns. DNB / DACH = the AG KVA requirements of the German-language networks and the DNB for e-book deliveries (they cover e-books; e-journals run through the ZDB). LC / PCC = the PCC Provider-Neutral guide, falling back to the BSR or CSR where it is silent (marked). OCLC = Bibliographic Formats and Standards input standards.
Applicability. ● core for that resource type · ○ if applicable · – not applicable.
DataMercs core. Rows named DataMercs core are decisions of this set that go beyond the three market documents. DataMercs extension marks a use that MARC 21 does not define as such.
Links. Every tag opens its MARC 21 Bibliographic page at the Library of Congress. BFAS opens the OCLC page for the same field.

The core field set

Tag	Name	Indicators · subfields	E-book	E-journal	Database	DNB / DACH	LC / PCC	OCLC	Notes
LDR BFAS	Leader	/05 n·c·d · /06 a · /07 m·s·i · /09 a · /17 # or 7 · /18 i or c	●	●	●	M	M	see BFAS	UTF-8 is /09 a. /06 and /07 per resource type, see the LDR/008 tables. BSR textual monographs: /17 blank, /18 i or c.
001	Control number	stable record ID, no indicators	●	●	●	M	—	—	Same ID on every update and delete, or the receiving system cannot match. e-ISBN is a common choice for e-books.
003	Control number identifier	MARC organization code / ISIL	●	●	●	M	—	—	AG KVA: data provider in 003 and/or 040 $a.
005	Date and time of latest transaction	yyyymmddhhmmss.f	●	●	●	—	—	—	Drives update detection on the receiving side. Keep it truthful.
006 BFAS	Additional material characteristics	/00 m · /06 o · /09 d (or by content)	●	●	●	—	A/O	see BFAS	PN: libraries cataloguing in OCLC or other shared databases must use 006/00 m when LDR/06 is not m.
007 BFAS	Physical description fixed field	/00 c · /01 r	●	●	●	M	M	see BFAS	007 cr. PN lists /00 and /01 only; further positions are optional.
008 BFAS	Fixed-length data elements	/06 · /07-14 dates · /15-17 country · /23 o (books) · /35-37 language	●	●	●	M	M	see BFAS	Books vs continuing resources layout, see the LDR/008 tables.
010 BFAS	LC control number	## $a	○	○	○	—	A	—	PN: do not transfer the print LCCN to the e-record.
016 BFAS	National bibliographic agency control number	7# $a [DNB IDN] $2 DE-101	○	○	○	—	—	A/A	Assigned by the national agency (DNB records carry it). Take it from the DNB record; never construct one.
020 BFAS	ISBN	## $a e-ISBN $q (PDF) · $z other ISBNs	●	–	○	A	M · n/a ser · A IR	A/A	$q qualifying information (since 2013) replaces bracketed qualifiers. PN: one 020 $a per e-ISBN; other ISBNs in 020 $z; print ISBN also in 776 $z.
022 BFAS	ISSN	0# $a e-ISSN · $l ISSN-L	–	●	○	—	A	A/A	For DACH serials the ZDB record is the reference.
024 BFAS	Other standard identifier	7# $a 10.xxxx/… $2 doi	●	●	○	A	A	O/O	"Bare DOI in $a, no resolver prefix, no ""doi:"". The resolver URL belongs in 856."
035 BFAS	System control number	## $a (ORGCODE)ID · $a (OCoLC)…	●	●	●	—	—	O/O	Prefix each number with its MARC organization code in parentheses. Only numbers for the e-version.
040 BFAS	Cataloguing source	## $a $b $e rda [$e pn] $c $d	●	●	●	M	M	M/M	$b = language of cataloguing (ger or eng). PN: $e rda followed by $e pn. OCLC keeps one record per language of cataloguing.
041 BFAS	Language code	#7 $a $2 iso639-2 · or ## with MARC codes	○	○	○	M	A	A/O	AG KVA: first language in 008/35-37 and 041 $a; further languages repeat $a. PCC core if 008 cannot hold them.
050 BFAS	LC call number	#4 $a $b	○	○	○	—	A (BSR)	A/O	BSR: at least one class number from an established scheme (LCC or DDC).
072 BFAS	Subject category code	#7 $a $x $2 bisacsh · #7 $a $2 thema	○	○	○	—	—	O/O	Trade subject codes. Useful for mapping and routing, not a substitute for 082/084 or 650.
082 BFAS	Dewey Decimal Classification	04 $a $2 23 · DNB: 04 $a $q DE-101 $2 22/ger	○	○	○	O	A (BSR)	A/O	DNB records also carry the DDC subject category (Sachgruppe) in 083 7# $a $q DE-101 $2 23sdnb (observed).
084 BFAS	Other classification number	## $a $2 rvk · bkl · sdnb	○	○	○	O	—	A/O	AG KVA lists 082 and 084 with $2. RVK and BK are common in the union catalogues.
1XX BFAS	Main entry (100/110/111)	1# $a $d $e $4 aut $0 (DE-588)… · $1 URI	○	–	–	A	A	A/A	AG KVA: first contributor with $4 and $0. One 1XX at most; editors go to 7XX.
245 BFAS	Title statement	10 $a $b $n $p $c	●	●	●	M ($a) · A ($b)	M ($a) · A	M/M	No $h general material designation; content, media and carrier go to 336–338.
246 BFAS	Varying form of title	31 parallel · 1# variant	○	○	○	—	A parallel · O variant	A/O	For journals, record title changes as 246 (minor) or new record with 780/785 (major).
250 BFAS	Edition statement	## $a	○	–	○	A	A	A/A	PN: only publisher editions, not provider versions.
264 BFAS	Production, publication, distribution	#1 $a $b $c · #4 $c ©yyyy	●	●	●	M	M ($a $b $c) · O ©	A/A	Replaces 260 under RDA. Second indicator carries the function; repeat for copyright.
300 BFAS	Physical description	## $a 1 online resource (xii, 300 pages)	●	○	○	O	M mono · O ser	A/A	"RDA wording in the language of cataloguing (DNB: ""1 Online-Ressource"")."
310 BFAS	Current publication frequency	## $a $b	–	●	●	—	A (CSR)	A/O	CSR: core if known. Pair with 008/18–19.
336 BFAS	Content type	## $a text $b txt $2 rdacontent	●	●	●	—	M	A/A	DNB records carry German terms (Text / txt).
337 BFAS	Media type	## $a computer $b c $2 rdamedia	●	●	●	—	M	A/O
338 BFAS	Carrier type	## $a online resource $b cr $2 rdacarrier	●	●	●	—	M	A/O	Must agree with 007 cr.
341 BFAS	Accessibility content	## $a content access mode · $b–$e assistive features · $2 source	○	○	○	—	O	A/O	Optional, growing in weight with the European Accessibility Act. Only if it applies to all versions on a provider-neutral record.
347 BFAS	Digital file characteristics	## $a text file $2 rdaft · ## $b PDF	●	○	○	—	O	A/A	File type in $a with $2 rdaft; encoding format such as PDF or EPUB in $b.
362 BFAS	Dates of publication and sequential designation	1# $a Began with …	–	●	○	—	A	A/A	Unformatted note (ind1 1) when the first issue is not in hand.
490 BFAS	Series statement	1# $a $x $v	○	–	–	A	A	A/A	Transcribed form. Pair with 8XX when traced.
500 BFAS	General note	## $a	○	○	○	—	A (500/550)	A/O	Keep for genuine notes; not for package or licence data.
500 BFAS	AI use disclosure (DataMercs core: when applicable)	## $a AI use disclosed by the author: [activity]; [tool]; human-reviewed.	○	○	○	—	—	—	AI is not an author (COPE, ICMJE), so no name heading. 500 because no specialised 5XX exists for it; 545 is for the creator's biography and 588 for the record. Name the activity with the STM classification of AI use where possible.
505 BFAS	Formatted contents note (DataMercs core: e-books and edited volumes with a TOC)	0# $a [part] -- [part] (basic) · 00 $t [title] / $r [responsibility] $g [pages] -- (enhanced) · 8# / 80 continuation	●	–	–	—	—	O/O	Core here wherever a table of contents exists: every chapter title, and in 00 every chapter author, becomes a search entry point. 00 for edited volumes and multi-author works; 0# for monographs or when only chapter titles are known. Complements the 856 42 $3 Table of contents link, does not replace it. Long contents: repeat 505, continuations with first indicator 8.
506 BFAS	Restrictions on access	0# $a Open access $f open access $2 coarar (or star) · $u COAR URI	●	●	●	A (OA)	O (OA)	O/O	DACH: 506 0# $a Open access. PN: one general 506 for open-access versions, plus 856 $7 0. First indicator 0 = no restrictions, 1 = restrictions apply.
520 BFAS	Summary (core: mandatory in this set)	## (summary) or 3# (abstract) $a · repeat per language	●	●	●	O	O	O/O	Mandatory here for e-books, e-journals and databases: abstracts drive discovery and relevance ranking, and OA titles almost always have one to reuse. One 520 per language. The market documents rate it optional.
532 BFAS	Accessibility note	## $a	○	○	○	—	O	A/O	Free-text counterpart to 341.
540 BFAS	Terms governing use and reproduction	## $a $f CC BY 4.0 $2 cc $u https://creativecommons.org/licenses/by/4.0/	●	●	○	A (OA)	O	O/O	AG KVA and PN use the same pattern. PN: only if the licence applies to all versions on the record.
540 BFAS	Record licence: CC0 (DataMercs core)	## $3 Bibliographic record $a Metadata in this record released under CC0 1.0 Universal. $f CC0 1.0 $2 cc $u https://creativecommons.org/publicdomain/zero/1.0/ $q [MARC org code]	●	●	●	—	—	—	Every record, separate from the resource licence above. $f, $2 cc, $u and $q are standard 540 subfields; using $3 to point at the record rather than part of the resource is a DataMercs extension. Reason: anyone can reuse, merge and enrich the record without asking.
546 BFAS	Language note	## $a	○	○	○	—	A	A/A
588 BFAS	Source of description note	0# $a Description based on online resource; title from PDF title page (…, viewed …) · 1# latest issue consulted	●	●	●	—	M	A/A	First indicator 0 = source of description, 1 = latest issue consulted.
6XX BFAS	Subject access (600–651)	#7 $a $0 (DE-588)… $0 https://d-nb.info/gnd/… $2 gnd · #0 LCSH $0/$1	●	●	●	O (650)	A (BSR)	A/O	GND in DACH, LCSH in the US. $0 = authority record, $1 = real-world object URI.
653 BFAS	Index term – uncontrolled	## $a	○	○	○	—	—	O/O	Publisher keywords belong here, not in 650 without a source.
655 BFAS	Genre/form	#7 $a Aufsatzsammlung $0 (DE-588)4143413-4 $2 gnd-content · #7 $a … $2 lcgft	○	○	○	—	A (BSR)	O/O	BSR: genre/form access per cataloguer judgement, supported by authority records.
70X–75X BFAS	Added entries (700/710/711…)	1# $a $e $4 edt $0 · $1	○	○	○	A	A	A/A	AG KVA: further contributors with $4 and $0.
758 BFAS	Resource identifier	## $4 [relationship URI] $i $a $1 [URI]	○	○	○	—	—	O/O	Identifiers of related entities (work, expression). 856 stays the access URL.
773 BFAS	Host item entry	08 $i $t $z $o	–	–	–	—	X	A/A	PN: not used for packages. DACH carries package data in 912 / 950 instead.
776 BFAS	Additional physical form entry	08 $i Erscheint auch als $n Druck-Ausgabe $z · 08 $i Print version: $t $z $w	●	●	○	A	A	O/O	PN: required if the description is based on the print record. Reciprocal links recommended.
780/785 BFAS	Preceding / succeeding entry	00 $t $x $w	–	●	○	—	A (CSR)	—	For major title changes of serials.
80X–83X BFAS	Series added entries	#0 $a $v $x [print ISSN]	○	–	–	—	A	A/O	PN: authorised print form; print ISSN in $x as last subfield.
856 BFAS	Electronic location and access	40 $u https://doi.org/… $7 0 · 42 $3 Table of contents $u …	●	●	●	A	A · $7 A (OA)	O/O	$7 access status: 0 open, 1 restricted, u unspecified. Do not use $z for institution-specific notes on shared records.
883	Metadata provenance (DataMercs core: when applicable)	0# / 1# $8 n\p $a [process] $c [0–1] $d [yyyymmdd] $q [MARC org code] $u [process URI] · $x $w $0 $1 if needed	○	○	○	—	—	—	Required here for every machine-generated or AI-assisted field (520 abstract, 6XX subjects, 082/084 classes). ind1 0 = fully, 1 = partially, 2 = not machine-generated. Link with $8 and link type p, e.g. 520 $8 1\p ↔ 883 $8 1\p. DNB records carry it for machine-assigned subjects and classes (observed in live records).
720 BFAS	AI tool trace (DataMercs extension, optional)	2# $a [tool name and version] $e [activity]	○	○	○	—	—	—	Only if the tool must be indexed. No MARC relator code exists for AI, so $e is free text and $4 stays empty. Never 100/700.
9XX	Local fields: 912, 950	912 ## $a [product ISIL] $b [year] · 950 ## $a [collection]	○	○	○	O	—	—	DACH union catalogue convention: AG KVA uses 912 for the product ISIL and licence year, 950 for collection text.

Field count. 56 rows. Ranges (1XX, 6XX, 70X–75X, 80X–83X, 9XX) count as one row each, as do 780/785.

Contents note: 505 alongside the 856 TOC link

DataMercs core Wherever a table of contents exists, e-books and edited volumes carry it as text in 505. A full-text contents note turns every chapter title, and in the enhanced form every chapter author, into a search and index entry point. A link in 856 42 $3 Table of contents gives one URL that most catalogues do not index. 505 complements the 856 link; it does not replace it. Send both when you have both.

505  0# $a Introduction -- Records in transit -- Identifiers that hold -- Licences in the record -- Index.
505  00 $t Introduction / $r A. Editor -- $t Records in transit / $r B. Author $g (pages 11–38) -- $t Identifiers that hold / $r C. Author and D. Author --
505  80 $t Licences in the record / $r E. Author -- $t Index.
856  42 $3 Table of contents $u https://example.org/toc.pdf

• 505 0# basic: all parts in a single $a, separated by --. Use it for monographs, or when only chapter titles are available.
• 505 00 enhanced: each part as $t title, $r statement of responsibility (after /) and $g other information such as part, volume or page numbering. Use it for edited volumes and multi-author works where chapter authors matter: systems can index $t and $r for title and author searches. They are not controlled headings; chapter authors who need authority control also get a 700 (or 730/740 for titles).
• Indicators (LoC): first 0 contents, 1 incomplete, 2 partial, 8 no display constant; second # basic, 0 enhanced.
• Punctuation: -- between parts, / before a statement of responsibility; end the field with a full stop unless the contents continue in another 505.
• Long contents: 505 is repeatable. Split a long table of contents over several 505 fields: the first carries first indicator 0, each continuation carries 8, so no second “Contents:” label is displayed. OCLC BFAS shows exactly this (505 80 continuing the note begun in the first). bd505 · BFAS 505

Leader, 006, 007 and 008 by resource type

The fixed fields carry most of the machine logic, so they get their own tables. Positions not listed are optional or follow the MARC definition. Each position links to its LoC page: Leader, 006, 007, 008 all materials, 008 books, 008 continuing resources.

E-books (monographs, 008 Books)

Position	Value	Meaning
LDR/05	n · c · d	new · corrected · deleted (record status)
LDR/06	a	language material (text)
LDR/07	m	monograph/item
LDR/09	a	UCS/Unicode (UTF-8)
LDR/17	# or 7	full or minimal level
LDR/18	i or c	ISBD punctuation included or omitted
006/00	m	computer file / electronic resource
006/06	o	online
006/09	d	document
007/00-01	cr	electronic resource, remote
008/06	s or t	single date · publication and copyright date
008/07-10	yyyy	date 1
008/15-17	gw · au · sz · xxu · enk	place of publication (MARC country code)
008/23	o	form of item: online (Books)
008/24-27	b · i …	nature of contents (bibliographies, indexes …)
008/29	0 or 1	conference publication
008/31	0 or 1	index
008/33	0	not fiction
008/35-37	ger · eng	language
008/39	d · c · #	cataloguing source

E-journals (serials, 008 Continuing resources)

Position	Value	Meaning
LDR/06	a	language material (text)
LDR/07	s	serial
006/00 · /06 · /09	m · o · d	electronic resource, online, document
007/00-01	cr	electronic resource, remote
008/06	c or d	currently published · ceased
008/07-10 · /11-14	yyyy · 9999	beginning · ending date (9999 = ongoing)
008/18	q · m · a · z …	frequency
008/19	r · n · x · u	regularity
008/21	j	journal (latest MARC 21 value, defined since 2021); p periodical still valid
008/22	#	form of original item: none of the following
008/23	o	form of item: online
008/34	0	successive entry
008/35-37	ger · eng	language

008/21. This set follows the latest MARC 21 values: e-journals take j journal, defined since its addition in 2021 (“Periodical addressing readers interested in a specific subject or profession”). p periodical remains valid where less granularity is wanted. bd008s
Example: 008 261017c20269999gw qr j o 0 0eng d (quarterly, regular, journal, online, successive entry).

Databases and websites (integrating resources)

Position	Value	Meaning
LDR/06	a (or m)	text-based database a; predominantly non-textual m (then 008 Computer files)
LDR/07	i	integrating resource
006/00 · /06 · /09	m · o · d / e / j	electronic resource, online; type of file by content (document, bibliographic data, online system or service)
007/00-01	cr	electronic resource, remote
008/06	c or d	currently published · ceased
008/07-10 · /11-14	yyyy · 9999	beginning · ending date
008/18	k (or other)	frequency: k continuously updated
008/19	r · n · x · u	regularity
008/21	d or w	updating database · updating website
008/23	o	form of item: online
008/34	2	integrated entry

Integrating resources. LDR/07 i uses the continuing-resources 008 with 008/34 2 integrated entry: one record that is updated as the resource changes, with no successive records. 588 describes the latest iteration consulted.

What the current documents ask for

Each document works on its own layer: a cataloguing rule (how to describe), an application profile (which elements a programme requires), or a delivery spec (what a supplier must send). The summaries below say which layer, then what matters for an e-resource record.

DNB and the German-language union catalogues

• AG KVA, Anforderungen der deutschsprachigen Verbundsysteme und der Deutschen Nationalbibliothek an Metadatenlieferungen zu E-Books und E-Book-Paketen (English: Metadata for e-books). Current online edition, valid from 1 June 2023; it replaces the PDF edition of 5 August 2016 (“überarbeitete Fassung für die Anwendung des Regelwerkes RDA ab 1. Oktober 2015”, PDF). Delivery spec of the networks and the DNB (BVB, DNB, GBV, hbz, hebis, KOBV, OBV, SLSP, SWB, ZDB). MARC 21 (ISO 2709 or MARCXML) or ONIX 3.0.8, UTF-8, SFTP or OAI-PMH. Each element is marked mandatory, mandatory if available, or optional, with a MARC field and example. Key MARC points: 001 stable ID; 003/040 $a provider; 020, 024 $2 doi, 776 08 $i Erscheint auch als $n Druck-Ausgabe $z; 1XX/7XX with $4 and $0; 506 0# $a Open access; 540 $a $f $2 cc $u; 912/950 for collections. KBART title lists go alongside. German · English
• RDA DACH. Cataloguing rule and application profile for the region, on the STA documentation platform since 2023; release 2026/1 came out in June 2026. It merges RDA, the former D-A-CH application rules and the explanations. sta.dnb.de/doc/RDA
• DNB MARC 21 field descriptions. Format application: how the DNB itself exports title, holdings and authority data. Title data are at version 4.4 (10 November 2025). dnb.de/marc21
• K10plus (GBV and SWB). MARC 21 export documentation of the shared catalogue, and its cataloguing manual for e-books. MARC21 export · E-books manual (PDF)

Library of Congress and PCC (US)

• PCC Provider-Neutral E-Resource MARC Record Guide (P-N/RDA combined, 30 September 2024). Application guideline for one record per e-resource across providers: monographs, serials and integrating resources. 040 $e rda $e pn; no package or provider-specific data in 773, 8XX, 506 or 540; 506 and 856 $7 0 for open access. Guidelines page · PDF
• BIBCO Standard Record (BSR) RDA MAP (26 April 2024). Application profile, a floor record for monographs. Textual monographs: LDR/17 blank, LDR/18 i or c, at least one class number, subject and genre/form access supported by authority records. BSR MAPs
• CONSER Standard Record (CSR) RDA MAP. Application profile for serials: 310 frequency core if known, always a source-of-title and “Description based on” note in 588. CSR (PDF)
• LC-PCC Policy Statements. Policy layer on top of RDA, free in the RDA Toolkit. Access
• Official RDA. PCC moves to the official RDA Toolkit on a rolling schedule (May 2024 to April 2027). Until PCC says otherwise, PCC records follow original RDA. PCC notice (PDF) · FAQ

OCLC

• Bibliographic Formats and Standards (BFAS). Input standard. Two levels: Full (ELvl blank or 1) and Minimal (ELvl 7). Every field page gives Full/Minimal for the field and each subfield. Introduction · Fixed fields
• Vendor Record Contribution Program. Delivery acceptance spec for supplier records: valid MARC 21 (or MARCXML, ONIX 3.0+), fewer than 2% machine-detectable coding errors, US cataloguing and heading standards, at least minimal-level completeness. VRCP
• WorldShare Collection Manager, knowledge base MARC delivery. Delivery spec on the library side: a title gets a record only with an OCLC number, a format, a coverage value and, for e-books and full-text journals, a title URL. That makes the KBART title_url and a WorldCat match part of the record supply. Troubleshooting

Minimum fields per resource type

// checklist

• E-bookLDR /06 a /07 m /09 a · 001 · 003 · 005 · 006 m · 007 cr · 008 Books /23 o · 020 · 024 doi · 040 $e rda · 041 · 1XX/7XX $4 $0 · 245 · 264 #1 · 300 · 336–338 · 347 · 490/8XX · 505 (where a TOC exists; 00 for edited volumes) · 506/540 (OA) · 520 · 588 · 6XX $0 $2 · 776 · 856 40 (+ 856 42 TOC link) · 540 record CC0 · when applicable: 500 AI disclosure, 883 for machine-generated fields
• E-journalLDR /06 a /07 s · 001 · 003 · 006 m · 007 cr · 008 CR /18 /19 /21 j /23 o /34 0 · 022 · 040 · 245 · 246 · 264 #1 · 310 · 336–338 · 362 · 506/540 (OA) · 520 · 588 · 6XX · 776 · 780/785 · 856 · 540 record CC0 · when applicable: 500 AI disclosure, 883 for machine-generated fields
• Database / websiteLDR /07 i · 001 · 003 · 006 m · 007 cr · 008 CR /18 k /19 /21 d or w /23 o /34 2 · 040 · 245 · 246 · 264 #1 · 310 · 336–338 · 520 · 588 (latest iteration) · 6XX · 856 · 540 record CC0 · when applicable: 500 AI disclosure, 883 for machine-generated fields

Sample field values

example Illustrative values for a fictional open-access e-book. Identifiers are placeholders. The GND IDs are real public authority records.

LDR  00000nam a2200000 i 4500
006  m     o  d
007  cr |||||||||||
008  261017t20262026gw      ob    001 0 eng d
020  ## $a 9783XXXXXXXXX $q (PDF)
024  7# $a 10.xxxx/example.2026 $2 doi
035  ## $a (XX-0000)EX000123
040  ## $a XX-0000 $b eng $e rda $c XX-0000
041  ## $a eng
082  04 $a 306.2 $2 23
245  10 $a Example title : $b a subtitle / $c edited by A. Editor.
264  #1 $a Berlin : $b Example Press, $c [2026]
264  #4 $c ©2026
300  ## $a 1 online resource (xii, 300 pages)
336  ## $a text $b txt $2 rdacontent
337  ## $a computer $b c $2 rdamedia
338  ## $a online resource $b cr $2 rdacarrier
347  ## $a text file $2 rdaft
347  ## $b PDF
505  00 $t Introduction / $r A. Editor -- $t First chapter title / $r B. Author -- $t Second chapter title / $r C. Author.
506  0# $a Open access $f open access $2 coarar
540  ## $a Creative Commons Attribution 4.0 International $f CC BY 4.0 $2 cc $u https://creativecommons.org/licenses/by/4.0/
588  0# $a Description based on online resource; title from PDF title page (viewed October 17, 2026)
650  #7 $a Politische Soziologie $0 (DE-588)4046558-5 $0 https://d-nb.info/gnd/4046558-5 $2 gnd
655  #7 $a Aufsatzsammlung $0 (DE-588)4143413-4 $2 gnd-content
700  1# $a Editor, A. $e editor $4 edt
776  08 $i Print version: $t Example title $z 9783XXXXXXXXX
856  40 $u https://doi.org/10.xxxx/example.2026 $7 0
856  42 $3 Table of contents $u https://example.org/toc.pdf

For DACH delivery, the 776 reads 776 08 $i Erscheint auch als $n Druck-Ausgabe $z …, and cataloguing in German gives 040 $b ger with German RDA terms in 300 and 336–338.

Illustrative OA e-book record

example Illustrative example, not a real record. A fictional open-access e-book in line format, 32 lines. Title, names, ISBNs, DOI and GND numbers are dummies. The field choice and the indicator and subfield patterns follow well-formed vendor practice.

LDR  00000nam a2200000 i 4500
006  m     o  d
007  cr |||||||||||
008  261017s2026    gw      ob    001 0 eng d
020  ## $a 9783000000000 $q (PDF)
024  7# $a 10.xxxx/example $2 doi
040  ## $a XX-0000 $b eng $e rda $c XX-0000
041  0# $a eng $a ger
082  04 $a 025.3 $2 23
100  1# $a Muster, Erika, $e author. $4 aut $0 (DE-588)0000000-0
245  10 $a Records that travel : $b a fictional guide to e-book metadata / $c Erika Muster.
264  #1 $a Berlin : $b Example Academic Press, $c [2026]
300  ## $a 1 online resource (xiv, 280 pages)
336  ## $a text $b txt $2 rdacontent
337  ## $a computer $b c $2 rdamedia
338  ## $a online resource $b cr $2 rdacarrier
347  ## $a text file $2 rdaft
490  0# $a Example studies in metadata, $x 0000-0000 ; $v 12
500  ## $a AI use disclosed by the author: language editing of chapters 2–4 with a generative AI tool; the author reviewed all text.
505  00 $t Introduction / $r Max Beispiel -- $t Why records travel -- $t Identifiers that hold -- $t Licences in the record -- $t Provenance and the machine -- $t Appendix: a field checklist $g (pages 251–268).
506  0# $a Open access $u http://purl.org/coar/access_right/c_abf2 $f Unrestricted online access $2 star
520  3# $8 1\p $a This fictional handbook follows an e-book record from publisher to library catalogue and shows which fields survive the trip. (Repeat 520 for each language of the abstract.)
540  ## $a Creative Commons Attribution 4.0 International $f CC BY 4.0 $2 cc $u https://creativecommons.org/licenses/by/4.0/
540  ## $3 Bibliographic record $a Metadata in this record released under CC0 1.0 Universal. $f CC0 1.0 $2 cc $u https://creativecommons.org/publicdomain/zero/1.0/ $q XX-0000
588  0# $a Description based on online resource; title from PDF title page (viewed October 17, 2026)
650  #7 $8 2\p $a Metadaten $0 (DE-588)0000000-1 $0 https://d-nb.info/gnd/0000000-1 $2 gnd
655  #7 $a Handbuch $0 (DE-588)0000000-2 $2 gnd-content
700  1# $a Beispiel, Max, $e writer of introduction. $4 win $0 (DE-588)0000000-3
776  08 $i Print version: $t Records that travel $z 9783000000017
856  40 $u https://doi.org/10.xxxx/example $7 0
883  1# $8 1\p $a abstract-llm-v1, human-reviewed $c 0.9 $d 20261018 $q XX-0000 $u https://example.org/provenance/abstract-llm-v1
883  0# $8 2\p $a subject-classifier-v2 $c 0.72 $d 20261018 $q XX-0000

The 505 is core here because the book has a table of contents; it uses the enhanced form because the introduction has its own author. The 500, the 520–883 link and the 650–883 link are conditional: use them only when AI was involved. The record CC0 line goes on every record. XX-0000 stands in for your MARC organisation code or ISIL.

Reference for a well-received OA e-book data sample: OA e-book collection, public metadata portal.

For a DACH delivery, swap the 776 for 776 08 $i Erscheint auch als $n Druck-Ausgabe $z …, add the RSWK chain as 689 00 $a … $0 (DE-588)… if the recipient wants it, and use 084 for RVK or BK. A traced series takes 490 1# plus 830 #0.

Provenance and licensing: the DataMercs layer

The three market documents stop at the resource. This set also says who may reuse the record and how a machine was involved in the work or the metadata. Each standard below is named by its layer.

CC0 on the record itself

DataMercs core Every record carries a CC0 statement for its own metadata. This is separate from the resource licence in 506/540. Reason: anyone can reuse, merge and enrich the record without asking.

540  ## $3 Bibliographic record $a Metadata in this record released under CC0 1.0 Universal. $f CC0 1.0 $2 cc $u https://creativecommons.org/publicdomain/zero/1.0/ $q XX-0000

• MARC 21 field 540 (format, LoC, December 2024): terms governing use and reproduction. $f takes a term from a standardised list such as Creative Commons. $2 cc is the Creative Commons code in the LoC Access Restriction Term Source Codes. $u takes a URI. $q names the supplying agency. LoC’s own CC example puts the licence URI in $0 (added 2024); this set uses $u, as the DNB does in its resource 540. bd540 · source codes
• The extension. 540 $3 is defined as “part of the described material”. Using it to point at the bibliographic record is a DataMercs extension. MARC 21 has no field for the licence of the record itself, and the MARC papers on open access and licences (2018-DP11, Proposal 2019-01, 2024-DP04) deal with the resource. Put the record line after the resource 540 so that a system ignoring $3 still shows the resource licence first. 2019-01 · 2024-DP04
• DNB (policy layer): all title data and GND authority data are available under CC0 1.0, stated on the business-model page and in the open-data download notes. The licence is not repeated in the records; live records carry 540 only for the resource (540 ## $u http://creativecommons.org/licenses/by/4.0 $2 cc). Geschäftsmodell · data.dnb.de
• OCLC (policy layer): OCLC recommends the Open Data Commons Attribution licence (ODC-BY) for member libraries that publish WorldCat-derived data, with an attribution sentence and a pointer to the WorldCat community norms. The terms live in WorldCat Rights and Responsibilities; origin travels in the record as 040 and the 035 (OCoLC) number. Press release, 6 August 2012 · WorldCat Rights and Responsibilities

AI in the resource

• COPE and ICMJE (publication-ethics layer): an AI tool cannot be an author because it cannot take responsibility for the work. Authors disclose the tool and how they used it. COPE · ICMJE
• MARC relator list (code list, LoC): it has no term or code for AI or machine generation. The nearest entries, software developer [swd] and music programmer [mup], describe persons. Relator terms
• CRediT (ANSI/NISO Z39.104-2022, contributor-role taxonomy): its 14 roles describe human contributors. The STM classification of AI use in manuscript preparation (September 2025) names the activities, such as language editing or drafting, that a disclosure can cite. The AID Framework (2024) gives a structured disclosure statement. CRediT · STM · AID Framework

So the disclosure is a note, not a heading. 500 fits: it is the general note for information without a specialised 5XX. 545 holds the creator’s biography, and 588 is about the record.

500  ## $a AI use disclosed by the author: language editing of chapters 2–4 with a generative AI tool; the author reviewed all text.

If the tool has to be indexed, an uncontrolled added entry can trace it. This is a DataMercs extension, optional, and never a 100/700:

720  2# $a Example language model 1.0 $e language editing tool

AI in the record

MARC 21 field 883 (format, LoC, May 2020) records metadata provenance for a linked field. First indicator: 0 fully machine-generated, 1 partially machine-generated, 2 not machine-generated, # no information. Subfields:

• $a creation process
• $c confidence value, from 0 to 1, with a point or comma
• $d creation date (yyyymmdd)
• $q agency, as a MARC organisation code
• $u URI of the process
• $x validity end date
• $w source record number
• $0 source authority number, $1 real-world object URI
• $8 field link

Link both fields with the same $8 number and link type p.

520  3# $8 1\p $a [abstract text]
650  #7 $8 2\p $a [subject] $0 (DE-588)… $2 gnd
883  1# $8 1\p $a abstract-llm-v1, human-reviewed $c 0.9 $d 20261018 $q XX-0000 $u https://example.org/provenance/abstract-llm-v1
883  0# $8 2\p $a subject-classifier-v2 $c 0.72 $d 20261018 $q XX-0000

XX-0000 is a placeholder for your MARC organisation code or ISIL. DNB records use the same pattern for machine-assigned DDC classes, for example 883 0# $8 6\p $a emakn $c 0,16014 $d … $q DE-101 $u https://d-nb.info/provenance/plan#emakn. bd883 · $8 link types

Data provenance $7 (MARC 21 Appendix J, added 2022, revised December 2025) is defined in 520, 650, 500 and 720, among others, but not in 540 or 883. It holds a provenance value for the other subfields of the same field and can carry a category code from the LoC Data Provenance Code List, for example dpenmw (note on metadata work). The values themselves are not controlled. Use it as an optional in-field echo; 883 stays the carrier. Appendix J · Code list

520  3# $a [abstract text] $7 (dpenmw)machine-generated, human-reviewed

A human-readable line in 588 is also within that field’s scope (“tracking and controlling the metadata”): 588 ## $a Abstract machine-generated and reviewed by the cataloguer.

Why

Provenance is the point of this site. A record that says who made it, by which process and under which licence can be trusted, corrected and passed on. This page practises what it describes: it names its author of record and its tool, credited as “OSDS AI, via Grok Bot”, which is a disclosure and not an authorship. Related posts: Ghost in the MARC and Who signs, who drives.

QA checklist

before delivery
1. LDR/09 a and the file really is UTF-8; no mixed encodings in one batch.
2. LDR/06–07 match 008 (Books vs Continuing resources) and 006/007 are present and agree with 338.
3. 001 is stable: the update file carries the same ID as the first delivery; deletes go out as a separate file.
4. 020 holds only e-ISBNs in $a; print ISBNs in 776 $z (and 020 $z under PN).
5. 024 $a is a bare DOI, ind1 7, $2 doi; the same DOI resolves in 856 $u.
6. 040 $b matches the language of 300, 336–338 and the notes; 040 $e rda is present.
7. 264 second indicator is right (1 publication, 4 copyright); no 260 alongside.
8. 506 first indicator agrees with $a (0 = no restrictions); 856 $7 agrees with 506.
9. 540 $f uses the CC short form, $2 cc, and $u points to the matching licence version.
10. Where a table of contents exists, 505 carries it as text (00 for edited volumes, 0# otherwise), parts separated by – , continuations with first indicator 8; an 856 42 $3 Table of contents link goes alongside, never instead.
11. Every controlled access point (1XX, 6XX, 7XX) has $2 or a thesaurus indicator, and a $0/$1 that resolves.
12. No package, platform or price data in 490/8XX or general notes; use 912/950 locally where the recipient wants it.
13. Every machine-generated or AI-assisted field has an 883 with the right first indicator (0 fully, 1 partially) and the same $8 number with link type p; $q holds a MARC organisation code.
14. Every record carries the record CC0 line (540 $3 Bibliographic record … $f CC0 1.0 $2 cc), separate from the resource licence.
15. AI involvement in the resource is a 500 note, never a 100/700 heading.
16. Validate the batch (MARC structure, field and indicator validity) before sending. OCLC loads vendor batches only if fewer than 2% of records have machine-detectable coding errors.

What changed since the 2016 core set

• Scope: e-journals and databases (integrating resources) join e-books, with their own LDR/008 tables.
• Markets: one column each for DNB/DACH, LC/PCC and OCLC instead of a single house level.
• Identifiers: 020 $q for format qualifiers; print ISBN to 776; 024 DOI kept; 016 for the DNB number; $0/$1 identifiers and URIs in 1XX, 6XX and 7XX.
• RDA: 264 with copyright in #4; 336–338 with $b codes; 347 split into $a … $2 rdaft and $b PDF; 040 $e pn for provider-neutral records; LDR/18 i or c.
• Open access: 506 with $f/$2, 540 with CC licence and link, 856 $7.
• Subjects: GND and LCSH with $0 and $2; 655 genre/form (gnd-content, lcgft); 082 and 084 (sdnb, rvk, bkl) alongside 072.
• Linking: 776 in DACH and PCC wording; 758 for identifiers of related entities; 856 kept for access.
• Packages: 773 package entries left out (PN: not used); package data go to local 912/950.
• Contents: 505 retained and now core for e-books and edited volumes wherever a table of contents exists: 00 enhanced (\(t/\)r/$g) for edited and multi-author works, 0# basic otherwise. The 856 42 $3 Table of contents link complements it and does not replace it.
• Dropped: 538 “Mode of access” (PN: only for digital preservation records).
• New, optional: 341/532 accessibility.
• Provenance and licensing (DataMercs core): CC0 for the record itself on every record; AI use in the resource as a 500 note; 883 with $8 links for machine-generated fields.

Sources

Library of Congress. MARC 21 Format for Bibliographic Data. https://www.loc.gov/marc/bibliographic/

AG Kooperative Verbundanwendungen. Anforderungen der deutschsprachigen Verbundsysteme und der Deutschen Nationalbibliothek an Metadatenlieferungen zu E-Books und E-Book-Paketen (online edition, valid from 2023-06-01). https://www.agkva.org/888668211.html · English: https://www.agkva.org/1013678130.html

AG Kooperative Verbundanwendungen. Anforderungen der deutschsprachigen Verbundsysteme und der Deutschen Nationalbibliothek an Metadatenlieferungen zu E-Books und E-Book-Paketen. Überarbeitete Fassung für die Anwendung des Regelwerkes RDA ab 1. Oktober 2015 (PDF, 5 August 2016; superseded). https://www.dnb.de/SharedDocs/Downloads/DE/Professionell/Standardisierung/AGV/anforderungenMetadatenEbooksMarcOnixRDA2015.pdf?__blob=publicationFile&v=1

Standardisierungsausschuss. RDA DACH, release 2026/1. https://sta.dnb.de/doc/RDA

Deutsche Nationalbibliothek. MARC 21. https://www.dnb.de/marc21

Program for Cooperative Cataloging. Provider-Neutral E-Resource MARC Record Guide: P-N/RDA Combined Version (30 September 2024). https://www.loc.gov/aba/pcc/scs/documents/PN-RDA-Combined.pdf

Program for Cooperative Cataloging. BIBCO Standard Record (BSR) RDA Metadata Application Profile (26 April 2024). https://www.loc.gov/aba/pcc/bibco/bsr-maps.html

Program for Cooperative Cataloging. CONSER Standard Record (CSR) RDA Metadata Application Profile. https://www.loc.gov/aba/pcc/conser/documents/CONSER-RDA-CSR.pdf

OCLC. Bibliographic Formats and Standards. https://www.oclc.org/bibformats/en/about/introduction.html

OCLC. Vendor Record Contribution Program (VRCP). https://help.oclc.org/Metadata_Services/WorldShare_Collection_Manager/Data_sync_collections/Reference/Vendor_Record_Contribution_Program_VRCP

Library of Congress. MARC 21 Bibliographic: 540 Terms Governing Use and Reproduction Note (December 2024); 883 Metadata Provenance (May 2020); Appendix J: Data Provenance Subfields (December 2025). https://www.loc.gov/marc/bibliographic/bd540.html · https://www.loc.gov/marc/bibliographic/bd883.html · https://www.loc.gov/marc/bibliographic/bdapndxj.html

Library of Congress. Access Restriction Term Source Codes; Data Provenance Code List; MARC Code List for Relators. https://www.loc.gov/standards/sourcelist/access-restriction.html · https://www.loc.gov/standards/valuelist/dataprov.html · https://www.loc.gov/marc/relators/relaterm.html

MARC Advisory Committee. Proposal 2019-01: Designating Open Access and License Information for Remote Online Resources; Discussion Paper 2024-DP04: Adding Subfields $0 and $1 to Fields 506 and 540. https://www.loc.gov/marc/mac/2019/2019-01.html · https://www.loc.gov/marc/mac/2024/2024-dp04.html

Deutsche Nationalbibliothek. Geschäftsmodell für Metadatendienste. https://www.dnb.de/DE/Professionell/Metadatendienste/Datenbezug/geschaeftsmodell.html

OCLC. WorldCat Rights and Responsibilities for the OCLC Cooperative. https://www.oclc.org/en/worldcat/cooperative-quality/policy.html

COPE. Authorship and AI tools. https://publicationethics.org/guidance/cope-position/authorship-and-ai-tools · ICMJE. AI use by authors. https://www.icmje.org/recommendations/browse/artificial-intelligence/ai-use-by-authors.html

NISO. CRediT, Contributor Role Taxonomy (ANSI/NISO Z39.104-2022). https://credit.niso.org/ · STM. Recommendations for a Classification of AI Use in Academic Manuscript Preparation (2025). https://stm-assoc.org/document/recommendations-for-a-classification-of-ai-use-in-academic-manuscript-preparation/ · Weaver, K. D. The Artificial Intelligence Disclosure (AID) Framework: An Introduction. C&RL News 85(10), 2024. https://crln.acrl.org/index.php/crlnews/article/view/26548

Byline: Olaf Schmalfuß (author of record). Tool disclosure: OSDS AI, via Grok Bot, was used for drafting and source checks; it is not a co-author.