Today
Closing soon
Published deadlines about to pass — the records where being wrong costs a student the most, and the last moment a mistake is still fixable. Each row says whether it needs you: a date carried forward from last cycle needs confirming, and one no person has agreed with is worth opening the site for. Check now re-fetches that source immediately.
Broken and dateless sources
A source that fetches fine but yields no date is almost always aimed at a homepage. Open it and point it at the page carrying the dates — or, if no scraper could ever read it, set it aside and it stops coming back.
Hand-entered, due a check 0
Nothing re-fetches these sources, so nothing else will ever question these dates. Open the site, confirm or correct them, and enter them again to renew the promise.
No longer on the page 0
Published records the source's last real read did not produce. A listing that still reads as a listing retires these by itself; these are the ones it will not judge, because a page that momentarily yields less looks exactly like a page that dropped something. Retiring one tells EdPathway to withdraw it.
Set aside 0
Sources a person has ruled out as unautomatable. They are not fetched and not counted above. Here so the decision can be re-read, and undone when a site is rebuilt.
Held for review
Each date shows the line of page text it was read from, so you can check it without opening the site. j k move · a approve · r reject · x select
What EdPathway has
Every activity here is in the Catalog; this is the same list seen by how far it has got. Pausing holds one back from EdPathway without going blind on it — it keeps being fetched and keeps being corrected, and everything it learns meanwhile goes out when you lift the pause.
Ready to go
The outbox 0
The announcements themselves, for when something has not arrived and you need to see why. One activity makes several of these over its life.
Held back 0
Announcements for records nobody has approved. They are on the feed so the history is complete, and they are not delivered — approving one in Review is what releases it.
Sources
Look at a site
Everything here is from outside the system, on its way in. Paste a URL and this reads the page and the pages it links to, then says what the pipeline would actually get from each — how many date-bearing lines, whether a deadline can be read, whether the site publishes machine-readable events. Nothing is saved until you say so.
Track a new page
Point this at the page that actually carries the dates — a registration or "important dates" page, not the site's homepage. Homepages rarely state a deadline, and you will get a low-confidence record instead.
Invite somebody
They sign in with a code sent to this address — there is no password to choose or to lose. A reviewer decides about records and adds sources. An administrator can also change the engine, invite people, and send records to EdPathway.
People
| Role | Status | Invited by | Last seen |
|---|
What people have done
Every change somebody made, newest first. The Engine page shows what the machine is doing; this shows who decided what, which no amount of run logs can answer.
| When | Who | Did | To | Detail |
|---|
Worker
—
Running now
Nothing running.
What has run
Every pass, however it started. Open one to see what each source in it did.
What runs next
The order the schedule will get to these in, and why each one is checked as often as it is. "Overdue" is a statement about the worker, not about the source.