Abstract: Embodiments implement data and meta data versioning in order to adapt reported data (“actuals”) for planning purposes. A versioning engine receives from an operative system (e.g. ERP system), root variants. These root variants may comprise existing actual data and corresponding underlying corporate meta data. Based upon user input, the versioning engine creates from these root variants, additional variants of the data and/or meta data. A new data variant may be based upon the original corporate meta data unchanged (e.g. for projecting existing product lines). A data variant may alternatively be based upon a new meta data variant reflecting changes to the original corporate meta data (e.g. for adopting an entirely new product line). By effectively depicting relationships between actual data and plan data, and between that data and its underlying meta data, versioning allows a user to visualize evolution of actual data into plan data for forecasting purposes.

Abstract: According to an example, an operation on a version of an electronic content may be performed and a determination as to whether the operation is an editing operation may be made. In response to the operation being an editing operation, a new version may be created and information pertaining to the performance of the operation on the new version may be recorded. In addition, for each significant version, information pertaining to the significant version may be displayed, in which the information may include an identification of the significant version, available operations on the significant version, and a last operation performed on the significant version, in which a significant version may include a version in which no editing operations have been applied or a version in which an operation that is visible to another user has been performed on the version and the operation is outstanding.

Abstract: A coherent file system and method of operation for a file state authority coupled to file state sub-set satellites addresses congestion and latency effects on a plurality of peer workstation clients organized in neighborhoods. Very large files are versioned and metadata recorded in a file state view determines which file blocks make up each version of a committed file. Metadata may be requested from neighboring workstations to locate desired file blocks. File block transmission is minimized to fulfill read requests only when not accessible at a workstation's local file block store.

Abstract: A system and technique for displaying a document's workflow history are disclosed. The system includes a graphical user interface for displaying one or more graphical representations of events generated by an application configured to edit a document. Each of the events generated by the application may be stored in a data structure that is associated with one or more portions of the document. The data structure may also be associated with a digital image that reflects the state of the document at the time the event was generated and one or more frames of digital video captured substantially simultaneously with the generation of the event. The system may display the stored events via graphical representations in the graphical user interface that represent a portion of the total document workflow history. A user may navigate through the graphical events based on a hierarchical algorithm for clustering events.

Abstract: A technique for improving the performance of RCU-based searches and updates to a shared data element group where readers must see consistent data with respect to the group as a whole. An updater creates one or more new group data elements and assigns each element a new generation number that is different than a global generation number associated with the data element group, allowing readers to track update versions. The updater links the new data elements into the data element group and then updates the global generation number so that referential integrity is maintained. This is done using a generation number element that is referenced by a header pointer for the data element group, and which in turn references or forms part of one of the data elements. After a grace period has elapsed, the any prior version of the generation number element may be freed.

Abstract: Data versioning in a non-volatile memory. An object key associated with a data object is created. An index into an object table is generated using the object key. A version number is stored in conjunction with the data object stored in the non-volatile memory. In an object linked-list, the object key and the location information of the data object in the non-volatile memory are stored. A record associated with the data object is created in an object table. The record includes an index, a reference to the object linked-list, and the version number. The index is generated based on the object key.

Abstract: A computer system may comprise a computer platform and input-output devices. The computer platform may include a plurality of heterogeneous processors comprising a central processing unit (CPU) and a graphics processing unit (GPU) and a shared virtual memory supported by a physical private memory space of at least one heterogeneous processor or a physical shared memory shared by the heterogeneous processor. The CPU (producer) may create shared multi-version data and store such shared multi-version data in the physical private memory space or the physical shared memory. The GPU (consumer) may acquire or access the shared multi-version data.

Abstract: A method of merging different versions of a file within a software development system can include, within a first window, presenting a graphic object which indicates a difference between a base version of the file and at least one contributor version of the file. Responsive to a pointing device being located within a defined area surrounding the graphic object, the method can include displaying a floating window having a first section and at least a second section. The first section can include a portion of the base version and the second section can include a portion of the at least one contributor version, wherein the first and second sections of the floating window are selectable. The method also can include receiving a selection of one of the sections of the floating window and accepting the base version or the at least one contributor version according to the selection.

