GENERAL SIP METADATA Sample Clauses

GENERAL SIP METADATA. The general SIP metadata is based on the METS standard and presented as a profile. METS profiles are intended to describe a class of METS documents in sufficient detail to provide both document authors and programmers with the guidance they need to create and process METS documents conforming to a particular profile.21 Creating a METS profile requires a good understanding of the METS Profile components. An overview of these components can be found in the METS online documentation22 and in Appendix D on page 44 in the D3.2 specification. There are 5 main sections in this METS profile: • <metsHdr> - METS header (metadata about the creator, contact persons, etc. of the IP). • <dmdSec> - descriptive metadata (references to EAD, EAC-CPF, etc.). • <amdSec> - administrative metadata (how files were created and stored, intellectual property rights, etc.). • <fileSec> - file section, lists all files containing content (may also contain metadata about files). • <structMap> - structural map, describes the hierarchical structure of the digital object and the whole IP (i.e. object + metadata). These sections will be described in more detail in sections 3.1 to 3.6. All these sections present the E- ARK SIP requirements for METS elements in table form according to the following structure: • Element - The name of the element in plain text used in the accompanying schema for elements or attributes. For more information regarding elements and attributes in XML see WWW Consortium (xxxx://xxx.x0.xxx/). • Definition - Defines the functions of the element. Contains an explanation of the element and some example values. • Cardinality – Represents the number of occurrences of an element (see below). o 0..1 The element is optional and cannot be repeated. o 0..* – The element is optional and can be repeated. o 1 The element is mandatory and can only be stated once. o 1.. The element is mandatory and has one or more occurrences. • METS - Defines the element in the METS standard used for designing the E-ARK element. The column uses XML-syntax. [ ] defines where the value is placed. 21 METS Profiles, xxxx://xxx.xxx.xxx/standards/mets/mets-profiles.html 22 METS Profile Components, xxxx://xxx.xxx.xxx/standards/mets/profile_docs/components.html
Sample 1
AutoNDA by SimpleDocs

Related to GENERAL SIP METADATA

  • Přetrvající platnost This Section 3 “

  • Přetrvávající platnost Tento odstavec 1.3 “Zdravotní záznamy a Studijní data a údaje” zůstane závazný i v případě zániku platnosti či vypršení platnosti této Smlouvy.

  • General Scope Except for matters on which the Members’ approval is required by the Act or this Agreement, the Manager has full power, authority and discretion to manage and direct the Company’s business, affairs and properties, including the specific powers referred to in paragraph (b), below.

  • General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:

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

  • SBC-12STATE 47.1.1 The terms contained in this Agreement and any Appendices, Attachments, Exhibits, Schedules, and Addenda constitute the entire agreement between the Parties with respect to the subject matter hereof, superseding all prior understandings, proposals and other communications, oral or written between the Parties during the negotiations of this Agreement and through the execution and/or Effective Date of this Agreement. This Agreement shall not operate as or constitute a novation of any agreement or contract between the Parties that predates the execution and/or Effective Date of this Agreement.

  • Business Auto Liability The following Automobile Liability will be required and coverage shall apply to all owned, hired, and non-owned vehicles used with minimum limits of: $100,000 bodily injury per person (B.I.) $300,000 bodily injury per occurrence (B.I.) $100,000 property damage (PD) or $300,000 combined single limit (C.S.L.) of B.I. and P.D.

  • General Background (Brief description of the national, sector-specific or other relevant context in which the individual contractor will operate)

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • Library Borrowing privileges available without charge. Upon retirement an employee shall be issued a permanent individual library card.

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