Abstract: In processing a transaction, a data storage system of a processing system stores and updates a progression created for the transaction that represents a timeline of events that occurred related to the transaction. A progression for a transaction that is processed across multiple processing systems is organized as a chronological chain of segments. Each segment in the progression includes records for events processed by a given processing system prior to the transaction reaching an intermediate state or a terminal state. When the transaction reaches a terminal state, the segmented progression includes records associated with all of the events that occurred in relation to the transaction across multiple processing systems. A segment in the progression is cryptographically linked to a previous segment in the progression using a linking object that includes a transaction signature of the last record stored in the previous segment.

Abstract: In processing a transaction, a data storage system of a processing system stores and updates a progression created for the transaction that represents a timeline of events that occurred related to the transaction. A progression for a transaction that is processed across multiple processing systems is organized as a chronological chain of segments. Each segment in the progression includes records for events processed by a given processing system prior to the transaction reaching an intermediate state or a terminal state. When the transaction reaches a terminal state, the segmented progression includes records associated with all of the events that occurred in relation to the transaction across multiple processing systems. A segment in the progression is cryptographically linked to a previous segment in the progression using a linking object that includes a transaction signature of the last record stored in the previous segment.

Abstract: In processing a transaction, a data storage system of a processing system stores and updates a progression created for the transaction that represents a timeline of events that occurred related to the transaction. When an event for a transaction occurs, the data storage system identifies data associated with the event. The data storage system creates an event signature for the event by hashing together the identified data. The data storage system identifies a stored progression of the transaction. The data storage system identifies a transaction signature included in the last record added to the progression. The data storage system creates a transaction signature for the event based on the transaction signature of the last record and the event signature created for the event. The data storage system adds a new record to the progression for the event and includes the transaction signature created for the event in the new record.

Abstract: Disclosed are methods and apparatus for enabling user communities around the world to engage in translation of web properties while using such web properties. In certain embodiments, a translation interface is provided with a served web property to allow users to submit translations for user interface (UI) strings from a particular property interface. While a user is engaging with the web property, the interface can also enable in-context editing and submission of translations. For example, translation submission can be presented as a replacement for the translated text within the page that is being rendered to the translator user. Certain interface embodiments also are configured to allow the user community to give feedback on the submitted translations.

Abstract: Disclosed are methods and apparatus for enabling user communities around the world to engage in translation of web properties while using such web properties. In certain embodiments, a translation interface is provided with a served web property to allow users to submit translations for user interface (UI) strings from a particular property interface. While a user is engaging with the web property, the interface can also enable in-context editing and submission of translations. For example, translation submission can be presented as a replacement for the translated text within the page that is being rendered to the translator user. Certain interface embodiments also are configured to allow the user community to give feedback on the submitted translations.