We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Making data interoperable Sample Clauses

Making data interoperable. Questions Answers
Sample 1Sample 2
Making data interoperable. ‌ In the TRIP project we will use standard file formats as mentioned above. Each dataset will have standard Zenodo metadata. Data referring to personal identifiable information will be restricted to internal use and not shared with third parties. Metadata domain model used in Zenodo deposition will include: title string Title of deposition. Created timestamp Creation time of deposition (in ISO8601 format). Creators string Authors of the deposition. doi string Digital Object Identifier (DOI) assigned by the DOI registrant doi_url url Persistent link to your published deposition. Available for published depositions only. id integer Deposition identifier Publication_date timestamp Date of publication in ISO8601 format (YYYY-MM-DD). modified timestamp Last modification time of deposition (in ISO8601 format). Keywords string Free form keywords for the deposition
Sample 1
Making data interoperable. One of the main goals of the project is to create a set of interoperable research and evaluation data. The first six months of the project have as the main goal the creation of common interfaces and services for allowing the interoperation of data and tools among the research teams and data providers working in different countries. In practice this is rather straightforward, for the data is available in well-known and accessible formats. In general, known best practices will be followed. As much as possible of the produced and used data is to be stored in formats that are well known and preferably open; structures text formats are preferred when suitable.
Sample 1
Making data interoperable. As already identified within D3.2 [3] although multiple ontologies/terminologies are available for modelling medical and clinical information, there is a limited set of resources available for modelling psychological resources. Nevertheless, the BOUNCE project has contributed to a novel ontology to this domain, i. e. the BOUNCE psychological ontology. The ontology is able to model all scales that are currently used within the BOUNCE project, promoting as such the interoperability and the reuse of the available data and is presented in D3.3 [5]. In addition, the ontology includes mappings to the more commonly used ontologies further promoting data reuse.
Sample 1
Making data interoperable. Data produced in the project are interoperable, therefore standard file formats and inter-disciplinary vocabularies will be used to facilitate data exchange and re-use. It is envisaged that every dataset will have metadata, aside of the project publications which will be open access and accessible as outlined in the previous section.
Sample 1
Making data interoperable. The CarE-Service project aims to collect and document the data in a standardized way to ensure that, the datasets can be understood, interpreted and shared in isolation alongside accompanying metadata and documentation. Widespread file formats will be generated to ensure the easy access, exchange and reuse of the generated data from other researchers, institutions, organizations, countries, etc. Metadata are data which describe other data. Metadata files contain information about the documents you're going to upload. A metadata file will be created manually in an Excel spreadsheet and linked within each dataset. It will include the following information: • Title: free text • Creator: Last name, first name • Organization: Acronym of partner’s organization • Date: DD/MM/YYYY • Contributor: It can provide information referring to the EU funding and to the CarE- Service project itself; mainly, the terms "European Union (EU)" and "Horizon 2020", as well as the name of the action, acronym and the grant number • Subject: Choice of keywords and classifications • Description: Text explaining the content of the data set and other contextual information needed for the correct interpretation of the data. • Format: Details of the file format • Resource Type: data set, image, audio, etc. • Identifier: DOI • Link to data repository: Zenodo link • Links to other publicly accessible locations of the data: e.g. Zenodo Community link, other publication platforms, etc.
Sample 1
Making data interoperable. In order to make the research outputs and underlying data generated within the POLYPHEM project interoperable, the consortium will use data in the standard formats and prioritize the available (open) software, whenever possible. The consortium will also respect the common standards officially applied to the various formats that will be used for the data. The repository Zenodo is organized and managed in order to make data interoperable, to the maximum extent, in agreement with the FAIR data rules and recommendations (see xxxx://xxxxx.xxxxxx.xxx/principles/): Moreover, in order to further enhance the data exchange and re-use between researchers, organizations, institutions, countries and other, the consortium intends also encourage Zenodo community to perform as far as possible a follow- up of the POLYPHEM data re-used by other community participants for retracing the derivatives works based on the re-used data. The aim is to make this interoperability data concept viable through the possibility and utility of consultation of the results of the re-used POLYPHEM data to enrich and stimulate further scientific reflexions.
Sample 1

Related to Making data interoperable

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Network Interface Device 4.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the End User’s on-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the End User each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable. 4.1.1 BellSouth shall permit Al-Call to connect Al-Call ’s loop facilities to on-premises wiring through the BellSouth NID or at any other technically feasible point.

  • Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).

  • Software Updates XXXXX agrees to keep current with software licensed from Skyward and will install new versions on a timeline approved by XXXXX governance. This timeline will be communicated by NWRDC to the Districts.

  • Software Upgrades All Software Releases (including all Error corrections made available pursuant to this Agreement) that RSA in its sole discretion: (a) deems to be logical improvements to the Software; (b) make generally available to all licensees of the Software; and (c) does not separately price or market.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Server Software Subject to the terms and conditions of this XXXX, Vocera grants you the non-exclusive right to (i) install and run (“Use”) the Server Software on computer systems (each, a “Server Computer”) located at End User’s Facilities in the geographic territory designated above (“Territory”); (ii) to Use the Client Software in conjunction with Authorized Client Devices and such Server Computers; and (iii) for pilot licenses for certain Software provided on a trial basis, use such Software for the limited term specified by Vocera in writing. You may Use the standard Server Software on one primary Server Computer (or a primary cluster of computers suitably configured for productive use of the Server Software). You may install backup copies of the Server Software on backup Server Computers to provide redundancy in the event of failure of the primary Server Computer(s) but, unless you have acquired additional licenses or a failover license from Vocera, you may not run such backup or additional copies concurrently with the primary copies. Vocera grants you the right to use the applicable License Key issued by Vocera only to enable Use of the Server Software in conjunction with the licensed Server Computers. Server Software may be licensed for a Subscription Term as specified in the Quote.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If ECI chooses to subtend a Verizon access Tandem, ECI’s NPA/NXX must be assigned by ECI to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 ECI shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from ECI’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office ECI utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow ECI’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • System and Data Access Services a. System. Subject to the terms and conditions of this Addendum and solely for the purpose of providing access to Fund Data as set forth herein, State Street hereby agrees to provide the Fund, or certain third parties approved by State Street that serve as the Fund`s investment advisors, investment managers or fund accountants (the "Fund Accountants") or as the Fund`s independent auditors (the "Auditor"), with access to State Street`s Multicurrency HORIZONR Accounting System and the other information systems described in Attachment A (collectively, the "System") on a remote basis solely on the computer hardware, system software and telecommunication links described in Attachment B (the "Designated Configuration") or on any designated substitute or back-up equipment configuration consented to in writing by State Street, such consent not to be unreasonably withheld.

Most Referenced Clauses

Most Referenced Definitions