Patent application number | Description | Published |
20100100567 | Processing of a generalized directed object graph for storage in a relational database - Creating transaction instructions is disclosed. A description of a set of objects is received. For each of at least a subset of objects in the set of objects, a description of one or more associated relationships is received. The description of the set of objects and the descriptions of the one or more associated relationships for each object in the at least a subset of the set of objects are processed to create an ordered list of transaction instructions for storing the set of objects and the one or more associated relationships for each object in the at least a subset of the set of objects. | 04-22-2010 |
20110202569 | PROCESSING OF A GENERALIZED DIRECTED OBJECT GRAPH FOR STORAGE IN A RELATIONAL DATABASE - Creating transaction instructions is disclosed. A description of a set of objects is received. For each of at least a subset of objects in the set of objects, a description of one or more associated relationships is received. The description of the set of objects and the descriptions of the one or more associated relationships for each object in the at least a subset of the set of objects are processed to create an ordered list of transaction instructions for storing the set of objects and the one or more associated relationships for each object in the at least a subset of the set of objects. | 08-18-2011 |
20110246542 | SYSTEM FOR LIGHTWEIGHT OBJECTS - Creating an object is disclosed. An instance of a sharable type is created. An instance of a lightweight type is created. The sharable type is designated as a parent of the lightweight type. The instance of the sharable type is designated as a parent of the instance of the lightweight type. The instance of the sharable type may be shared by one or more other instances of the lightweight type. | 10-06-2011 |
20120110024 | IDENTIFIERS FOR NON-SEARCHABLE ATTRIBUTES - An attribute is received for storage. Whether the attribute is searchable or non-searchable in storage is determined. Storing the attribute as a searchable attribute comprises storing the attribute in a database table corresponding to a hierarchical class-based object. Storing the attribute as a non-searchable attribute comprises storing the attribute together with one or more other non-searchable attributes as a set of attributes. The set of attributes is stored in a database location outside the database table corresponding to the hierarchical class-based object, and the database location is accessed before the database table. A unique attribute identifier is associated with the attribute to distinguish between a name of the attribute and a name of one of the one or more other non-searchable attributes in the event that the name of the attribute and the name of the one of the one or more other non-searchable attributes are assigned the same name. | 05-03-2012 |
20120110029 | DATA MODEL FOR SERVICE ARCHITECTURE - Processing for a data package is disclosed. An operation is received including a data package. The operation is performed with respect to each of one or more data objects included in the data package, in a manner determined at least in part by a context data applicable to the operation. | 05-03-2012 |
20120124097 | REUSING SYSTEM CONFIGURATION INFORMATION AND METADATA FOR RELATED OPERATIONS - Reusing system configuration information and metadata for related operations is disclosed. It is determined that a group of content management system commands may be treated as a related set for purposes of updating content management system configuration information and/or metadata. The content management system configuration information and/or metadata are updated once for purposes of processing the group. | 05-17-2012 |
20120185504 | RETRIEVAL OF SEARCHABLE AND NON-SEARCHABLE ATTRIBUTES - Retrieving stored data is disclosed. A retrieval request is received for an object. A retrieval response is generated that includes: 1) a first set of searchable attributes associated with the object, wherein an attribute of the first set of attributes is stored in a database in a manner that enables a database query to be performed against the attribute of the first set of attributes; and 2) a second set of non-searchable attributes associated with the object, wherein an attribute of the second set of attributes is stored in the database in a manner that does not enable a database query to be performed against the attribute of the second set of attributes. | 07-19-2012 |
20120185514 | OPTIMIZED FETCHING FOR CUSTOMIZATION OBJECT ATTRIBUTES - An attribute of a hierarchical class-based object is received. The attribute in a database is stored both in a first location in a first table at a first level of a hierarchy of database tables which table hierarchy is based at least in part on a class hierarchy associated with the hierarchical class-based object and in a second location in a second table at a second level of the table hierarchy which second level is higher than the first level. | 07-19-2012 |
20120254848 | DEPLOYING AND DISTRIBUTING CONTENT MANAGEMENT CODE - Deploying and distributing content management code is disclosed. A software object class is received at a repository. The software object class is stored at the repository. The software object class is downloaded from the repository to an application server associated with the repository. | 10-04-2012 |
20120290623 | EFFICIENT STORAGE OF NON-SEARCHABLE ATTRIBUTES - Storing data is disclosed. An attribute is included in a combined set of attributes. The combined set of attributes is stored in one or more database locations not specific to any one attribute in the combined set. | 11-15-2012 |
20120330917 | BATCHING CONTENT MANAGEMENT OPERATIONS TO FACILITATE EFFICIENT DATABASE INTERACTIONS - Batching content management operations to facilitate efficient database interactions is disclosed. Two or more content management-related requests are received. The two or more content management-related requests are treated as a batch, including by formulating and sending to a database in a single database interaction a grouped request to add, delete, or modify each of a plurality of database records. | 12-27-2012 |
20130125146 | IN PLACE OBJECT RECONSTRUCTION - Updating an implementation object is disclosed. A proxy is configured to provide access to a first implementation object that is used to manage an item of content included in a collection of managed content. The first implementation object is replaced with a second implementation object. The proxy is associated with the second implementation object. | 05-16-2013 |
20130151733 | REUSING SYSTEM CONFIGURATION INFORMATION AND METADATA FOR RELATED OPERATIONS - Reusing system configuration information and metadata for related operations is disclosed. It is determined that a group of content management system commands may be treated as a related set for purposes of updating content management system configuration information and/or metadata. The content management system configuration information and/or metadata are updated once for purposes of processing the group. | 06-13-2013 |
20130179463 | RETRIEVAL OF SEARCHABLE AND NON-SEARCHABLE ATTRIBUTES - Retrieving stored data is disclosed. A retrieval request is received for an object. A retrieval response is generated that includes: 1) a first set of searchable attributes associated with the object, wherein an attribute of the first set of attributes is stored in a database in a manner that enables a database query to be performed against the attribute of the first set of attributes; and 2) a second set of non-searchable attributes associated with the object, wherein an attribute of the second set of attributes is stored in the database in a manner that does not enable a database query to be performed against the attribute of the second set of attributes. | 07-11-2013 |
20130297637 | OBJECT IDENTITY AND ADDRESSABILITY - Identifying a repository object is disclosed. An object identifying information usable to identify a repository object with respect to which an operation is desired to be performed is included in a request not specific to any one manner of identifying objects. The request is sent to a node associated with a repository in which the repository object is or will be stored. At the receiving end, e.g., a content server, the object identifying information included in the request is used to identify the repository object with respect to which the operation is desired to be performed, for example to retrieve the repository object. | 11-07-2013 |
20140059080 | SYSTEM FOR LIGHTWEIGHT OBJECTS - Creating an object is disclosed. An instance of a sharable type is created. An instance of a lightweight type is created. The sharable type is designated as a parent of the lightweight type. The instance of the sharable type is designated as a parent of the instance of the lightweight type. The instance of the sharable type may be shared by one or more other instances of the lightweight type. | 02-27-2014 |
20140074917 | REUSING SYSTEM CONFIGURATION INFORMATION AND METADATA FOR RELATED OPERATIONS - Reusing system configuration information and metadata for related operations is disclosed. It is determined that a group of content management system commands may be treated as a related set for purposes of updating content management system configuration information and/or metadata. The content management system configuration information and/or metadata are updated once for purposes of processing the group. | 03-13-2014 |
20140181059 | BATCHING CONTENT MANAGEMENT OPERATIONS TO FACILITATE EFFICIENT DATABASE INTERACTIONS - Batching content management operations to facilitate efficient database interactions is disclosed. Two or more content management-related requests are received. The two or more content management-related requests are treated as a batch, including by formulating and sending to a database in a single database interaction a grouped request to add, delete, or modify each of a plurality of database records. | 06-26-2014 |
20140189715 | CONVERSION OF LIGHTWEIGHT OBJECT TO A HEAVYWEIGHT OBJECT - Processing an object that shares a parent with another object is disclosed. An indication is received with respect to an object that shares a parent object instance with one or more other objects that a change associated with the object is to be made to a data comprising the shared parent object instance. The parent object instance is cloned to create a new parent object instance. The new parent object instance is designated as the parent of the object instance. | 07-03-2014 |