"search" bar that checks for all kinds of IDs, as well as exact maker names and level names #2

Open
opened 2026-07-13 22:48:15 +00:00 by jneen · 1 comment
Owner

Currently, there are four namespaced categories of 9-digit ID:

  • NSO level code
  • NSO maker code
  • OCW level code
  • OCW maker code

We also have a table, nso_course, which maintains a mapping of NSO level code -> imported OCW level code, and nso_user, which maintains a verified mapping (so long as the verified flag is checked) of OCW maker code to NSO maker code.

Since there are no overlaps in these ID spaces, we should at the very least have a "generic" ID lookup, which can take any form of 9-digit ID and return the proper OCW record attached to it, whichever type it is.

Currently, there are four namespaced categories of 9-digit ID: * NSO level code * NSO maker code * OCW level code * OCW maker code We also have a table, `nso_course`, which maintains a mapping of NSO level code -> imported OCW level code, and `nso_user`, which maintains a verified mapping (so long as the `verified` flag is checked) of OCW maker code to NSO maker code. Since there are no overlaps in these ID spaces, we should at the very least have a "generic" ID lookup, which can take any form of 9-digit ID and return the proper OCW record attached to it, whichever type it is.
Author
Owner

The ORM seems to have a config for nso_user but not nso_course. Its columns are id, pid, and nso_id, all uint64s, where "pid" is an index into course_info.

The ORM seems to have a config for `nso_user` but not `nso_course`. Its columns are `id`, `pid`, and `nso_id`, all uint64s, where "pid" is an index into course_info.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ocw/ocw-server#2
No description provided.