Abstract: Retention of complex objects is disclosed. An indication is received that retention applied to a root object of a complex object is to be extended to child objects, such as attachments or included files or other content. A snapshot of at least the child objects is stored and the retention that is applied to the root object is extended to the snapshot. Retention of the snapshot ensures that the child objects are retained, so long as and in the same manner as the root object, in the form (e.g., version) in which they are stored at the time retention is applied to the snapshot.

Abstract: A content management system (CMS) uses an element deletion mechanism to maintain referential integrity of dynamically assembled elements in a repository. Element properties such as probability, popularity and recent usage that are not explicit relationships between parent documents and child elements are logged. A deletion policy is then defined in terms of the logged element properties. When a request to delete an element is received, the deletion mechanism checks the logged properties against the deletion policy. If the element's logged properties satisfy the deletion policy, the element is deleted from the repository. If the element's logged properties do not satisfy the deletion policy, the element is not deleted. In this manner referential integrity may be enforced for elements that are dynamically assembled.

Abstract: Techniques involve storing digital assets in a distributed digital asset management environment. The techniques includes (a) receiving, by a server from a client, an asset identification tag associated with an original version of a digital asset which is initially created and stored on the client; (b) identifying, by the server and in response to receiving the asset identification tag, a risk-management policy corresponding to the client and the digital asset; (c) executing an action dictated by the risk-management policy; and (d) transmitting, by the server to the client, a transfer command which identifies the digital asset and directs the client to transfer the digital asset from the client to the server. The techniques further include (e) obtaining, by the server from the client, a copy of the digital asset while the client concurrently deletes the original version of the digital asset in response to the transfer command.

Abstract: A technique is described that reduces the complexity and resource consumption associated with performing record expiry in a distributed database system. In accordance with the technique, a record is checked to see if it has expired only when it has been accessed for a read or a write. If at the time of a read a record is determined to have expired, then it is not served. If at the time of a write a record is determined to have expired, then the write is treated as an insertion of a new record, and steps are taken to treat the insertion consistently with regard to the previous expired version. A background process is used to delete records that have not been written to or actively deleted by a client after expiration.

Abstract: In a system having a plurality of caches, a method for maintaining cached objects includes storing an object in a plurality of caches. In response to a request to update the object, a future invalidation time is determined when the object should be invalidated in caches currently storing the object. Updating of the object is delayed until the invalidation time has passed.

Abstract: Systems and/or methods for storing and/or retrieving assets in connection with an extremely large scale computer storage system are provided. An asset catalog may comprise a plurality of asset catalog entries stored according to at least one schema and corresponding to a plurality of assets. A storage architecture may be capable of storing the plurality of assets, with the storage architecture comprising a storage locator and a federator. An item identification scheme may be capable of providing identifiers to reference, locate, and/or access said assets and/or said asset catalog entries stored in the asset catalog in the storage architecture. The computer storage system may be scalable essentially without limitation while maintaining asset storage and retrieval flexibility and substantially obsolescence-proof survivability of assets.

Abstract: An example method may obtain a request to delete a plurality of data items satisfying a first condition from a database, and request a retrieval of a first database item from a first predefined storage block associated with the database based on a query including a negation of the first condition. It may be determined whether the first database item is retrieved from the first predefined storage block in response to the requesting the retrieval of the first database item from the first predefined storage block. When it is determined that the first database item is not retrieved, deletion of the first predefined storage block may be requested, else deletion of each one of the plurality of data items satisfying the first condition from the first predefined storage block may be requested.

Abstract: An apparatus and method efficiently delete a first items within a distributed datastore. In particular, an already well defined procedure for insertion of data is used for deletion. Deletion of a first item is effected through the insertion of a second item. The second item can contain a deletion key or be denoted by an appended flag or modified associated meta-data value. The first item can be deleted upon arrival of the second item or subsequent to arrival through an offline garbage collection process.

Abstract: A method of synchronous deletion of managed files in a file system includes receiving a destroy event for a file to be deleted from the file system, the destroy event being generated upon request to destroy a file or corresponding objects of the files system; processing the received destroy event. Processing the destroy event includes determining if hierarchical storage management of the file system is initiated, and if initiated, continuing processing of the received destroy event; blocking threads indefinitely for an event storm during processing of the received destroy event; determining if the file to be deleted is being premigrated, migrated or is being recalled; aborting migration of the file based on the determination of migration and recall; and deleting the file and server objects corresponding to the file from the file system, where initiation of file deletion and server object deletion are synchronous.

