Abstract: Described herein are methods and system for electronic file management having a central server that periodically scans files accessible to multiple computers to identify every file stored onto multiple electronic data repositories. The central server then executes a predetermined protocol to generate a unique identifier for each identified file. The central server then generates an interconnected nodal data structure computer model where each node represents an identified file and where the nodes are linked based on their respective files having similar unique identifiers. The central server periodically scans the electronic data repositories to identify related data. When a related file is identified, the central server modifies the nodal data structure accordingly. When a user requests access to a file, the central server displays all related data to the requested file.

Abstract: Systems and methods for synchronizing data between a customer data management system and a data warehouse system. A data warehouse server may constantly monitor a dynamic metadata flow from the customer data management system, compare it with the metadata in the data storage device, and dynamically update the metadata in the data storage device. The data warehouse server may track activities over time and accumulate a long running history, which may include multiple versions of accounts in the customer data management system, e.g., the account as of today, the account as of yesterday, and another version that was the account two weeks ago.

Abstract: Example systems and methods for cloning catalog objects are described. In one implementation, a method identifies an original catalog object associated with data and creates a duplicate copy of the original catalog object without copying the data itself. The method allows access to the data using the duplicate catalog object and supports modifying the data associated with the original catalog object independently of the duplicate catalog object. The duplicate catalog object can be deleted upon completion of modifying the data associated with the original catalog object.

Abstract: Embodiments permit searching across different system landscapes, for data associated with master data objects. A map is constructed comprising (explicit, inferred) connections between different pieces of data located in various databases, systems, and landscapes. In certain embodiments the map is constructed utilizing a parameter (e.g., family name) present in a received query, as a boundary condition. The map may be in tabular form, and may conform to a particular notation scheme. Once the map is constructed, the query is executed thereupon to search for relevant data. The corresponding query result is received and stored, ultimately for communication back to the user posing the original query. Embodiments may be particularly suited to returning private data of a unique entity (e.g., natural person, corporation, juristical person) that is stored over a variety of different master data objects (e.g., employee, customer, supplier) and across complex system landscapes.

Abstract: Various techniques for managing heat and backwards-incompatible updates in cloud-based networks are described. In an example method, a virtualized resource, is identified. At least one first host may include an updated version of an element and at least one second host may include a previous version of the element. The updated version may be incompatible with the previous version. A first desirability index corresponding to the at least one first host may be less than a second desirability index corresponding to the at least one second host. The virtualized resource may be live-migrated from the source host to a target host among the at least one first host.

Abstract: Methods and systems for reducing the amount of time to restore a database or other application by dynamically generating and storing synthetic snapshots are described. When backing up a database, an integrated data management and storage system may acquire snapshots of the database at a snapshot frequency and acquire database transaction logs at a frequency that is greater than the snapshot frequency. In response to detecting that the database is unable to provide a database snapshot, the integrated data management and storage system may generate a synthetic snapshot of the database by instantiating a compatible version of the database locally, acquiring a previously stored snapshot of the database, applying data changes from one or more database transaction logs to the previously stored snapshot to generate the synthetic snapshot, and storing the synthetic snapshot of the database within the integrated data management and storage system.

Abstract: Information source agent systems and methods for distributed content storage and management using content signatures that use file identicality properties are provided. A data management system is provided that includes a content engine for managing the storage of file content, a content signature generator that generates a unique content signature for a file processed by the content engine, a content signature comparator that compares content signatures and a content signature repository that stores content signatures. Information source agents are provided that include content signature generators and content signature comparators. Methods are provided for the efficient management of files using content signatures that take advantage of file identicality properties. Content signature application modules and registries exist within information source clients and centralized servers to support the content signature methods.

Abstract: Systems and methods are provided for master-to-master OT-based artifact peering. A “master-to-master” architecture for artifacts is implemented in a network comprising a plurality of nodes and clients, where no node is designated a “master” or “primary” for a given artifact. A first node receives a subset of remote proposed operations from a second node and determines if a conflict exists between the received subset of remote proposed operations and at least one of a plurality of locally-proposed operations. The first node resolves the conflict based on a total-ordering agreed upon between the first node and the second node. The first node transforms at least one operation, either received or locally-proposed, based on the resolved conflict. The first node than updates a local log to include the transformed operation.

