APG5782 Chap.9 Programming and Curation

Programming and Curation

Programming and Curation gives APG5782 students a retrieval path through selection, exclusion, taste, thematic relations, sequence and programme coherence. Current Topic 4 grounds programming history and practice. No source programme, poster, film still, rubric or past student structure is reproduced.

The first decisions concern programming as criticism, programming and curation, taste and exclusion, theme as a proposition; the later decisions extend the map through build a coherent slate, sequence and rhythm, programme notes and framing, programming for a specified audience, defend a curatorial decision.

Programming as criticism: Explain why a selection is an argument about value rather than a neutral sample of available work. The original Signal/Noise question is whether to treat selection of an invented short as criticism and state the value being declared. Programming as criticism therefore operates here as a mechanism to explain, not a label to attach after the decision.

Programming and curation: Use the distinction as a difference of emphasis between selection/planning and relational care, not a rigid occupational wall. The original Signal/Noise question is whether to separate the act of choosing works from caring for the relations built around them. Programming and curation therefore operates here as a mechanism to explain, not a label to attach after the decision.

Taste and exclusion: Make aesthetic and political criteria discussable while naming what the programme leaves outside. The original Signal/Noise question is whether to record what a taste criterion excludes as well as what it recognises. Taste and exclusion therefore operates here as a mechanism to explain, not a label to attach after the decision.

Theme as a proposition: Turn a broad topic into a claim that can discriminate among possible works and frames. The original Signal/Noise question is whether to turn listening under technological pressure into an arguable curatorial proposition. Theme as a proposition therefore operates here as a mechanism to explain, not a label to attach after the decision.

Build a coherent slate: Balance relation, contrast and surprise so each work remains distinct while contributing to the programme argument. The original Signal/Noise question is whether to combine three invented shorts through contrast instead of topical sameness. Build a coherent slate therefore operates here as a mechanism to explain, not a label to attach after the decision.

Sequence and rhythm: Consider duration, intensity, transition and discussion when arranging an experience across time. The original Signal/Noise question is whether to sequence an intense fictional work away from another when discussion needs recovery time. Sequence and rhythm therefore operates here as a mechanism to explain, not a label to attach after the decision.

Programme notes and framing: Write context that opens inquiry without dictating a single interpretation or making unsupported claims. The original Signal/Noise question is whether to write an original note that offers context without fixing one interpretation. Programme notes and framing therefore operates here as a mechanism to explain, not a label to attach after the decision.

Programming for a specified audience: Use audience knowledge to design access and invitation without reducing curation to presumed popularity. The original Signal/Noise question is whether to design entry points for a specified novice audience without choosing only familiar work. Programming for a specified audience therefore operates here as a mechanism to explain, not a label to attach after the decision.

Defend a curatorial decision: Connect mission, work, audience and operational feasibility in a concise, evidence-led rationale. The original Signal/Noise question is whether to defend removal of an attractive work that weakens programme coherence. Defend a curatorial decision therefore operates here as a mechanism to explain, not a label to attach after the decision.

Use these ideas as analytical moves, not as phrases to paste into assessed work. For programming and curation, begin by naming the festival relation or organising decision, identify the institution or participant position that produces evidence, preserve a credible counter-reading and state a conclusion no broader than the represented source.

A programme or promotional artefact can show designed framing, but it cannot by itself prove audience reception. A field note can establish a situated observation, but it cannot represent every participant. A group decision log can show that a choice was made, but it cannot establish current rights, prices or venue capability. The original Signal/Noise cases in Programming and Curation are fictional rehearsal environments.

They contain invented festival decisions, film descriptions, roles, planning records and visuals. They do not supply a real programme, screening permission, ticket price, rights fee, attendance result, supplier quote or current platform condition. If a practice case suggests a real implementation question, convert that suggestion into a verification item for an authorised current source.

Assessment transfer must remain task-specific. For the Attendance Report, students should work from their own festival visit, personal observations and critical reflection, using GenAI only for grammar and spelling under the captured current instruction.

