Public Site
Families and visitors listen, browse stories, explore the map, search names, play history games, and submit memories.
VisitorsFamiliesCommunity
The whole system
Six areas, one archive.
Hamanteh is organized so each person can stay in their lane: community members explore and submit, field staff capture files, transcribers clean recordings, reviewers publish, and admins keep the system healthy.
Field PWA
Mobile staff create recording packages, add files, capture consent, collect metadata, and hand work to the admin queue.
MobileOffline draftsConsent
Admin Transcript Desk
Transcribers pick a recording, prepare an AI draft, correct the Wolof/Wolish transcript, label voices, and send to review.
WolofWolishQueue
Review and Publish
Reviewers check quality, consent, sensitivity, family records, and whether the story should become public.
QualitySensitivityPublish
Train and Export
Admins export consent-safe confirmed transcript data, review exclusions, and track language and entity quality.
JSONLCorpusAudit
System Control
Admins monitor Google Drive, health, users, feature flags, backups, trash, and audit logs.
DriveBackupsHealth
Daily work
The routine for a busy recording day.
This is the working rhythm for thousands of files. The goal is to move each recording through the correct next step without losing context.
Transcriber checklist
- Open the Admin Desk and choose the next best file.
- Use Sync latest when new Google Drive recordings arrive.
- Confirm the recording plays before editing anything.
- Run or review the AI draft, but do not trust it blindly.
- Name speakers with simple labels if full names are unknown.
- Correct the transcript while using the sticky play controls.
- Mark unclear words, language switches, and sensitive moments.
- Save draft often, then send clean work to review.
Morning: sync Drive and check the queue.
Use Sync latest so Hamanteh imports only new or newly modified Google Drive files since the last watermark. Existing Drive files are skipped, so staff do not repeat work.
Work in short batches.
Select one file for careful editing or assign many simple files to staff. Batch actions help volume, but the active transcript stays the main focus.
Finish the file before switching.
The fastest workflow is listening, typing, speaker labeling, metadata cleanup, and handoff in one focused place.
End of day: review exceptions.
Check missing consent, unclear language, no audio, duplicate uploads, sensitive content, and files that need a human decision.
Primary staff tool
Admin Transcript Desk.
This is the main place to process recordings. It works like an inbox plus an editor: files on the left, audio and transcript in the middle, details on the right.
Left: Inbox Queue
Find the next recording. Filter by status, search, batch assign, and check Drive ingest.
Next fileBatchDrive
Center: Transcript
Listen and type in the same place. Click timestamps to seek, correct text inline, and mark uncertainty.
PlaybackSpeakersWolish
Right: Details Drawer
Set title, narrator, place, date, language, speakers, consent, sensitivity, AI notes, and handoff status.
MetadataConsentReview
Select a file from the inbox.
Prefer the next best file unless you are working on a specific person, location, or assigned batch.
Prepare with AI.
AI can draft transcript guesses, speaker suggestions, language tags, summaries, and sensitivity notes. Treat all AI output as help, not authority.
Listen and correct.
Use play, pause, skip, speed, loop selection, and timestamps while editing text. The transcript and audio should stay tightly linked.
Name speakers and mark sections.
Use real names when known, or simple labels like Narrator, Elder, Interviewer, and Speaker 2. Colored chips help voices stay clear.
Save or hand off.
Save draft if more work remains. Send to review when transcript, metadata, speakers, consent, and sensitivity notes are ready.
Rules for transcript quality
- Keep mixed Wolof and English naturally in one transcript.
- Do not invent names, dates, or places.
- Use unclear markers when a word cannot be confirmed.
- Flag sensitive stories before sending to review.
- Confirm consent before anything becomes public.
Mobile-first intake
Field PWA.
Field is for staff who receive recordings on phones. It supports packages, uploads, metadata, speaker notes, consent, and handoff.
Create a package.
A package is one bundle of material from one recording session or source. Add a plain working title even if the final title is unknown.
Add audio, photos, and notes.
Upload phone recordings, pictures, consent notes, and source details. Raw audio is uploaded while connected in this version.
Capture the basics.
Record narrator, interviewer, place, date, language, family, consent status, and urgent sensitivity notes.
Hand off to admin review.
When the package has enough information, send it to the admin queue for transcription and review.
After transcription
Review, push back, publish.
Review is where the archive protects people. A file can be ready for transcript work but still not ready for the public site.
Review
Check transcript quality, title, summary, names, dates, places, speaker labels, and language notes.
Push Back
Return the file to staff with a clear note when something is missing or needs correction.
Reject or Hold
Keep files private when consent is missing, the source is unclear, or sensitivity risk is too high.
Publish
Approved files become visible in the public archive, listening pages, map, stories, and family surfaces.
Open the review queue.
Use submissions, pipeline, or file detail screens to see what is waiting.
Check consent first.
No consent means no public release. Add the reason so staff understand what is missing.
Check public presentation.
The published title, description, people, places, and language tags should make sense to families without showing internal notes.
For families and visitors
Public community site.
The public site is the living history side. It should feel warm, clear, and rooted in Banjul and Gambian oral history, not like an internal data system.
Listen to stories.
Visitors open published recordings, read context, and follow related people, places, and themes.
Explore Banjul and family memory.
Map, lineage, archive, and story screens help people move by place, family, topic, and time.
Submit new material.
The submit flow lets community members share memories, files, and contact details for review before publication.
Search and learn.
Find, games, projects, about, privacy, terms, and status pages make the archive easier to understand and trust.
Better tools over time
Training and exports.
Training is not automatic publishing or blind AI approval. It is a consent-safe way to prepare clean archive data for future tools, search, language support, and quality checks.
Corpus Manager
Choose which confirmed transcripts can be included. Exclude private, sensitive, or unconsented sections.
Export JSONL
Create structured data for future analysis or model improvement. Each line keeps source and consent information.
QA Counts
Check language, entity, family, place, and exclusion counts so the team knows what the archive is learning from.
Important rule
AI output should always be described as a draft or suggestion. For Gambian Wolof and Wolish, the human transcript is the trusted version.
When something goes wrong
Support and safety.
These screens are mainly for admins, but staff should know what to ask for when files do not appear, audio fails, or a workflow seems blocked.
Common problems
- No new Drive files: use Sync latest, then check Integrations and Drive ingest status.
- Files still missing: confirm the Drive folder is shared with the Hamanteh service account.
- Audio will not play: check the file detail, original source, and upload status.
- Wrong speaker labels: rename the speaker once in the drawer so transcript chips update.
- Sensitive story: hold it for review and leave a clear note.
Admin control screens
- Health: confirms app and API status.
- Integrations: checks Google Drive and storage.
- Backups: protects the archive.
- Audit log: shows important changes.
- Users: manages staff access when auth is enabled.
Plain terms
Words the system uses.
These are the meanings staff should use when talking about the workflow. Keeping the language consistent prevents confusion.
Package
One bundle of recordings, photos, notes, consent, and metadata from a source or session.
AI Draft
Helpful guesses from AI. A person must listen, correct, and confirm.
Speaker
A person speaking in the recording. Use real names when known, or simple labels when unknown.
Wolish
Mixed Wolof and English in the same conversation or sentence.
Unclear
A word, name, or phrase that the transcriber cannot confidently confirm.
Sensitivity
Anything that may need privacy, family permission, or careful review before public release.
Push Back
Return a file to staff because it needs more work.
Published
Approved and visible to public visitors.
Screen index
Every screen and what it is for.
Use this table when someone asks, "Where do I do that?" The links open the screen inside Hamanteh.
| Screen | Who uses it | Purpose | Link |
|---|---|---|---|
| Home | Visitors | Start point for the living archive. | / |
| Stories | Visitors | Curated narrative entry points into the archive. | /stories |
| Archive | Visitors, reviewers | Browse published records and details. | /archive |
| Listen | Visitors | Open a published audio story and transcript context. | /listen/1 |
| Map | Visitors | Explore stories by place. | /map |
| Lineage | Visitors | Explore family and relationship context. | /lineage |
| Find | Visitors, staff | Search people, places, topics, and files. | /find |
| Games | Visitors | Interactive learning and archive engagement. | /games |
| Projects | Visitors, partners | Explain collection work and community projects. | /projects |
| Submit | Community | Share memories, files, and contact details. | /submit |
| Help and Docs | Everyone | Plain-language guide to the screens and workflows. | /help |
| Field PWA | Field staff | Mobile intake, upload, metadata, consent, handoff. | /field |
| Work Alias | Field staff | Compatibility path into field/pass workflows. | /work |
| Admin Desk | Transcribers, admins | Main inbox and transcript editor. | /admin |
| Pipeline | Reviewers | Track where files are in the process. | /admin/pipeline |
| Submissions | Reviewers | Review public submissions before adding to archive work. | /admin/submissions |
| Files | Admins | Manage individual files, source status, and file details. | /admin/files |
| Families | Admins | Create and update family records. | /admin/families |
| Export | Admins | Produce training/corpus exports and review excluded segments. | /admin/export |
| Analytics | Admins | See collection and usage signals. | /admin/analytics |
| Integrations | Admins | Check Google Drive and external services. | /admin/control/integrations |
| Health | Admins | Confirm app health and API status. | /admin/control/health |
| Backups | Admins | Protect and restore archive data. | /admin/control/backups |
| Users and Audit Log | Admins | Manage access and see important changes. | /admin/control/users |
| Trash | Admins | Recover or permanently handle removed items. | /admin/trash |
Source of truth
Design references used in this guide.
These sheets show the approved visual direction and information architecture that live screens should keep following.