Abstract: In some aspects, multi-slot transport block (TB) configurations for communicating data between wireless devices, such as between a base station and a user equipment (UE), in a wireless communication system are described. Some examples of multi-slot configurations enable the communication of large payloads. For example, an application of a wireless device may jointly process data from a large file or other large set of packets. In such examples, the wireless device transmitting the large file may utilize a multi-slot TB including multiple TB segments corresponding to respective slots of a transmission. Similarly, a wireless device receiving the large file may utilize the multi-slot TB configuration for receiving the data.

Abstract: A system (100) for Partial Unstructured Information Processing, constituting storing, indexing, querying and retrieval of partially specified unstructured data, the system (100) comprising: Quantum Clustering Algorithm (101) that partitions data records in different clusters such that the data in each cluster can be indexed efficiently, a Compressed Ternary Tree (111, 112, 113) that replaces all conceivable indices for each cluster thereby solving the Unthinkable Query Problem (110) for each cluster, and a Virtual Query Processor (120) that converts traditional data base queries to raw Compressed Ternary Tree queries and appropriate filters (121, 122, 123).

Abstract: Example systems and methods for cloning catalog objects are described. In one implementation, a method includes copying first metadata of a first catalog object to create second metadata of a second catalog object such that a second portion of the second metadata and a first portion of the first metadata are associated with same data of a same data file, and generating a response to a data storage or data retrieval request directed to the first catalog object by accessing the data file using the second metadata of the second catalog object.

Abstract: A computing system may determine different patterns of modifications that are to be made to data of a file to generate respective modified versions of the file, the different patterns of modifications enabling identification of other files derived from the respective modified versions of the file, the different patterns of modifications including a first pattern of modifications. The computing system may generate a first modified version of the file at least in part by modifying the data based on the first pattern of modifications, may send the first modified version of the file to a client device, and may store signature data indicative the first pattern of modifications so as to enable identification of other files derived from the first modified version of the file.

Abstract: An information processing device, includes a memory; and a processor coupled to the memory and configured to: generate second data by adding, to first data including a machine language, first machine language data that may be destroyed at a time of transfer of the first data and second machine language data that is not destroyed at the time of the transfer, and transmit the second data.

Abstract: A system, methods, and apparatus for point-in-time requirement tracking are disclosed. In an example embodiment, requirements for a project are stored in a database communicatively coupled to a server, the requirements including at least a first requirement stored in a first record and a second requirement stored in a second record. The server receives changes to the first requirement and the second requirement during the edit session and stores the changed first requirement to a third record and the changed second requirements to a fourth record. The server then provides the first and third records to a client device so that the client device can concurrently display the first requirement as specified in the first record and the first requirement as specified in the third record.

Abstract: A branch of a main database is created, comprising a copy of the main database schema. A user edits the branch and requests that it be merged back into the main database. A schema diff is generated and used to determine differences between the main database and the edited branch. The merge is performed if it does not create a conflict. A second branch is created and edited by a second user. When the second user indicates to merge the second branch back into the main database, differences between the two branches are determined, relative to the main database. If merging the second branch back into the main database on top of the first branch does not create a conflict, a three-way merge is performed of the first branch, the second branch, and the version of the main database from which the first and second branches were generated.

Abstract: A secondary device receives presence information for a content item that is synchronized by a content management system with the secondary device and with a primary device. If a user of the primary device is present as indicated by the presence information, a collaboration element is displayed on the secondary device. Responsive to a user input at the collaboration element, a collaboration request is sent to the primary device, and collaboration information enabling collaborative interaction with an instance of the content item on the primary device is received.

Abstract: An approach for determining similar text documents. The approach can calculate a first set of vectors for a first cluster of text documents and a first comparison vector for a text document of interest. The approach can select a subset of text documents from the cluster of text documents based on comparing the vectors from the first set of vectors to the first comparison vector and picking a predetermined number of closest comparison text documents. The approach can calculate a second set of vectors for the subset of documents and second comparison vector for the document of interest. The approach can generate similarity ratings for the subset of documents based on pairwise comparisons of the second comparison vector and the second set of vectors. The approach can generate a ranked list of the second cluster of text documents based on the similarity ratings.

