> For the complete documentation index, see [llms.txt](https://holland.gitbook.io/eli-review-users-guide-sfsu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://holland.gitbook.io/eli-review-users-guide-sfsu/webinar-weekly-topics.md).

# Fall Semester, 2021—Webinar Weekly Webinar Schedule

### Eli Review Beginner’s Workshop, August 13, at 10–12 AM Pacific <a href="#elireviewbeginnere28099sworkshopaugust13at10-12ampacific" id="elireviewbeginnere28099sworkshopaugust13at10-12ampacific"></a>

* Recording: <https://youtu.be/cS7FSuR17zY>&#x20;
* Slides: [Fall 2021 Slides and Embedded Recording](https://docs.google.com/presentation/d/14K6Af4CXw40nURVJT7jjpg3FzXugkMQs_w2EwZVWuoM/edit?usp=sharing)
* Key Resource: <https://holland.gitbook.io/eli-review-users-guide-sfsu/>

This session will address the big questions of course design:\
\- How does Eli connect to iLearn?\
\- How do you plan for Eli Review work in the course calendar?\
\- How do you grade Eli R eview work?\
\- How do students enroll in Eli?

### Fall Semester, 2021 Eli Review Office 1/2 Hours

#### August-September–What Instructors Can Do to Improve Feedback <a href="#august-september--whatinstructorscandotoimprovefeedback" id="august-september--whatinstructorscandotoimprovefeedback"></a>

Aug 27, Friday, 10 AM ( PST) **Starting Small**\
NOTE: In Roster, “Suspend” students who drop.\
Sept 3,, Friday, 10 AM (PST) **Forming & Managing Groups**\
Sept 10, Friday, 10 AM (PST) **Describe-Evaluate-Suggest As Review Task Design**\
Sept 17, Friday, 10 AM (PST) **Describe-Evaluate-Suggest as Comment Pattern**\
NOTE: In Roster, “Suspend” students who drop before the Withdraw date.\
Sept 24, Friday, 10 AM (PST) **Bellwether Four Writers and Reviewers**

#### October–What Students Can Do to Improve Feedback <a href="#october--whatstudentscandotoimprovefeedback" id="october--whatstudentscandotoimprovefeedback"></a>

Oct 1, Friday, 10 AM (PST) **Praise**\
Oct 8, Friday, 10 AM (PST) **One long comment > many short ones**\
Oct 15, Friday, 10 AM (PST) **Helpfulness Ratings**\
Oct 22, Friday, 10 AM (PST) **Add to Revision Plan & Reflect**\
Oct 29, Friday, 10 AM (PST) **#Hashtags**

#### November-December–What Instructors Can Do to Improve Revision <a href="#november-december--whatinstructorscandotoimproverevision" id="november-december--whatinstructorscandotoimproverevision"></a>

Nov 5, Friday, 10 AM (PST) **Time & Scope**\
Nov 12, Friday, 10 AM (PST) **Coach Revision Decisions**\
Nov 19, Friday 10 AM (PST) **Reward Revision**\
Nov 26, Friday, 10 AM (PST) **NO MEETING: Fall Break**\
Dec 3, Friday, 10 AM (PST) **Blaming and Crediting Eli** (surveys!)

Click [here](https://docs.google.com/presentation/d/14K6Af4CXw40nURVJT7jjpg3FzXugkMQs_w2EwZVWuoM/edit?usp=sharing) to view videos of each session that we have embedded in the slide deck.

Click [here](https://us06web.zoom.us/j/467756901?pwd=U0hINDRzMTFDY2VyVVdIcVRiQTBwZz09) on the Zoom link to join our Weekly Zoom Sessions (Fridays at 10:00 am)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://holland.gitbook.io/eli-review-users-guide-sfsu/webinar-weekly-topics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.