Abstract: Processing a prepared update is disclosed. A prepared update associated with a request that has been used by the sender to update a local version of a data associated with the sender is received from a sender. Based at least in part on an identifier included in the prepared update, a selected data handler is selected among a plurality of data handlers. The selected data handler is used to update a centralized version of the data at least in part by using the received prepared update. The centralized version of the data has been previously updated using a plurality of prepared updates received from a plurality of senders. The updated centralized version of the data is sent to update the local version of the data associated with the sender.

Abstract: A method of managing at least one print media database server for print media attributes of print media is disclosed, the method includes hosting print media attributes for a plurality of image forming apparatuses on the at least one print media database server, and wherein the at least one print media database server contains print media attributes for a plurality of print media from one or more manufacturers; receiving, by the at least one print media database server, additional print media attributes from either of the one or more manufacturers and one of the plurality of image forming apparatuses; confirming accuracy of the additional print media attributes; and enabling, by the at least one print media database server, access to the additional print media attributes in the print media database from the plurality of image forming apparatuses, after the accuracy of the additional print media attributes is confirmed.

Abstract: In accordance with one or more aspects of the application-managed file versioning, a request to store a new version of a file is received from an application, the request having been generated by the application. A filename for the new version of the file is generated, derived from a standardized naming convention. The filename includes a first portion having at least a portion of a name of the file, and a second portion having data indicating that the new version of the file is a version of the file. A set of application programming interfaces (APIs) can be exposed that allow the application to manage file versions, such as creating a new version of a file, identifying one or more versions of the file, listing one or more versions of the file, and deleting one or more versions of the file.

Abstract: A sub-container concurrency component of a tiered middleware framework ensures optimistic concurrency for transactions on hierarchical data containers. The component identifies an uppermost container level of a data read for performing a requested data modification to one or more data containers. The component further reads one or more of a parent version value or a child version value of the data container in the uppermost container level at a first time and a second time. Thus, the component writes data to the one or more data containers when each version value, such as the parent version value or the child version value, read at the first time matches its corresponding read version value read at the second time.

Abstract: The recovery of a transaction, and perhaps the recovery of multiple transactions, in a computing system in which one or more persistent systems are coupled via a bus to one or more processors. As an example, the persistent system may serve as part of the main memory of the computing system. The transaction might implement multi-versioning in which a record is not updated in place. Rather, each record is represented as a sequence of one or more record versions, each version having a valid interval during which that the record version is considered to properly represent the record. Torn write guards may be used to verify that there are no torn writes in the record versions or in the log buffer associated with the transaction.

Abstract: Performing a transaction in the context of a computing system that has one or more persistent systems coupled to one or more processors over a bus. As an example, the persistent system may serve as at least part of the main memory of the computing system. The transaction might implement multi-versioning in which a record is not updated in place. Rather, each record is represented as a sequence of one or more record versions, each version having a valid interval during which the record version is considered to properly represent the record. The transaction processing uses torn write detection so that recovery processes may use such guards to verify that there are no torn writes. For instance, torn write guards may be used to verify the integrity of record versions as well as the log buffers that refer to the record versions.

Abstract: A method and system for providing unified local storage support for file and cloud access is disclosed. The method comprises writing a chunk on a storage server, and replicating the chunk to other selected storage servers when necessary. The method and system further comprise writing a version manifest on the storage server; replicating the version manifest to other selected storage servers when necessary. Object puts or appends are implemented by first chunking the object, determining if the chunks are new, transferring the chunks if required, followed by creation of a new version manifest referencing the chunks. Finally, the method and system include providing concurrent file-oriented read and write access consistent with the stored version manifests and chunks.

