Method and apparatus for handling edge-cases of event-driven disposition
First Claim
1. A computer implemented method for managing retention of data and for enforcing data holds, comprising the steps of:
- providing at least one event consumer data source containing data, wherein the data is subject to a retention schedule defining rules for the disposition of the data;
providing an enterprise retention management (ERM) application, wherein the at least one event consumer is coupled with the ERM;
accepting at least one hold request in the ERM, wherein the hold request defines at least a portion of the data that must be held from disposition, forming held data;
accepting a disposition request in the ERM, wherein the disposition request comprises an instruction to dispose of at least a portion of the data based on the rules within the retention schedule;
filtering the disposition request, without the need for approval from an operator, forming a filtered request comprising an instruction to dispose of a portion of data comprising the portion of data identified in the disposition request minus the held data, said held data comprising disposition survivor data;
executing the filtered request; and
providing an event-driven disposition mechanism for disposing of said disposition survivor data in an immediately subsequent disposition cycle after said disposition survivor data is released from hold or unlocked, wherein the step of providing an event-driven disposition mechanism further comprises;
providing a file system connector that is responsible for putting files on hold and storing a list of files on hold in a connector database;
once said connector receives a disposition request, said connector attempting to delete all files matching said disposition request criteria, unless said files are identified as being on hold in said connector database;
wherein if a file on hold is identified during said disposition request, said connector persisting a current disposition request into said database and periodically trying to re-execute said request until there are no files matching the request criteria that remain on hold;
thereafter deleting said request from said connector database; and
informing said disposition mechanism logic whether an event consumer is disposition survivor-safe or unsafe in response to a configuration service request, said response to said configuration service request comprising any or all of the following parameters;
a consumer disposition survivor-safe (disposition survivor-unsafe) flag that is set to indicate whether the consumer is disposition survivor-safe or unsafe;
a reminder frequency (reminder period) parameter that is set to indicate how often a reminder should be sent to the event consumer; and
a maximum disposition transaction lifespan parameter that is set to indicate for how long the ERM should remind the event consumer about disposition and/or for how long a disposition survivor-safe event consumer attempts to get rid of disposition survivors.
3 Assignments
0 Petitions
Accused Products
Abstract
Retention of data is managed and data holds are enforced. At least one event consumer data source contains data that is subject to a retention schedule that defines rules for the disposition of the data. An enterprise retention management (ERM) application accepts at least one hold request that defines at least a portion of the data that must be held from disposition. A disposition request is also accepted by the ERM that comprises an instruction to dispose of at least a portion of the data based on the rules within the retention schedule. The disposition request is filtered to dispose of the portion of data identified in the disposition request minus the held data, which comprises disposition survivor data. An event-driven disposition mechanism disposes of the disposition survivor data as soon as possible after the disposition survivor data is released from hold or unlocked.
-
Citations
27 Claims
-
1. A computer implemented method for managing retention of data and for enforcing data holds, comprising the steps of:
-
providing at least one event consumer data source containing data, wherein the data is subject to a retention schedule defining rules for the disposition of the data; providing an enterprise retention management (ERM) application, wherein the at least one event consumer is coupled with the ERM; accepting at least one hold request in the ERM, wherein the hold request defines at least a portion of the data that must be held from disposition, forming held data; accepting a disposition request in the ERM, wherein the disposition request comprises an instruction to dispose of at least a portion of the data based on the rules within the retention schedule; filtering the disposition request, without the need for approval from an operator, forming a filtered request comprising an instruction to dispose of a portion of data comprising the portion of data identified in the disposition request minus the held data, said held data comprising disposition survivor data; executing the filtered request; and providing an event-driven disposition mechanism for disposing of said disposition survivor data in an immediately subsequent disposition cycle after said disposition survivor data is released from hold or unlocked, wherein the step of providing an event-driven disposition mechanism further comprises; providing a file system connector that is responsible for putting files on hold and storing a list of files on hold in a connector database; once said connector receives a disposition request, said connector attempting to delete all files matching said disposition request criteria, unless said files are identified as being on hold in said connector database; wherein if a file on hold is identified during said disposition request, said connector persisting a current disposition request into said database and periodically trying to re-execute said request until there are no files matching the request criteria that remain on hold; thereafter deleting said request from said connector database; and informing said disposition mechanism logic whether an event consumer is disposition survivor-safe or unsafe in response to a configuration service request, said response to said configuration service request comprising any or all of the following parameters; a consumer disposition survivor-safe (disposition survivor-unsafe) flag that is set to indicate whether the consumer is disposition survivor-safe or unsafe; a reminder frequency (reminder period) parameter that is set to indicate how often a reminder should be sent to the event consumer; and a maximum disposition transaction lifespan parameter that is set to indicate for how long the ERM should remind the event consumer about disposition and/or for how long a disposition survivor-safe event consumer attempts to get rid of disposition survivors. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26)
-
-
27. An apparatus for managing retention of data and for enforcing data holds, comprising:
-
at least one event consumer data source containing data, wherein the data is subject to a retention schedule defining rules for the disposition of the data; an enterprise retention management (ERM) application, wherein the at least one event consumer is coupled with the ERM; at least one connector comprising an interface between Said ERM and said at least one event consumer, wherein said at least one connector comprises a plurality of processing modules for performing operations on said data sources, said at least one connector further comprising; a module for accepting at least one hold request in the ERM, wherein the hold request defines at least a portion of the data that must be held from disposition, forming held data; a module for accepting a disposition request in the ERM, wherein the disposition request comprises an instruction to dispose of at least a portion of the data based on the rules within the retention schedule; a module for filtering the disposition request, forming a filtered request comprising an instruction to dispose of a portion of data comprising the portion of data identified in the disposition request minus the held data, said held data comprising disposition survivor data; a module for executing the filtered request; an event-driven disposition mechanism for disposing of said disposition survivor data in an immediately subsequent disposition cycle after said disposition survivor data is released from hold or unlocked; and a module for informing said disposition mechanism logic whether an event consumer is disposition survivor-safe or unsafe in response to a configuration service request, said response to said configuration service request comprising any or all of the following parameters; a consumer disposition survivor-safe (disposition survivor-unsafe) flag that is set to indicate whether the consumer is disposition survivor-safe or unsafe; a reminder frequency (reminder period) parameter that is set to indicate how often a reminder should be sent to the event consumer; and a maximum disposition transaction lifespan parameter that is set to indicate for how long the ERM should remind the event consumer about disposition and/or for how long a disposition survivor-safe event consumer attempts to get rid of disposition survivors.
-
Specification