Raisd LMS — research posture

Student LMS features (Moodle-like)

Raisd does not ship a separate Moodle product. Student LMS capability is the enrolled-student learning surface on the student portal via Portal API — course content, activities, assessment, communication, and progress — with lecturer/staff write-paths elsewhere. Analogy below is for shape only; CAP IDs and Demo/Live status remain authoritative (SDD-11, SDD-05). Materials alone is still not an LMS (BASE-44).

Moodle-like area	Student experience (proposed)	Raisd CAP	Demo today	Live target
Course home / topics	Module hub with weeks/topics, outcomes, and release-aware lists	23, 27	Partial Materials weeks	M3 / M5
Resources (files, pages, media, links)	Study guides, lecture notes, videos, authorised downloads	17, 18	Placeholder / Partial	M3
Assignments	Briefs, deadlines; submit / replace / withdraw files	19, 20	Partial / Demo (metadata)	M3 + file store
Quizzes / online exams	Take quizzes/exams with attempt rules and integrity guidance	24, 29	Placeholder / Not started	M5
Practice / revision	Revision activities and past papers (authorised)	21, 22	Not started	M3
Gradebook / feedback	Published results, marks, and lecturer feedback	13, 28	Demo / Not started	M3
Calendar / attendance	Class timetable and attendance records	11, 12	Demo	M3
Forums / messaging	Student–lecturer and peer communication (moderated)	25	Demo (session)	M5
Live class (BBB-like)	Join approved live online classes	26	Not started	M5 (tool TBC)
Completion / release	Self-paced path, dated release, completion evidence	27	Partial (date lock)	M5
Announcements	Important campus / module announcements	16	Partial	M3
Study plan	Programme study plan and prerequisites	14	Demo	M3
Library / e-resources	Digital library and licensed e-resources	31	Not started	M5
Induction / site orientation	Student orientation and digital-learning skills	32	Not started	M3
Feedback / surveys	Course evaluation and learner feedback	30	Placeholder	M5
Help & accessibility	IT helpdesk, learner support, accessibility adjustments	33, 35	Partial / Demo	M3 / M2

Moodle ≠ Raisd product. We use Moodle only as a familiar feature vocabulary. Raisd keeps four portals + Portal API + existing CMS SoR (ADR-1); learning content and durable submissions need a Live file store (SDD-10 Q5).

LMS capability details

Learning-related capabilities from SDD-11. Frontend / Backend statuses are authoritative there; this page groups the LMS slice by role surface. Demo ≠ Live.

Student learning capabilities

CAP	Capability	Dept	Frontend	Backend	Milestone	Next action / blocker
CAP-11	Class timetable	Faculty	Demo	Needs checking	M3	Map current timetable records and update rules from the old CMS.
CAP-12	Attendance records	Faculty	Demo	Needs checking	M3	Identify the authoritative attendance source and staff correction workflow.
CAP-13	Grades, results and student progress	Registry	Demo	Needs checking	M3	Confirm result approval/publication rules and legacy data fields.
CAP-14	Study plan and prerequisites	Faculty	Demo	Needs checking	M3	Validate programme versions, prerequisites and credit-transfer rules.
CAP-16	Important announcements	Registry	Partial	Needs checking	M3	Confirm audiences, publishing ownership, full announcement viewing and the real feed.
CAP-17	Study guides	Faculty	Not started	Needs checking	M3	Identify required guides and arrange lecturer publishing and student access.
CAP-18	Lecture notes and learning-media access	Faculty	Placeholder	Needs checking	M3	Enable authorised resource viewing/download and supported media delivery.
CAP-19	Assignment briefs	Faculty	Partial	Needs checking	M3	Provide real brief files and release/access rules.
CAP-20	Submit, replace and withdraw assignments	Faculty	Demo	Needs checking	M3	Agree durable secure submission storage and staff receipt/marking handoff.
CAP-21	Revision work and practice activities	Faculty	Not started	Needs checking	M3	Define revision materials and any required practice/feedback activities.
CAP-22	Past examination papers	Faculty	Not started	Needs checking	M3	Identify approved papers and access/release restrictions.
CAP-23	Course information and learning outcomes	Faculty	Partial	Needs checking	M3	Add approved outcomes and complete course information to the contract.
CAP-24	Online quizzes and examinations	Faculty	Placeholder	Needs checking	M5	Define assessment modes, allowed attempts and approval/integrity requirements.
CAP-25	Student–lecturer and student–student communication	Faculty	Demo	Needs checking	M5	Agree persistent communication, moderation and response responsibilities.
CAP-26	Live online classes	Faculty	Not started	Needs checking	M5	Confirm whether and how an approved meeting tool will be integrated.
CAP-27	Self-paced learning and release schedules	Faculty	Partial	Needs checking	M5	Define the self-paced learning journey and release/completion rules.
CAP-28	View marks and lecturer feedback	Faculty	Not started	Needs checking	M3	Confirm staff marking, feedback and publication workflows in the old CMS.
CAP-29	Assessment identity checks and integrity guidance	Faculty	Not started	Needs checking	M3	Confirm required identity and integrity controls for each delivery mode.
CAP-30	Student feedback and course evaluation	Quality Assurance	Placeholder	Needs checking	M5	Approve survey scope, confidentiality and reporting ownership.
CAP-31	Digital library and e-resources	TBC	Not started	Needs checking	M5	Identify licensed resources and library access integration.
CAP-32	Student orientation and digital-learning skills	TBC	Not started	Needs checking	M3	Prepare induction content and required completion evidence.
CAP-33	Learner support and IT helpdesk	TBC	Partial	Needs checking	M3	Confirm support channels, owners, operating hours and escalation process.
CAP-34	Study-centre and regional support	TBC	Not started	Needs checking	M5	Confirm centres, local support arrangements and evidence required.
CAP-35	Accessibility and special-needs support	TBC	Demo	Needs checking	M2	Audit journeys with assistive technology and confirm student support adjustments.