Abstract: A method, article of manufacture, and apparatus for protecting data, comprising receiving a changed block, reading a previous backup to get a file list in change block tracking, checking a file in a modified master file table list for a reference flag, wherein the modified master file table list is based on the changed block, and modifying a database entry based on the reference flag.

Abstract: A method, an apparatus, and a computer-readable medium are provided. Whether at least one significant change occurs in a use of at least one word of a group of text documents of a text corpus is determined. A display based, at least in part, on at least one change point corresponding to the at least one significant change is presented when the at least one significant change is determined to have occurred.

Abstract: Searching for objects in a distributed version control system. A method includes accessing a single index. The single index indexes objects in a plurality of pack files. Each pack file is a single object container aggregating the content of what would otherwise be loose objects of a version control system within the single object container such that the single object container includes the aggregated content. The method further includes from the single index, determining a location of a version control system object by determining from the index which pack file from among the plurality of pack files the object is stored in, and a location in the pack file where the object is stored. The method also includes retrieving the version control system object from the pack file.

Abstract: A method and apparatus for managing a number of images. A plurality of resolutions in which the number of images are to be stored and a style of presentation for the number of images is identified using a policy. A plurality of copies of the number of images in the plurality of resolutions are stored. A copy of a particular image in the number of images for a selected location in a layout defining a presentation for the number of images is selected using the style of presentation. The copy of the particular image has a desired resolution in the plurality of resolutions for the selected location in the layout.

Abstract: Disclosed is a method including storing selected historical persist dimension attribute data utilizing a row insertion without updating all previous versions of the selected persist dimension attribute, and generating a view of persisted dimension attribute data as dual values utilizing a star join.

Abstract: Methods, systems, and apparatus, including computer programs encoded on computer storage media, for metadata management. One of the methods includes receiving user input selecting a first node. The method includes receiving a first data lineage of a first object, the first object having a type, the first data lineage describing relationships between the first object and one or more datasets or transforms. The method includes receiving user input selecting a second node. The method includes receiving a second data lineage of a second object, the second object having the same type as the first object. The method includes performing a comparison of the first node and the first data lineage to the second node and the second data lineage. The method includes generating a report based on the comparison.

Abstract: Arrangements described herein relate to managing versions of artifacts stored across disparate tools. In a multi-dimensional configuration space, dimensions can be defined. The dimensions can represent respective variations of respective versions of a plurality of artifacts for at least a first configuration of a system. Via the dimensions, versions of the plurality of artifacts can be mapped to at least a corresponding first configuration of the system, the mapped versions of the plurality of artifacts corresponding to the versions of the artifacts used in the first configuration. The first configuration can be identified by a point in the multi-dimensional configuration space defined by the respective dimensions. At least a first of the plurality of artifacts can be stored by a first tool, and at least a second of the plurality of artifacts can be stored by a second tool disparate from the first tool.

Abstract: Arrangements described herein relate to versioning configurations of reusable artifacts. An artifact baseline corresponding to the present version of a first artifact can be created. Responsive to creating that artifact baseline, the present version of the first artifact, and present versions of children artifacts of the present version of the first artifact, are made immutable. Responsive to identifying a change to the present version of the first artifact, a new version of the first artifact can be automatically created, wherein the new version of the first artifact is mutable.

Abstract: Systems and methods presented here allow recreation of prior scenes, even if assets used in the scenes have evolved over time. The systems and methods employ query of a database to obtain data for backup and retrieval, e.g., information about shots made at prior points in time, where a “shot” refers to a scene or associated set of sequential frames (a single image may also be considered a shot in some instances), rendered or not depending on context. In the VP-VCR systems and methods, information may be obtained about rendered scenes which allow knowledge and subsequent use of each asset employed in the scene, including its proper version and representation at the time of the rendering. Such may be employed not only to obtain prior versions of shots, but also to allow modification of assets in prior shots to obtain new effects.

Abstract: The different advantageous embodiments provide a method for identifying changes in data sets. An ending version for a data set is received. A beginning version for the data set is identified. The ending version for the data set is compared with the beginning version for the data set. A number of differences is calculated between the ending version and the beginning version. A data structure is created that identifies the number of differences between the ending version and the beginning version.

