Multi-Jurisdiction Retention Scheduling For Record Management

• US 20130024429A1
• Filed: 04/29/2010
• Published: 01/24/2013
• Est. Priority Date: 04/29/2010
• Status: Abandoned Application

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Raas, Urs
• Application Number:
  US13/579,390
• Publication Number:
  US 20130024429A1
• Time in Patent Office: Days
• US Class Current: 707/689
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A retention schedule is assigned to a record based on classification information associated with the record, wherein the retention schedule is linked to a plurality of jurisdiction triggers. Expiration dates for those jurisdiction triggers that correspond to jurisdiction information associated with the record are determined. A record expiration date for the record is selected from the determined expiration dates.

Claims

1. A method for managing retention of records for multiple jurisdictions, comprising:

assigning, using a processor-based device, a retention schedule to a record based on classification information associated with the record, wherein the retention schedule is linked to a plurality of jurisdiction triggers;

determining expiration dates for the jurisdiction triggers linked to the retention schedule that correspond to jurisdiction information associated with the record; and

selecting a determined expiration date as a record expiration date.

2. The method as recited in claim 1, wherein the jurisdiction triggers linked to the retention schedule include a default jurisdiction trigger, and wherein the method further comprises determining a default expiration date for the default jurisdiction trigger, and wherein selecting a determined expiration date comprises selecting the default expiration date as the record expiration date if none of the jurisdictional triggers corresponds to jurisdictional information associated with the record.

3. The method as recited in claim 1, wherein selecting one of the expiration dates comprises selecting the expiration date that expires at a latest time.

4. The method as recited in claim 1, further comprising:

generating a storage specification that includes the record expiration date; and

storing the storage specification and the corresponding record in a record repository.

5. The method as recited in claim 1, further comprising automatically updating the record expiration date in response to modification of a jurisdiction trigger linked to the retention schedule assigned to the record.

6. The method as recited in claim 1, further comprising automatically updating the record expiration date in response to modification of the jurisdiction information assigned to the record.

7. The method as recited in claim 1, further comprising assigning the classifying information to the record upon creation of the record, wherein the classifying information includes at least one of a business context and a record type.

8. The method as recited in claim 1, further comprising:

aggregating records in a group; and

selecting a group expiration date from the record expiration dates corresponding to the records in the group.

9. The method as recited in claim 1, wherein the jurisdiction triggers define retention periods and base trigger events for determining expiration dates.

10. The method as recited in claim 9, wherein each jurisdiction trigger includes a jurisdiction code, and wherein determining expiration dates comprises:

comparing the jurisdiction code for each jurisdiction trigger to jurisdiction information associated with the record; and

determining an expiration date for a jurisdiction trigger only if the jurisdiction code matches the jurisdiction information associated with the record.

11. An article comprising at least one machine-readable storage medium storing instructions that upon execution cause a computer system to:

determine a class of a record to be stored in a record repository managed by the computer system;

select a retention schedule for a record based on the determined class, wherein the retention schedule is linked to a plurality of jurisdiction triggers;

identify the jurisdiction triggers linked to the selected retention schedule that correspond to jurisdiction codes associated with the record; and

determine a record expiration date for the record using the identified jurisdiction triggers.

12. The article as recited in claim 11, wherein the instructions upon execution further cause the computer system to:

select a default jurisdiction trigger if none of the jurisdiction triggers correspond to jurisdiction codes associated with the record; and

determine a record expiration date for the record using the default jurisdiction trigger.

14. The article as recited in claim 12, wherein the default jurisdiction trigger is selected based on the class of the record.

15. The article as recited in claim 11, wherein the instructions upon execution further cause the computer system to:

generate a storage specification including the record expiration date; and

store the record and the storage specification in a record repository.

16. The article as recited in claim 11, wherein the instructions upon execution further cause the computer system to update the record expiration date for a particular record responsive to a modification of a jurisdiction trigger linked to the retention schedule assigned to the particular record.

17. The article as recited in claim 11, wherein the instructions upon execution further cause the computer system to update the record expiration date for a particular record responsive to a modification of a jurisdiction code associated with the particular record.

18. The article as recited in claim 11, wherein the record expiration date is determined by calculating expiration dates for the identified jurisdiction triggers and selecting the longest expiration date of the calculated expiration dates as the record expiration date.

19. The article as recited in claim 11, wherein the instructions upon execution further cause the computer system to:

aggregate records into a group; and

determine a group expiration date from the record expiration dates for the records in the group.

20. A computer system, comprising:

at least one processor;

a storage specification generator executable on the at least one processor to;

assign a multi-jurisdiction retention schedule to a record based on a class of the record, wherein the multi-jurisdiction retention schedule is linked to a plurality of jurisdiction triggers;

identify the jurisdiction triggers linked to the assigned retention schedule that correspond to jurisdiction information associated with the record;

determine a record expiration date for the record using the identified jurisdiction triggers; and

generate a storage specification associated with the record, the storage specification including the record expiration date.