Digital information · Lesson 37 · Approx. 7 minutes including practice
Field mapping and transformation
A mapping states how each source field becomes a target field, including types, units, defaults and required values. Document transformations and obtain owner approval. Preserve source identifiers so exceptions can be traced back.
Step 1: Source field
A documentation workflow, not an equipment operating sequence. Animation starts only when you choose Play.
Make transformations explicit and testable
A mapping is a controlled specification of how source data becomes target data. For each field, record source, target, data type, allowed values, transformation rule, default behaviour and validation. Preserve source identifiers so rejected or changed records can be traced back. Do not use a convenient default to conceal a missing business decision. Distinguish a formatting transformation from a change to the meaning of the data.
Prepare and check the work
Test rules with normal records, blanks, unusual characters, boundary values and known exceptions. Check unit conversions and code translations against approved definitions. Document whether a transformation is reversible and how the source is retained. Have the relevant data owner approve the rule before applying it broadly. Keep the mapping version linked to each test import so a reconciliation can be reproduced.
Worked example · demonstration only
A source status A means active in one table and awaiting approval in another. A universal A-to-active replacement would corrupt meaning. Map the status in its entity context and obtain owner approval for each translation.
Guided practice and review evidence
Use only a demonstration dataset for this exercise: Map five fictional item fields and document one unit conversion rule. Before starting, write down the question the finished record should answer and identify the source information you would need on a real job. Keep a separate list of missing inputs. Prepare a first draft, then compare it with the topic-specific checks above. Ask another person to follow your references without explaining them verbally. Record where they hesitate, what information they cannot locate and any different interpretation. Keep a brief review log with four columns: observation, proposed action, responsible reviewer and closure evidence. Revise the example and repeat the information-finding check. Your evidence of completion is the revised demonstration record plus that log, not simply time spent reading. Do not upload client information to the academy or practise on operating equipment.
What good completion looks like
A useful result can be understood by someone who did not prepare it. They can identify its purpose, applicable item, source and review status, and they can distinguish confirmed information from unresolved questions. Pay particular attention to this failure mode: A blank value and a zero may have different business meanings. Check the output in the format the recipient will use. A native file, spreadsheet and exported PDF can expose different problems. Keep the source revision and the issued output linked, and record any limitations of the handover. On a real project, follow the customer's authorised checking and approval arrangements before the information is used. The knowledge check below tests understanding of this lesson; it does not assess practical competence or authorise regulated work.
Practical workflow
- Establish the source: identify the approved input, document revision and person responsible for its technical content. Record missing information as an open question.
- Prepare a small representative example before applying the approach to a whole project. Check identifiers, units, references and the intended reader’s needs.
- Ask the nominated reviewer to check technical meaning. Capture the response, resolve comments and issue only under the agreed document-control process.
Review checklist
- Can another reader identify the source and applicable revision?
- Are assumptions and unresolved decisions clearly recorded?
- Is there evidence of the required review before issue?
Educational material and demonstration examples. Not accredited training, practical competency assessment or authority to perform regulated work. Use current approved sources and your responsible technical authority on real projects.