stichtingsem / technology-prototype

Source code for any services or APIs created in the technology track in Summer 2020
6 stars 1 forks source link

Define content and structure of Usage Entity #16

Closed cliftonc closed 3 years ago

cliftonc commented 4 years ago

Discuss and define Usage entity:

mcginkel commented 4 years ago

Ok, so Lets start on this on: Usage.

Based on entitlement?

  1. So we could based the usage on the entitlement: the LA will send notifications to MP: At 23-jan-2020 12:01, student id-xxx, accessed product :EAN, based on entitlement E-xxx
  2. We just send the usage if entitlement is not available... (not prefered)

How often

  1. send first time only This is not prefered as you cannot see errors in setup process that make students acces a product, findout it is the wrong one, etc
  2. Send everytime
  3. Send ones a week ( and include number of times?)

image

mcginkel commented 4 years ago

drawing: https://yuml.me/sem/edit/fba64821

hhaarsma commented 4 years ago

Should we have an indication how often information should be communicated? I can imagine that notifying the market place everytime a student opens the learning application can be considered undersirable privacy sensitive information.

hhaarsma commented 4 years ago

Do we need to communicate the id along with the eckid?

edwinverwoerd commented 3 years ago

Domain of Usage is to get information about the state of an entitlement. Als MP I whant to see if the entitlement is: 1) still not used (nog niet geactiveerd) 2) used (geactiveerd) 3) blocked (geblokkeerd) 4) expirered (verlopen)

And timestamp information about. entitlement for User X has status used and the first and last time was [time stamp]

I looked at the pull request but I can not see if this will coverd the wish of a MP?