Content migration framework

• US 10,114,843 B2
• Filed: 11/09/2011
• Issued: 10/30/2018
• Est. Priority Date: 11/09/2011
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Fischer, Martin P., Kiessling, Heiko, Guendisch, Dieter, Rieder, Alexander, Weigel, Achim, Goetz, Paul, Hermes, Martin, Klevenz, Stephan, Kreyscher, Martin, Mitu, Corneliu D., Schneider, Juergen, Weber, Johannes
• Primary Examiner(s): Boccio, Vincent F
• Application Number:
  US13/292,647
• Publication Number:
  US 20130117289A1
• Time in Patent Office: 2,547 Days
• Field of Search: 707999204, 707E17117, 707692, 707694, 707602, 707756
• CPC Class Codes: G06F 16/214 Database migration support
• CPC Class Codes: G06F 16/254 Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database

Abstract

The present disclosure involves computer-implemented methods, software, and systems for supporting migration of unstructured data stored in enterprise content management systems. A computer-implemented method includes generating a search for content matching at least one content search rule, receiving a list of matched documents, wherein each document in the list of matched documents is associated with at least a source repository identifier and a unique document identifier, calculating a target repository identifier and at least one metadata change instruction for each unique document identifier using at least one migration rule, and modifying metadata for the document associated with each unique document identifier using the calculated at least one metadata change instruction.

Claims

1. A computer-implemented method for supporting migration of unstructured data stored in enterprise content management systems, comprising:

generating a search for the unstructured data matching at least one content search rule, the unstructured data comprising information that does not have a predefined data model, the at least one content search rule comprising an enterprise identifier and a document identifier and the at least one content search rule being retrieved from a migration engine server configured to provide support for migration of the unstructured data and structured data stored in an enterprise resource planning system;

receiving a list of matched documents, wherein each document in the list of matched documents comprises at least a portion of the unstructured data and is associated with at least a source repository identifier and a unique document identifier;

calculating a target repository identifier and at least one metadata change instruction for each unique document identifier using at least one migration rule defining how the unstructured data is to be migrated to maintain an integrity of the unstructured data, the at least one migration rule being compliant with international regulations; and

modifying metadata for the document associated with the document identifier using the calculated at least one metadata change instruction to generate a modified copy of the document, the at least one metadata change instruction specifying that any matched content with a particular source repository identifier is to be modified to reflect a particular target repository identifier, the particular target repository identifier comprising at least one of a prefix and a suffix different from the particular source repository identifier and the at least one metadata change instruction specifying deletion of the metadata matching the particular source repository identifier from a source repository associated with the particular source repository identifier upon migration to a target repository associated with the particular target repository identifier.

2. The computer-implemented method of claim 1, wherein the at least one content search rule is associated with a unique content search identifier.

3. The computer-implemented method of claim 1, wherein the at least one migration rule is associated with a unique migration rule identifier.

4. The computer-implemented method of claim 1, further comprising linking the at least one migration rule and the at least one content search rule with a unique migration task identifier.

5. The computer-implemented method of claim 1, further comprising, associating the calculated target repository identifier and the at least one metadata change instruction for each unique document identifier with a unique migration run identifier.

6. The computer-implemented method of claim 5, further comprising storing the calculated target repository identifier, the at least one metadata change instruction, and the unique migration run identifier in a persistence layer.

7. The computer-implemented method of claim 1, wherein the modified metadata for the document is copied to a calculated target repository associated with the target repository identifier.

8. The computer-implemented method of claim 1, further comprising deleting the modified metadata for the document from the source repository associated with the source repository identifier if the target repository identifier is different than the source repository identifier.

9. The computer-implemented method of claim 8, wherein the modified metadata for the document is verified as readable prior to deletion from the source repository.

10. A computer-program product for supporting migration of unstructured data stored in enterprise content management systems, the computer-program product comprising computer-readable instructions embodied on tangible, non-transitory media, the instructions operable when executed to:

generate a search for the unstructured data matching at least one content search rule, the unstructured data comprising information that does not have a predefined data model, the at least one content search rule comprising an enterprise identifier and a document identifier and the at least one content search rule being retrieved from a migration engine server configured to provide support for migration of the unstructured data and structured data stored in an enterprise resource planning system;

receive a list of matched documents, wherein each document in the list of matched documents comprises at least a portion of the unstructured data and is associated with at least a source repository identifier and a unique document identifier;

calculate a target repository identifier and at least one metadata change instruction for each unique document identifier using at least one migration rule defining how the unstructured data is to be migrated to maintain an integrity of the unstructured data, the at least one migration rule being compliant with international regulations; and

modify metadata for the document associated with the document identifier using the calculated at least one metadata change instruction to generate a modified copy of the document, the at least one metadata change instruction specifying that any matched content with a particular source repository identifier is to be modified to reflect a particular target repository identifier, the particular target repository identifier comprising at least one of a prefix and a suffix different from the particular source repository identifier and the at least one metadata change instruction specifying deletion of the metadata matching the particular source repository identifier from a source repository associated with the particular source repository identifier upon migration to a target repository associated with the particular target repository identifier.

11. The computer-program product of claim 10, the instructions further operable when executed to associate the calculated target repository identifier and the at least one metadata change instruction for each unique document identifier with a unique migration run identifier.

12. The computer-program product of claim 10, the instructions further operable when executed to delete the modified metadata for the document from the source repository associated with the source repository identifier if the target repository identifier is different than the source repository identifier.

13. The computer-program product of claim 12, wherein the modified metadata for the document is verified as readable prior to deletion from the source repository.

14. A system for supporting migration of unstructured data stored in enterprise content management systems, comprising:

memory operable to store unstructured data; and

at least one hardware processor interoperably coupled to the memory and operable to;

generate a search for the unstructured data matching at least one content search rule, the unstructured data comprising information that does not have a predefined data model, the at least one content search rule comprising an enterprise identifier and a document identifier and the at least one content search rule being retrieved from a migration engine server configured to provide support for migration of the unstructured data and structured data stored in an enterprise resource planning system;

receive a list of matched documents, wherein each document in the list of matched documents comprises at least a portion of the unstructured data and is associated with at least a source repository identifier and a unique document identifier;

calculate a target repository identifier and at least one metadata change instruction for each unique document identifier using at least one migration rule defining how the unstructured data is to be migrated to maintain an integrity of the unstructured data, the at least one migration rule being compliant with international regulations; and

modify metadata for the document associated with the document identifier using the calculated at least one metadata change instruction to generate a modified copy of the document, the at least one metadata change instruction specifying that any matched content with a particular source repository identifier is to be modified to reflect a particular target repository identifier, the particular target repository identifier comprising at least one of a prefix and a suffix different from the particular source repository identifier and the at least one metadata change instruction specifying deletion of the metadata matching the particular source repository identifier from a source repository associated with the particular source repository identifier upon migration to a target repository associated with the particular target repository identifier.

15. The system of claim 14, the at least one hardware processor further operable to associate the calculated target repository identifier and the at least one metadata change instruction for each unique document identifier with a unique migration run identifier.

16. The system of claim 14, the at least one hardware processor further operable to delete the modified metadata for the document from the source repository associated with the source repository identifier if the target repository identifier is different than the source repository identifier.

17. The system of claim 16, wherein the modified metadata for the document is verified as readable prior to deletion from the source repository.