Descriptive metadata Sample Clauses

Descriptive metadata. The package must include a simple EAD file which uses the mandatory elements as defined for the general DIP format. In short, EAD metadata must use the tags set out in the E-ARK DIP Pilot Specification D5.3, among others the following mandatory elements need to be used: • The title for each descriptive unit within the package (element did/unittitle); • The creation date of the record or descriptive unit (one of the elements did/unitdate or • The relative path to the file or folder within the \representations\[repID]\Data folder of the DIP (element did/dao with the href attribute referring to the relative location of the file, other attributes used according to the official EAD3 standard). If the record includes multiple computer files the additional use of the element did/daoset is needed102. The use of all other elements is optional. Example: … <c02 level="record"> <did> <unittitle>Circular no 25</unittitle> <unitdate type="single" normal="20010324">March 24, 2001</unitdate> … <daoset label="Computer Files" coverage="whole"> <dao daotype="borndigital" linktitle="Circular no 25 body" href="/representations/ID0023dfc33/Circular_no_25/C25_main.pdf"> </dao> <dao daotype="borndigital" linktitle="Circular no 25 Annex I" href="/representations/ID0023dfc33/Circular_no_25/AnnexI.pdf"> </dao> </daoset> </did> </c02> … 102 Like mentioned before, the final linking method is yet to be established. For scenario b) above the package is also expected to include further metadata taken from the extended EAD set as described in Appendix 1 of the E-ARK SMURF Profile (D3.3). The mandatory elements which need to be included: • archival aggregation level(s) to which the records belong (using the @level attribute on the archdesc, c, c01 etc element); • and archival history of the record (using the custodhist element); • if applicable, EAD metadata must also include information about any access restrictions to the records (using the accessrestrict element).
Sample 1
AutoNDA by SimpleDocs
Descriptive metadata. The descriptive metadata section (<dmdSec>) references descriptive metadata contained in the AIP. Mul- tiple <dmdSec> elements are allowed so that descriptive metadata can be referenced for each separate item within the METS object. Descriptive metadata is referenced by means of the <mdRef> element as part of the descriptive metadata element <dmdSec>. Listing 4 shows an example linking to an EAD XML metadata file. <dmdSec ID="ID550e8400-e29b-41d4-a716-44665544000a"> <mdRef LOCTYPE="URL" MDTYPE="EAD" MIMETYPE="text/xml" CREATED="2015-04-26T12:00:00+01:00" xlink:type="simple" xlink:href="file://./metadata/EAD.xml" CHECKSUMTYPE="SHA-256" CHECKSUM="..." SIZE="2321"/> </dmdSec>
Sample 1
Descriptive metadata. The METS descriptive metadata element <dmdSec> references to archival description metadata (EAD, EAC- CPF, etc.) as seen in Figure 6. May contain <dmdSec> Archival information can be included in the METS package. For the core interest groups in E-ARK – archival institutions – this information is delivered to the recipient in EAD and EAC-CPF formats. To include EAD and EAC-CPF in a METS profile the use of <dmdSec> is to be preferred according to the METS implementation guide referenced above. The complete rules for all elements and attributes in the <dmdSec> are stated in the profile, the specific elements used when referencing and embedding is shown below. Other metadata standards for description and administrative purposes can be used and referencing or embedding32 them must adhere to the <amdSec> and <dmdSec> rules stated in the profile. EAD metadata file Metadata file in EAD format referenced in the METS document Metadata file in EAD 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..* <dmdSec> <mdRef: MDTYPE=”EAD” xlink:href=”file:/// 33[EAD-metadata file]” xlink:type=”simple ”> EAD metadata Metadata in EAD format embedded in the METS document Metadata in EAD format when it is embedded34 in the METS document. Its needs to be stated in the submission agreement if referencing or embedding are used. 0..* <dmdSec> <mdWrap: MDTYPE=”EAD”> <xmlData> [EAD metadata in XML-format] EAC-CPF metadata file Metadata file in EAC-CPF format referenced in the METS document Metadata file in EAC-CPF 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..* <mdSec> <mdRef: MDTYPE= ”EAC-CPF” xlink:href=”file:///[ EAC-CPF metadata file]” xlink:type=”simple 32 The Common Specification recommends to avoid embedding. 33 The coice of using ”///” or ”//” depends on implementations. For example, a Windows file path could be file://C:/somefile.txt and file:///somefile.txt would be the corresponding Unix path in case of absolute paths. 34Usually if EAD metadata has been embedded in the METS document once, it will be not referenced as EAD file again.
Sample 1

