# ORA Rubric Point Field Accepts Only Integers — Why Not Decimals?

**URL:** <https://discuss.openedx.org/t/ora-rubric-point-field-accepts-only-integers-why-not-decimals/17465>\
**Category:** Authoring\
**Tags:** how-to\
**Created:** [October 30, 2025, 4:26pm UTC](https://discuss.openedx.org/t/ora-rubric-point-field-accepts-only-integers-why-not-decimals/17465 "2025-10-30T16:26:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yagnesh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/yagnesh/32/9571_2.png) [@Yagnesh](https://discuss.openedx.org/u/Yagnesh)\
**Post date:** [October 30, 2025, 4:26pm UTC](https://discuss.openedx.org/t/ora-rubric-point-field-accepts-only-integers-why-not-decimals/17465/1 "2025-10-30T16:26:31Z")

</div>

Hi everyone,

I’m working with the Open Response Assessment (ORA) feature in our instance of edx‑ora2, and I’ve encountered a limitation in the rubric configuration that I hope someone can explain (or point to a plan/issue).

**What I see:**

- In the Studio interface, when editing an assessment’s Rubric tab and using “Option Points”, I can set integer values (for example: `5`) and save successfully.

- When I try to set a **decimal** value (for example: `4.55`) and then click Save, I get the error:

- After some investigation, I found that the system appears to accept **only integer** values and rejects any fractional or decimal points.

- [GitHub - openedx/edx-ora2: Open Response Assessment Suite](https://github.com/openedx/edx-ora2)

**My questions:**

- Is there a **technical or design reason** why ORA/edx-ora2 currently restricts Option Points to integers only?

- Is there **any open issue** , **pull request** , or **roadmap item** under consideration that would allow decimal (floating) values for rubric points in a future version of edx-ora2?

Thanks in advance for any clarification, pointers to relevant issues, or suggestions. 🙂

---

<div class="post-metadata">

**Author:** ![joel.edwards](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/joel.edwards/32/3193_2.png) [@joel.edwards](https://discuss.openedx.org/u/joel.edwards)\
**Post date:** [October 31, 2025, 6:09am UTC](https://discuss.openedx.org/t/ora-rubric-point-field-accepts-only-integers-why-not-decimals/17465/2 "2025-10-31T06:09:55Z")

</div>

I don’t have an “official” answer for you but if I were to guess it would be that using integers simplifies the aggregation and avoids floating-point strict validation to prevent malformed XML from causing runtime errors. I suppose in theory it _could_ be modified to support floats instead of integers but there may well have been a good reason it wasn’t designed this way.

If you’d like to dig deeper, I think this is the bit of code specific to the issue you’re having, though there may probably be other areas that consume this value which might be expecting an integer, so I don’t anticipate it’ll be as simple as changing `int()` to `float()`

> <https://github.com/openedx/edx-ora2/blob/801fbd14ebb059ab8c5ee8d5a39c260c7f87ab81/openassessment/xblock/utils/xml.py#L326-L333>
