Notes, documents and course material · Open to partnership
Zotero
Many academics keep a course's readings in a Zotero library rather than a folder of files: each entry is citation metadata first (author, title, year), with any PDF attached as a secondary item rather than being the record itself. The route in, if built, would be Zotero's own Web API and a scoped API key: read-only, and limited to the personal or group library a course's reading list actually lives in. None of it is built yet.
Not yet verified
- There is no Zotero connection: no API key registered, and no library, personal or group, chosen.
- Whether Lectora would read only the citation metadata or also follow through to attached PDFs is not decided.
How it connects
The route in would be Zotero's own Web API. An API key is created by the library's owner, not by Lectora, and at creation it is scoped to a personal library, one or more specific group libraries, or both, with read-only or read-write access chosen independently. A course's reading list, brought in this way, would arrive as bibliographic records (author, title, year) rather than files; where a PDF exists it hangs off its record as a child attachment, reachable separately, so what Lectora would read first is the citation, not the document. Nothing of this is registered yet: no API key, no library chosen.
Data and access
Lectora reads only what the assessment needs, and writes nothing back until an educator approves it. The Canvas access page documents the full scope, and our privacy policy, subprocessors and DPA cover the legal side.