Circulation Status

Names

Name	Guidance / Context	Reference

Information	Note

How is this mapping used by DCB, and what to expect when it’s not right

Workflows: what use cases or workflows use the mapping and to what end
Technical: principal classes (or other technical elements) that apply in this case
Missing: what to expect when the mapping is missing
Incorrect: what to expect when the mapping is present but wrong

Workflow / Use Case	Technical Reference	Missing	Incorrect

Workflow / Use Case	Technical Reference	Missing	Incorrect

Fields: list expected source and destination fields, including additional fields.
Description: what the field represents, and where values may be sourced
Validation: describe expected data formats any validation expected applied
Example: provide good and bad examples in expected format and case

Field	Description	Validation	Example

Field	Description	Validation	Example
`fromContext`	The source context - normally the hostLMS code of the system being mapped.	String code that must exist as the `HostLMS ID`	Valid: “SLOUC”, “cs00000001_0059” Invalid: “St Louis”, “STLOUIS”, “SLCC”, “6slu”, “BRIDGES”
`fromCategory`	The category of mapping	Must be a known (Case sensitive) category “TBC”	Valid: Invalid:
`fromValue`	The value encoded as a STRING		Valid: `RECEIVED`, `REQUESTED`, Invalid:
`toContext`			Valid: `DCB` Invalid:
`toCategory`	The category of mapping		Valid: Invalid:
`toValue`	The DCB Canonical Code to use	A case-sensitive string value	Valid: `AVAILABLE`, `UNAVAILABLE` Invalid: `-`, `Unavailable`
`Label`			Valid: Invalid:
`Additional1`			Valid: Invalid:
`Additional2`			Valid: Invalid:
`AgencyName`			Valid: Invalid:
`LocalID`			Valid: Invalid:

List of accepted DCB values that sources can map to

Value	Interpretation

Value	Interpretation
`AVAILABLE`
`UNAVAILABLE`