Methods and systems for storing and retrieving rejected data
First Claim
1. A method for storing and retrieving a data object, wherein the data object is received from a first system that connects asynchronously with a second system, the second system comprising a data repository, the data object being subsequently rejected from storage on the data repository of the second system, the method comprising the steps of:
- collecting the rejected data object, the rejected data object containing a first value;
converting the rejected data object into a storage format;
storing the rejected data object in the storage format on a storage medium;
storing information for relating the rejected data object in the storage format to a first data model, the information allowing the rejected data object to be translated from the storage format into a first object format consistent with the first data model.
2 Assignments
0 Petitions
Accused Products
Abstract
Methods, computer-readable media, and systems are provided to facilitate the storage, retrieval, and display of rejected data objects. Even when a data object is accepted on a user system, the data object may be rejected before reaching a backend repository if the user system and backend repository are asynchronously connected. In one implementation, a rejected data object is collected, converted into a storage format, and stored on a storage medium. Information relating the rejected data object in the storage format to a first data model is also stored. At some future time, a request is received and utilized to locate the rejected data object. Then, the rejected data object is translated from a storage format into the first object format by using the relational information. A value from the translated rejected data object can then be displayed contemporaneously with a second data value from an accepted data object. This may allow a user to see transactions and data that might otherwise be lost. Further, this may allow a system analyst to correct system problems when abnormal trends in the rejected data are observed.
28 Citations
21 Claims
-
1. A method for storing and retrieving a data object, wherein the data object is received from a first system that connects asynchronously with a second system, the second system comprising a data repository, the data object being subsequently rejected from storage on the data repository of the second system, the method comprising the steps of:
-
collecting the rejected data object, the rejected data object containing a first value; converting the rejected data object into a storage format; storing the rejected data object in the storage format on a storage medium; storing information for relating the rejected data object in the storage format to a first data model, the information allowing the rejected data object to be translated from the storage format into a first object format consistent with the first data model. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A computer-readable medium containing instructions that cause a processor to perform stages when the processor executes the instructions, the stages comprising:
-
receiving a request from a user system for a first data value included in a rejected data object, the rejected data object having been rejected from storage on a data repository, the user system being asynchronous with the data repository; retrieving the rejected data object from a storage medium; translating the rejected data object from a storage format into a first object format consistent with a first data model by using information relating the rejected data object in the storage format to the first data model, the rejected data object in the first object format being usable for displaying the first data value; and displaying the first data value from the rejected data object contemporaneously with a second data value from an accepted data object. - View Dependent Claims (10, 11, 12, 13, 14, 15)
-
-
16. A system for storing and retrieving a rejected data object, the system comprising:
-
a backend data repository for storing accepted data; a documentation data repository for storing rejected data; and a server, operatively coupled to the backend repository and the documentation repository, comprising; a processor; and a memory containing instructions executable by the processor, the instructions, when executed, causing the processor to; receive a data object that is sent from a user system, the user system being asynchronous with the backend data repository;
the data object subsequently being rejected from storage in the backend data repository;convert the rejected data object into a storage format; store the rejected data object on the documentation data repository along with information establishing a relationship between the rejected data object and a first data model, the information allowing the rejected data object to be translated from the storage format into a first object format consistent with the first data model. - View Dependent Claims (17, 18, 19, 20, 21)
-
Specification