Abstract: A computer software program for improving electronic spreadsheets to manage and control scenarios. The program provides methods for the user to record specific changes made to selected value of cells in the spreadsheet. Each recorded item can be dragged and re-ordered via a graphical user interface (GUI) to build up a scenario script. The script can be executed whereby the spreadsheet is updated with the recorded items. The method allows complex scenarios to be played back in step by incremental step, modified, re-ordered, corrected, and re-played while generating user-defined output reports & charts detailing each step change. The method provides a detailed information trail of all value changes made to the spreadsheet suitable for an independent third-party review. Different scenario components can be recorded in parallel by multiple users and then merged to produce a complete solution.

Abstract: A multiple interface data exchange system utilizes a persistent in-memory storage in asynchronous data communication with a plurality of interfaces. Each interface is configured to communicate with at least one application using a particular communication protocol. The persistent in-memory storage stores tuple data sets received from applications transmitting data to the connected interface in a canonical (universal) format, automatically creating new tuples and updating existing tuples. The canonical format of the data is quickly queried in the persistent in-memory storage and available to other applications in connection with the multiple interface data exchange system regardless of the communication protocol used by a requesting application.

Abstract: One example method of operation may include identifying a plurality of active project files in a database, identifying one or more deliverables included in the plurality of active project files, performing a simulation test based on a current set of allocated resources and a current set of deadlines associated with each of the one or more deliverables to determine whether the one or more deliverables will fail, determining the one or more deliverables includes one or more failed project risk metrics indicating that the one or more deliverables will fail to be completed by a corresponding deadline among the current set of deadlines, selecting one or more of the active project files which does not have a failed project risk metric, and reallocating resources, from the one or more of the active project files which does not have a failed project risk metric, to one or more of the active project files which has one or more failed project risk metrics.

Abstract: The present disclosure provides a generic multi-source heterogeneous large-scale data system, including a sync node config unit, an install & deployment unit, a block & pipelining unit, a unilateral sync unit, a bilateral sync unit and a correctness guarantee unit. The system operates on a middle layer which is above a node database layer and beneath an application logic layer. In a data synchronization process, a client end transmits captured local change information to a server end in accordance with a synchronization task plan; the server end receives and transfers the change information to an asynchronous parallel message processing mechanism to be stored in a corresponding message queue; the server end polls a local message queue for reading to-be-processed change information, and then performs subsequent data change in accordance with rules for heterogeneous data mapping, so as to maintain consistence of synchronized data objects between a source end and a target end.

Abstract: A system, method, and apparatus for implementing workflows across multiple differing systems and devices are provided herein. During operation a workflow is automatically generated upon the detection of new device capabilities. In particular, a workflow server will detect the presence of new device capabilities in a particular area. The new device capabilities will be analyzed, and an appropriate trigger and action will be determined based on the new device capabilities. The appropriate trigger and action will then be implemented as a newly-created workflow.

Abstract: Described herein is a computer implemented method. The method comprises receiving, by an issue tracking system, a deployment update from a deployment system which includes deployment information in respect of one or more issues maintained by the issue tracking system. The method further comprises associating one or more issues maintained by the issue tracking system with deployment information by identifying the one or more issues to which the deployment information in the deployment update relates, extracting the deployment information from the deployment update, and associating the deployment information with each of the identified issues.

Abstract: In an approach to linking operational data with issues, a new event is received. The new event is associated to a story, where the story is related to an identified problem within the system, and further where the new event is associated with the story using machine learning techniques. The story is associated to related change requests based on a similarity between the story and related change requests, where the similarity between the story and the related change requests is associated using the machine learning techniques. A cost is calculated for the story. Responsive to associating the new event with a specific change request, the priority of the specific change request is updated based on the cost for the story.

Abstract: A data attack detection system that includes a record host and an orchestration host. The record host stores account information for card holders. The orchestration host includes a switch interface configured to receive transaction information for a card from a network. The orchestration host further includes a velocity trap engine that stores received transaction information for the card in a cardholder file. The velocity trap engine creates entries in a velocity transaction timestamp record for the card when the number of transactions for the card in the cardholder record within a first predetermined time interval exceeds a first activity level threshold. The velocity trap engine discontinues a transaction flow between the orchestration host and the record host for the card when the number of transactions for the card in the velocity transaction timestamp record within a second predetermined time interval exceeds a second activity level threshold.

