Google 课堂插件现已面向开发者正式推出!如需了解详情,请参阅
插件文档。
评分准则结构和已知限制
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
如果您不熟悉 Google 课堂中的评分标准,请参阅以下帮助中心文章,了解评分标准的一般结构以及如何在 Google 课堂界面中进行评分标准评分。
评分准则结构
使用 API 与评分标准互动时,有一些重要的概念可能值得重点介绍:
- 一个
CourseWork
最多只能关联一个评分标准,并且该评分标准对于相应 CourseWork
而言是唯一的(无法在多个 CourseWork
资源之间共享)。
- 评分标准由标准组成,而标准又由等级组成。评分标准必须始终至少包含一个评分标准,而评分标准必须始终至少包含一个等级。
- 关卡可以计分(有分数),也可以不计分(没有分数)。在评分标准中,级别必须完全得分或完全不得分。
- 如果对级别进行评分,则一个条件中的所有级别都必须设置唯一的分值。积分可以是整数(例如 10),也可以是浮点数值(例如 9.99)。这可以包括 0。系统不接受 null 值。
此外,评分标准不能包含单个等级为 0 分的单个标准。
- 如果关卡不计分,则应省略 points 字段;系统不接受 null 值。
- 标准和等级的顺序具有实际意义,反映了它们在 Google 课堂界面中的显示顺序。
- 在同一评分准则中,您最多可以创建 50 条评分标准,并最多可为每条评分标准创建 10 个表现等级。
StudentSubmission
对象支持与评分标准相关的字段:
- 除了现有的
draftGrade
和 assignedGrade
属性之外,使用评分标准评分的学生提交内容还具有 draftRubricGrades
和 assignedRubricGrades
属性。这些分别表示学生在评分期间从评分标准中获得的评分标准成绩(所选等级和分值)(处于草稿和已布置状态)。
- 目前,这些属性是只读的。这意味着该 API 无法用于对提交内容进行评分,但您可以读取在 Classroom 界面中评分的提交内容。
评分标准行为
为了保持一致性,该 API 旨在尽可能地镜像 Google 课堂界面,但这可能会导致开发者难以理解的行为,因此值得一提:
- 评分标准旨在指导评分,同时又不限制教师。因此,教师在通过评分标准为提交内容评分时可以执行以下操作:
- 在评分时完全忽略评分准则。
- 替换某个评分标准的分数,而不论该评分标准等级中提供的分数是多少。
- 仅为部分评分标准选择等级。
- 为评分标准分配了分数,但未选择相应的等级。
- 替换作业的总分,无论评分标准会产生多少分。
此外,该 API 不支持 Google 课堂界面尚不具备的行为。例如,该 API 无法强制要求在作业中使用评分标准,也无法像现在这样替换教师编辑评分标准和提交内容的能力。
评分期间的限制
同样,教师开始使用评分准则打分后,在修改评分准则时会受到一些额外的限制。在评分开始后,只能进行以下修改:
- 允许对标准和等级的标题及说明进行文字修改。
- 级别顺序可以在条件内更改。
其他范围
教师可以手动将评分标准导出到 Google 电子表格,以便日后重复使用。
如果您通过这些电子表格创建或更新评分标准(请参阅指南中的示例),您的应用需要请求 https://www.googleapis.com/auth/spreadsheets.readonly
或 https://www.googleapis.com/auth/spreadsheets
范围。请注意,spreadsheets
范围被视为敏感范围,可能需要您的应用通过验证。
第三方课程
只有创建父级 CourseWork
项的 Google Cloud 项目才能创建评分标准。这是 Classroom API 中更广泛的设计模式,可防止不同的应用影响不属于自己的资源。
这同样适用于用户在 Google 课堂应用中创建的资源。例如,即使教师是某个应用的所有者,该应用也无法管理教师在 Google 课堂界面中创建的作业的评分标准。如果这严重限制了您的使用情形,请在公开问题跟踪器中分享反馈。
执照要求
只有在满足以下条件时,用户才能使用 Classroom API 创建、更新和删除评分标准:
请参阅用户资格要求,详细了解如何向用户公开 API 功能;另请参阅 Classroom API 前提条件,熟悉并申请用于开发的演示账号。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-29。
[null,null,["最后更新时间 (UTC):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."]]