Related to Descriptive metadata

  • Descriptive Data The contractor shall deliver data in accordance with and as specified in Section J, Exhibit A (Contract Data Requirements List (CDRL)) and as cited in each individual task order.

  • Descriptive Headings, Etc The headings in this Agreement are for convenience of reference only and shall not limit or otherwise affect the meaning of terms contained herein. Unless the context of this Agreement otherwise requires: (i) words of any gender shall be deemed to include each other gender; (ii) words using the singular or plural number shall also include the plural or singular number, respectively; (iii) the words “hereof,” “herein” and “hereunder” and words of similar import when used in this Agreement shall refer to this Agreement as a whole and not to any particular provision of this Agreement, and Section and paragraph references are to the Sections and paragraphs of this Agreement unless otherwise specified; (iv) the word “including” and words of similar import when used in this Agreement shall mean “including, without limitation,” unless otherwise specified; (v) “or” is not exclusive; and (vi) provisions apply to successive events and transactions.

  • Descriptive Headings Descriptive headings of the several Sections of this Agreement are inserted for convenience only and shall not control or affect the meaning or construction of any of the provisions hereof.

  • Descriptive Heading The descriptive headings of this Agreement are for convenience of reference only, are not to be considered a part hereof and shall not be construed to define or limit any of the terms or provisions hereof.

  • Headings Descriptive The headings of the several sections and subsections of this Agreement are inserted for convenience only and shall not in any way affect the meaning or construction of any provision of this Agreement.

  • Labels The Contractor shall provide fuel content labels/signs for each pumping station. These labels shall identify significant amounts of alcohols in the fuel and satisfy the requirements of 1NYCRR, Part 224 and 6NYCRR, Part

  • Descriptive Headings; Governing Law The descriptive headings of the paragraphs of this Warrant are inserted for convenience only and do not constitute a part of this Warrant. The construction, validity and interpretation of this Warrant will be governed by the laws of the State of Delaware.

  • Descriptive Headings and Governing Law The descriptive headings of the several sections and paragraphs of this Warrant are inserted for convenience only and do not constitute a part of this Warrant. This Warrant shall be construed and enforced in accordance with, and the rights of the parties shall be governed by, the laws of the State of California.

  • Contract Database Metadata Elements Title: Great Neck Union Free School District and Great Neck Paraprofessionals Association (2011) Employer Name: Great Neck Union Free School District Union: Great Neck Paraprofessionals Association Local: Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 5132 Unit Size: Number of Pages: 28 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/ ARTICLE# TITLE PAGE# Preamble 2 Article 1 Association Rights 2 Article 2 Board-Administration-Association Relationship and Procedures 4 Article 3 Exchange of Proposals 6 Article 4 Professionals Duties and Responsibilities of Paraprofessionals 7 Article 5 Work Assignments 8 Article 6 Annual Appointment 10 Article 7 Selection and Promotion 10 Article 8 Evaluations and Standards 11 Article 9 Procedures for Termination of Employment 11 Article 10 Conferences 12 Article 11 Human Resource File 12 Article 12 Professional Growth 13 Article 13 Sick Leave 14 Article 14 Personal Leave 16 Article 15 Other Leaves 17 Article 16 Grievance Procedures 18 Article 17 Legal Assistance 19 Article 18 Conformity to Law 19 Article 19 Health Insurance 20 Article 20 Retirement Plan 20 Article 21 Salary Schedule 21 Article 22 Seniority Policy 23 Article 23 Compensation for Financial Loss 24 Article 24 Duration of Agreement 25 Appendix A Determination of Negotiating Unit 25 Appendix B Payroll Deduction Authorization 26 Appendix C Bus Aides 26 Appendix D Salary Schedules 27

  • Metadata Where the Contractor has or generates metadata as a result of services provided to the Province, where that metadata is personal information, the Contractor will: not use it or disclose it to any other party except where the Agreement otherwise specifies; and remove or destroy individual identifiers, if practicable.

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