Custodia Registry · R08
Metadata import
40 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
Import results match approved rows without bypassing record locks or clearance.
Read the full explanation
Our audience is director, admin or custom import officer. Before the demonstration, confirm these prerequisites: C01, C02; fictional training record and approved account. The action-level access conditions are: record_import; duplicate updates also require normal edit/access authority. Check the actual account and record state. The goal is not simply to find a button: Import results match approved rows without bypassing record locks or clearance.
Supported input
- Download the supported template and prepare fictional metadata.
What to check
Use the supplied template and fictional metadata. Check identifier, column meaning and date values before upload. Import permission is a specific assignment and is not included in the default records-manager preset.
Read the full explanation
Download the supported template and prepare fictional metadata. Use the supplied template and fictional metadata. Check identifier, column meaning and date values before upload. Import permission is a specific assignment and is not included in the default records-manager preset. 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.
Mapping and preview
- Upload and map columns, then inspect preview errors and duplicate choices.
What to check
Map each column to its intended field and inspect preview errors. A successful file upload is only the beginning. Preview allows you to find invalid rows and review duplicate handling before committing.
Read the full explanation
Upload and map columns, then inspect preview errors and duplicate choices. Map each column to its intended field and inspect preview errors. A successful file upload is only the beginning. Preview allows you to find invalid rows and review duplicate handling before committing. 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.
Duplicate targets
- Verify each duplicate target is visible and editable; do not provision around denied records.
What to check
A duplicate update still needs normal visibility, edit authority and state checks. Inaccessible duplicates must not be used to reveal protected titles. Do not change grants just to get a batch through.
Read the full explanation
Verify each duplicate target is visible and editable; do not provision around denied records. A duplicate update still needs normal visibility, edit authority and state checks. Inaccessible duplicates must not be used to reveal protected titles. Do not change grants just to get a batch through. 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.
Cancel and correct
- Cancel a faulty batch, correct it, preview again and confirm only the intended valid rows.
What to check
Cancel the faulty practice batch and repair the source data. Preview again before confirming intended valid rows. Keep the preview decision distinct from the actual commit.
Read the full explanation
Cancel a faulty batch, correct it, preview again and confirm only the intended valid rows. Cancel the faulty practice batch and repair the source data. Preview again before confirming intended valid rows. Keep the preview decision distinct from the actual commit. 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 imported rows
- Reopen one created and one updated record and inspect history.
What to check
Reopen a created record and an updated record. Compare the saved fields with the approved input and inspect history. Counts are useful, but they do not replace checking the individual results.
Read the full explanation
Reopen one created and one updated record and inspect history. Reopen a created record and an updated record. Compare the saved fields with the approved input and inspect history. Counts are useful, but they do not replace checking the individual results. 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
Import is not granted to the default records_manager preset. Preview is not commit; inaccessible duplicates must not disclose titles. Do not run imports against production during training.
Read the full explanation
Consider the exception before deciding to retry. Import is not granted to the default records_manager preset. Preview is not commit; inaccessible duplicates must not disclose titles. Do not run imports against production during training. 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
Review a fictional import containing a valid new row, an editable duplicate and an invalid date. Explain the correction and verification sequence without importing into production.
Read the full explanation
Now use the approved fictional example. Review a fictional import containing a valid new row, an editable duplicate and an invalid date. Explain the correction and verification sequence without importing into production. 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 separates preview from commit, rejects or corrects the invalid row, respects duplicate access checks and verifies both create and update results.
Read the full explanation
The answer should establish the following: The learner separates preview from commit, rejects or corrects the invalid row, respects duplicate access checks and verifies both create and update results. 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.