Abstract: Systems and methods for providing mass customized media items, such as songs or other audio items, are provided. Multiple versions of one or more song segments may be generated, as well as a version of a song using each of the segment versions. One or more generated versions of the song may be provided to a user. The song version or versions may be provided in response to a user selection of one or more of the segment versions.

Abstract: Arrangements described herein relate to managing versions of artifacts stored across disparate tools. In a multi-dimensional configuration space, dimensions can be defined. The dimensions can represent respective variations of respective versions of a plurality of artifacts for at least a first configuration of a system. Via the dimensions, versions of the plurality of artifacts can be mapped to at least a corresponding first configuration of the system, the mapped versions of the plurality of artifacts corresponding to the versions of the artifacts used in the first configuration. The first configuration can be identified by a point in the multi-dimensional configuration space defined by the respective dimensions. At least a first of the plurality of artifacts can be stored by a first tool, and at least a second of the plurality of artifacts can be stored by a second tool disparate from the first tool.

Abstract: A method and apparatus for a middleware approach to initializing and updating required data entry fields, pushing such required data entry fields to mobile devices and applications, collecting entered data from such mobile devices, and the synchronizing and integrating of the data is presented. A “form builder” software component of the present invention allows for the creation of easy to read and use data entry forms by company management. A “web application” software component of the present invention allows for the forms to then be distributed via electronic and/or wireless means to mobile client devices, such as PDA's, Tablets, and Laptops, and to Desktop computers. The mobile client devices run applications to utilize the data entry forms and are that into which collected data can be entered. A “synchronization server” software component of the present invention then allows for two-way communication, storage and conflict resolution (versioning) of the collected data.

Abstract: A set of edited changes associated with an editable file is displayed on a display associated with a computing device in response to receipt of a request via a user input device to display the plurality of edited changes. A contextual representation of the editable file is displayed. A context indicator is displayed within the contextual representation of the editable file that represents a location within the editable file associated with a first of the displayed set of edited changes. The context indicator is iteratively updated to represent a location within the editable file associated with each selected element of the displayed set of edited changes in response to detection of user selections of elements of the displayed set of edited changes received via the user input device.

Abstract: A distributed balanced tree having a plurality of nodes distributed across a plurality of servers is accessed. Version information associated with a node of the distributed balanced tree is retrieved. Validity of a lookup transaction performed on the balanced tree is determined by verifying a version value of only the leaf node accessed during the lookup operation against the retrieved version information.

Abstract: The present invention provides systems and methods for determining the originality of data content. In one embodiment, the determined originality of a particular item (e.g., a book) as compared to one or more other items can be used as a factor in recommending the item to a user. For example, in one embodiment, upon a user's selection of an item (e.g., a book), one or more items that have content most diverse from the selected item are determined and provided to the user. In another embodiment, various versions of an item are compared to each other to determine how content in each version differs from that in another version. In another embodiment, content in a collection of items are compared against content from publicly (freely) available sources (e.g., web pages) to determine the originality of the content in the collection of items.

Abstract: Techniques are described herein for using a management pack to define a structure of management packs. A management pack is business logic expressed in terms of an extensible language, such as extensible markup language (XML). Instances of entities that are described by a management pack are stored in an instance space that is defined by the management pack. An entity can be a computer, software program, employee, customer, management pack, management pack element, or anything else in the system that an administrator may wish to describe. A management pack that defines the structure of management packs is referred to as a “management pack management pack” (MPMP). Accordingly, management packs (including MPMPs) having a structure that is defined by a MPMP are stored in an instance space that is defined by the MPMP. The instance space that is defined by the MPMP is materialized in a database.

