Abstract: A history preserving data pipeline computer system and method. In one aspect, the history preserving data pipeline system provides immutable and versioned datasets. Because datasets are immutable and versioned, the system makes it possible to determine the data in a dataset at a point in time in the past, even if that data is no longer in the current version of the dataset.

Abstract: A transaction entity handles event messages associated with events of interest. At least one type of event is identified that is of interest to a user. Each type of event further corresponds to an event type that is to be repeated by a transaction entity to an aggregating entity. Further, a description is associated with each identified type of event. The transaction entity identifies an occurrence of an event that is an identified type of event and generates an event message comprising a token that associates the user with an account maintained by the aggregating and the description that is associated with the identified type of event corresponding to the identified occurrence of the event. The event message is transmitted to the aggregating entity.

Abstract: An event message is created that is associated with an event of interest to a user. A transaction entity obtains a token that corresponds to an account of an aggregating entity. Additionally, at least one type of event is identified. Each identified type of event comprises an event type that is of interest to a user and is intended by the user to be reported to the aggregating entity. The transaction entity identifies an occurrence of an event that corresponds to a previously identified type of event and creates an event message that includes the token. The transaction entity then transmits the event message to the aggregating entity. The transmitted event message is adapted to correspond to at least one indicator of the occurrence of the event that is provided by the aggregating entity for review by the user.

Abstract: A user inspects at least one indicator of an event. The user enables a token corresponding to an account of an aggregating entity to be received by a transaction entity and identifies at least one type of event of interest to be reported by the transaction entity to the aggregating entity. The user obtains and inspects at least one indicator from the account of the aggregating entity, where each obtained indicator is adapted to be created by the aggregating entity based upon an event message received from the transaction entity. The event message comprises the token, which is adapted to be used by the aggregating entity to identify the account and the event message corresponds to an occurrence of an event of at least one type of event of interest to be reported by the transaction entity to the aggregating entity.

Abstract: An account is associated with a token that is adapted to be distributed to at least one transaction entity. An event message is received from the transaction entity that comprises the token and optional additional information corresponding to an event of interest to a user. The event message is associated with the account based upon the token received with the event message and at least one indicator of the event of interest to the user is aggregated with any other existing indicators in the account. The indicators in the account are made available to the user for inspection.