Abstract: The disclosed embodiments provide a system for processing data. During operation, the system obtains a function call for a function that calculates an attribute associated with a machine learning model. For each argument of the function call, the system identifies a parameter type of the argument, wherein the parameter type represents a type of data used with the machine learning model. The system also obtains a value accessor for retrieving features specific to the parameter type and obtains a value represented by the argument using the value accessor. The system then calculates the attribute by applying the function to the value and uses the attribute to execute the machine learning model.

Abstract: Techniques are described herein for handling transactions where only a portion of submitted changes are committed. In some embodiments, a system receives, through a page of a user interface, a request to submit a plurality of changes to a set of data objects. The system identifies, based on the page of the user interface through which the request was submitted, a first subset of one or more changes that require further review and a second subset of one or more changes that do not require further review before being committed to the database. The first subset of one or more changes are cached for further review, and a respective approval transaction may be initiated. A commit transaction may be initiated directly for the second set of one or more changes to commit the changes to the database without further review.

Abstract: A system communicates a client application and a web application and receives configuration data operable within the web application and the client application. The system distributes the configuration data to the client application and the web application. The distributed configuration data is then used to configure the client application and the web application.

Abstract: A system includes a memory and a processor. The processor is configured to determine a first cluster configuration for a particular service that is running on both a first and a second computing clusters. The first cluster configuration includes a first configuration value for configuring the particular service to run on the first computing cluster. The processor is further configured to determine a second cluster configuration for the particular service that is running on both the first and second computing clusters. The second cluster configuration includes a second configuration value for configuring the particular service to run on the second computing cluster. The first configuration value is different from the second configuration value. The processor is further configured to send one or more instructions to the second computing cluster in order to change the second configuration value to match the first configuration value.

Abstract: In one embodiment, a method includes at a mapping server receiving from a plurality of regional servers a plurality of regional magnetic data sets; at the mapping server updating a geomagnetic map with one or more of the regional magnetic data sets, wherein the geomagnetic map comprises one or more of the geographic regions; and from the mapping server communicating one or more portions of the geomagnetic map as updated to one or more of the regional servers for distribution as geomagnetic map information to one or more of the magnetic navigation devices for localization or navigation.

Abstract: A method of using artificial intelligence to provide source code from an original programming language in a target programming language showing regions of low confidence. The method includes receiving, by a computing device, a code base in an original programming language. The computing device further provides the code base in the original programming language to a target programming language using an artificial intelligence tool. The computing device additionally displays the code base in the target programming language using a visualization tool in a visual interface. The computing device still further displays the regions of uncertainty to a human user in the visual interface. The regions of uncertainty provide low confidence regions of the code base in the target programming language for targeted user intervention. The regions of low confidence correlate with violations to provide displayed actionable insight regions.

Abstract: Techniques for modifying application behavior at run-time are disclosed. The application behavior is controlled as a function of an application definition schema that is deployed and maintained independently of the application. The application definition schema maps tasks to operations, object types, layouts, and/or fields. A change in the application definition schema results in a change, for example, in the operations performed by an application to complete a task.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable media for an improved database management system that provides database transactions on a non-transactional database. The database management system executes garbage collection on data stored in a database to remove data values written to the database as part of uncommitted transactions. Each uncommitted transaction is associated with a respective transaction identifier that is not included in a list of committed transaction identifiers. The list of committed transaction identifiers lists, in sequential order, transaction identifiers for committed transaction. After removing each data value written to the database as part of an uncommitted transaction, the database management system modifies the list of committed transaction identifiers to include the transaction identifier for the uncommitted transaction.

Abstract: One or more techniques and/or computing devices are provided for non-disruptively establishing a synchronous replication relationship between a primary volume and a secondary volume and/or for resynchronizing the primary volume and the secondary volume. For example, a baseline snapshot and one or more incremental snapshots of the primary volume are used to construct and incrementally update the secondary volume with data from the primary volume. A dirty region log is used to track modifications to the primary volume. A splitter object is used to split client write requests to the primary volume and to the secondary volume. A synchronous transfer engine session is initiated to processing incoming client write requests using the dirty region log. A cutover scanner is used to transfer dirty data from the primary volume to the secondary volume. In this way, a synchronous replication relationship is established between the primary volume and the secondary volume.