Abstract: An XBRL taxonomy migration system includes: a processor having a memory on which a program executable by the processor is stored for performing a method of XBRL taxonomy migration; an XBRL taxonomy module including a first version of an XBRL taxonomy having XBRL concepts and a second version of the XBRL taxonomy having related XBRL concepts; and an automated taxonomy migration module that facilitates migrating XBRL concepts of an XBRL document having XBRL tags by replacing XBRL concepts of the first version of the XBRL taxonomy with XBRL concepts of the second version of the XBRL taxonomy.

Abstract: A second program, which becomes inoperable as a result of updating of a first program and operates using the first program, is updated to an operable version using an appropriate update data file. When the version of the second program is not a version operable on the first program, one or more update data files including a full update data file which fully updates the second program to a version of the second program operable on the first program are determined as the update data files. When the version of the second program is a version operable on the first program, one or more differential update data files which do not include any full update data file and update some data files of the second program are determined as the update data files.

Abstract: Calculation of aggregated values in a history database table can be optimized using an approach in which an ordered history table is accessed. The ordered history table can include a sequential listing of commit identifiers associated with updates, insertions, and/or deletions to values in the database table. The ordered history table can be traversed in a single pass to calculate an aggregation function using an optimized algorithm. The optimized algorithm can enable calculation of an aggregated metric of the values based on a selected method for tracking invalidated values to their corresponding commit identifiers. The calculated metric is generated for a current version of the database table; and promoted.

Abstract: A method for retrieving versioned data in a non-volatile memory is provided. The method includes: (1) receiving a read request for a data object, (2) in response to the request, determining, via an object table, whether one or more versions of the data object exist in memory, (3) in accordance with a determination that one or more versions exist in memory, obtaining, via the object table, a respective location where each of the one or more versions of the data object are stored, and (4) reading at least one of the one or more versions of the data object from the respective location into volatile memory.

Abstract: Data can be serialized in such a manner as to facilitate later delta encoding, even when the serialization is performed using a lossy compression algorithm or an algorithm in which portions of the serialized data are encoded relative to other portions which may be modified. This can be achieved by approaches including preserving keyframe information across modified versions of a file, duplicating information from a previously created compressed file when serializing a later version, or adding change information showing differences between versions of a file during the serialization process.

Abstract: The present disclosure provides an advantageous systems and related methods for scalable object storage. One embodiment relates to a system that includes at least a manifest tracking subsystem and a chunk payload subsystem. The manifest tracking subsystem stores version manifests and encodes forward-references from the version manifests to chunks. The chunk payload subsystem stores the chunks and encodes back-references to version manifests that reference the chunk. Other embodiments, aspects and features are also disclosed.

Abstract: A distributed group activity network system and corresponding method over a computer network. It synchronizes and provides access by system users to shared data files of a group activity. The distributed group activity network system comprises one or more server computers and client computers that are connected to the server computer(s) by network connections. Each of the server computers comprises a network server and a memory system. The system modules of the client computers use the memory systems of the client computers and the available basic network services at the server computer(s) to synchronize and provide access to the shared data files by the system users by also using the memory systems of the client computers and the available basic network services at the server computer(s) to synchronize access to and access the synchronization files.

Abstract: Implementations of the present disclosure are directed to a method, system, and storage media for receiving an indication that an attempt to make a modified first version of a directory a current version of the directory in a file system using a consensus protocol did not succeed and, in response thereto, obtaining a most recent second version of the directory including second pointers and a second name associated with each of the second pointers, wherein each second pointer is a reference to an immutable data object in the file system; and identifying one or more of the second names, each identified second name being the same as one of the first names but being associated with a second pointer that is different than the first name's respective first pointer, and obtaining for each identified second name, the data object referenced by the respective second pointer from the file system.

Abstract: An apparatus includes a map data storage device, a map update device, a determination device, and a data production device. The storage device stores map data. The update device reflects a first map update to a first version of the map data to produce a second version of the map data when the first map update occurs. The update device reflects a second map update to the second version of the map data to produce a third version of the map data when the second map update occurs after the first map update. The determination device determines whether the first and second map updates depend on each other. The production device produces map differential data from the first and second map updates when the determination device determines that the first and second map updates depend on each other.

