System and method for providing content services to a repository

• US 7,162,504 B2
• Filed: 08/10/2004
• Issued: 01/09/2007
• Est. Priority Date: 04/13/2004
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Owen, James, Posner, Brad, Patadia, Jalpesh, Toussaint, Alexander, McCauley, Rodney
• Primary Examiner(s): LE, UYEN T
• Application Number:
  US10/915,521
• Publication Number:
  US 20050251506A1
• Time in Patent Office: 882 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/188 Virtual file systems
• CPC Class Codes: G06F 16/219 Managing data history or versioning querying versioned data G06F16/2474; querying temporal data G06F16/2477
• CPC Class Codes: G06F 16/256 in federated or virtual databases
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A system and method for providing one or more content services to a repository in a plurality of repositories that includes integrating the plurality of repositories into a virtual content repository (VCR), maintaining a logical namespace that encompasses the plurality of repositories, and providing the one or more content services to the VCR. The one or more content services includes at least one of: a versioning capability and a lifecycle capability. The VCR stores at least one of: content information and schema information. The content and schema information is accessible through a logical namespace that encompasses the plurality of repositories.

Claims

1. A method for providing one or more content services to a repository in a plurality of repositories, said method comprising:

integrating the plurality of repositories, including a first repository storing content information and a second repository storing schema information, into a virtual content repository (VCR) that maintains a logical namespace encompassing the plurality of repositories;

providing access to the VCR to one or more content services that include a versioning capability; and

accessing the content and schema information through the logical namespace that encompasses the plurality of repositories using the versioning capability to provide uniform content services across each of the repositories including the first repository storing content information and the second repository storing schema information.

2. The method of claim 1, further comprising:

maintaining a version history for at least one repository to track changes to at least one of;

the content information and the schema information.

3. The method of claim 2 wherein:

the version history can be rolled back.

4. The method of claim 1, further comprising:

transitioning the content information through a set of states according to a lifecycle definition.

5. The method of claim 4 wherein:

the content information transitions from a first state in the set of states to a second state in the set of states when there is a transition defined between the first state and the second state.

6. The method of claim 4, further comprising:

skipping the second state if a user or a process is in a superior role to a role associated with the transition.

7. The method of claim 5 wherein:

constraining the transition to at least one of;

a user, a group of users, a capability, and a role.

8. The method of claim 5, further comprising:

performing an action associated with a state in the set of states or a transition between two states in the set of states.

9. The method of claim 8 further comprising:

constraining the action by at least one of;

a policy, a capability, and a role.

10. The method of claim 4 wherein:

a transition between states is initiated by at least one of a user and a process.

11. The method of claim 1 wherein the integrating includes:

integrating with a service provider interface that is compatible with the VCR.

12. The method of claim 1 wherein:

the content information includes a link to information outside of the VCR.

13. The method of claim 1 wherein:

the repository does not natively support the one or more content services.

14. The method of claim 1 wherein:

the namespace is hierarchical.

15. A system for providing one or more content services to a repository in a plurality of repositories, said system comprising:

a virtual content repository (VCR) including

a plurality of repositories, including a first repository storing content information and a second repository storing schema information, integrated therein

and a logical namespace encompassing the plurality of repositories; and

one or more content services provided access to at least one repository integrated into the VCR,

the one or more content services including a versioning capability;

wherein at least one version of the content and schema information is accessible through the logical namespace that encompasses the plurality of repositories using the versioning capability to provide uniform content services across each of the repositories including the first repository storing content information and the second repository storing schema information.

16. The system of claim 15, further comprising:

a version history for the repository to track changes to at least one of;

the content information and the schema information.

17. The system of claim 16 wherein:

the version history includes a rollback capability.

18. The system of claim 15, further comprising:

a lifecycle definition to define at least one transition through a set of states for the content information.

19. The system of claim 18 wherein:

the content information transitions from a first state in the set of states to a second state in the set of states when there is a transition defined between the first state and the second state.