Lecturer learning capabilities

Write-side of student learning — publish, mark, deliver, workspace.

CAP	Capability	Dept	Frontend	Backend	Milestone	Next action / blocker
CAP-11	View teaching timetable and class allocations	Faculty	Not started	Needs checking	M3	Confirm view teaching timetable and whether the old CMS already supports it.
CAP-12	Record and correct class attendance	Faculty	Not started	Needs checking	M3	Confirm record and correct class attendance and whether the old CMS already supports it.
CAP-17	Publish study guides	Faculty	Not started	Needs checking	M3	Confirm publish study guides and whether the old CMS already supports it.
CAP-18	Publish lecture notes and learning media	Faculty	Not started	Needs checking	M3	Confirm publish lecture notes and learning media and whether the old CMS already supports it.
CAP-19	Publish assignment briefs and deadlines	Faculty	Not started	Needs checking	M3	Confirm publish assignment briefs and deadlines and whether the old CMS already supports it.
CAP-20	Receive and review submitted assignments	Faculty	Not started	Needs checking	M3	Confirm receive and review submitted assignments and whether the old CMS already supports it.
CAP-21	Publish revision work and practice activities	Faculty	Not started	Needs checking	M3	Confirm publish revision work and practice activities and whether the old CMS already supports it.
CAP-22	Prepare past papers for authorised publication	Faculty	Not started	Needs checking	M3	Confirm prepare past papers for authorised publication and whether the old CMS already supports it.
CAP-23	Maintain course information and learning outcomes	Faculty	Not started	Needs checking	M3	Confirm maintain course information and learning outcomes and whether the old CMS already supports it.
CAP-24	Prepare and conduct online quizzes and examinations	Faculty	Not started	Needs checking	M5	Confirm prepare and conduct online quizzes and examinations and whether the old CMS already supports it.
CAP-25	Communicate with students and teaching groups	Faculty	Not started	Needs checking	M5	Confirm communicate with students and teaching groups and whether the old CMS already supports it.
CAP-26	Deliver live online classes	Faculty	Not started	Needs checking	M5	Confirm deliver live online classes and whether the old CMS already supports it.
CAP-27	Schedule self-paced learning and content release	Faculty	Not started	Needs checking	M5	Confirm schedule self-paced learning and content release and whether the old CMS already supports it.
CAP-28	Mark assessments and publish lecturer feedback	Faculty	Not started	Needs checking	M3	Confirm mark assessments and publish lecturer feedback and whether the old CMS already supports it.
CAP-29	Check assessment identity and academic integrity	Faculty	Not started	Needs checking	M3	Confirm check assessment identity and academic integrity and whether the old CMS already supports it.
CAP-40	Review class learning analytics	Faculty	Not started	Needs checking	M5	Confirm review class learning analytics and whether the old CMS already supports it.
CAP-43	Submit course materials for quality review	Faculty	Not started	Needs checking	M3	Confirm submit course materials for quality review and whether the old CMS already supports it.
CAP-44	Lecturer workspace and course access	Faculty	Not started	Needs checking	M3	Confirm lecturer workspace and course access and whether the old CMS already supports it.

