Branches, locations and item types
Build a small, consistent code list before configuration and migration.
Check the official Koha manual for your installed version.
Keep different decisions separate
Koha configuration distinguishes libraries, item types and other authorised values. Plan the meaning of each field before mapping data from an existing catalogue. A label that looks similar may represent a different concept.
Make a configuration sheet
| Concept | Use it to describe | Illustrative value |
|---|---|---|
| Library | A branch or library sharing the system | Central library |
| Shelving location | Where an item is placed within a library | Children’s room |
| Item type | A configured category relevant to lending | Standard loan book |
| Collection | A grouping within the holdings | Local history |
Review before you import
For every source code, write down the destination code, its label and the person who approved the mapping. Flag unmapped values instead of silently merging them.
Try the model with a book, reference item, journal and any unusual material your library lends. Check that staff can explain the distinction between branch, location, type and collection. Keep the approved sheet with the migration plan.