Some Profile and attribute is missing in the caliper

[rakeshqainfotech]

Hi Team ,

I was looking the caliper event store code and found that many Entities like Assignable , Attempt etc is missing in the caliper modal . Also some attribute like from base metric profile like isPartOf , membership etc is not implements in the code .

will it be available in the future releases or i am missing something ?

if i implements these changes in the code can i contribute on this github ?

Best Regards,
Rakesh

[ggilbert-unicon]

Hi Rakesh,

We would welcome your contributions. Please do submit pull requests.

The long term plan is to, yes - support the full Caliper specification.

Best,
Gary

[rakeshqainfotech]

Hi Team ,

Greetings !!

I have looked the latest LRS code . Based on my understanding I have some concern regarding this -

1. Why did you use conversion process i mean conversion from xAPI to Caliper and store the converted event into Elasticsearch .
2. After supporting full specification of Caliper will it be passed caliper conformance as page says every thing should be profile (Collection of events ) .

Please do let me know if more information is required from my side .

Best Regards,
Rakesh

[ggilbert-unicon]

Hi Rakesh,

The short answer to #1 is that storing two different formats made it very difficult to query the lrs. The choice to ultimately store the event in Caliper format was made because Caliper is intended for education specific use cases and xAPI is a little more general purpose (in our opinion). We will be making a similar consolidation to the data stores that we support - i.e., supporting multiple different backends (mongo, es, aws es) really, really slows down development - so we will likely be consolidating to MongoDB sometime in the future.

Ultimately yes we would like to pass IMS Caliper conformance. There is, as I'm sure you realized, a good amount of development remaining to make that happen.

Thank you for your continued interested. We would love to add you as a team member.

Best,
Gary

[rakeshqainfotech]

Hi Gary,

Thanks for your prompt reply .

I have a question if event store will not store learning content as profile (as described in conformance page) how would it be pass .

Please do let me know if more information is required from my side .

Best Regards,
Rakesh

[ggilbert-unicon]

Hi Rakesh,

The plan is to convert into the appropriate metric profile on read. There is enough data stored in the message to do this (and if there isn't we'll fix it).

Best,
Gary

[rakeshqainfotech]

Thanks for your help Gary. I really appreciate it.

We are trying to implement a very basic PoC of Caliper Event store and have the following additional questions:

1. I am still a bit unclear on Metric profiles. What is the role of profiles in the Caliper Analytics framework?

o Is this a logical term only ? It seems that only the events will be stored in the Event Store. There is no need to store Metric profiles as they are essentially defining the data model. Is that correct?

o If we are not going to store metric profiles in an Event store, they won’t be subjected to any conformance tests. Is this correct? The confusion is due to the Caliper Analytics conformance guide which enumerates certifications based on different metric profiles.

1. What is the way by which different events could be linked with one another? Currently, there is a federatedSession event attribute, but it is optional as per Caliper implementation as well as conformance guides. So what is the way to link different events (from same or different metric profiles) which are being performed by the same actor in the same session? Or is this a theoretical need as the current recommendations in Caliper standards are going to be sufficient? Please comment.
2. If some user logs in to a page and does not logout, eventually timeout will happen. According to the conformance guide, logout event is a mandatory event. So in the timeout case, are we responsible to send a dummy logout event to the Event store?

Kindly reply. Thanks for your help.

Best regards,
Rakesh.

[rakeshqainfotech]

Hi Gary,

Any update on above mentioned comments .

I am still waiting for your reply .

Best Regards,
Rakesh

[ggilbert-unicon]

Hi Rakesh,

Apologies for the slow response.

I would say that since these questions are more about the Caliper specification (and less about the OpenLRS application) it would be better to pose these questions to the IMS Caliper working group - perhaps here.

Best,
Gary

[stuartf]

We're also interested in getting an LRS with full caliper support set up, and I may be able to contribute to implementing the missing entity models. Is there a list of which are missing, and perhaps an estimate of how difficult each is to implement?