Partially update a catalogue subject
Partially updates a subject, using JSON Merge Patch semantics (RFC 7386):
- a field present with a value is set
- a field present as
nullis CLEARED - a field you omit is left exactly as it was
That last point is the difference from PUT, which replaces: there, omitting a field clears
it. Use PATCH when you’re changing one thing and don’t want to resend description,
learningOutcomes and conditions correctly just to avoid losing them.
An unknown field name is a 400 rather than being ignored. Under merge semantics a typo would otherwise do nothing at all, silently.
externalIds still merges per system, and null is rejected there: omit it to leave existing
ids alone. code and year identify the subject and can’t be patched.
Authentication
Paste a Keycloak access token (no "Bearer " prefix)
Path parameters
Request
Only the fields you want to change. Same field names as the PUT body; send a field as null to clear it.
Credit points (UOC) the subject is worth.
Whether this row is a specific subject or an unspecified credit block (a placeholder used to grant credit without naming a subject).
How advanced the subject is. Free text, but use the same vocabulary as the studyLevel recorded on applicants' subjects (introductory, intermediate, advanced), because credit matching compares the two and a mismatch fails to match silently rather than erroring.
What a student can do on completing the subject. Same purpose as description: display now, similarity matching later.
Your own identifiers for this subject, keyed by system name. Merged per system: a system you omit keeps its existing id. An id already used for a different subject is rejected.
Response
The supplied fields were applied; everything else is unchanged.
created | updated.
