Understanding Book Accession Numbers

Define the unit you are tracking

A register might assign a number to each physical volume, while another local procedure may organize acquisitions differently. Write the unit into the policy: one copy, one volume, one set, or another clearly defined unit. Ambiguity becomes costly when staff add a second copy or receive the remaining volumes of a set.

For the fictional examples in this guide, assume one number per physical item. A two-volume set then receives two accession entries, and a second copy of volume one receives a third. This is an example policy for teaching, not a requirement imposed by LibCatalogTools.

Decide how accession numbers and barcodes relate

Some libraries use the accession number itself as the value encoded in the item barcode. For example, accession number 2026-00421 may also be the value returned when its barcode is scanned. Other libraries assign a separate circulation identifier. Both arrangements should be documented in the local workflow; separate identifier values are not always necessary.

The first row uses accession number 2026-00421 as the barcode value. The second row illustrates a separate barcode value, LIB000813. These rows demonstrate two possible practices; follow the policy adopted by your library. REF is the example location code for the reference collection and appears before the class number in both sample call numbers. Your system may maintain these in separate fields even when the values match. The two copies share a main shelf mark but retain distinct item identifiers. Store identifier values as text so leading zeros and punctuation survive exports. Do not infer a publication year from the first four digits of an accession number unless your local scheme explicitly defines them that way.

Plan for corrections and withdrawals

A useful local procedure preserves a traceable history. If a transcription error is corrected, retain a note linking the old value to the corrected entry. If an item is withdrawn, record its status and the action date in the appropriate system. Avoid silently assigning its old identifier to an unrelated new item: old reports and labels could then point to the wrong object.

For a migration, keep a crosswalk between legacy accession values and new item identifiers. Test for duplicates before import and investigate whether each duplicate is an error, an intentionally shared set number, or a collision between branch sequences. Fix the meaning before forcing a unique value.

Connect accessioning to label work

1. Receive and verify the item against the acquisition documentation.
2. Assign the accession entry under the local policy.
3. Create or attach the item record, using the accession number as its barcode value or assigning a separate value according to local policy.
4. Review the bibliographic and call-number information.
5. Print the spine label from the approved shelf data, keeping the accession value separate unless local policy places it on the label.

The current generator has no dedicated accession field. Putting an accession number into the class-number field would misrepresent its purpose. Maintain accession records in your library system or register, and use this tool for the call-number components it actually supports.

Frequently asked questions

Can the accession number also be the barcode value?

Yes. Some libraries encode the accession number in the item barcode and use that same value for circulation. Others assign a separate barcode value. Follow your local policy and ensure the scanned value identifies the intended item in your system.

Is an accession number an ISBN?

No. An ISBN concerns a publication product; an accession number belongs to the local acquisition or item-tracking workflow.

Does every copy need a different accession number?

That depends on the unit defined by local policy. In a one-number-per-item scheme, yes.