Custodia Registry · C04
Physical borrowing
30 minutes. · 10 slides
Lesson video coming soon. The player below contains a sample video, not this lesson. You can use the written lesson and slide guide now.
Work through the lesson
Use these explanations alongside the slide guide. Expand any section to read its full explanation.
Your task and authority
- Confirm your assigned duties
- Use the fictional training case
- Verify the result and its history
Learning outcome
Borrower can show the physical handoff and return chain without claiming an unreceived file was shelved.
Read the full explanation
Our audience is Members, digitization interns and other borrowers. Before the demonstration, confirm these prerequisites: C01, C02; fictional training record and approved account. The action-level access conditions are: record_physical_request; ownership and clearance checks. Check the actual account and record state. The goal is not simply to find a button: Borrower can show the physical handoff and return chain without claiming an unreceived file was shelved.
Request the file
- Submit a physical request with reason for the assigned record.
What to check
Identify the record and state the business reason for borrowing it. Physical-request authority is separate from a digital grant. Read the saved request before arranging collection.
Read the full explanation
Submit a physical request with reason for the assigned record. Identify the record and state the business reason for borrowing it. Physical-request authority is separate from a digital grant. Read the saved request before arranging collection. As we work through this example, identify the record or account involved and point out the evidence that confirms this step. If the expected control or result is missing, pause and explain the condition before continuing.
Approval and readiness
- Track approval and readiness before visiting the Registry.
What to check
Wait for the appropriate approval and ready state. A submitted request does not prove the file is available at the desk. Confirm the collection arrangement with the Registry through the approved channel.
Read the full explanation
Track approval and readiness before visiting the Registry. Wait for the appropriate approval and ready state. A submitted request does not prove the file is available at the desk. Confirm the collection arrangement with the Registry through the approved channel. As we work through this example, identify the record or account involved and point out the evidence that confirms this step. If the expected control or result is missing, pause and explain the condition before continuing.
Confirm actual pickup
- Confirm pickup only after receiving the matching file.
What to check
Compare the physical label with the record you requested. Confirm pickup only after the matching file is in your hands. A notification alone does not establish physical possession.
Read the full explanation
Confirm pickup only after receiving the matching file. Compare the physical label with the record you requested. Confirm pickup only after the matching file is in your hands. A notification alone does not establish physical possession. As we work through this example, identify the record or account involved and point out the evidence that confirms this step. If the expected control or result is missing, pause and explain the condition before continuing.
Due date and return
- Review due date and any recall; initiate return when handing the file back.
What to check
Monitor the due date and any recall. Initiate return when handing the file back through the agreed process. The request to return and the Registry’s receipt are separate events.
Read the full explanation
Review due date and any recall; initiate return when handing the file back. Monitor the due date and any recall. Initiate return when handing the file back through the agreed process. The request to return and the Registry’s receipt are separate events. As we work through this example, identify the record or account involved and point out the evidence that confirms this step. If the expected control or result is missing, pause and explain the condition before continuing.
Verify receipt
- Confirm Registry receipt and final status rather than assuming Initiate return means reshelved.
What to check
Locate the receipt and resulting custody state. Registry staff still need to confirm the final storage location. Do not report a file as reshelved merely because you clicked the return action.
Read the full explanation
Confirm Registry receipt and final status rather than assuming Initiate return means reshelved. Locate the receipt and resulting custody state. Registry staff still need to confirm the final storage location. Do not report a file as reshelved merely because you clicked the return action. As we work through this example, identify the record or account involved and point out the evidence that confirms this step. If the expected control or result is missing, pause and explain the condition before continuing.
Exceptions and recovery
- Identify the blocked condition
- Preserve the relevant evidence
- Use the authorized next step
Important boundary
Do not confirm physical possession from a notification alone. A pending return requires Registry receipt and location confirmation.
Read the full explanation
Consider the exception before deciding to retry. Do not confirm physical possession from a notification alone. A pending return requires Registry receipt and location confirmation. Explain what you expected and what was actually shown. Keep the record identifier and sanitized error context, then refer the issue to the person responsible for that decision. A missing or blocked control is not a reason to borrow a more powerful account.
Guided practice
- Work within the assigned role
- Show the resulting state
- Explain one exception
Your exercise
Use a fictional file to explain request, readiness, pickup and return. Identify the evidence still missing immediately after a borrower initiates return.
Read the full explanation
Now use the approved fictional example. Use a fictional file to explain request, readiness, pickup and return. Identify the evidence still missing immediately after a borrower initiates return. Explain the identity, current state and intended action before acting. At the end, show the evidence of the result and name the next responsible person if the workflow cannot proceed. Destructive actions and live external sends are discussed using prepared examples.
Practice debrief
- Correct identity and authority
- Traceable result and history
- A justified next step
Expected answer
The learner ties every handoff to the correct file. Initiated return is followed by Registry receipt and final location confirmation; it is not treated as completed shelving.
Read the full explanation
The answer should establish the following: The learner ties every handoff to the correct file. Initiated return is followed by Registry receipt and final location confirmation; it is not treated as completed shelving. Walk through the evidence in the same order as the workflow. Explain the specific boundary discussed in this lesson. If a result could not be established, report it as unverified and identify what would be needed to complete the task.