INST0089 Chap.6 Encoding Project and Critical Reflection
Encoding Project and Critical Reflection
Encoding Project and Critical Reflection turns the module concepts into an evidence-driven design project. Assessment 1 asks students to work with one complete resource collection, choose one metadata standard and encode the same resource in two formats for two scenarios. The standard carries meaning; the formats carry representations.
Resource analysis defines the unit, boundary, core facts, relationships and sensitivities. Audience analysis identifies users, tasks and constraints. These findings justify the standard, field selection, value rules and format choices. CSV, XML or JSON should be evaluated through observed effects on flattening, hierarchy, machine readability, interoperability, maintenance, validation and ethical description.
The published rubric gives equal weight within Part 1 to resource and scenario design, conceptual understanding, technical encoding and validation, critical evaluation and reflection, and academic writing with sources. Strong work connects every judgement to evidence and acknowledges a specific limitation before proposing the next FAIR improvement.
What this chapter covers
- 01
Resource boundary and complete resource collection
- 02
Audience tasks and scenario constraints
- 03
One standard across two formats
- 04
CSV, XML and JSON trade-offs
- 05
Validation evidence and documentation
- 06
Critical evaluation and FAIR improvement
Worked example · free
Compare CSV and XML for archive interviews
- 2Define interview, transcript and collection boundaries and identify access sensitivities.
- 2Design internal review and public discovery scenarios with concrete user tasks.
- 2Choose one metadata element set and document repeated subjects and typed relations.
- 2Use CSV for internal scanning and XML for hierarchical exchange, then validate both.
- 2Evaluate flattening, maintenance and interoperability with evidence from the files.
Key terms
- Resource analysis
- Study of a resource's boundary, characteristics, relationships and descriptive evidence.
- Audience analysis
- Study of users, tasks and constraints that shape an information design.
- Scenario
- A specific combination of users, purposes, tasks and operational constraints.
- Critical reflection
- Evidence-based evaluation of decisions, consequences, limitations and possible improvements.
Encoding Project and Critical Reflection FAQ
Why must the resource collection be analysed first?
The resource boundary determines which entities, facts and relationships the metadata must represent. If encoding starts before that analysis, fields may mix levels, omit important relations or carry values copied from the wrong source. A clear boundary also makes the later format comparison fair because both representations describe the same thing.
How should two scenarios differ?
The scenarios should have distinct users, tasks or constraints that lead to meaningful design consequences. An internal team checking completeness and a public service supporting discovery may share metadata meanings but need different interfaces, structures and access controls. Cosmetic changes in audience labels do not create a defensible comparison.
What should the evaluation paragraph contain?
Begin with a scenario requirement, name the implementation choice, present evidence from validation or use testing and explain the consequence. Then acknowledge a limitation and propose a proportionate improvement. This chain turns a generic feature statement into a critical judgement grounded in the submitted resource and files.
Assessment move
Treat the assessment as a traceable project rather than a report written after coding. Begin with a resource inventory. Define the unit of description, list every item in the selected set, identify relationships and record sensitivities or contested labels. Design two scenarios by naming the primary users, their tasks, the information they need and the constraints affecting access, maintenance or technology.
Choose one metadata standard only after that analysis and write a compact data dictionary covering field meanings, value rules, cardinality and sources. Keep this model stable across the two formats. Build representative sample records first, including repeated values, missing values and relationships. Validate early so structural decisions can still change.
For CSV, test delimiters, UTF-8, headers and any flattening convention. For XML, test well-formedness, the declared schema and a transformation or query. For JSON, test syntax and document whether schema validation is used. Maintain an evidence log containing each design choice, test result, observed benefit, limitation and next action. Draft the report from that log.
Use the rubric to audit coverage: resource and scenario design, conceptual distinction between standard and format, technical quality and validation, critical reflection, and academic writing with integrated sources. Revise every broad claim such as flexible, simple or interoperable by naming the field or operation it concerns.
End with a FAIR improvement that identifies the beneficiary, required change, evidence needed and new cost or risk. The strongest reflection shows what the project learned from its limitations rather than pretending that one format solved every problem. Schedule a reconciliation pass after the files are final.
Search the report for every field name, format claim and validation statement, then compare it with the packaged encodings rather than an earlier draft. Build a five-row rubric evidence map and point to the paragraph, file or test that demonstrates each criterion. Any empty row needs either more evidence or a narrower claim.
Finally, rehearse a short defence of one limitation and one next step so the evaluation remains specific under time pressure. Keep both statements tied to the submitted files and the named users.