XXX Modules Sample Clauses

XXX Modules. The table below shows the XXX modules and describes the functionality they deliver. Module Functional Description 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 Table 1: Summary of XXX functionality 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.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Network Interface Device 2.7.1 The NID is defined as any means of interconnection of the End User’s 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 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.

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

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

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