Authoring tool compatibility about adapt-contrib-assessment

[dancgray]

Issues validating _quizBankID and _split.

If _banks is enabled, blocks must be organised into questions banks by adding the _quizBankID attribute. We cannot validate for this in the authoring tool.

_quizBankID must start at 1 and increment by 1. In _split the position of the number in the list corresponds to the _quizBankID assigned in a block.

[dancgray]

_attempts can be a string (only infinite allowed) or a number. This element is currently defined as a number in the schema. We may need to change the schema type to a select and populate with ''infinite" and a number selection (if that's possible).

[moloko]

or maybe we could separate this out into a new property _allowInfiniteAttempts?

Or allow _attempts to be left blank and assume infinite if it is?

[oliverfoster]

_attempts - will be infinite if the value is < 0 or null or undefined or "infinite". so a number is fine. just put the default as -1 and update the description to explain

[oliverfoster]

_quizBankIDs can be moved if it makes more logical sense? is there an authoring tool reason for it or just for convention?

[oliverfoster]

_quizBankIDs and _split. what's the easiest way to store split to allow it to validate? or is it simply that one is on the article and the other on the blocks and validation isn't possible?

[dancgray]

@oliverfoster the _attempts suggestion should work fine.

I think the convention for extension JSON in the authoring tool is to put it within an object to allow JSON to be added/removed when plugins are added/removed from courses. Would there be a code change in the assessment model to move this to _assessment._quizBankId in the block?

It may be that validation is not possible without some custom validation for this plugin. I think we will need to re-address the authoring tool component inputs again as they are fairly lengthy now.

[oliverfoster]

Cool. yea a small set of changes i'd think. want me to do it before the schema gets accepted?