A method, computer program and apparatus is disclosed. The method, performed by one or more processors, may comprise receiving, from one or more predetermined organizations, datasets representing entities and datasets representing one or more tasks for those entities and storing in a database, in accordance with an ontology which is common to the organizations, the received one or more datasets as data objects, the ontology defining properties of data objects and relationships between the data objects. The method may also comprise mapping the data objects stored in the database to the organization from which the one or more datasets were received and receiving, through a querying application, a query from a user of one of the predetermined organizations to view one or more data objects relating to a task. The method may also comprise identifying the organization to which the user is associated, generating, based on the mapping, a view including at least the one or more task data objects associated with the identified organization and not data objects associated with other organizations and displaying the view on a user interface.

A method of naming documents according to a document naming convention (DNC) includes receiving, from any of a plurality of data processing applications (DPAs) within an enterprise, a request for a document name and generating a document name “infix” portion in compliance with the DNC for inclusion in the document name. The prefix may be descriptive of a characteristic of the document and the suffix may indicate a document type, a document format, or both. The infix may include a fixed portion and a modifiable portion. The fixed portion may include a datestamp and a document unification identifier. The infix may include a variable portion that can be modified by a DPA that creates a new or modified document, but the name of the modified document maintains the fixed portion of the original document.

Direct storage loading may be used to add data to a database. New data may be added to a database, using nodes different than a database engine to access a database. The addition of the new data may be assigned to different nodes. The nodes may obtain the data and store the data to storage locations according allocated space in the database by the database engine. The new data can then be made available for access at the database engine.

A storage unit operates by: receiving a write slice request, wherein the write slice request includes a plurality of encoded data slices and wherein the write slice request corresponds to a range; determining whether a write lock conflict exists based on the range; issuing an unfavorable write slice response when the write lock conflict is determined to exist; and when the write lock conflict is determined to not exist: initiating local storage of the plurality of encoded data slices; and issuing a favorable write slice response.

The present disclosure relates to systems for creating, organizing, viewing, and connecting annotations of web documents within web browsers that are made to be annotation capable. The rationale for designing systems using the principles disclosed herein is explained in detail. This rationale is illustrated using sequence diagrams and use case diagrams to elucidate the need for the design principles and data structures employed. The disclosure also provides exemplary hardware specifications and describes design tradeoffs.

Disclosed are a method, device and/or system of a model-driven engineering of efficient industrial automation process and business process modeling with BPMN using native computation of XML schemas and objects. In one embodiment, it models a business/industrial automation process using BPMN. It creates an XML schema associated with a business object class in BPMN using XSD and natively computes the XML schema and/or an XML object using a processor and a memory. It generates an XML-transport map and dynamically creates a user interface for the XML schema. It creates the XML object with associated data resource based on the XML schema. It associates the XML object with a business object/industrial automation object. It customizes and/or processes the XML object using the user interface associated with the XML schema according to the characteristics of the business/industrial automation object.

Application programming interfaces (APIs) may have different API schemas that may have different organizations of schema properties and entities or use different names for schema properties and entities. Where two or more APIs with different schemas are being used, it may be desired to map schema properties and/or entities between them. Semantic representations of API schema properties and entities may be used to assist with the mapping of schema properties and entities. The semantic representations may be used to suggest possible mappings to a user or to automatically determine a mapping without the involvement of a user.

A query referencing a function associated with a remote software component is received by a network-based data warehouse system. Temporary security credentials corresponding to a role at a cloud computing service platform are obtained. The role has permission to send calls to a web endpoint corresponding to the remote software component. A request comprising input data and electronically signed using the temporary security credentials is sent to a web Application Programming Interface (API) management system of the cloud computing service platform. The request, when received by the web API management system, causes the web API management system to invoke external functionality provided by the remote software component at the web endpoint with respect to the input data. A response comprising a result of invoking the external functionality is received from the web API management system, and the result data is processed according to the query.

A method and/or system includes: adding a new source of data to be stored in the data storage system; obtaining the schema for the new source of data to be stored in the data storage system; storing the data to be stored in the data storage system in a Not Only Structured Query Language (NOSQL) database in the data storage system; and storing schema for the data to be stored in the data storage system in a metadata store in the electronic data storage system wherein the metadata store is separate from the NOSQL database.

The present disclosure concerns systems and methods and computer program products for processing hierarchical document data (e.g., XML, JSON documents) and storing them in relational database structures. The methods herein read input document data and analyze the schema of the document to create both dynamic data tables and metadata tables for the destination tabular structure storage. Thereafter, the key-value data stored in the document is extracted, transformed, and mapped to a generated table structure that references the metadata tables. In this way, information can be stored in tabular or relational databases or structures and reconstructed into the original document if necessary.