...

Publisher data is Subscribers must “subscribe” to a Program in order to pull its data from the Hub. The Publisher’s data are not publicly accessible to prevent it from being scraped, and to give Publishers controls over their data. Therefore, Subscribers must “subscribe” to a Program in order to pull its data from the Hub.

Heuristics staff establish these relationships partially to manage the complex templates that are required, but also to ensure that the Subscriber has a legitimate need to access that Publisher’s data.

...

LbApiPayloadTemplate syntax and purpose

Publishers and Subscribers think about and model their data differently, so the publisher’s data typically needs modified or converted before it can be imported into LearningBuilder.

Each Event Subscription specifies:

• Which PublisherEventCategory values it cares about

• A Handlebars template that specifies how to convert Events of that category into a JSON format that can be imported through the Subscriber’s API/WorkflowImportQueue/CreateBatch API.

Those templates are stored in the LbApiPayloadTemplate property of an EventSubsription:

"LbApiPayloadTemplate": {
  "{EventCategory1}": {
    "action": "import (default) | ignore",
    "label": "human readable note",
    "importProcessId": {WIQ Process Id},
    "

...

batchRowTemplate": "{handlebars template}"
  }, 

  // ... additional category mappings as needed ...

  "*": {
    "action": "import (default) | ignore",
    "label": "human readable note",
    "importProcessId": {WIQ Process Id},
    "batchRowTemplate": "{handlebars template}"
  }
}

...

See below for detailed explanation

Converting Provider data into Subscriber data

Publishers and Subscribers think about and model their data differently, so the publisher’s data typically needs modified or converted before it can be imported into LearningBuilder.

...

Each key within the LbApiPayloadTemplate should match one of the Publisher’s PublisherEventCategory values, or the special marker “*” which indicates a default template.

There are two reasons to include a PublisherEventCategory mapping:

• To import it into the Subscriber, using the specified batchRowTemplate

• To ignore it, because the Subscriber isn’t interested in that category of publisher data

Syntax examples

"LbApiPayloadTemplate": {
  "*": {
    "action": "import",
    "label": "Import everything",
    "importProcessId": {WIQ Process Id},
    "batchRowTemplate": "{handlebars template}"
  }
}

"LbApiPayloadTemplate": {
  "COURSE": {
    "action": "import",
    "label": "ACME Course",
    "importProcessId": {WIQ Process Id},
    "batchRowTemplate": "{handlebars template}"
  },
  "*": {
    "action": "import",
    "label": "Import everything",
    "importProcessId": {WIQ Process Id},
    "batchRowTemplate": "{handlebars template}"
  }
}

"LbApiPayloadTemplate": {
  "COURSE": {
    "action": "import",
    "label": "ACME course",
    "importProcessId": {WIQ Process Id},
    "batchRowTemplate": "{handlebars template}"
  },
  "*": {
    "action": "ignore",
    "label": "Nothing else matters"
  }
}

"LbApiPayloadTemplate": {
  "SOME_CATEGORY": {
    "action": "ignore",
    "label": "ACME course"
  },
  "*": {
    "action": "import",
    "importProcessId": {WIQ Process Id},
    "batchRowTemplate": "{handlebars template}"
  }
}

Detailed data flow

It works like this:

• When Publishers push data into the Hub, they specify a PublisherEventCategory value. (For example, this might differentiate between data representing a completed course and data representing work history)

• A Subscriber’s EventSubscription contain contain one or more templates, each one mapped to a specific PublisherEventCategory value. (This allows the subscriber to convert those courses and work history entries in different ways)

• Each template converts a single PublisherEventData JSON object into a different JSON schema that can be passed to the Subscriber’s API/WorkflowImportQueue/CreateBatch API endpoint.

• When LearningBuilder synchronizes data, it loops through each PublisherEventData item, converts it using the relevant template, and then makes a single call to API/WorkflowImportQueue/CreateBatch to import the data.

...

[
  { 
    "ProgramId": "subscriber_program_id", 
    "PublisherProgramId": "publisher_program_id", 
    "CreatedUtc": "UTC date/time",
    "LastSyncUtc": "UTC date/time",
    "SynEnabled": true,
    "LbApiPayloadTemplate": "... (see docs above) ..."
  },
  ...
]

...

GET /api/programs/{programId}/eventSubs/{publisherId}

Handy status macro
set 36399 isLabeled false historySnapshotId 7cfb151d-d309-448c-9e11-ef4dcd1953cc status 185953 historyChainId 995d84a4-485f-470b-9882-e5f4d573912a

...

{ 
  "ProgramId": "foo", 
  "PublisherProgramId": "bar", 
  "CreatedUtc": "UTC date/time",
  "LastSyncUtc": "UTC date/time",
  "SynEnabled": true,
  "LbApiPayloadTemplate": "... (see docs above) ..."  
}

...

POST /api/programs/{programId}/eventSubs

Handy status macro
set 36399 isLabeled false historySnapshotId 7cfb151d-d309-448c-9e11-ef4dcd1953cc status 185953 historyChainId 995d84a4-485f-470b-9882-e5f4d573912a

...

{
    "PublisherProgramId": "PublisherId",
    "SyncEnabled": true,
    "LbApiPayloadTemplate": "... (see docs above) ..."    
}

Responses

...

{
    "LastSyncUtc": "date",
    "SyncEnabled": true,
    "LbApiPayloadTemplate": "... (see docs above) ..."
}

Responses

...