For the Curatorial Portfolio, the captured instruction permits GenAI use in any way if appropriately acknowledged; the group must still verify sources, rights and facts and follow the live acknowledgement rule. Portfolio permission does not transfer to the Attendance Report. A useful programming and curation conclusion joins mechanism, evidence and consequence.

Mechanism explains how a choice or institution produces a relation. Evidence records a perspective, time and purpose. Consequence shows what changes for programme, access, authority, circulation or participation. The counter-reading tests whether another mechanism explains the same trace. The verification line then tells the reader what remains unresolved.

That sequence supports original analysis without reconstructing a Monash rubric, sample answer or past student structure.

What this chapter covers

• 01

  Programming as criticism

• 02

  Programming and curation

• 03

  Taste and exclusion

• 04

  Theme as a proposition

• 05

  Build a coherent slate

• 06

  Sequence and rhythm

• 07

  Programme notes and framing

• 08

  Programming for a specified audience

• 09

  Defend a curatorial decision

AskSia-authored practice weighting (not official): original Signal/Noise decision model

Key terms

Programming as criticism

In Programming and Curation, this term directs attention to the relation described here: Explain why a selection is an argument about value rather than a neutral sample of available work. The original Signal/Noise question is whether to treat selection of an invented short as criticism and state the value being declared. Programming as criticism therefore operates here as a mechanism to explain, not a label to attach after the decision.

Programming and curation

In Programming and Curation, this term directs attention to the relation described here: Use the distinction as a difference of emphasis between selection/planning and relational care, not a rigid occupational wall. The original Signal/Noise question is whether to separate the act of choosing works from caring for the relations built around them. Programming and curation therefore operates here as a mechanism to explain, not a label to attach after the decision.

Taste and exclusion

In Programming and Curation, this term directs attention to the relation described here: Make aesthetic and political criteria discussable while naming what the programme leaves outside. The original Signal/Noise question is whether to record what a taste criterion excludes as well as what it recognises. Taste and exclusion therefore operates here as a mechanism to explain, not a label to attach after the decision.

Theme as a proposition

In Programming and Curation, this term directs attention to the relation described here: Turn a broad topic into a claim that can discriminate among possible works and frames. The original Signal/Noise question is whether to turn listening under technological pressure into an arguable curatorial proposition. Theme as a proposition therefore operates here as a mechanism to explain, not a label to attach after the decision.

Build a coherent slate

In Programming and Curation, this term directs attention to the relation described here: Balance relation, contrast and surprise so each work remains distinct while contributing to the programme argument. The original Signal/Noise question is whether to combine three invented shorts through contrast instead of topical sameness. Build a coherent slate therefore operates here as a mechanism to explain, not a label to attach after the decision.

Programming and Curation FAQ

Assessment move

Start programming and curation revision by writing the page titles as a left-hand index: Programming as criticism; Programming and curation; Taste and exclusion; Theme as a proposition; Build a coherent slate; Sequence and rhythm; Programme notes and framing; Programming for a specified audience; Defend a curatorial decision.

Beside each programming and curation title, add one mechanism sentence, one evidence noun, one counter-reading and one current verification need. Practise first with a fresh fictional decision so the method becomes visible without reproducing live work. Then rebuild the record from your own festival observation or genuine group evidence.

For an Attendance Report paragraph, move from field note to context, concept, alternative and qualified evaluation. For a portfolio section, move from mission to decision, owner, dependency, evidence and cross-section consequence.

Review every transition: programme affects rights and technical delivery; access affects audience and communication; finance affects scale and contingency; feedback affects the final report and reflection. Finally check authorship, sources, rights, acknowledgement, file access and submission receipt against current Moodle. This independent guide cannot settle a live instruction conflict, hurdle rule or updated condition.

Working through Programming and Curation in APG5782? Sia is AskSia’s AI Arts and Humanities tutor — ask any APG5782 Programming and Curation question and get a clear, step-by-step explanation grounded in how APG5782 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.