20. The system of claim 18 wherein:

the second state can be skipped if a user or a process is in a superior role to a role associated with the transition.

21. The system of claim 19 wherein:

the transition can be constrained to at least one of;

a user, a group of users, a capability, and a role.

22. The system of claim 19, further comprising:

an action associated with a state in the set of states or a transition between two states in the set of states.

23. The system of claim 22 wherein:

the action can be constrained by at least one of;

a policy, a capability, and a role.

24. The system of claim 18 wherein:

a transition between states can be initiated by a user or by a process.

25. The system of claim 15 wherein the integrating includes:

integrating with a service provider interface that is compatible with the VCR.

26. The system of claim 15 wherein:

the content information includes a link to information outside of the VCR.

27. The system of claim 15 wherein:

the repository does not natively support the one or more content services.

28. The system of claim 15 wherein:

the namespace is hierarchical.

29. A machine readable medium having instructions stored thereon that when executed by one or more processors cause a system to:

integrate the plurality of repositories, including a first repository storing content information and a second repository storing schema information, into a virtual content repository (VCR) that maintains a logical namespace encompassing the plurality of repositories;

provide access to the the VCR to one or more content services that include a versioning capability; and

access at least one version of the content and schema information through the logical namespace that encompasses the plurality of repositories using the versioning capability to provide uniform content services across each of the repositories including the first repository storing content information and the second repository storing schema information.

30. The machine readable medium of claim 29, further comprising instructions stored thereon that when executed by the one or more processors cause the system to:

maintain a version history for at least one repository to track changes to at least one of;

the content information and the schema information.

31. The machine readable medium of claim 30 further comprising instructions stored thereon that when executed by the one or more processors cause the system to:

roll back the version history.

32. The machine readable medium of claim 29, further comprising instructions stored thereon that when executed by the one or more processors cause the system to:

transition the content information through a set of states according to a lifecycle definition.

33. The machine readable medium of claim 32 wherein instructions stored thereon that when executed by the one or more processors cause the system to transition the content information through a set of states according to a lifecycle definition include instructions that when executed by the one or more processors cause the system to:

transition the content information from a first state in the set of states to a second state in the set of states when there is a transition defined between the first state and the second state.

34. The machine readable medium of claim 32, further comprising instructions stored thereon that when executed by the one or more processors cause the system to:

skip the second state if a user or a process is in a superior role to a role associated with the transition.

35. The machine readable medium of claim 33 further comprising instructions stored thereon that when executed by the one or more processors cause the system to:

constrain the transition to at least one of;

a user, a group of users, a capability, and a role.

36. The machine readable medium of claim 33, further comprising instructions stored thereon that when executed by the one or more processors cause the system to:

perform an action associated with a state in the set of states or a transition between two states in the set of states.

37. The machine readable medium of claim 36 wherein:

the action can be constrained by at least one of;

a policy, a capability, and a role.

38. The machine readable medium of claim 32 wherein:

a transition between states can be initiated by a user or by a process.

39. The machine readable medium of claim 29, further comprising instructions stored thereon that when executed by the one or more processors cause the system to:

implement a service provider interface that is compatible with the VCR.

40. The machine readable medium of claim 29 wherein:

the content information can include a link to information outside of the VCR.

41. The machine readable medium of claim 29 wherein:

the repository does not natively support the one or more content services.

42. The machine readable medium of claim 29 wherein:

the namespace is hierarchical.

43. A method for transmitting code over a transmission medium, comprising:

transmitting a code segment including instructions for integrating a plurality of repositories, including a first repository storing content information and a second repository storing schema information, into a virtual content repository (VCR) that maintains a logical namespace encompassing the plurality of repositories;

transmitting a code segment including instructions for providing access to the VCR to one or more content services that include a versioning capability; and

transmitting a code segment including instructions for accessing the content and schema information through the logical namespace that encompasses the plurality of repositories using the versioning capability to provide uniform content services across each of the repositories including the first repository storing content information and the second repository storing schema information.