Does anyone have a clean method to map Montessori work cycle observations to SIS fields without losing context? We use Transparent Classroom for observations and OpenApply for admissions, then batch into PowerSchool every Friday at 3:00 p.m.; I’m looking for sample field maps/naming conventions and a retention schedule that keeps auditors satisfied while preserving the 3–6 and 6–9 progression…
I’d map Transparent Classroom lesson IDs to PowerSchool Standards/Store Codes via a lookup, then sync only metadata (plane 3–6, strand, status, date) plus the TC observation UUID into a PS custom field, keeping the narrative in TC as the “single source of truth” — breadcrumbs back to the loaf. For retention, export a quarterly CSV to cold storage and purge PS comments after 2–3 years while keeping the standards record for 7; does that fit your Friday 3:00 p.m. batch, or do you also need OpenApply fields in the map?