Making data interoperable Sample Clauses

Making data interoperable. Questions Answers
AutoNDA by SimpleDocs
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.
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.
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.
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.
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.

Related to Making data interoperable

  • 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 Upgrade versions of licensed software/apps are available from time to time. Students may be required to check in their iPads for periodic updates and synching.

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

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!