Staff LMS assurance capabilities

Approvals, QA, copyright, orientation, and workspace — not a full staff CMS rebuild.

CAP	Capability	Dept	Frontend	Backend	Milestone	Next action / blocker
CAP-23	Approve course information and learning outcomes	Faculty	Not started	Needs checking	M3	Confirm approve course information and learning outcomes and the responsible old-CMS workflow.
CAP-30	Review institutional learning analytics and quality reports	Quality Assurance	Not started	Needs checking	M5	Define useful learning/engagement measures and evidence reports.
CAP-32	Publish orientation and digital-learning guidance	TBC	Not started	Needs checking	M3	Confirm publish orientation and digital-learning guidance and the responsible old-CMS workflow.
CAP-40	Review institutional learning analytics and quality reports	Quality Assurance	Not started	Needs checking	M5	Define useful learning/engagement measures and evidence reports.
CAP-42	Record copyright permissions and provider approvals	TBC	Not started	Needs checking	M3	Confirm copyright / provider permissions for learning resources.
CAP-43	Approve course materials for quality	Quality Assurance	Not started	Needs checking	M3	Confirm material approval workflow for LMS readiness evidence.
CAP-44	Staff and administrator workspace and role access	TBC	Not started	Needs checking	M2	Confirm existing-CMS staff access; build new staff screens only for verified gaps.

Full catalogue (all portals): SDD-11 capability catalogue. Student IA by milestone: SDD-05. Lecturer write-side: SDD-06.

Student learning journey (proposed)

Typical Moodle-like path on Raisd student portal — Demo screens may exist; Live requires CMS acknowledgement and durable files where applicable.

flowchart LR
  A[Module hub
CAP-23 / 27] --> B[Resources
CAP-17 / 18]
  B --> C[Assignments
CAP-19 / 20]
  B --> D[Quizzes
CAP-24]
  B --> E[Live class
CAP-26]
  C --> F[Marks & feedback
CAP-13 / 28]
  D --> F
  A --> G[Comms
CAP-25]
  A --> H[Timetable & attendance
CAP-11 / 12]

M3 core Guides, notes, briefs, assignment submit, timetable, attendance, results path.

M5 depth Quizzes/exams, live class, full self-paced completion, persistent comms, library.

Research domains F04–F16, F19–F24 map onto these student surfaces — not universal mandates.

Generated pages (Option 1)

Raisd-only sources. Status on every page: proposed / research-backed, not Live product.

LMS architecture Role surfaces on Portal API · CMS SoR · file store LMS features (F01–F37) Research domain × CAP matrix with Demo / milestone Student Moodle-like map Familiar vocabulary ↔ CAP Demo/Live (this page)

Q37 closed — Option 1. Raisd LMS pages from CAP + F01–F37. Tracked in SDD-10 Q37.

What Raisd already has for LMS

Enough to generate architecture and features pages in the same style as Distributed CMS / Raisd CMS — marked research-backed, not Live.

37 research domains INPUT-F01–F37 mapped to CAPs (LMS_Feature_Requirements_8_Countried.xlsx (also mirrored in student-portal planning JSON). Supplied research, not universal mandates — SDD-09.
Learning CAPs mostly Not started / Placeholder / Partial (guides, materials, assignments, quizzes, live class, lecturer workspace, …) — SDD-11.
Explicit gap: student Materials alone is not an LMS (BASE-44).
Diagrams hub already has the pattern (docs/diagrams/*.html) — this page is the LMS entry; dedicated architecture / features pages are proposed below.

Architecture sketch (proposed)

LMS as role surfaces on Portal API — not a fifth portal product.

flowchart TB
  subgraph Portals["Role surfaces"]
    S[Student portal]
    L[Lecturer portal]
    T[Staff portal]
  end

  API[Portal API]
  ACL["CMS bridge CAP-53"]
  CMS[(Existing CMS · SoR)]
  FS[(File store · Live evidence / live class)]

  S --> API
  L --> API
  T --> API
  API --> ACL
  ACL --> CMS
  API --> FS

Student Consume materials, assignments, quizzes, live join when agreed.

Lecturer Publish, mark, deliver live class, workspace (CAP-44).

Staff Approvals / QA / orientation where CAP-owned.

Live file store Required for durable assignments and Live artefacts — see SDD-10 Q5.