Atlas project production

Aeries Photo Release Sync

Updates the Aeries photo-release field from current media-release authorization records so downstream permissions stay aligned.

Internal-only entry. Do not publish externally without review.
Type
System
Lifecycle
Active
Last touched
2026-03-24
Visibility
Internal

Purpose

Maintain the Aeries photo-release field from the most recent active media-release authorization record.

Current state

Active SQL-driven maintenance exists in production config, but downstream consumer inventory is still incomplete.

Next step

Document the exact scheduler, reconciliation steps, and all systems that depend on `STU.U11`.

Interfaces

Inputs
  • Aeries authorization records
  • student tables
Outputs
  • updated `STU.U11` photo-release values

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Not in scope.

Automation Engines

Contributes in this stage.

Human Interfaces

Not in scope.

Operational Adoption

Contributes in this stage.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Data integrity and contracts

Source of truth rules

  • Aeries authorization records are canonical for media-release state.
  • The maintained student field should mirror the latest valid authorization.

Safe handling

  • Restrict SQL write access and authorization-table visibility.
  • Treat permissions data and logs as sensitive.

Operational notes

Reliability posture

Write-back path is clear, but downstream consumer inventory and approval expectations still need documentation.

Observability

  • Integr8r logs
  • SQL execution output

Security and privacy

Restricted student permissions data; internal only.

Dependencies

Upstream
  • current media-release authorizations
  • Aeries schema stability
  • Integr8r runtime
Downstream
  • downstream photo-release consumers

Ownership

Owners

Technology Services

Users

Technology Services, student-data stakeholders

Aeries Photo Release Sync

Operational Notes

  • The registry resolves this as an internal authorization-to-student-field write-back job.
  • Integr8r directly executes the SQL that maintains STU.U11 from current AUT.CD = MR records.
  • Failure can leave photo-release status inaccurate for downstream communications or media-use workflows.

Registry Alignment

  • Mapped registry entry: INT-039
  • Registry clarified: the workflow is a concrete SQL write-back inside Aeries, not just an inventory label.
  • Validation gaps: Identify all downstream consumers of the maintained photo-release field and document run governance.