The Metadata Catalog Sample Clauses

The Metadata Catalog. The metadata catalog is stored using CERIF. General information on CERIF may be found at the euroCRIS website1; the detailed datamodel (in TOAD modeller) can be accessed directly2. CERIF consists of base entities (e.g., person, project, organisational unit, research product, equipment…) and link entities which express relationships (role and temporal interval) between base entities (e.g., <Person P><manager of><Equipment E><2019-01-31:09:00><2019-10-31:17:00>). It thus provides a fully connected labelled graph with a rich syntax. The roles are not coded directly in the syntactic layer but are represented by persistent unique identifiers which point to the relevant term in the semantic layer (thus ensuring integrity of terminology) which has the same structure as the syntactic layer so terms (in base entities of the semantic layer) can be related to each other (link entities of the semantic layer) providing a full ontological structure. The metadata catalog is populated from the heterogeneous metadata formats used within the TCS via EPOS- DCAT-AP in an ingestion pipeline (Figure 7) but work is underway for dynamic update by specified TCS managers within a secure environment.
AutoNDA by SimpleDocs

Related to The Metadata Catalog

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

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

  • Contract Database Metadata Elements Title: Whitesville Central School District and Whitesville Central School Educational Support Staff Association (2003) Employer Name: Whitesville Central School District Union: Whitesville Central School Educational Support Staff Association Local: Effective Date: 07/01/2003 Expiration Date: 06/30/2006 PERB ID Number: 10699 Unit Size: Number of Pages: 23 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ AGREEMENT BETWEEN WHITESVILLE CENTRAL SCHOOL EDUCATIONAL SUPPORT STAFF ASSOCIATION AND THE WHITESVILLE CENTRAL SCHOOL DISTRICT JULY 1, 2003 THROUGH JUNE 30, 2006 TABLE OF CONTENTS ARTICLE TITLE PAGE Preamble 1 I Recognition 1 II Collective Bargaining U n i t 1 III Dues/Agency Fee Ckoffand Payroll Deduction 1 IV Rights of Employees 2 V Rights of Employer ------------- 2 VI Personnel F i l e 2 VII Employee Definitions 3 VIII Permanent Status/Seniority 4 IX Wages 5 X Overtime 7 XI Vacation 7 XII Holidays 8 XIII Sick Leave and Leavesof A b s e n c e 8 XIV Conference, Workshops,Required Courses 10 XV Meal Allowance and M i l e a g e 11 XVI Retirement 11 XVII Insurance 12 XVIII Cafeteria P l a n 14 .XIX Uniform Allowance------------------ 14 XX Hours of W o r k 14 XXI Transfers/Promotions 15 XXII Job Descriptions 15 XXIII Grievance Procedure 15 XIV Copies of the Contract 18 XV Zipper C x x x x x 18 XXVI Legislative Clause 18 XXVII Duration 19 SIGNATURES 19 APPENDIX A Grievance F o r m 20 APPENDIX B Dues Authorization F o r m 21

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

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

  • Software Components At any time during the contract period of performance, the Government may require the Contractor to remedy any failure of the software to comply with the requirements of this contract. Support shall consist of correction of errors, provision of modifications, improvements, and other products the original manufacturer makes available to the Government without charge. The Government shall also be provided full documentation of changes and/or modifications to the software provided to meet the Government's requirements.

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • End Users Customer will control access to and use of the Products by End Users and is responsible for any use of the Products that does not comply with this Agreement.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

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