Gloss Verifier opens a student's .gloss file — every highlight and note they made on an assigned reading — and lets you review it: check it wasn't tampered with, and read the notes against the actual pages. Everything happens in your browser; nothing is uploaded, including to Veriprose.
The whole workflow in four sentences:
.gloss files students submitted, from D2L or Google Classroom.Open Gloss Verifier and drop a .gloss file onto the upload card, or click it to choose a file. If a learning platform ever mangles the file's extension or contents, a "Paste JSON instead" fallback under the drop zone accepts the raw file contents pasted directly — the file is plain JSON underneath.
Nothing leaves your browser. The file is read and reviewed locally. Loading a submission or your copy of a reading never sends anything to a server, including to Veriprose's own.
The first card reports whether the file matches its signature, same as the essay tool: Signature valid means the file matches its signature. It does not prove the file was never edited, or who wrote it — the signing key is readable in the student page's own source, so anyone who reads it can re-sign an edited file. Cannot verify almost always means the file came from a different build of Veriprose, not a student's doing. Treat either non-valid state as a reason to ask for a fresh export, not an accusation.
Below the verdicts, a dashboard summarizes the same aggregate activity gloss.html shows the student as they work: active focus time, how many separate sittings it was written across, characters typed versus pasted, and a typing-cadence histogram (burst / fast / fluid / paused). None of it is content — never what was typed or pasted, only counts and timings.
The Notes panel carries the student's name at the top, and it stays put as you scroll the notes, so a long submission never leaves you wondering whose work you are reading. Beside the name is the number of notes, and when the notes cover more than one reading, each reading gets its own line and count underneath.
The Notes panel lists every highlight with its note, searchable and filterable by color or tag, the same controls students have on their own page. If the reading was a PDF, a "Load your copy…" button appears next to each source — pick your own copy of that PDF from disk and the student's highlights render positioned on the actual pages, rather than as quoted text alone. The .gloss file itself never carries the PDF's bytes, by design; this is how you see it in context anyway.
A student who keeps working in the same Gloss session all term hands in last assignment's reading alongside this one. Once you load your copy of this assignment's reading, the signals and the activity figures count only the notes on the reading your copy matches, and a line above them says how many notes on other readings were left out. The other reading is marked not matched to a copy you loaded, and its notes are still listed in full. Until you load a copy, everything in the file is counted, and nothing is marked. Carrying earlier notes along is a habit, not a signal.
Click "Batch…" and select every .gloss file for the assignment — or drag them all onto the Submission box, or click that box and select them all there. Select the files, not the folder holding them: a folder is not something a browser can read, and dropping one will tell you so rather than loading anything. Any of the three gets you the same worklist; dropping or choosing a single file still opens that one submission on its own. You get one row per student: whether you have opened it yet, Signature, and the signals you have chosen to see.
Choose your columns. Under Columns above the table, switch on any of the signals from section 2 — words per note, active focus time, quoted vs note words, notes with a question, typed vs pasted, sources. The table starts with words per note and active focus time because those tend to differ most across a class, while Sources is often the same value in every row and tells you least at a glance. Whatever you pick is remembered on this computer for next time.
A tick marks what you have opened, and the count above the table reads "12 of 29 opened". It records where you are in your own pass through the class — it is not a score, and it is not saved: reload the page and you start the pass again. Once you have opened a submission from the table, the page asks before a reload or a closed tab would discard that, and before a new batch would replace the worklist — so adding one late submission does not cost you the other twenty. Cancel keeps everything as it was.
It's a worklist, not a ranking. It opens in the order you selected the files in, and you can reorder it by student, signature, export time, or what you have already opened — click one of those headings. You cannot sort by a signal, deliberately: the table exists so that nothing gets missed, not so a class can be put in order of apparent quality. Click any row to open that submission in full below, with everything in section 2 available for it. From the keyboard, Tab to a row and press Enter or Space; Worklist brings you back to the row you were reading.
Load your copy of the reading once. When you open your own copy of an assigned PDF (section 2), it stays open as you step through the rest of the class — you do not load it again per student. Each submission is still checked against it on its own terms: whether that student's passages are found in your copy, and whether they annotated the same file you have, are worked out fresh every time. A source shown from a copy you loaded earlier is marked your kept copy. Loading it also narrows every row's signals to that reading, as described in section 2; a Notes cell then reads like 40 + 25 other. Your copy is held only while this tab is open and is never uploaded or saved anywhere.
Loading a copy also fills in "Passages not found" for the whole worklist. Until you open a copy there is nothing to check highlights against, so that column reads "not computed" rather than zero — the two mean different things. Once a copy is loaded, every row is checked against it at once, and a number above zero means some of that student's highlighted passages were not found in your file. That is a prompt to open the submission and ask, never a verdict: where a row also says against a copy that differs from theirs, the student annotated a different file from the one you loaded, and passages will be missing for that reason alone.
Once a submission is open, a bar above it carries Previous and Next — step straight to the student before or after this one without scrolling back to the table, with the position ("7 of 30") so you can see how far through the class you are. Worklist takes you back to the table, where the row you are reading stays marked. Unreadable files are stepped over. Alt plus the left or right arrow key does the same as the buttons.
There is a second Prev and Next beside the Notes heading, and if you read the notes first it is the one to use: stepping from there keeps you at the notes instead of returning you to the top of the report, so you can go through a class without scrolling up and down between students. Both steppers move together and always agree about where you are. Alt and the arrow keys follow whichever part of the page you are reading.
One bad file costs one row. If a submission is unreadable or malformed, that row shows an error and every other row still renders — a single corrupted file can't take down the worklist for the rest of the class.
Students submit their .gloss file the way any file attachment works on your platform:
.zip if your dropbox offers it. Unzip into a folder named for the assignment before loading them into Batch..gloss files, and download — Drive hands you a .zip for a multi-file selection.Either way, download the files themselves rather than opening them from within Drive or D2L's own viewer — Gloss Verifier needs the actual file, not a preview of it.
No. Students often keep annotating in the same session, so last assignment's reading comes along with this one. Load your copy of this assignment's reading and the signals count only that reading; the earlier one is marked not matched to a copy you loaded and its notes stay readable (section 2).
The .gloss file never carries the PDF's bytes — only the text and the resolved positions. Use "Load your copy…" next to that source and pick the same PDF from your own files to see the highlights rendered on the real pages.
No submission content is. The page does load fonts from the internet and counts page visits for ordinary site measurement — no .gloss content involved. See the privacy statement for details.
Same posture, different material: instead of a written draft's edit history, you're reviewing a set of highlights and notes on an assigned reading, read against your own copy of it rather than replayed as a writing session. The "signals, not scores" rule holds in both.