Abstract: Data is received at a source system and characterizing a modified first software object for transport to a destination system via a request and to update a first software object deployed on the destination system. A first dependency of the modified first software object on a second software object is determined by the source system. An inconsistency between the modified first software object and the second software object is identified by the source system and using the first dependency. Data indicative of the inconsistency is provided. Related apparatus, systems, techniques and articles are also described.

Abstract: Embodiments of this specification disclose a system and a method for providing an embedded integrated development environment (IDE). The system may include a server interface; an index data storage, configured to store application index data; a component data storage, configured to store component dependency data; and an access control module, configured to: receive a first access request through the server interface from a terminal device; retrieve the application index data according to the first access request from the index data storage to determine a first application component; retrieve the component dependency data according to the first application component from the component data storage to determine a resource component on which the first application component depends; and send the first application component and the resource component to the terminal device through the server interface.

Abstract: Provided are a computer program product, system, and method for determining available remote storages in a network to use to replicate a file based on a geographical requirement with respect the file. A determination is made as whether available remote storages satisfy constraints associated with a document class of the file. The constraints include a geographical location at which to replicate the file and a minimum number of replications to create for the file. At least one remote storage of the available remote storages is selected that satisfies the constraints to store at least one copy of the file. The file is replicated to the selected at least one remote storage.

Abstract: Described herein is a computer implemented method. The method comprises receiving, by an issue tracking system, a build update from a build system which includes build information in respect of one or more issues maintained by the issue tracking system. The method further comprises associating one or more issues maintained by the issue tracking system with build information by identifying the one or more issues to which the build information in the build update relates, extracting the build information from the build update, and associating the build information with each of the identified issues.

Abstract: A system includes a device coupleable to a first memory. The device includes a second memory to cache data from the first memory. The second memory is to store a set of compressed pages of the first memory and a set of page descriptors. Each compressed page includes a set of compressed data blocks. Each page descriptor represents a corresponding page and includes a set of location identifiers that identify the locations of the compressed data blocks of the corresponding page in the second memory. The device further includes compression logic to compress data blocks of a page to be stored to the second memory and decompression logic to decompress compressed data blocks of a page accessed from the second memory.

Abstract: The invention relates to a build validation engine for a software build process. According to an embodiment of the present invention, a computer implemented system a build validation engine further configured to perform the steps comprising: receiving inputs from a software platform, the inputs comprising a build identifier and a mode indicator; initiating, via the build validation engine, validation of a plurality of configuration file categories for a software build; identifying and applying, via the build validation engine, a set of configuration rules, the set of configuration rules associated with each configuration file category and further comprising server class validation, inputs validation, indexes validation and props validation; and determining whether a successful build is achieved and if a successful build is not determined, failing the build and deleting corresponding deployment bundles.

Abstract: An apparatus, computer program, and method are provided for trigger-based tracking of database modifications. One or more input tables associated with a database are identified. Further, one or mom triggers are generated, based on the one or more input tables. Such one or more triggers are then installed in connection with an application configured for modifying the database. In response to at least one of the one or more triggers being triggered, one or more modifications to the database are tracked. Further, information is stored where such information is associated with the one or more modifications to the database.

Abstract: Software updates that cause changes to a database accessible by software can be identified. A first database can be modified using first instructions associated with a first software update to generate a first modified database, and a second database can be modified using second instructions associated with a second software update to generate a second modified database. A difference between the first and second modified databases can be determined, and one or more instructions of the first or second instructions that caused the difference can be identified based on the difference. The first and second instructions can be converted into operations that, when performed against the first and second databases, result in first and second many-to-many tables being generated. The many-to-many tables can be queried to identify the operations associated with the difference between the first and second modified databases.

