Google Classroom 外掛程式現已全面開放開發人員使用!詳情請參閱
外掛程式說明文件。
評分量表和已知限制
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
如果不熟悉 Classroom 評量表,請參閱這些說明中心文章,瞭解評量表的一般結構,以及如何在 Classroom 使用者介面評量評量表。
評分量表結構
使用 API 與評量表互動時,建議特別注意以下幾個重要概念:
- 每個
CourseWork
最多只能有一個相關聯的評量表,且該評量表專屬於該 CourseWork
(無法在 CourseWork
資源之間共用)。
- 評量表由評量標準組成,而評量標準又由等級組成。評量表至少須包含一項評量標準,而評量標準至少須包含一個等級。
- 等級可以計分 (有分數) 或不計分 (沒有分數)。評分量表中的所有等級都必須評分或不評分。
- 如果層級有分數,準則中的所有層級都必須設定不重複的分數值。分數可以是整數 (例如 10) 或浮點值 (例如 9.99)。包括 0。不接受空值。
此外,評分量表不得只有一項準則,且該準則只有一個等級,且為 0 分。
- 如果等級未評分,則應省略分數欄位;系統不接受空值。
- 準則和等級的順序具有意義,反映了這些項目在 Classroom 使用者介面中的顯示順序。
- 每個評分量表最多可包含 50 項準則,每項準則最多可分為 10 個表現等級。
StudentSubmission
物件支援與評量表相關的欄位:
- 除了現有的
draftGrade
和 assignedGrade
屬性之外,以評量表評分的學生提交內容還具有 draftRubricGrades
和 assignedRubricGrades
屬性。這些分別代表學生在評分期間,從評分量表獲得的評分量表成績 (所選等級和分數值),以及草稿和已指派狀態。
- 這些資源目前僅供讀取,也就是說,您無法使用 API 評估提交內容,但可以讀取在 Classroom 使用者介面中評估的提交內容。
評分量表行為
為確保一致性,API 會盡可能反映 Classroom 使用者介面,但這可能會導致開發人員覺得不直覺的行為,因此值得一提:
- 評量表旨在引導評分,不會限制老師。因此,老師在透過評分表為提交內容評分時,可以執行下列動作:
- 評分時完全忽略評分量表。
- 覆寫準則的分數,無論準則等級的分數為何。
- 只為部分準則選取等級。
- 為準則指派分數,但未選取對應等級。
- 覆寫作業總分,無論評分量表的分數為何。
此外,如果 Classroom 使用者介面尚未提供某項功能,API 也不支援該功能。舉例來說,API 無法強制在作業中使用評量表,也無法像現在一樣,覆寫老師編輯評量表和提交內容的權限。
評分期間的限制
同樣地,老師開始使用評分量表評分後,編輯評分量表時也會受到一些額外限制。評分開始後,只能進行下列編輯:
- 您可以編輯準則和等級的名稱和說明。
- 等級順序可能會在條件內變更。
其他範圍
老師可以手動匯出評量表至 Google 試算表,以供重複使用。
如果您從這些試算表建立或更新評量表 (請參閱指南中的範例),應用程式必須要求 https://www.googleapis.com/auth/spreadsheets.readonly
或 https://www.googleapis.com/auth/spreadsheets
範圍。請注意,spreadsheets
範圍屬於私密資訊,應用程式可能需要驗證。
第三方課程
只有建立上層 CourseWork
項目時使用的 Google Cloud 專案,才能建立評量表。這是 Classroom API 中更廣泛的設計模式,可防止不同應用程式影響不屬於自己的資源。
這也包括使用者在 Classroom 應用程式中建立的資源。舉例來說,即使老師擁有應用程式,應用程式也無法管理老師在 Classroom 使用者介面中建立的課程作業評量表。如果這項限制嚴重影響您的用途,請在公開問題追蹤工具中分享意見回饋。
執照規定
如要使用 Classroom API 建立、更新及刪除評量表,使用者必須符合下列條件:
請參閱使用者資格,進一步瞭解如何向使用者公開 API 功能,並參閱 Classroom API 先決條件,熟悉開發用的示範帳戶並提出申請。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-08-29 (世界標準時間)。
[null,null,["上次更新時間:2025-08-29 (世界標準時間)。"],[],[],null,["# Rubrics structure and known limitations\n\nIf unfamiliar with Classroom Rubrics, see these Help Center articles to learn\nabout the [general structure](https://support.google.com/edu/classroom/answer/9335069?co=GENIEPlatform%3DDesktop#zippy=%2Cdelete-an-assignments-rubric%2Cedit-an-assignments-rubric%2Cshare-rubrics-with-export-and-import%2Csee-an-assignments-rubric%2Cadd-a-rubric-to-an-existing-assignment%2Creuse-a-rubric%2Ccreate-a-rubric%2Crubric-overview) of a rubric and how [rubric grading](https://support.google.com/edu/classroom/answer/9335428?ref_topic=11599451&sjid=7396534141168895349-NA) is done in\nthe Classroom UI.\n\nRubrics structure\n-----------------\n\nThere are some important concepts that may be worth highlighting when using the\nAPI to interact with rubrics:\n\n- There is (at most) a single [rubric](/workspace/classroom/reference/rest/v1/courses.courseWork.rubrics) associated with a [`CourseWork`](/workspace/classroom/reference/rest/v1/courses.courseWork) and that rubric is unique to that `CourseWork` (it is not shareable across `CourseWork` resources).\n- The rubric consists of [criteria](/workspace/classroom/reference/rest/v1/courses.courseWork.rubrics#criterion), which consist of [levels](/workspace/classroom/reference/rest/v1/courses.courseWork.rubrics#level). A rubric must always have at least one criteria, and a criterion must always have at least one level.\n- Levels can be scored (have points) or unscored (no points). Levels must be entirely scored or entirely unscored in a rubric.\n - If the levels are scored, all levels in a criterion must have a unique points value set. Points can be integers (like 10) or floating point values (like 9.99). This can include 0. Null values are not accepted. Additionally, a rubric can't have a single criteria with a single level that is 0 points.\n - If the levels are unscored, the points field should be omitted; null values are not accepted.\n- The order for criteria and levels is meaningful and reflects the order they are represented in the Classroom UI.\n - Scored levels in particular must always be sorted by points in either increasing or decreasing order.\n- There can be up to 50 criteria per rubric and up to 10 performance levels per criterion.\n\nRelated student submission fields\n---------------------------------\n\n[`StudentSubmission`](/workspace/classroom/reference/rest/v1/courses.courseWork.studentSubmissions) objects support rubrics-related fields:\n\n- In addition to the existing `draftGrade` and `assignedGrade` properties, a student submission graded with a rubric has `draftRubricGrades` and `assignedRubricGrades` properties. These represent the rubric grades (levels selected and point values) the student receives during grading from the rubric, in the draft and assigned states, respectively.\n- For now, these properties are read-only. This means that *the API can't be\n used to grade submissions*, but you can read submissions graded in the Classroom UI.\n\nRubrics behaviors\n-----------------\n\nThe API aims to mirror the Classroom UI whenever possible for consistency, but\nthis can lead to behaviour that may be unintuitive for developers and is worth\nmentioning:\n\n- Rubrics are intended to *guide* grading without constraining teachers. As a result, a teacher can do the following when grading a submission with a rubric:\n - Completely ignore the rubric when grading.\n - Override the points for a criterion, irrespective of the points available in the criterion's levels.\n - Select levels for only a subset of criteria.\n - Assign points for a criteria without selecting a corresponding level.\n - Override the assignment's total points, irrespective of the points that would come from the rubric.\n\nAdditionally, the API doesn't support behavior the Classroom UI doesn't already\nhave. For example, the API doesn't enable enforcing rubrics usage on assignments\nor overriding a teacher's ability to edit rubrics and submissions as they can\ntoday.\n\nLimitations during grading\n--------------------------\n\nSimilarly, there are some additional limitations place on editing rubrics once a\nteacher has started grading with it. Only the following edits are possible after\ngrading as started:\n\n- Text edits are allowed for criterion and level titles and descriptions.\n- Level ordering can change within criteria.\n\nAdditional scopes\n-----------------\n\nRubrics can be manually [exported](https://support.google.com/edu/classroom/answer/9335069?co=GENIE.Platform%3DDesktop#zippy=%2Cshare-rubrics-with-export-and-import) to Google Spreadsheets for re-use by\nteachers.\n\nIf you create or update a rubric from these spreadsheets (see an [example in the\nguide](/workspace/classroom/rubrics/getting-started#export-and-import-rubrics)), your application needs to request the\n`https://www.googleapis.com/auth/spreadsheets.readonly` or\n`https://www.googleapis.com/auth/spreadsheets` scope. Be aware that the\n`spreadsheets` scopes are considered sensitive and may require your application\nto be [verified](https://support.google.com/cloud/answer/9110914).\n\nThird-party coursework\n----------------------\n\nRubrics can only be created by the Google Cloud project that created the parent\n`CourseWork` item. This is a broader design pattern in the\nClassroom API which prevents different applications from impacting\nresources that aren't thiers.\n\nThis extends to resources created by users in the Classroom app.\nFor example, It's not possible for an application to manage rubrics for a\ncoursework that a teacher created in the Classroom UI, even if\nthe same teacher owns the application. If this significantly limits your use\ncase, share feedback in the [public issue tracker](https://issuetracker.google.com/issues/new?component=191645&template=823907).\n\nLicense requirements\n--------------------\n\nA user can only create, update, and delete rubrics with the\nClassroom API if the following conditions are met:\n\n- The user making the request has a [Google Workspace for Education Plus](https://edu.google.com/intl/ALL_us/workspace-for-education/editions/compare-editions/) license assigned to them.\n- The course owner of the corresponding course has a [Google Workspace for Education Plus](https://edu.google.com/intl/ALL_us/workspace-for-education/editions/compare-editions/) license assigned to them.\n\nSee [user eligibility](/workspace/classroom/guides/key-concepts/user-eligibility) to learn more about how API\ncapabilities are exposed to users and Classroom API [prerequisites](https://developers.google.com/workspace/classroom/guides/onboarding/prerequisites) to\nbecome familiar with, and request, a demo account for development."]]