Content and Metadata Formats Sample Clauses

Content and Metadata Formats. The information model is still under definition. When ready, it will be also used to define requirements on content and metadata formats required to represent the preservation objects discussed in this document. Nevertheless, the project has already released the first integrated prototype, described in D8.3, and has identified several content and meta- data formats and the associated technologies to properly represent the core concepts of the information model described here. For example the adoption of the CMIS xxxx- dard enables the content and metadata exchange between the user applications and the framework, while the standards used for content packaging and archival (such as METS, DublinCore, PREMIS and others) are suitable to support the representation of contents, their exchange between user applications and preservation systems, their evolution over time (see deliverables D8.1 and D8.3). The definition of the archival units and the most suitable data model in the PoF Framework requires further investigation.
AutoNDA by SimpleDocs
Content and Metadata Formats. The information model provides a representation of the main preservation entities and their relationships from the user and middleware perspective, providing a guideline for the choice of the appropriate content and metadata formats used to preserve the content generated in the different user applications.

Related to Content and Metadata Formats

  • Contract Database Metadata Elements Title: Spencerport Central School District and Spencerport Paraprofessional Association (2008) Employer Name: Spencerport Central School District Union: Spencerport Paraprofessional Association Local: Effective Date: 07/01/2008 Expiration Date: 06/30/2012 PERB ID Number: 6253 Unit Size: Number of Pages: 26 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 the SUPERINTENDENT OF SCHOOLS SPENCERPORT CENTRAL SCHOOL DISTRICT Town of Ogden, Gates, Greece and Parma and SPENCERPORT PARAPROFESSIONAL ASSOCIATION July 1, 2008 - June 30, 2012 TABLE OF CONTENTS ARTICLE PAGE PREAMBLE 1 RECOGNITION 1 ELIGIBLITY FOR BENEFITS 1 ARTICLE 1 DUES DEDUCTION 2 ARTICLE 2 SICK LEAVE 2 ARTICLE 3 PERSONAL LEAVE 3 ARTICLE 4 ILLNESS IN FAMILY 4 ARTICLE 5 FAMILY MEDICAL LEAVE ACT 4 ARTICLE 6 HEALTH INSURANCE 5 ARTICLE 7 WORKER'S COMPENSATION 8 ARTICLE 8 BEREAVEMENT 9 ARTICLE 9 SNOW DAYS AND EMERGENCY CLOSING 9 ARTICLE 10 JURY DUTY 9 ARTICLE 11 WORK YEAR 9 ARTICLE 12 EXTRA HOURS WORKED 10 ARTICLE 13 1:1 AIDES 10 ARTICLE 14 LUNCH BREAKS 10 ARTICLE 15 LONGEVITY 10 ARTICLE 16 PAID HOLIDAYS 11 ARTICLE 17 SALARY 12 ARTICLE 18 UNUSED SICK DAYS AT RETIREMENT 14 ARTICLE 19 GRIEVANCE PROCEDURE 15 ARTICLE 20 UNPAID LEAVES OF ABSENCE 17 ARTICLE 21 SENIORITY 18 ARTICLE 22 VACANCY NOTIFICATIONS 19 ARTICLE 23 CREDIT FOR IN-SERVICE COURSES 19 ARTICLE 24 PROBATIONARY PERIOD 20 ARTICLE 25 SMOKE-FREE ENVIRONMENT 20 ARTICLE 26 FLEXIBLE SPENDING ACCOUNT 20 ARTICLE 27 ATTENDANCE INCENTIVE 20 ARTICLE 28 PERSONNEL FILES 21 ARTICLE 29 EVALUATIONS 21 ARTICLE 30 EARLY DISMISSAL 21 ARTICLE 31 DIRECT DEPOSIT 21 ARTICLE 32 PAYROLL DEDUCTION 21 ARTICLE 33 PAYROLL DISTRIUBTION 22 ARTICLE 34 CONFORMITY OF LAW 22 ARTICLE 35 CHAPERONING AND PROCTORING 22 ARTICLE 36 BUS ATTENDANTS 22 ARTICLE 37 DURATION OF AGREEMENT 23

  • Content and Services Neither Licensor nor the provider of the wireless network is the provider of any financial services available through or related to the Software, and neither Licensor nor the provider of the wireless network or any contractor of the provider of the financial services available through or related to the Software, is responsible for any of the materials, information, products or services made available to you via the Software.

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

  • Software Updates XXXXX agrees to keep current with software licensed from Skyward and will install new versions on a timeline approved by XXXXX governance. This timeline will be communicated by NWRDC to the Districts. School District Workstations Configuration requirements for devices and their software that school district personnel use to access WSIPC’s software modules can be found on our website: xxxxx://xxx.xxxxx.xxx/technology‐team/. State Reports XXXXX will provide, at no additional fee, all data reports required by the state that impact 50% or more of the school districts in the state. WSIPC and NWRDC will work with state agencies to gather requirements on the required data. WSIPC will inform NWRDC staff of any mandated changes to state reports and NWRDC will communicate the information to the District. Appendix B NWRDC FTE Fees Fiscal Only NWRDC Software Support Services XXXXX Software Licensing Total FTE Fee $13.63 $20.34 $33.97 $15.56 $13.08 $28.64 $24.52 $20.34 $44.86 Student Only Full Service

  • Technical Specifications 1. A procuring entity shall not prepare, adopt or apply any technical specification or prescribe any conformity assessment procedure with the purpose or effect of creating an unnecessary obstacle to trade between the Parties.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

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