Journal
Preparing a hashed export that a reader can actually use
Strip names, keep stable hashed IDs, send the teaching calendar, and say when a module was renamed. That bundle is the difference between a reading and a delay.
Most delays in our Malacca diary are not intellectual. They are files that still contain student names, module codes that changed in week six with no map, or a term that started on a different Monday than the spreadsheet’s first row.
A usable export for a remote education app analytics audit usually holds:
- A hashed identifier that stays the same for a student across the term, without a name, email, or matrix number.
- Lesson or resource opens with a timestamp.
- Video progress as a share of the file, not only a play count.
- Quiz attempts with timestamps and the due time as posted.
- Last-open dates.
- A flag if an account is a parent, a demonstrator, or staff, common in tuition-centre homework apps.
Send the academic calendar in the same message: teaching weeks, public holidays, and any week live classes moved. If a module was renamed, send a two-column list of old code and new code. If two apps served the same cohort, say which lessons lived where.
We return named files unread. That is not fuss. It is how the practice keeps student identities off the desk at Office 7, 58 Test Avenue. A vendor who needs two extra weeks to strip names will shift the briefing; we would rather shift it than invent a reading from a file we should not hold.
If you are unsure whether your export is ready, describe the fields in a first note without attaching the file. We will say what is missing before anyone sends a spreadsheet across the country.