Komodo Hub — Week 5 Community Contributions

Current increment: Week 5, derived from PB-13 in the original backlog. Five members; xiangbangyin is Product Owner and operates the complete recording.

Start: double-click start-demo.cmd, then open http://127.0.0.1:4000.
中文录屏指南（启动、重置、每一段点击什么）
Five English speeches and 04:30 timeline
Week 5 allocation, scope and acceptance
Verification report: 14/14 tests
Approved community page screenshot

New: community/member contribution pages, optional fictional contributor attribution, approved-only publication, input checks and nondestructive migration of existing databases. Demo aliases are not real authentication. Existing Week 1/2 documentation below is historical; Week 3/4 completion is not asserted. This Week 5 snapshot was prepared locally. The institutional migration target is https://github.coventry.ac.uk/xiangb3/Software-Engineering-Komodo_Hub; remote publication must be verified separately.

The launcher uses its own server-data/week5-recording.sqlite. To reset fictional rehearsal data, stop the server and follow the recording guide. Ordinary startup preserves reports.

Historical Week 1/2 README

Komodo Hub Sprint 1 - Week 2 Increment

This repository contains the Week 1 foundation and Week 2 strengthening increment for CUH601CMD Software Engineering, Study Case 01: Komodo Hub. It is a dependency-free Node.js and SQLite demo so it can run in the current lab environment without npm package installation.

Week 2 Increment

Species can be filtered by name, category, and demonstration region.
Species details include connected conservation projects and approved public sightings.
Project details link back to related species.
Report this species opens the sighting form with that species selected.
New sightings remain pending until server-authorised review.
Moderators must enter a reason; decisions create persistent audit history.
Repeated review attempts return a conflict instead of changing the original decision.
The home page shows live demonstration counts from SQLite.
Public endpoints continue to exclude private school/student records.

Requirements

Node.js 22 or later.
sqlite3 CLI on PATH. This environment uses D:\anaconda\Library\bin\sqlite3.exe.
No npm package installation is required.

Local Configuration

Copy .env.example to .env if you want to override defaults. The default local demo token is intentionally simple and must not be used as a real secret.

$env:PORT = "4000"
$env:KOMODO_DB_PATH = "server-data/komodo-hub.sqlite"
$env:KOMODO_ADMIN_TOKEN = "demo-admin-token"

Commands

npm run db:seed
npm test
npm run build
npm start

Open http://127.0.0.1:4000 after npm start.

Demo Flow

Open Species, search for Rhino, and filter the region to Java.
Open Javan Rhinoceros and inspect its connected projects and approved sightings.
Select Report this species; confirm the sighting form is preselected.
Submit fictional data and confirm that the result remains pending and non-public.
Open Admin, enter demo-admin-token, and load the moderation workspace.
Enter a review reason and approve or reject the pending record.
Inspect the persistent review history.
Return to the species detail; an approved record now appears there and in Sightings.

Project Structure

public/ - frontend HTML, CSS, and browser JavaScript.
server/ - Node.js API, validation, SQLite access, and server startup.
scripts/ - database seeding and static frontend build script.
tests/ - Node native automated tests.
docs/week1/ - Week 1 course evidence and role documents.
docs/week2/ - Week 2 role drafts, design evidence, test report, and evidence index.
docs/week2/08_team_task_allocation.md - proposed role rotation and detailed individual tasks.
docs/week2/09_video_demo_script.md - 4-6 minute four-person script and exact screen sequence.
evidence/week2/ - local visual verification screenshots.
server-data/ - generated local SQLite database, ignored by Git.

Evidence Notes

All species, project, sighting, and generated visual records are demo coursework content. The application does not collect real child personal data, precise GPS data, or real field sightings. The private student table exists only to test that public endpoints do not return private school/student records.

Week 2 roles and their effective date remain proposals until the four students confirm them. Individual Week 2 documents therefore use To be confirmed and do not claim unheld meetings or unverified personal contributions.

xiangb3/Software-Engineering-Komodo_Hub

About

Resources

Uh oh!

Stars

Watchers

Forks

Releases

Contributors 1

Languages