...
Excerpt | ||
---|---|---|
| ||
RESTful APIs for the “Event Store” functionality of the Learning Hub, where the hub acts as a centralized “clearinghouse” of accomplishments and activities. These APIs are called by publishers Publishers to put data into the Learning Hub. |
...
EVENT | |||||||
---|---|---|---|---|---|---|---|
An Event is the thing being recorded in the hub: user completed a course, earned a credential, etc. This design is influenced by the idea of a Learning Record Store in xAPI, but with less complexity. | |||||||
Field | Type | Notes | |||||
| UUID (universally unique Identifier) |
The Event Ids are assigned by the Learning Hub. | |||||
| string (25 char) | Descriptive name for the Program that published this event. | |||||
| string (25 char) | Identifier for the type of system that published this data. Currently, only the value “LB” is supported, for LearningBuilder. | |||||
| string (50 char) | The type of event as reported by the publisherPublisher. As of 12.4, the only supported value is AI_COMP_SUCCESS, indicating a successfully completed Activity in LearningBuilder. This will probably change over time as the Hub is extended to support edits and deletes. See also | |||||
| string (200 char) | The Program’s unique identifier for the source event. For LearningBuilder this will be something like “AI:1234”, which would be the Activity Instance WFI #1234 | |||||
| string (200 char) | The Program’s unique identifier for the person, organization, or entity that the event relates to.
| |||||
| JSON object | High level classification of this event, within the publisher’s Publisher’s system.
The The The This data can be used by the subscriber Subscriber to map different types of publisher Publisher data to different import templates. If omitted, subscribers Subscribers will not be able to differentiate between different types of records coming from the publisherPublisher. See also: | |||||
| JSON blob | The Publisher’s representation of the event data.
| |||||
| UTC date/time | Non-null date/time the event started. (If only a single date/time is associated with the event, it is stored here). | |||||
| UTC date/time | Nullable date/time that the event ended. | |||||
| UTC date/time | UTC timestamp when this record was created. | |||||
| string |
Gathers the year, month, and date from the Identifier used by the LearningHub query that gathers events to process. |
...
PublisherEventCategory
is a publisher Publisher concept that differentiates different types of events in their system, such as “Course” or “Exam Result”. These are NOT fixed values and will vary by publisherPublisher. (For LearningBuilder publishersPublishers, this will usually be the Activity Type)
Subscribers can subscribe to specific event categories for specific publishersPublishers, with separate mapping templates for each category.
...
Parameter | Description | ||
---|---|---|---|
| The Program that owns the Event. The API Key must have access to this Program. | ||
| The type of system that published the event. This is an arbitrary string provided by the publisherPublisher. Can be used when a publisher Publisher has multiple systems pushing data into the Hub. | ||
| The type of Learning Hub Event this record represents. For now, the only supported value is “AI_COMP_SUCCESS” | ||
| A value that uniquely identifies this event in the publisher’s Publisher’s system. For LearningBuilder publishersPublishers, this will be an “entity-scoped identifier” such as | ||
| Email address or some other piece of information that uniquely identifiers the primary participant within the publisherPublisher's system. Ideally, this is an email address or some other identifier that is shared with the subscribersSubscribers. | ||
| JSON object containing information about the type of Event, according to the source Program’s system. The The
| ||
| JSON object representing the Event in the source Program’s system. When calling | ||
| The UTC date/time when this Event occurred, or the time that the Event started. | ||
| The UTC date/time when this Event ended. For Events with only a single timestamp, rather than a range, set this equal to |
...
The exact fields and field names in the PublisherEventData
node will be determined as part of the implementation process, as these are determined by the LearningBuilder instance configuration and that data the publisher Publisher is providing to the LearningHub.
...