Abstract: Software build isolation is provided. Systems, methods and computer-readable devices provide for receiving a request from a user who is a member of a team or group for allocation of a machine from a pool of machines. A determination is made as to whether a limit has been reached on the number of machines available to the team or group. If the limit has not been reached, the machine is provisioned and the user is notified that the machine has been provisioned and allocated to the user. In addition, in response to receiving a notification that an asset is ready for backup, an asset is replicated on an archive server. Dependencies of the asset on dependent assets are determined and the dependent assets are replicated on the archive server.

Abstract: In response to detecting a software build break during testing, a change to a particular file committed to the software build that caused the software build to break is identified. A record of the change to the particular file is added to a sensitivity database, the sensitivity database accumulating multiple records of changes to the files of the software build during development of the software build. A relative level of failure of the particular file from the files of the software build based on the record in comparison with the multiple records is calculated. A sensitivity rating of the particular file to cause breaks in the software build based on the relative level of failure of the particular file weighted by one or more factors is generated. The sensitivity rating is output to one or more integrated development environment interfaces with access to the particular file of the software build.

Abstract: A file cloning mechanism allows for quickly creating copies (clones) of files within a filesystem, such as when a user makes a copy of a file. In exemplary embodiments, a clone of a source object is at least initially represented by a structure containing references to various elements of the source object (e.g., indirect onodes, direct onodes, and data blocks). Both read-only and mutable clones can be created. The source file and the clone initially share such elements and continue to share unmodified elements as changes are made to the source file or mutable clone. None of the user data blocks or the metadata blocks describing the data stream (i.e., the indirect/direct onodes) associated with the source file need to be copied at the time the clone is created. At appropriate times, cloned files may be “de-cloned.

Abstract: Provided are a computer program product, system, and method for establishing a point-in-time copy relationship between source logical addresses and target logical addresses. A point-in-time (PiT) copy establish command specifies a source set comprising a subset of source logical addresses in at least one storage and a target set comprising a subset of target logical addresses in the at least one storage. The source set of source logical addresses are copied to the target set of target logical addresses. The source logical addresses map to source tracks and wherein the target logical addresses map to target tracks. Copy information is generated indicating whether the source logical addresses in the source set have been copied to the target set. Complete is returned to the PiT copy establish command after generating the copy information and before copying all the source logical addresses to the target logical addresses.

Abstract: As a conflict resolution method for the modification/editing of databases, the mechanism “for assigning priority to editing based on more up-to-date information” is disclosed. The method is effective in both full-fledged “parallel DB editing” in which a computer holds duplicated DBs permanently and the case in which a computer holds the duplicated DBs temporarily. The method is characterized in that “editing based on old information is determined to be ineffective.” When the information for which a conflict is predicted is edited, the possibility that the editing becomes ineffective can be reduced by a “substantially online operation” which performs “the synchronization with the up-to-date information, the editing, and the transmission of the editing records” quickly.

Abstract: A technique of backing up a workload in a virtual environment includes identifying one or more files that are associated with the workload. One or more source volumes that include the one or more files are identified. A respective target volume is provisioned for each of the one or more source volumes identified. Only dirty blocks are copied (in a snapshot mode that prevents an update to the one or more source volumes during the snapshot mode) from each of the one or more source volumes to its respective target volume. The one or more dirty blocks are then copied from each target volume to a backup medium.

Abstract: An interface between an existing local file system and a data store generates and exports to the data store a versioned file system. The state of the local file system at a given point in time can be determined using the versioned file system. In operation, the interface creates and exports to the data store structured data representations, which correspond to versions of the local file system, as well as actual file system data that these structured data representations represent. A cache associated with the interface stores recently used data and metadata, as well as all write data and metadata waiting to be transferred to the data store. Prior to transfer, one or more data transformations may be applied to the data and metadata. In one embodiment, the data store comprises one or more cloud storage service providers. A content control system is used to configure and manage the interface.

Abstract: A technique of backing up a workload in a virtual environment includes identifying one or more files that are associated with the workload. One or more source volumes that include the one or more files are identified. A respective target volume is provisioned for each of the one or more source volumes identified. Only dirty blocks are copied (in a snapshot mode that prevents an update to the one or more source volumes during the snapshot mode) from each of the one or more source volumes to its respective target volume. The one or more dirty blocks are then copied from each target volume to a backup medium.