Administrative metadata Sample Clauses

Administrative metadata. The METS administrative metadata element <amdSec> references to technical and preservation metadata as seen in Figure 7. <amdSec> May contain Administrative metadata section PREMIS MIX ADDML Other technical metadata Figure 7: METS administrative metadata Preservation metadata can be included36 in the METS package. It is recommended that PREMIS37 is used for preservation metadata. For further reading: 35 Usually if EAC-CPF metadata has been embedded in the METS document once, it will be not referenced as EAC-CPF file again. 36 The Common Specification recommends avoiding embedding preservation or any other type of metadata directly in to the METS file. • More information about PREMIS can be found at: xxxx://xxx.xxx.xxx/standards/premis/ . • A guide on using PREMIS with METS may be found at: xxxx://xxx.xxx.xxx/standards/premis/guidelines-premismets.pdf. • Decisions made during the use of PREMIS can be recorded using this document: xxxx://xxx.xxx.xxx/standards/premis/premis_mets_checklist.pdf The guide on using PREMIS with METS (referenced above) recommends using the <amdSec> in order to reference PREMIS metadata. The complete rules for all elements and attributes in the <amdSec> are stated in the profile, the specific elements used when referencing or embedding are shown below. However, please note that preservation metadata varies for different content types and therefore best practice guidelines should be applied as required. Table 4: PREMIS metadata Element Definition Explanation Card. METS PREMIS metadata file Metadata file in PREMIS format referenced in the METS document Metadata file in PREMIS format when it is referenced in the METS document. Its needs to be stated in the submission agreement if referencing or embedding are used. 0..* <amdSec> <digiProvMD> <mdRef: MDTYPE= ”PREMIS” xlink:href=”file:///[ PREMIS metadata file]” xlink:type=”simple ”> PREMIS metadata38 Metadata in PREMIS format embedded in the METS document Metadata in PREMIS format when it is embedded in the METS document. It needs to be stated in the submission agreement if referencing or embedding are used. 0..* <amdSec> <digiProvMD> <mdWrap: MDTYPE= ”PREMIS”> <xmlData> 37 We expect that PREMIS will be created automatically by the E-ARK SIP and AIP Creation Tools. 38 We do not recommend embedding PREMIS metadata into the METS file. Element Definition Explanation Card. METS [PREMIS metadata in XML-format] Example: <amdSec ID="ID1a57e479-20e2-4e99-868b-88d0f816d109"> <digiprovMD ID="ID41d...
AutoNDA by SimpleDocs
Administrative metadata. Requirement 22: The AIP METS must have a single <amdSec> element which contains one or several <digiprovMD> elements. The <mdRef> child of at least one of these elements must be of type “PREMIS” (@MDTYPE=”PREMIS”) with the reference to a PREMIS file in the “Metadata” directory of the AIP root. Listing 5 shows an example with a link to a PREMIS.xml file: 30 Encoded Archival Description, xxxx://xxx.xxx.xxx/ead/ <amdSec ID="..."> <digiprovMD ID="...">

Related to Administrative metadata

  • Administrative data Before the mobility, it is necessary to fill in page 1 with information on the student, the Sending and the Receiving Institutions. The three parties have to agree on this section to be completed before the mobility. On page 1, most of the information related to the student, Sending and Receiving Institutions will have to be encoded in the Mobility Tool+ (for Capacity Building projects, in the EACEA Mobility Tool).

  • Administrative information IV.2.2) Time limit for receipt of tenders or requests to participate Date

  • Administrative Evaluation It is the intent of the SCD administration to conduct evaluations of non-priority- hire faculty as early as possible in a faculty member's employment in an SCD instructional unit. Administrative evaluation should occur before the beginning of the fifth quarter within the nine (9) out of twelve (12) quarter sequence outlined in Article 10.7.a.

  • Administrative Procedure iTrip staff will administer and determine whether a damage qualifies as Covered Damage. Such staff will have the sole authority to determine the nature and extent of damages, necessary repairs and eligibility for the waiver of liability described herein. The Covered Guest must report any theft or damage to the unit or its contents to iTrip staff by the time of check-out or any otherwise applicable damage waiver for such Covered Guest will be void. The iTrip Franchisee has ultimate claim administration authority. Arbitration is required prior to litigation.

  • Administrative Costs Administrative costs will not be included in the budget neutrality agreement, but the state must separately track and report additional administrative costs that are directly attributable to the demonstration. All administrative costs must be identified on the Forms CMS-64.10 Waiver and/or 64.10P Waiver.

  • Administrative Appeals An administrative appeal is a request for us to reconsider a full or partial denial of payment for covered healthcare services for the following reasons: • the services were excluded from coverage; • we determined that you were not eligible for coverage; • you or your provider did not follow BCBSRI’s requirements; or • a limitation on an otherwise covered benefit exists. You are not required to file a complaint (as described above), before filing an administrative appeal. If you call our Customer Service Department, a Customer Service Representative will try to resolve your concern. If the issue is not resolved to your satisfaction, you may file a verbal or written administrative appeal with our Grievance and Appeals Unit. If you request an administrative appeal, you must do so within one hundred eighty (180) days of receiving a denial of payment for covered healthcare services. The Grievance and Appeals Unit will conduct a thorough review of your administrative appeal and respond within: • thirty (30) calendar days for a prospective review; and • sixty (60) calendar days for a retrospective review. The letter will provide you with information regarding our determination.

  • Administrative Penalty That Respondent shall pay an Administrative Penalty of $1,000.00 to the Participating States to be distributed equally amongst the Participating States (the “per-state payment”).

  • Administrative Procedures Administrative procedures with respect to the sale of Notes shall be agreed upon from time to time by the Agents and the Company (the "Procedures"). The Agents and the Company agree to perform the respective duties and obligations specifically provided to be performed by them in the Procedures.

  • 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

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