Pickup Location
Names
Name | Guidance / Context | Reference |
---|---|---|
Common Name | Pickup Location | |
Alternative Names | FOLIO: Service Point
| |
DCB Technical Name |
|
Provision
Information | Note |
|
---|---|---|
Scope |
| |
Owner |
| |
Purpose |
|
DCB Implementation
DCB Service and Client Adaptors
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 |
---|---|---|---|
|
|
|
|
|
|
|
|
DCB Admin
Integration status: Not Integrated Viewable importable Editable
Tracking issue link: <LINK>
Admin page link: <LINK>
Mapping Model
Type: Reference Numeric Range
Target Mapping Scope: System Spine DCB
Link to import template: <LINK>
Mapping Structure
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 |
---|---|---|---|
|
|
| Valid: Invalid: |
|
|
| Valid: Invalid: |
|
|
| Valid: Invalid: |
|
|
| Valid: Invalid: |
|
|
| Valid: Invalid: |
|
|
| Valid: Invalid: |
|
|
| Valid: Invalid: |
|
|
| Valid: Invalid: |
|
|
| Valid: Invalid: |
|
|
| Valid: Invalid: |
|
|
| Valid: Invalid: |
DCB Canonicals
List of accepted DCB values that sources can map to
Authorative Codebase Referent:
Value | Interpretation |
---|---|
|
|
|
|
Operated as a Community Resource by the Open Library Foundation