PrestoPRIME Metadata Mapping Tool Sample Clauses

PrestoPRIME Metadata Mapping Tool. The PrestoPRIME3 project has also developed an approach for metadata mapping. In contrast to MINT, the approach is based on defining mappings between metadata models/schemas rather than starting from instances. The approach uses a high-level intermediate representation of metadata elements serving as a hub for mapping between formats. Therefore, hand-crafted one-to-one mappings between each pair of metadata formats are avoided, as the mappings for a specific pair of source and target format can be derived automatically. Metadata elements from a specific metadata format are described in relation to these generic elements. In addition, mapping templates on data type level are used. From these sources the code for a mapping problem between a pair of formats can be derived. The core of this approach is the meon ontology [6], which describes generic metadata elements and the relations between them. meon was originally developed to model metadata elements used throughout the audiovisual media production workflow in a format independent way in order to support content exchange and its automation. The meon ontology has been extended to express mapping relations between metadata formats. In addition to the ontology of generic metadata concepts, specific ontologies are created for each format taken into account. Then it is possible to infer how concepts from different metadata formats are related by observing the relations among generic concepts and to the format specific concepts. Since mapping instructions are derived from the ontology description, these mapping instructions are easier to maintain than hard coded mapping instructions. Adding a new metadata format can be done without side effects to existing definitions.
Sample 1
AutoNDA by SimpleDocs
PrestoPRIME Metadata Mapping Tool. 3.1.1.1 Assessment results Characteristics Sub-characteristics Level of Need Fulfilment Functional suitability Functional completeness Metadata input formats Dublin Core Mandatory 1 ESE Desirable 0 EDM Desirable 0 EBU Core Mandatory (for broadcasting related CoPs) / Recommended 0,5 MPEG-7 Recommended (for CoPs using automatic content analysis) 1 (profile dependent) LIDO Mandatory (for museum/gallery related) / Recommended 0 EAD Mandatory (for non-a/v archive related) / Recommended 0,5 Metadata output formats Dublin Core Mandatory 1 ESE Recommended 0 EDM Recommended 0,5 EBU Core Mandatory (for broadcasting related CoPs) / Recommended 0 MPEG-7 Recommended (for CoPs using automatic content analysis) 0,5 LIDO Mandatory (for 0 Characteristics Sub-characteristics Level of Need Fulfilment museum/gallery related) / Recommended EAD Mandatory (for non-a/v archive related) / Recommended 0,5 option to add custom formats Recommended 0 XML representation support Mandatory 1 RDF representation support Recommended 0,5 Metadata model constructs single -> multiple elements Recommended 1 multiple -> single elements Mandatory 1 structure using context elements Mandatory 1 conditional mapping based on element/attribute values Mandatory 0,5 map collections Recommended 0,5 merge string values Mandatory 1 split string values Recommended 1 number of levels in data structure Mandatory: 2 / Recommended: 2+ 1 / 1 start from example(s) Recommended 0 start from schema Recommended 1 configuration user interface Mandatory 1 user interface drag & drop mappings Recommended 1 preview Mandatory 1 map constructs not found in available examples Recommended 0 Functional correctness Tested mappings Dublin Core -> EDM 1 Functional appropriateness ingest of metadata (e.g. SIP creation) 1 B2B exchange 1 provision to portals (e.g. Europeana) 0,7 Performance efficiency Time behaviour processing time simple document (one bibliographic record) not tested complex document (detailed metadata) not tested document with collections not tested response time of user interface not tested time for generating preview not tested Resource utilization RAM requirement 4 GB RAM Characteristics Sub-characteristics Level of Need Fulfilment CPU requirements dual core GPU requirement not required Capacity Number of metadata elements per core/minute >300 Compatibility Interoperability configuration desktop UI 0 web-based UI 1 Reliability Fault tolerance incorrect input file format passed load incomplete mapping definition...
Sample 1

Related to PrestoPRIME Metadata Mapping Tool

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

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

  • Metadata Bibliographical, structural & descriptive data of the Licensed Material as defined in Schedule 5.

  • End User An “End User” is you, an individual or entity, which receives the Models from Licensee or Authorized Licensee User pursuant to this End User Agreement to use in the regular course of your affairs, but not for resale, modification, distribution or exploitation by third parties without AnyLogic’s prior written consent.

  • Network Interface Device (NID) 2.7.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 customer-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.

  • Catalog Information about Community Regional Medical Center – Diagnostic Medical Sonography Program (CRMC-DMSP) is published in a school catalog that contains a description of certain policies, procedures, and other information about the school. CRMC-DMSP reserves the right to change any provision of the catalog at any time. Notice of changes will be communicated in a revised catalog, an addendum or supplement to the catalog, or other written format. Students are expected to read and be familiar with the information contained in the school catalog, in any revisions, supplements and addenda to the catalog, and with all school policies. By enrolling in CRMC-DMSP, the Student agrees to abide by the terms stated in the catalog and all school policies.

  • Computer Equipment Recycling Program If this Contract is for the purchase or lease of computer equipment, then Contractor certifies that it is in compliance with Subchapter Y, Chapter 361 of the Texas Health and Safety Code related to the Computer Equipment Recycling Program and the Texas Commission on Environmental Quality rules in 30 TAC Chapter 328.

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

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

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