Abstract: A computer-implemented method for data management of product variants in control unit development is provided. Consistent data management is ensured by initially specification of product features in a variant model, specification of components in at least one domain, and definition of feature/component dependencies by associating components with at least one product feature, and subsequently specification of at least one product variant of interest by selecting product features, specification of at least one domain of interest, automated identification of the components pertaining to the product variant of interest through automated evaluation of the feature/component dependencies, and automated output of the identified components.

Abstract: System and methods for storage object distribution using dynamic policy controls are provided. An embodiment method deleting an object in a distributed storage system includes receiving, from a client, a delete request for an object, retrieving, by a primary datacenter, an object metadata list corresponding to the object to be deleted, and inserting, by the primary datacenter, a delete marker on a top of a stack data structure in an object metadata list.

Abstract: A method for managing data, the method includes: providing a write-back cache unit coupled to at least one storage unit; receiving a request to write a new data version to a certain cache data allocation unit; determining, in response to a data storage policy, whether to overwrite a cached data version being cached in the certain cache data allocation unit or to perform a destage of the cached data version to a first storage unit before writing the new data version to the certain cache allocation unit; receiving a request to read a data version that corresponds to a certain point in time and scanning a first data structure representative of write operations and a second data structure representative of revert operations to determine a location of the requested data version.

Abstract: Example systems and methods of upgrading a single-database, multiple-tenant software system are presented. In one example, a target database schema for a target version of the software system is created. For each tenant of a current database schema for a current version of the software system, a current state of the data corresponding to the tenant in the current database schema is captured. The data corresponding to the tenant is transitioned from the current database schema to the target database schema. The tenant in the target database schema is tested to verify the tenant. If the tenant in the target database schema is verified, the tenant in the target database schema is opened for users. If not verified, the tenant in the current database schema is restored using the captured state.

Abstract: A method and apparatus for of storing data comprising monitoring a plurality of storage units within a mass storage area and detecting when a storage unit within the mass storage area is overloaded. The method further comprising randomly distributing the data on the overloaded storage unit to the other storage units within the mass storage area.

Abstract: Information describing a transaction is received and a set of hierarchical documents pertinent to the transaction are identified based at least in part on the received information. The set of hierarchical documents is pruned responsive to data describing documents that a user involved in the transaction has previously accepted. Information describing the pruned set of hierarchical documents is output for presenting the pruned set of hierarchical documents to the user involved in the transaction for acceptance as part of the transaction.

Abstract: A device may store information associated with a group of items in a database. The information associated with a particular item may include a group of versions of a particular attribute. A particular version of the particular attribute may include a value associated with the particular attribute and a timestamp. The device may receive a query that specifies a time; determine that the query is associated with the particular item; and determine, based on the specified time, which version of the particular attribute is associated with the query. The device may determine which version of the particular attribute is associated with the query by identifying, based on the timestamps associated with the versions of the particular attribute, a version of the particular attribute that is a newest version, of the versions of the particular attribute that are associated with timestamps that are before or concurrent with the specified time.

Abstract: In an illustrative embodiment, an apparatus, computer-readable medium, or method may be configured to manage a configuration. Files may be inserted into a file container in a computing environment and state information on the files may be stored. A change to a file in the file container may be received. A comparison result may be obtained by comparing a previous version of the file container to the file container after receiving the change to the file. The comparison result may be provided.

Abstract: A method of determining print media attributes of print media, which includes the following steps: obtaining information from a package of print media using an image recognition system associated with the image forming apparatus; sending the information via a network connection to at least one print media database server for determination of print media attributes for the package of print media; determining the print media attributes of the package of print media by matching the information obtained from the image recognition system to a print attribute database hosted by the at least one print media database server, the print attribute database containing print media attributes for a plurality of print mediums, which are available to a plurality of image forming apparatuses; and sending the print media attributes for the package of print media to the image forming apparatus, which generates printer configuration settings for the print media.