Custodia Registry · R06
Storage locations
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
The location structure matches physical storage and eligible moves remain traceable.
Read the full explanation
Our audience is records_manager, director; specifically authorized location staff. Before the demonstration, confirm these prerequisites: C01, C02; fictional training record and approved account. The action-level access conditions are: record_location_manage; location QR permissions separately. Check the actual account and record state. The goal is not simply to find a button: The location structure matches physical storage and eligible moves remain traceable.
Storage hierarchy
- Inspect the existing parent/child structure and capacity.
What to check
Read the parent and child locations and any capacity information. The structure should describe real storage. A convenient name is not enough if it places a shelf under the wrong room.
Read the full explanation
Inspect the existing parent/child structure and capacity. Read the parent and child locations and any capacity information. The structure should describe real storage. A convenient name is not enough if it places a shelf under the wrong room. 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.
Create the location
- Create a fictional location under the correct parent with a clear code.
What to check
Use the approved fictional code and correct parent. Check for an existing equivalent before saving. Location-management authority does not automatically include every label action.
Read the full explanation
Create a fictional location under the correct parent with a clear code. Use the approved fictional code and correct parent. Check for an existing equivalent before saving. Location-management authority does not automatically include every label 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.
Labels and print views
- Print an authorized label and verify the resulting location view.
What to check
Print only when the account has the relevant authority. Compare the label with the saved location view before attaching it. A label for a similarly named shelf can send future movements to the wrong place.
Read the full explanation
Print an authorized label and verify the resulting location view. Print only when the account has the relevant authority. Compare the label with the saved location view before attaching it. A label for a similarly named shelf can send future movements to the wrong place. 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.
Move eligible records
- Move eligible training records and inspect their new location.
What to check
Check the record’s availability and custody state before a move. Confirm the new location after saving. A borrower holding a file and a shelf designated for storage describe different facts.
Read the full explanation
Move eligible training records and inspect their new location. Check the record’s availability and custody state before a move. Confirm the new location after saving. A borrower holding a file and a shelf designated for storage describe different facts. 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.
Location dependencies
- Explain deactivation/deletion constraints and escalate checked-out records instead of forcing a move.
What to check
Inspect dependencies before proposing deactivation or deletion. Escalate checked-out or locked records through their normal workflows. Do not force a location change to make a storage report look tidy.
Read the full explanation
Explain deactivation/deletion constraints and escalate checked-out records instead of forcing a move. Inspect dependencies before proposing deactivation or deletion. Escalate checked-out or locked records through their normal workflows. Do not force a location change to make a storage report look tidy. 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 alter live shelves as an exercise. A current holder and a storage location are different concepts; custody locks must be respected.
Read the full explanation
Consider the exception before deciding to retry. Do not alter live shelves as an exercise. A current holder and a storage location are different concepts; custody locks must be respected. 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
Describe a fictional room and shelf structure, identify the correct parent, and explain why a checked-out file cannot be treated as already moved to the shelf.
Read the full explanation
Now use the approved fictional example. Describe a fictional room and shelf structure, identify the correct parent, and explain why a checked-out file cannot be treated as already moved to the shelf. 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 hierarchy and code are unambiguous; label authority is checked; the learner preserves custody restrictions and verifies the resulting location.
Read the full explanation
The answer should establish the following: The hierarchy and code are unambiguous; label authority is checked; the learner preserves custody restrictions and verifies the resulting location. 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.