Currently, the search feature uses Algolia under the hood.

In order to capture new courses, the search index must be updated periodically otherwise new courses will not show up in search while showing up when manually navigating courses.

Each record in the index should be shaped like the following:

{
      "subjectCode": "PAAS342",
      "subject": "PAAS",
      "code": "342",
      "pid": "BJm2a_pXV",
      "description": "For students who wish to expand their working vocabulary and develop their skills in reading modern Japanese. Course content may vary from year to year.",
      "title": "Advanced Readings in Japanese II"
}

https://www.algolia.com/doc/api-client/methods/indexing/

Records can either be added or updated. Each record in the index requires a unique id. If an id is given when creating records in the index it will be used, otherwise it will be given a generated one.

https://www.algolia.com/doc/api-reference/api-methods/save-objects/?client=javascript

The script should take the current courses (hitting the courseup API probably) and transform the values to match the above object shape. Whether to update records or purge the index and create records from scratch will require some work and research on the developer.

Historically, the pid is usually consistent between terms but it's not a guarantee. As such it may make sense to add term to list of attributes indexed, this would allow searching between terms and do things like searching for courses via extended attributes like class_in_session etc.