System and method for providing link property types for content management

• US 7,917,537 B2
• Filed: 05/22/2006
• Issued: 03/29/2011
• Est. Priority Date: 09/26/2005
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Zhou, Xiaojiang, McVeigh, Ryan Sean, Posner, Brad, Roth, Steven L., Saarva, Tanya, Patadia, Jalpesh
• Primary Examiner(s): Vy; Hung T
• Assistant Examiner(s): CAO, PHUONG THAO
• Application Number:
  US11/438,164
• Publication Number:
  US 20070073744A1
• Time in Patent Office: 1,772 Days
• Field of Search: 707/802, 707/792, 707/999.101, 707/999.104
• US Class Current: 707/802
• CPC Class Codes: G06F 16/289 Object oriented databases

Abstract

In accordance with embodiments, there are provided mechanisms and methods for providing linked property types in a content management system. These mechanisms and methods for providing linked property types in a content management system can enable users to specify a new property definition type, which refers to another node instance in the content management system. By specifying a link property definition type on a type, the user can then relate a node instance of the modeled type (link source) to any other node instance (link target) in the system. For example, a user can create a type Article with property definitions such as title, body and authorLink. The authorLink property definition can be a link type property definition. Then the user could define an Author content type. When an instance of an Article is created (anArticle), the authorLink property associated with anArticle could refer to a node instance of an Author.

Claims

1. A method for providing a link property definition type mechanism in a content management system, the method comprising:

providing a virtual content repository (VCR) with a plurality of content repositories;

associating the VCR with an application programming interface (API), wherein a user of the VCR uses the API to manipulate content in the plurality of content repositories in a programming language;

modeling content in the plurality of content repositories using a general service provider interface (SPI), wherein the general SPI isolates direct interaction with each content repository in the plurality of content repositories from the API;

associating a plurality of format specific content repositories with the general SPI, wherein each format specific content repository is associated with the general SPI through a format specific SPI implementation, and wherein each format specific SPI implementation connects indirectly with the API through the general SPI and provides a different format specific SPI for a different format specific content repository;

providing a link property definition type that relates a plurality of source nodes to a plurality of target nodes, wherein one source node of the plurality of source nodes is a first node within a first content repository in the VCR, and one target node of the plurality of target nodes is a second node in a second content repository in the VCR, wherein one of the first content repository and the second content repository uses a format specific SPI that is different from the general SPI;

instantiating a software object type in the programming language using the API, wherein the software object type is associated with the link property definition type;

accessing, via an instance of the software object type and the API, said target node from said source node through both the general SPI and the format specific SPI, based on the definition of the link property definition type; and

managing content in the plurality of content repositories based upon the VCR.

2. The method of claim 1, further comprising:

receiving a specification of the link property definition type.

3. The method of claim 1, further comprising:

blocking creation of property choices for the link property definition type.

4. The method of claim 3, further comprising:

blocking specifying default values for a property.

5. The method of claim 1, further comprising:

retrieving a property of the first node by at least one of;

retrieving a target node when the target node exists, wherein the target node is a node in the second content repository;

returning null when a target node has not yet been specified; and

raising an exception.

6. The method of claim 1, further comprising:

permitting a node which other nodes have as a link property target to be deleted.

7. The method of claim 1, further comprising:

relating the first node to another target node of the plurality of target nodes during operations on the VCR.

8. The method of claim 1, further comprising:

associating the general SPI with a general SPI library, and the general SPI library is at least one of linked to and loaded in at run-time by an API library that is associated with the API.

9. A machine-readable storage medium carrying one or more sequences of instructions for providing a link property definition type mechanism in a content management system, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of:

providing a virtual content repository (VCR) with a plurality of content repositories;

associating the VCR with an application programming interface (API), wherein a user of the VCR uses the API to manipulate content in the plurality of content repositories in a programming language;

modeling content in the plurality of content repositories using a general service provider interface (SPI), wherein the general SPI isolates direct interaction with each content repository in the plurality of content repositories from the API;

associating a plurality of format specific content repositories with the general SPI, wherein each format specific content repository is associated with the general SPI through a format specific SPI implementation, and wherein each format specific SPI implementation connects indirectly with the API through the general SPI and provides a different format specific SPI for a different format specific content repository;

providing a link property definition type that relates a plurality of source nodes to a plurality of target nodes, wherein one source node of the plurality of source nodes is a first node within a first content repository in the VCR, and one target node of the plurality of target nodes is a second node in a second content repository in the VCR, wherein one of the first content repository and the second content repository uses a format specific SPI that is different from the general SPI;

instantiating a software object type in the programming language using the API, wherein the software object type is associated with the link property definition type;

accessing, via an instance of the software object type and the API, said target node from said source node through both the general SPI and the format specific SPI, based on the definition of the link property definition type; and

managing content in the plurality of content repositories based upon the VCR.

10. The machine-readable storage medium as recited in claim 9, further include instructions for carrying out the step of:

receiving a specification of the link property definition type.

11. The machine-readable storage medium as recited in claim 9, further include instructions for carrying out the step of:

blocking creation of property choices for the link property definition type.

12. The machine-readable storage medium as recited in claim 11, wherein the instructions for carrying out the step of blocking creation of property choices for a link property definition type include instructions for carrying out the step of:

blocking specifying default values for a property.

13. The machine-readable storage medium as recited in claim 9, further include instructions for carrying out the step of:

retrieving a property of the first node by at least one of;

retrieving a target node when the target node exists, wherein the target node is a node in the second content repository;

returning null when a target node has not yet been specified; and

raising an exception.

14. The machine-readable storage medium as recited in claim 9, further include instructions for carrying out the step of:

permitting a node which other nodes have as a link property target to be deleted.

15. The machine-readable storage medium as recited in claim 9, wherein the instructions for carrying out the step of managing content in the plurality of content repositories based upon the VCR include instructions for carrying out the step of:

relating the first node to another target node of the plurality of target nodes during operations on the VCR.

16. An apparatus for providing a link property definition type mechanism in a content management system, the apparatus comprising:

a processor; and

one or more stored sequences of instructions which, when executed by the processor, cause the processor to carry out the steps of;

providing a virtual content repository (VCR) with a plurality of content repositories;

associating the VCR with an application programming interface (API), wherein a user of the VCR uses the API to manipulate content in the plurality of content repositories in a programming language;

modeling content in the plurality of content repositories using a general service provider interface (SPI), wherein the general SPI isolates direct interaction with each content repository in the plurality of content repositories from the API;

associating a plurality of format specific content repositories with the general SPI, wherein each format specific content repository is associated with the general SPI through a format specific SPI implementation, and wherein each format specific SPI implementation connects indirectly with the API through the general SPI and provides a different format specific SPI for a different format specific content repository;

providing a link property definition type that relates a plurality of source nodes to a plurality of target nodes, wherein one source node of the plurality of source nodes is a first node within a first content repository in the VCR, and one target node of the plurality of target nodes is a second node in a second content repository in the VCR, wherein one of the first content repository and the second content repository uses a format specific SPI that is different from the general SPI;

instantiating a software object type in the programming language using the API, wherein the software object type is associated with the link property definition type;

accessing, via an instance of the software object type and the API, said target node from said source node through both the general SPI and the format specific SPI, based on the definition of the link property definition type; and

managing content in the plurality of content repositories based upon the VCR.