Abstract: Systems, methods, and software for archiving structured data and associated unstructured data associated are disclosed. Particularly, the structured and unstructured data are archived such that the structured data and the unstructured data remain associated to each other. Properties of the structured data are also applied to the unstructured data, enabling the unstructured data to be retained with the structured data throughout the retention period of the structured data. Moreover, destruction (or prevention of destruction) of the archive data object can be managed and propagated to the unstructured data instances.

Abstract: In a network system including a server apparatus, client apparatus, and database, when a registration request of catalog data of a catalog is received from the client apparatus, the catalog data is registered in the database as one file of the catalog. When a registration request of merchandise information to be associated with the catalog data is received from the client apparatus, the merchandise information is registered as one page of the catalog data. Hence, the merchandise information of the catalog can be associated with catalog data of each page.

Abstract: A system, method, computer program and system for suspending a result set and continuing from a suspended result set for a scrollable cursor is disclosed. The rows from a row source corresponding to the scrollable cursor result set are suspended into storage so that when a fetch is requested the data can be sent (continued) from the suspended storage and does not depend on the original scrollable cursor row source or session to be available.

Abstract: A method by which a disk-based distributed data storage system is organized for protecting historical records of stored data entities. The method comprises recording distinct states of an entity, corresponding to different moments of time, as separate entity versions coexisting within the distributed data storage system, and assigning expiration times to the entity versions independently within each of a plurality of storage sites according to a shared set of rules, before which times deletion is prohibited.

Abstract: Embodiments presented herein provide systems and methods for managing data decay. A system is provided for maintaining metadata about data attributes or relationships between data. A data decay engine can read the metadata and perform a decay calculation. The type of decay calculation can be associated with the type of data or be determined from user inputs. The decay engine can provide a score as to the staleness of the data. An update engine can determine specific data attributes that may require updating. The update engine may be able to update the data from external data sources.

Abstract: File retention is performed based on a retention attribute. Information indicating creation of an electronic file is received, and a retention attribute is generated for the electronic file. The retention attribute indicates how long the electronic file should be retained. Retention of the electronic file is monitored based on the retention attribute. The retention attribute may indicate a minimum time period for retaining the electronic file and/or a maximum time period for retaining the file. The electronic file may be automatically destroyed after the maximum time period for retaining the file, or an indication may be provided whether to retain or destroy the electronic file based on the retention attribute and how long the electronic file has been retained Retention of hard copies of electronic files may be performed in a similar manner.

Abstract: A method for managing medias of an electronic device is provided. The method includes: detecting whether a communication connection between the electronic device and the computer is established; searching a first type of medias of electronic device if yes; moving the first type of medias from the electronic device to the computer; searching a second type of medias of the computer; and downloading the second type of medias from the computer to the electronic device. An electronic device executing the method is also provided.

Abstract: A method and apparatus for managing synchronization configuration files at a computing device is provided. It is determined that at least one configuration file has expired, the at least one configuration file associated with a second computing device and comprising data for synchronizing the second computing device with the computing device. A location of the at least one configuration file is then determined. The at least one configuration file is then deleted at the location.

Abstract: Techniques to manage retention policy tags are described. A system may comprise a tagging component operative to tag a message with an expiration tag to form an expiration tagged message, the expiration tag having expiration information used to expire the expiration tagged message in accordance with a retention policy. The system may further comprise a presentation component communicatively coupled to the tagging component, the presentation component operative to present a view of the expiration tagged message with an expiration field having the expiration information for the expiration tagged message. Other embodiments are described and claimed.

Abstract: A storage unit stores flow definition data defining process flow of at least one process for data input from a data input apparatus. A communication unit controls transmission/reception of data between the data input apparatus and an arbitrary apparatus connected via a network. A flow-execution control unit controls execution of the at least one process based on the flow definition data. A flow-definition-data control unit defines an upload mode to avoid a data overwrite when a file of an identical name exists upon uploading the data to the arbitrary apparatus, sets the upload mode in the flow definition data, and stores it in the storage unit.

Abstract: This disclosure describes techniques of managing electronic documents as electronic records that do not require moving the electronic documents to a different repository. As described herein, an electronic document is stored at a first repository prior to a time when the electronic document is declared to be an electronic record. An administrator is able to configure a document management system (DMS) to manage the electronic document as an electronic record after the electronic document is declared to be an electronic record. In addition, the administrator is able to configure the DMS to store a copy of the electronic document at a second repository after the electronic document is declared to be an electronic record and to manage the copy of the electronic document as an electronic record.