Student Database — Centralised Student Records Platform for Schools and Universities

The two terms overlap substantially in modern usage. "Student database" emphasises the data-storage and data-access layer — the central source-of-truth for per-student records (demographics, enrolment, attendance, grades, fees, parent contacts). "Student information system" (SIS) emphasises the full operational workflow on top of the database (admissions, enrolment, attendance, gradebook, reporting). In practice, modern systems combine both — the underlying database plus the operational workflow on a single platform. Per per-vendor marketing nuance, some vendors emphasise "database" for K-12 markets and "SIS" for higher-ed markets, but the platforms operate similarly across both segments. OpenEduCat provides both the database layer and the operational workflow as integrated modules on the same platform.

Per-jurisdiction student-database requirements vary substantially. US K-12: per-state SEA field requirements per ESSA / IDEA / Title VI; race / ethnicity per OMB Directive 15; ELL status per Title III; IEP / 504 per IDEA; FRPL per per-state policy. US Higher-ed: per-IPEDS field requirements per per-cycle reporting; per-state state-system reporting; per-federal-financial-aid eligibility per Title IV. EU: per-GDPR Article 15-17 data-subject rights; per-Member-State localisation. India: per-UDISE Plus per-school-per-year reporting; per-Aadhaar per-student linkage; per-NCERT per-state. The platform supports per-jurisdiction field-set configuration with per-jurisdiction reporting format and per-jurisdiction data-residency. Per-jurisdiction operational logic varies; the platform handles major jurisdictions as configurable workflows.

Per FERPA §99.32, US institutions must maintain per-access record of per-student education-record disclosure. The platform maintains audit-grade per-access per-user per-record-type audit log: per-user per-timestamp per-record-id per-access-type (view, modify, export, delete) per-access-purpose. Per-access logging is automatic across all platform interactions; per-quarter audit-log review for unusual-access-pattern detection per institutional data-governance policy. Per-FERPA per-disclosure record retention per per-§99.32 requirement (typically per-institution per-policy of 5-7 years). Per-FERPA per-disclosure record available for per-§99.10 student access-of-record-of-disclosure request. Per institutional data-governance policy, per-quarter automated audit-log review identifies unusual-access-pattern (excessive per-user per-day access volume, per-record-type unusual-access, per-after-hours access pattern) for institutional review.

Per GDPR Article 15 (right-of-access), Article 16 (right-of-rectification), Article 17 (right-of-erasure), Article 18 (right-of-restriction), Article 20 (right-of-portability), EU data subjects have specific rights regarding their personal data. The platform handles per-student right-of-access workflow (per-request per-student per-record-set export within GDPR per-month-response-window), per-student right-of-deletion workflow (per-request per-jurisdiction-specific deletion-scope with audit-log preservation per per-institutional retention obligation), per-student right-of-portability workflow (per-request structured-data-export in machine-readable format per GDPR Article 20), and per-student right-of-rectification workflow (per-request per-record per-field amendment with audit log per GDPR Article 16). Per-Member-State per-jurisdiction implementation nuance varies; the platform handles major Member-State variations.

Per-jurisdiction student-data-residency requirements: US institutions under FERPA require US-accessible-by-school-officials hosting; EU institutions under GDPR require EU-hosted hosting per per-Member-State data-residency policy (Schrems II ruling restricts US-vendor data transfer for EU institutions); India under DPDP Act 2023 requires India-hosted hosting for certain data categories; UAE per-Emirate data-law requires per-Emirate hosting; per-country localisation requirements per per-jurisdiction. Self-host deployment keeps per-student data inside per-institutional infrastructure with per-jurisdiction residency choice. Per-jurisdiction data-residency configures per institution; cross-jurisdiction data transfer (for multi-campus international groups) operates on per-jurisdiction transfer-mechanism (per-GDPR Standard Contractual Clauses, per-GDPR Adequacy Decision, per-per-country bilateral arrangement).

Licence cost is zero for OpenEduCat Community Edition (LGPLv3 open-source). Deployment cost varies by scale: 1,000-student K-12 school typically lands at $5K-15K per year (hosting + per-year platform-upgrade + training); 10,000-student K-12 district typically $50K-150K per year; 10,000-FTE university typically $80K-250K per year. Implementation one-time cost ranges from $30K-200K depending on data-migration complexity (legacy-system migration is the primary cost driver). Total 5-year TCO typically lands at 30-50% of commercial SaaS for similar deployment scope. Per-commercial-vendor 5-year TCO comparison: PowerSchool ~$800K-2M for 10,000-student district; Ellucian Banner ~$2M-5M for 10,000-FTE university; OpenEduCat ~$300K-600K for either scale.

Per-family per-sibling relationship-linking supports per-family operational workflow. Per-family record links per-parent account to all per-child accounts in the same family; per-family contact-management consolidates per-family communication preferences; per-family per-sibling-discount application per per-school per-family sibling-discount policy (typical per-school per-family sibling-discount: 5-15% per per-additional sibling per per-AY); per-family per-event communication (per-school-event communication goes to per-family rather than per-child, eliminating duplicate parent notifications); per-family per-payment consolidation (per-family per-term fee statement consolidates across siblings per per-family preference); per-family transfer workflow handles per-family relocation (multiple siblings transferring together).

Per-student transfer-history maintains chronological per-student per-AY transfer-out, transfer-in, per-school transfer record. Per-AY mid-AY transfer workflow handles per-AY enrolment-status-change (per-AY enrolled, per-AY transferred-out, per-AY transferred-in, per-AY graduated, per-AY withdrawn) with per-AY status-effective-date. Per-student incoming-transfer workflow handles per-prior-school transcript import (per-prior-AY per-subject grade, per-prior-AY attendance, per-prior-AY academic-status). Per-student outgoing-transfer workflow handles per-receiving-school transcript export per per-receiving-school format. Per-mid-AY-transfer per-receiving-school articulation-agreement applies per per-receiving-school per-subject credit-recognition.