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...
AutoNDA by SimpleDocs

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.

  • E-Mail Access Patient shall be given the Physician’s e-mail address to which non-urgent communications can be addressed. Such communications shall be dealt with by the Physician or staff member of the Practice in a timely manner. Patient understands and agrees that email and the internet should never be used to access medical care in the event of an emergency, or any situation that Patient could reasonably expect may develop into an emergency. Patient agrees that in such situations, when a Patient cannot speak to Physician immediately in person or by telephone, that Patient shall call 911 or the nearest emergency medical assistance provider, and follow the directions of emergency medical personnel.

  • 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 B.

  • -wire Unbundled Digital/DS0 Loop These are designed 4-wire Loops that may be configured as 64kbps, 56kbps, 19kbps, and other sub-rate speeds associated with digital data services and will come standard with a test point, OC, and a DLR.

  • MOBILE DATA COMPUTERS 20 1. As part of the law enforcement services to be provided to CITY, COUNTY 21 has provided, or will provide, mobile data computers (hereinafter called 22 “MDCs”) that are or will be mounted in patrol vehicles and motorcycles, 23 designated by COUNTY for use within CITY limits.

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only) The wind generation facility shall, at a minimum, be required to provide the Transmission Provider with site-specific meteorological data including: • Temperature (degrees Fahrenheit) • Wind speed (meters/second) • Wind direction (degrees from True North) • Atmosphere pressure (hectopascals) • Forced outage data (wind turbine and MW unavailability)

  • Hosted Services We shall use commercially reasonable efforts to make the Hosted Services you have purchased available 24 hours a day, 7 days a week, except for: (a) planned downtime under our direct control (of which we shall give at least 8 hours notice via the Hosted Services and which we shall schedule to the extent practicable during the weekend hours from 6:00 p.m. Pacific time Friday to 3:00 a.m. Pacific time Monday), (b) to the extent we are notified by third party service providers of planned downtime (of which we shall provide such notice to you via the Hosted services as soon we can reasonably do so), or (c) any unavailability caused by circumstances beyond our reasonable control, including, without limitation, acts of God, acts of government, flood, fire, earthquakes, civil unrest, acts of terror, strikes or other labor problems, internet service or third party hosting provider failures or delays ("Force Majeure"). Hosted Services are provided in accordance with applicable laws and government regulations.

  • Log and Load Reporting Service This contract may at the States discretion, require the services of a State approved third party log and load reporting service. Purchaser shall ensure log volume measurement, weight, or scale and weight data for each load is received by the log and load reporting service within 1 business day of logs being measured or weighed. If during the term of this contract, the State discontinues use of the Log and Load Reporting Service, the State will notify the Purchaser in writing, and will approve an alternative log and load reporting process. L-080 Scaling Rules Determination of volume and grade of any forest products shall be conducted by a state approved third party scaling organization and in accordance with the Westside log scaling and grading rules and Xxxxxxxx Volume Table, revised July 1, 1972, contained in the Northwest Log Rules Eastside and Westside Log Scaling Handbook (developed and produced by the Northwest Log Rules Advisory Group) and in effect on the date of confirmation of this contract. Special scaling specifications shall be noted on the State’s Brand Designation form which is hereby incorporated to this contract by reference. X-000 Xxxxx Xxxxxxxx of Log Scaling and Weighing Locations Forest Product measurement and weighing facilities required by this contract must be approved by the State. Forest products sold under the contract which require log scaling shall be scaled, measured, or counted by a State approved third party log scaling organization. Forest products sold under the contract which require weighing shall be weighed at a location that meets Washington State Department of Agriculture approval. Prior to forest products being hauled, the Contract Administrator must authorize in writing the use of State approved measurement and/or weighing facilities that are at or en-route to final destinations. Forest products from this sale shall be measured or weighed at facilities, which are currently approved for use by the State and are currently authorized for this sale. The State reserves the right to verify load volume and weights with State employees or contractors at the State's own expense. The State reserves the right to revoke the authorization of previously approved measurement locations.

Time is Money Join Law Insider Premium to draft better contracts faster.