Making data interoperable Sample Clauses

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.
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. 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. 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/): « (Meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation: Zenodo uses JSON Schema as internal representation of metadata and offers export to other popular formats such as Dublin Core or MARCXML. » « (Meta)data use vocabularies that follow FAIR principles: For certain terms we refer to open, external vocabularies, e.g.: license (Open Definition8), funders (FundRef9) and grants (OpenAIRE). » « (Meta)data include qualified references to other (meta)data: Each referenced external piece of metadata is qualified by a resolvable URL. » 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.

Related to Making data interoperable

  • 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. School District Workstations Configuration requirements for devices and their software that school district personnel use to access WSIPC’s software modules can be found on our website: xxxxx://xxx.xxxxx.xxx/technology‐team/. State Reports XXXXX will provide, at no additional fee, all data reports required by the state that impact 50% or more of the school districts in the state. WSIPC and NWRDC will work with state agencies to gather requirements on the required data. WSIPC will inform NWRDC staff of any mandated changes to state reports and NWRDC will communicate the information to the District. Appendix B NWRDC FTE Fees Fiscal Only NWRDC Software Support Services XXXXX Software Licensing Total FTE Fee $13.63 $20.34 $33.97 $15.56 $13.08 $28.64 $24.52 $20.34 $44.86 Student Only Full Service

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

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