XXX Modules Sample Clauses

XXX Modules. The table below shows the XXX modules and describes the functionality they deliver. CMS: XXX supporting functionality All functionality that must be provided within or alongside a CMS in order to meet the functional requirements set out in D2.4, including Data Push and/or OAI-PMH repository and content re-ingestion. XXX Core The gateway to the various modules, so supports all interfaces that all the other modules support. Metadata Definition Provides definitions for metadata elements within profiles and error messages in the different languages Data Mapping / Transformation Converts between formats, e.g. Native format to LIDO or LIDO to EDM Preview Provides a preview of how the record will be rendered in the Europeana user interface PID Generation Provides a persistent id for the record Set Manager Manages the sets and records Statistics Provides statistics about the performance of modules Validation Validates the record to ensure it conforms to a provided profile (of either LIDO or EDM). Aggregator: XXX supporting functionality Accepts data via data push or OAI-PMH, supplies data to Europeana via OAI-PMH and provides management information and enriched records for re-ingestion As reported in section 1, CMS:XXX supporting functionality (i.e. the software components that are specific to an individual partner’s implementation of the XXX) is not covered in this deliverable.
Sample 1Sample 2
AutoNDA by SimpleDocs
XXX Modules. The table below shows the XXX modules and describes the functionality they deliver. These functional areas were identified by analysis of the requirements specification in conjunction with the high level design principles set out in section 3.1.
Sample 1

Related to XXX Modules

  • API If the Software offers integration capabilities via an API, your use of the API may be subject to additional costs or Sage specific policies and terms and conditions (which shall prevail in relation to your use of the API). You may not access or use the API in any way that could cause damage to us or the Software, or in contravention of any applicable laws. We reserve the right in our sole discretion, to: (i) update any API from time to time; (ii) place limitations around your use of any API; and (iii) deny you access to any API in the event of misuse by you or to otherwise protect our legitimate interests.

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

  • Licensed Software Computer program(s) provided by Contractor in connection with the Deliverables, subject to Section 14 of this Contract.

  • Software Warranty We warrant that the Tyler Software will perform without Defects during the term of this Agreement. If the Tyler Software does not perform as warranted, we will use all reasonable efforts, consistent with industry standards, to cure the Defect in accordance with the maintenance and support process set forth in Section C(9), below, the SLA and our then current Support Call Process.

  • Software Products Save as otherwise set forth in the Agreement, the right to use any Software Product is personal to the Licensee, for its own internal use, and is non-transferable, except with the Licensor’s prior written consent, in which case the Licensee shall cause the assignee or sub-licensee to agree to the terms of this Software License.

  • Supply of Materials The following materials will be supplied by the department Name of Materials Rate. Place of delivery 1.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Manufacturing Services Jabil will manufacture the Product in accordance with the Specifications and any applicable Build Schedules. Jabil will reply to each proposed Build Schedule that is submitted in accordance with the terms of this Agreement by notifying Company of its acceptance or rejection within three (3) business days of receipt of any proposed Build Schedule. In the event of Jabil’s rejection of a proposed Build Schedule, Jabil’s notice of rejection will specify the basis for such rejection. When requested by Company, and subject to appropriate fee and cost adjustments, Jabil will provide Additional Services for existing or future Product manufactured by Jabil. Company shall be solely responsible for the sufficiency and adequacy of the Specifications [***].

  • Equipment and Materials CONTRACTOR shall provide all equipment, materials, and supplies necessary for the performance on the Agreement except:

  • Licensed Materials The materials that are the subject of this Agreement are set forth in Appendix A ("Licensed Materials").

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