# Resource Review Rubric

### Start your review

1. [Login to ITC](https://idahotc.com/login)
2. Open the [My Resources page](https://idahotc.com/Resources/My-Resources) (Hover over the resources menu and select my resources)
3. Sort your resources by review date with the oldest review date coming first.
4. Select the edit button on your top resource (resource will open in a new tab)
5. Follow the steps in the rest of this document to complete your review.
6. Once the review is complete, close the tab to return to the My Resources page.
7. Select the Edit button on the next non-reviewed resource.
8. Repeat steps 6 through 8 until you have reviewed all resources. 
   1. You can refresh the page to reset your list such that the oldest review is again at the top at any point. *If refreshing the page restart this process from step 5.*

### Details Tab

<mark style="background-color:blue;">**Check the following in your details tab:**</mark>

* **Publish** status is appropriate.
* **Title** is appropriate.
* **Description** is appropriate.
* **Keywords** are appropriate.
  * When setting keywords, consider what someone might type in to find your content. Also consider if adding a keyword will make it harder to find another resource.
* **Collection, Provider** and **Type** are appropriate.
* All three owner spaces are appropriate.
  * owner 1 is the lead, owner 2 is the assist, owner 3 is second assist.

{% hint style="info" %}
**Note** – “appropriate” may mean the field is blank for some scenarios.

**Example 1** – a resource is standalone and not part of a collection therefore it is appropriate for the collection field to be blank

**Example 2** – a resource has an owner1 (lead) and an owner 2 (assist). The project doesn’t require further owners therefore the owner 3 field is appropriately left blank.
{% endhint %}

{% hint style="warning" %}
If changes have been made **select the update details button** before moving on to the files tab. If no changes are made, continue with your review in the files tab.
{% endhint %}

### Files Tab

<mark style="background-color:blue;">**Check the following in the files tab:**</mark>

* **Content is up to date and links are live**
  * <mark style="background-color:red;">**Flag the resource and email leadership**</mark> if content is out of date or there are dead links
* **Links lead to accessible content**
  * <mark style="background-color:yellow;">**Email ITC**</mark> if you have questions about the accessibility of linked content. <mark style="background-color:green;">**Do not flag the resource**</mark><mark style="background-color:green;">.</mark>
* **Logos are up to date**
  * Make a <mark style="background-color:yellow;">**one time note**</mark> in the resource notes tab if logos are not up to date. <mark style="background-color:green;">**Do not flag the resource**</mark><mark style="background-color:green;">.</mark>
* **Dates at the bottom of the document are not more than 3 years old**
  * <mark style="background-color:red;">**Flag the resource and email leadership**</mark> if document has not been updated in more than 3 years. This should happen even if the content is still relevant, accurate and typo-free.
* **Source folder link exists and is accurate**
* **Publish status is appropriate**
* **Adobe API Check states "Pass"**
  * <mark style="background-color:yellow;">**Email ITC**</mark> if the check is not passing. This means that the PDF has one or more issues that could cause accessibility barriers.

{% hint style="warning" %}
If you need to change any file details, select the **actions button** next to the appropriate file and then select edit. Once changes have been made to the file details make sure to save changes with the save button to the right of the file before moving on to the Topic Page(s) tab. No need to save if no updates were made.&#x20;
{% endhint %}

### Topic Page(s) Tab

<mark style="background-color:blue;">**Check that topic pages listed are appropriate.**</mark>

*Remember **adding a topic page*** ***ONLY populates the resource into the page’s baby grid**. Consider if the topic page baby grid is appropriate or if a link should be added, or both. If you are unsure*  <mark style="background-color:yellow;">**Email ITC**</mark> to discus&#x73;*.* <mark style="background-color:green;">**Do not flag**</mark><mark style="background-color:green;">.</mark>

#### Understanding adding a resource to a topic page vs requesting a custom link

<details>

<summary>Adding a Resource to a Topic Page</summary>

<figure><img src="/files/dr8rZlogZPq0be7o9OT3" alt="the baby grid on the behavior page which shows resources that have the behavior topic page added in the topic page tab. "><figcaption><p><strong>All resources underneath a page’s baby grid are controlled by the topic page tab. Removing the topic page in the resource will remove the resource from the baby grid.</strong></p></figcaption></figure>

</details>

<details>

<summary>Requesting a custom link</summary>

<figure><img src="/files/dZO9ic5pMHz5pJPo1nCn" alt="a custom build tabs space showing links that have been built using html"><figcaption><p><strong>All links underneath the tabs on the behavior page are custom built. Removing behavior as a topic page does not remove any of these links. Reach out to ITC to remove links that have been placed manually.</strong></p></figcaption></figure>

</details>

{% hint style="warning" %}
If you need to remove a resource from a topic page, select the remove button. If you need to add a resource to a topic page, select the add topic button and begin typing the name of the topic page. Once found select from the dropdown.
{% endhint %}

### Videos Tab

<mark style="background-color:blue;">**If a video is present, check the following:**</mark>

* youTube Preview is live and video plays
  * If the YouTube preview is not live <mark style="background-color:red;">**flag the resource and email leadership**</mark><mark style="background-color:red;">.</mark>
* Content presented in the video is up to date
  * If the content is out of date <mark style="background-color:red;">**flag the resource and email leadership**</mark><mark style="background-color:red;">.</mark>
* Closed Captions box states "**Professionally Captioned**"
  * If this box states "**Automatically Captioned**" first check the resource notes to see if someone has checked the auto captions and certified that they are good.&#x20;
  * If nobody has checked the auto captions you can either check the auto captions (see note below) or <mark style="background-color:red;">**Flag the resource and email the ITC.**</mark>

{% hint style="warning" %}
At this time, each resource can only have a single video, and the video must be hosted on YouTube. If you update the YouTube ID select the update video button
{% endhint %}

### Modules Tab

<mark style="background-color:blue;">**Open the module and check:**</mark>

* Module content is up to date and links are live
  * If content is out of date or there are dead links <mark style="background-color:red;">**flag the resource and email leadership.**</mark>
  * Logos in the module are up to date
* Make a <mark style="background-color:yellow;">**one time note**</mark> in the resource notes tab if logos are not up to date. <mark style="background-color:green;">**Do not flag the resource**</mark><mark style="background-color:green;">.</mark>
* Links lead to accessible content
  * <mark style="background-color:yellow;">**Email ITC**</mark> if you have questions about the accessibility of linked content. <mark style="background-color:green;">**Do not flag the resource**</mark><mark style="background-color:green;">.</mark>
* Embedded files are up to date and links within the embedded content are live
  * If content is out of date or there are dead links <mark style="background-color:red;">**flag the resource and email leadership.**</mark>
  * <mark style="background-color:yellow;">**NOTE**</mark> <mark style="background-color:yellow;"></mark><mark style="background-color:yellow;">that only 3rd party content should be embedded. All ITC content should be provided through a descriptive link or button</mark>
* Links within embedded files lead to accessible content
  * <mark style="background-color:yellow;">**Email ITC**</mark> if you have questions about the accessibility of linked content. <mark style="background-color:green;">**Do not flag the resource**</mark><mark style="background-color:green;">.</mark>

<mark style="background-color:blue;">**On the module details in the resource:**</mark>

Check that the owner/manager roles are recorded and appropriate. If you are unsure who the owner and manager are email ITC to check. Roles can only be seen in Rise by someone who is an owner, manager or editor for the module.&#x20;

{% hint style="info" %}
If the resource is a module resource but doesn't have anything listed in the module tab **email ITC but do not flag the resource**. This is a result of an update to the system and will work itself out over time as modules are updated.&#x20;
{% endhint %}

{% hint style="warning" %}
**If changes are made to the actual module in Rise, email ITC.** We will republish the module and replace in the resource.

If changes are made to the module details make sure to save those changes using the save button.
{% endhint %}

### Notes Tab

#### Types of Notes

* <mark style="background-color:blue;">**General**</mark>
  * added using the "**Add Note**" button
  * use for notes that are not captured as part of a Flag, Remove Flag or Complete Review note
* <mark style="background-color:orange;">**Flag**</mark>
  * added using the "**Flag Resource**" button
  * use to describe the reason for flagging the resource. Should always be accompanied with an <mark style="background-color:red;">**email to leadership**</mark>
* <mark style="background-color:green;">**Remove Flag**</mark>
  * add using the "**Remove Flag**" button&#x20;
  * only avaible on a resource that is flagged
  * use to describe the reason for removing the flag
* <mark style="background-color:green;">**Complete Review**</mark>
  * add using the "**Complete Review**" button
  * only used at the end of a resource review
  * use to describe any items that should be known for subsequent reviews or anything that others should know when editing the resource after a review&#x20;
    * for example you can note old logos here that don't rise to the need to redo the resource at this point.

{% hint style="info" %}
All notes must be "**submitted**" when done. When editing a note the submit button will say "edit" instead of submit.&#x20;
{% endhint %}

{% hint style="warning" %}
Be detailed with your notes entries. Write so that they can be understood by someone not familiar with the resource or issue.
{% endhint %}

### To flag or not to flag

This section is intended as a quick reference for when to flag a resource and when not to. This list is not exhaustive. If you have questions about a flag email ITC or Leadership to discuss.&#x20;

{% columns %}
{% column %}

#### Do Flag

**AND email leadership or the ITC**

* Out of date content
* Content with dead links
* Resource with a date at the bottom over 3 years old
* A video with no functional preview
* A video with out of date content
* A video with unverified auto captions
* Module with out of date content
* Module with dead links
* Module with out of date embedded content
  {% endcolumn %}

{% column %}

#### Don't Flag

**AND either make a note, email leadership or email ITC**

* Links that lead to content where accessibility is questionable
* Old logos
* Adobe API Check is not passing
* Questions about adding topic pages or custom links
  {% endcolumn %}
  {% endcolumns %}


---

# Agent Instructions: 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:

```
GET https://idahotc.gitbook.io/user-manual/resource-review-rubric.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.