Meta data scalability Sample Clauses

Meta data scalability. Section 1.4 above describes why a scalable metadata capability is fundamental to across disciplinary, federated archive architecture. This section explains how progress on this has been managed within 7.1.1, given the wider uncertainties surrounding metadata services across EUDAT. From the start of the EUDAT project, while there has been good progress in developing many of the services, safe replication, data staging or dynamic replication, and so on, there has been much more uncertainty about what metadata services EUDAT should be delivering. This is made clear in the opening statement of the Meta Data Task Force Discussion Document3: “In the EUDAT DoW a task is described to come to a Joined Metadata Domain for the resources managed by EUDAT services. However this work is underspecified and no clear goals were set. To come to a clearer picture especially about what the scope and ambitions of EUDAT in this respect should be, the EUDAT EB decided to create a Metadata Task Force (MTF) chaired by Xxxxx Xxxxxxxxx (FT) (DKRZ/ENES) and Xxxx Xxxxxxx (DB) (MPI-TLA/CLARIN) to guide internal EUDAT discussions and come to a ‘position’ document until end of April. In the MTF Xxxxxxx Xxxxxxxxxxxxxx (ML) represents the EB and the MTF itself will work in the work package concerning EUDAT Services and Technology Appraisal”. As a result of this it was agreed that the current task would (could) not define the scope of how to address metadata scalability, until the wider EUDAT project had first defined its approach and scope of EUDAT metadata services. The EUDAT Meta Data Task Force was convened for that purpose, and developed the Meta Data Task Force Discussion Document as a vehicle for defining the approach and scope for EUDAT. The MD TF discussion document was approved by the EUDAT Executive board on June 4th 2012. Subsequently4, it has been agreed that WP7 would work directly within the EUDAT MD TF to clarify and contribute to the forthcoming detailed work plan and that resource contributed by Assessing Scalability and Preservation work package to the MDTF can contribute to all and any key problem areas, 3 See Metadata_TF-DiscDoc-V10.docx at xxxxx://xxxxxxxxxx.xxx.xx/display/Eudat/Metadata+Task+Force 4 9th EUDAT Executive Board Meeting 2nd July 2012. See xxxxx://xxxxxxxxxx.xxx.xx/display/Eudat/Executive+Board+Meetings not specifically to scalability issues5. The work plan will eventually be submitted to the EB6’7, and once approved, and the work underway, this will then ...
Sample 1
AutoNDA by SimpleDocs

Related to Meta data scalability

  • Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case.

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

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

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

  • Geometric visibility The visibility of the illuminating surface, including its visibility in areas which do not appear to be illuminated in the direction of observation considered, shall be ensured within a divergent space defined by generating lines based on the perimeter of the illuminating surface and forming an angle of not less than 5° with the axis of reference of the headlamp. The origin of the angles of geometric visibility is the perimeter of the projection of the illuminating surface on a transverse plane tangent to the foremost part of the lens of the headlamp.

  • Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Internet Connectivity School must provide sufficient hardline internet connectivity and the required network configurations (provided in Exhibit A) for each Pixellot System to allow live broadcasts. PlayOn will provide the point-to-point wireless internet base station (“Point to Point”) when needed to deliver hardline internet connectivity to Pixellot Systems installed in outdoor venues; provided that PlayOn is able to select the make and model of the Point to Point system. In the event that School requests, or requires, a specific Point to Point system that is different from what is provided by PlayOn, then School must provide and install the Point to Point system at its own expense.

  • Authorized User Overview and Mini-Bid Process Project Based IT Consulting Services Contracts enable Authorized Users to use a competitive Mini-bid Process to acquire Services on an as-needed basis, for qualified IT Projects. Project Based IT Consulting Services may include, but will not be limited to projects requiring: analysis, data classification, design, development, testing, quality assurance, security and associated training for Information Technology based applications. See section 1.3 Out of Scope Work for a listing of projects expressly excluded from the scope of this Contract. An Authorized User Agreement for Project Based IT Consulting Services will be governed first by the terms and conditions specified in the OGS Centralized Contract and second by terms and conditions added to the Authorized User Statement of Work. Additional terms and conditions shall not conflict with or modify the terms and conditions of the OGS Centralized Contract. NYS Executive Agencies must adhere to all internal processes and approvals including, as required, approval from NYS Office of Information Technology Services. Other Authorized Users must adhere to their own internal processes and approvals. In accordance with Appendix B, section 28, Modification of Contract Terms, an Authorized User may add additional required terms and conditions to this Mini-Bid and resultant Authorized User Agreement only if such terms and conditions (1) are more favorable to the Authorized User and (2) do not conflict with or supersede the OGS Centralized Contract terms and conditions. Examples of additional terms and conditions include: • Expedited delivery timeframe; • Additional incentives, such as discount for expedited payment/Procurement Card use; and • Any additional requirements imposed by the funding source or Federal law.

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