Interactive and dynamic timeline data merging and management

A non-transitory computer-readable storage medium comprising computer-readable program code that, when executed using one or more computer processors, performs an operation comprising:

• in response to receiving a first request indicating that a first client desires to sell an asset indicated in the first request:
• generating, by a transaction server, a seller timeline for the first client comprising a first set of events for the asset indicated in the first request, wherein:
• the first set of events are generated, from a defined set of events, based on a role of the first client, and
• each respective event in the defined set of events comprises a respective set of criteria indicating:
• (i) a transaction stage when the respective event is applicable, and (ii) a role for which the respective event is applicable;
• and
• generating and adding a first unique identifier to the seller timeline;
• in response to receiving a second request indicating that a second client desires to search for one or more assets for subsequent purchase:
• generating, by the transaction server, a buyer timeline for the second client, distinct from the seller timeline, comprising a second set of events distinct from the first set of events, wherein the buyer timeline is maintained on the transaction server separately from the seller timeline on the transaction server;
• and
• generating and adding a second unique identifier to the buyer timeline;
• providing, to the first client and from the second client, a first submission for the asset, comprising updating a first graphical user interface (GUI) output on a first device of the first client;
• in response to determining that the first client approved the first submission, generating, by the transaction server, a merged timeline based on the seller and buyer timelines, wherein the merged timeline comprises both the first and second sets of events, comprising:
• adding the first unique identifier to the buyer timeline to point to the seller timeline;
• adding the second unique identifier to the seller timeline to point to the buyer timeline;
• generating a third set of events for the merged timeline based on a determined stage of the merged timeline;
• updating the first GUI output on the first device to indicate the merged timeline;
• and
• updating a second GUI output on a second device of the second client to indicate the merged timeline, comprising using a bidirectional communication protocol to automatically modify the second GUI using a push notification;
• in response to determining that the merged timeline has reached a new stage, generating a fourth set of events for the merged timeline based at least in part on the new stage of the merged timeline;
• updating the first GUI output on the first device to indicate a first subset of the fourth set of events based on the role of the first client;
• and
• updating the second GUI output on the second device to indicate a second subset of the fourth set of events based on a role of the second client.

A system comprising:

• one or more computer processors;
• and
• logic encoded in a non-transitory medium, the logic executable by operation of the one or more computer processors to perform an operation comprising:
• in response to receiving a first request indicating that a first client desires to sell an asset indicated in the first request:
• generating, by a transaction server, a seller timeline for the first client comprising a first set of events for the asset indicated in the first request, wherein:
• the first set of events are generated, from a defined set of events, based on a role of the first client, and
• each respective event in the defined set of events comprises a respective set of criteria indicating:
• (i) a transaction stage when the respective event is applicable, and (ii) a role for which the respective event is applicable;
• and
• generating and adding a first unique identifier to the seller timeline;
• in response to receiving a second request indicating that a second client desires to search for one or more assets for subsequent purchase:
• generating, by the transaction server, a buyer timeline for the second client, distinct from the seller timeline, comprising a second set of events distinct from the first set of events, wherein the buyer timeline is maintained on the transaction server separately from the seller timeline on the transaction server;
• and
• generating and adding a second unique identifier to the buyer timeline;
• providing, to the first client and from the second client, a first submission for the asset, comprising updating a first graphical user interface (GUI) output on a first device of the first client;
• in response to determining that the first client approved the first submission, generating, by the transaction server, a merged timeline based on the seller and buyer timelines, wherein the merged timeline comprises both the first and second sets of events, comprising:
• adding the first unique identifier to the buyer timeline to point to the seller timeline;
• adding the second unique identifier to the seller timeline to point to the buyer timeline;
• generating a third set of events for the merged timeline based on a determined stage of the merged timeline;
• updating the first GUI output on the first device to indicate the merged timeline;
• and
• updating a second GUI output on a second device of the second client to indicate the merged timeline, comprising using a bidirectional communication protocol to automatically modify the second GUI using a push notification;
• in response to determining that the merged timeline has reached a new stage, generating a fourth set of events for the merged timeline based at least in part on the new stage of the merged timeline;
• updating the first GUI output on the first device to indicate a first subset of the fourth set of events based on the role of the first client;
• and
• updating the second GUI output on the second device to indicate a second subset of the fourth set of events based on a role of the second client.