Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


FeatureEvent NameProperties
1Youtube video in the ECML ContentINTERACT

actor.type='User'

context.env='contenteditor'

object.type='content'

edata.type='select'

edata.plugin.id='org.ekstep.video'

2Question Plugin INTERACT

actor.type='User'

context.env='contenteditor'

object.type='content'

edata.type='click'

edata.id='button'

edata.subtype='select'

edata.plugin.id='org.ekstep.questionbank'

3Content suggestion in textbookINTERACT

actor.type='User'

context.env='contenteditor'

object.type='content'

edata.type='click'

edata.id='button'

edata.subtype='select'

edata.plugin.id='org.ekstep.suggestioncontent'


4Math symbol and formulaINTERACT

actor.type='User'

context.env='contenteditor'

object.type='content'

edata.type='TOUCH'

edata.id='input'

edata.pageid='question-creation-mcq-form'

edata.plugin.id='org.ekstep.questionunit.mcq'


5Assessment summariser in the mobile appIMPRESSION

actor.type='User'

context.env='reports-users-group'

edata.pageid='user'

edata.uri='user'

edata.type='view'



6User Groups in mobile appIMPRESSION

actor.type='User'

context.env='user'

edata.pageid='users-groups'

edata.uri='users-groups'

edata.type='view'



Conclusion:


* Instead of generating new `FEATURE` event object from the upstream component, generate a INREACT Event with cdata object having featureId with this we can compute the feature usage.

* For the existing features implement data product to compute the feature usage only if the computation is not possible from the druid.