Provenance Data Storage and Querying Sample Clauses

Provenance Data Storage and Querying. The Provenance Service stores workflow provenance in the provenance store in order to provide refined data to both clinical researchers and analysis applications. The provenance data store uses a relational database schema and has been designed in a way that it separates the workflow/activity specifications from the workflow/activity instance (execution) related information (as shown in Figure 9). Thus, this enabled rich provenance querying, including queries about the general structure of the workflows, the activities in the workflows, the links between different workflow activities and activity results. Moreover, within the provenance data store any change in a workflow’s description is represented by the workflow version. Here, each change in the workflow description spawns one provenance version describing the state of the workflow after the change. Each workflow and its related versions are identified internally by its unique id. In order to identify its source the workflow-id, version-description and times-stamp are utilised. This storage of all workflow versions provides a tracking facility and enables clinical researchers to compare different versions of a workflow. The WorkflowDesc table has WorkflowID, WorkflowVersion, WorkflowName, OwnerName, CreationDate, WorkflowDesc, WorkflowData, AbstractWorkflowData and Approved columns. Here, WorkflowID is a unique value assigned to each user generated workflow stored in the provenance database. In addition to the workflow owner related information, this table also stores complete workflow specifications in the XML format. The Approved column confirms the approval status of a specific workflow as a boolean i.e. true/false. The associated annotations of each workflow are stored in the WorkflowAnnotation table that has 1:M relationship with the WorkflowDesc table. This WorkflowAnnotation table stores the information about WorkflowAnnotationID, WorkflowID, AnnotationKey and AnnotationValue. The ActivityDesc table has ActivityID, WorkflowID, ActivityName, ActivityExternalID, ActivityType, ActivityDesc, IsExecutable, Executable, Architecture, Priority, DataElement, StdOutLogFilename and StdErrLogFilename columns. Here, tbe ActivityID column uniquely identifies each activity of a workflow, which is different than the ActivityExternalID value. The ActivityExternalID column stores the user defined activity identification value. The StdOutLogFilename and StdErrLogFilename columns contain the file names in which act...
View Source

Related to Provenance Data Storage and Querying

  • Data Storage Where required by applicable law, Student Data shall be stored within the United States. Upon request of the LEA, Provider will provide a list of the locations where Student Data is stored.

  • Device Data We may share certain personal information and device-identifying technical data about you and your devices with third party service providers, who will compare and add device data and fraud data from and about you to a database of similar device and fraud information in order to provide fraud management and prevention services, which include but are not limited to identifying and blocking access to the applicable service or Web site by devices associated with fraudulent or abusive activity. Such information may be used by us and our third party service providers to provide similar fraud management and prevention services for services or Web sites not provided by us. We will not share with service providers any information that personally identifies the user of the applicable device.

  • COVID-19 Vaccine Passports Pursuant to Texas Health and Safety Code, Section 161.0085(c), Contractor certifies that it does not require its customers to provide any documentation certifying the customer’s COVID-19 vaccination or post-transmission recovery on entry to, to gain access to, or to receive service from the Contractor’s business. Contractor acknowledges that such a vaccine or recovery requirement would make Contractor ineligible for a state-funded contract.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • Verizon Operations Support Systems Verizon systems for pre- ordering, ordering, provisioning, maintenance and repair, and billing.