Metadata standards Sample Clauses

Metadata standards. The metadata standards are described for each Content Partner’s collection individually below. The reasons to the individual approach were described in the deliverable D2.1. In short summary these reasons are: • different types of original documents • different cataloguing practices, tools and formats • different approaches to digitisation
AutoNDA by SimpleDocs
Metadata standards. All available collections Descriptive metadata UNIMARC slim in the form of XML UNIMARC slim format conforms regular cataloguing guides and will be converted to TEI P5 using a dedicated connector. Possible derivations from the cataloguing manual guides and content of possible national specifics fields will be discussed with the responsible BNCF cataloguers. UNIMARC slim profile is agreed to be included later during ENRICH progress. Structural metadata MAG The MAG format contains not only a physical structure information but also the valuable applicable foliation/application (which is appreciated by the end-users as the researchers can refer to or can be referred to a particular page/folio both in the original AND the digitised document. Additional metadata related notes BNCF uses a DC format to share bibliographic descriptions (DC based profile is mandatory for OAI-PMH interface). The records contain only a substraction of the original structure, therefore will not be processed.
Metadata standards. Manuscripts, maps Descriptive metadata MARC 21 in the form of XML The MARC 21 format conforms regular cataloguing guides and will be converted to TEI P5 using a dedicated connector. Possible derivations from the cataloguing manual guides and content of possible national specifics fields will be discussed with the responsible BNE cataloguers. Structural metadata none There are no structural metadata that would enable the construction of documents according the basic principles of cooperation within the ENRICH project. The metadata are being prepared during the project to enable the collaboration. Additional metadata related notes BNE uses also a DC format to present the bibliographic descriptions (DC based profile is mandatory for OAI-PMH interface). The records contain only a substraction of the original structure, therefore will not be processed.
Metadata standards. All documents Descriptive metadata local format in the form of XML wrapped in the METS format The local format structure was analysed and it will be converted to TEI P5 using a dedicated connector. Structural metadata METS structural maps According to the common METS format practice.
Metadata standards. Manuscripts, incunabulas Descriptive metadata MASTER+ using M-Tool Structural metadata MASTER+ using M-Tool Charters Descriptive metadata CEI a TEI based XML format; structure was analysed and it will be converted to TEI P5 using a dedicated connector. Structural metadata CEI Additional metadata related notes Some of the documents contain full texts.
Metadata standards. Manuscripts Descriptive metadata MASTER+ using M-Tool Structural metadata MASTER+ using M-Tool
Metadata standards. Manuscripts Descriptive metadata DC The content of the primary local metadata format is very similar, near the sane, as the DC. Therefore the DC is processed. Structural metadata METS with DC wrapped; special mets_exp profile exist in the OAI-PMH interface as the JPEG files are generated ad-hoc for the ENRICH project needs
AutoNDA by SimpleDocs
Metadata standards. Incunabulas Descriptive metadata ISTC The primary format will possibly be replaced in the processing by DC records in case it will be confirmed it contains the same ENRICH-useful information content as the primary metadata. Structural metadata METS structural maps Manuscripts Descriptive metadata TEI P5 UZK will migrate to the TEI P5 during the ENRICH project. Structural metadata TEI P5
Metadata standards. All documents Descriptive metadata MARC 21 in the form of XML The MARC 21 format conforms regular cataloguing guides and will be converted to TEI P5 using a dedicated connector. Possible derivations from the cataloguing manual guides and content of possible national specifics fields will be discussed with the responsible BNE cataloguers. Structural metadata METS structural maps According to the common METS format practice.

Related to Metadata standards

  • OMB Standards Unless specified otherwise within this agreement, the Subrecipient shall procure all materials, property, or services in accordance with the requirements of 24 CFR 84.40−48.

  • Safety Standards Performance of the Contract for all commodities or contractual services must comply with requirements of the Occupational Safety and Health Act and other applicable State of Florida and federal requirements.

  • Quality Standards Each Party agrees that the nature and quality of its products and services supplied in connection with the other Party's Marks will conform to quality standards set by the other Party. Each Party agrees to supply the other Party, upon request, with a reasonable number of samples of any Materials publicly disseminated by such Party which utilize the other Party's Marks. Each Party will comply with all applicable laws, regulations, and customs and obtain any required government approvals pertaining to use of the other Party's marks.

  • Technical Standards The Generation System shall be installed and operated by the Interconnection Customer consistent with the requirements of this Agreement; the Technical Requirements; the applicable requirements located in the National Electrical Code (NEC); the applicable standards published by the American National Standards Institute (ANSI) and the Institute of Electrical and Electronic Engineers (IEEE); and local building and other applicable ordinances in effect at the time of the installation of the Generation System.

  • Service Level Standards In addition to all other requirements in this Agreement, and in accordance with the Best Claims Practices & Estimating Guidelines, Vendor shall use reasonable and good faith efforts to meet the Service Level Standards set forth below.

  • Content Standards You agree that you will not upload or provide content or otherwise post, transmit, distribute, or disseminate through the Zelle® Payment Service any material that: (1) is false, misleading, unlawful, obscene, indecent, lewd, pornographic, defamatory, libelous, threatening, harassing, hateful, abusive, or inflammatory; (2) encourages conduct that would be considered a criminal offense or gives rise to civil liability; (3) breaches or infringes any duty toward or rights of any person or entity, including rights of publicity, privacy or intellectual property; (4) contains corrupted data or any other harmful, disruptive, or destructive files; (5) advertises products or services competitive with Zelle®, as determined by Zelle® in its sole discretion; or (6) in Zelle®’s or our sole judgment, is objectionable, restricts or inhibits any person or entity from using or enjoying any portion of the Zelle® Payment Service, or which may expose us, Zelle® or our respective affiliates or customers to harm or liability of any nature.

  • Security Standards The Provider shall implement and maintain commercially reasonable security procedures and practices that otherwise meet or exceed industry standards designed to protect Student Data from unauthorized access, destruction, use, modification, or disclosure, including but not limited to the unauthorized acquisition of computerized data that compromises the security, confidentiality, or integrity of the Student Data (a "Security Breach"). For purposes of the DPA and this Exhibit G, "Security Breach" does not include the good faith acquisition of Student Data by an employee or agent of the Provider or LEA for a legitimate educational or administrative purpose of the Provider or LEA, so long as the Student Data is used solely for purposes permitted by SOPPA and other applicable law, and so long as the Student Data is restricted from further unauthorized disclosure.

  • ETHICAL STANDARDS a. Distributor and each of its sub-distributors will comply with the United States Foreign Corrupt Practices Act and without derogating from the generality of the foregoing, will not have its directors, officers or employees, directly or indirectly, offer, promise or pay any bribes or other improper payments for the purposes of promoting and/or selling Products to any individual, corporation, government official or agency or other entity. No gift, benefit or contribution in any way related to MEC or the promotion and/or sale of Products will be made to political or public officials or candidates for public office or to political organizations, regardless of whether such contributions are permitted by local laws.

  • CONTRACT WORK HOURS AND SAFETY STANDARDS As per the Contract Work Hours and Safety Standards Act (40 U.S.C. 3701-3708), where applicable, all Customer Purchase Orders in excess of ,000 that involve the employment of mechanics or laborers must include a provision for compliance with 40 U.S.C. 3702 and 3704, as supplemented by Department of Labor regulations (29 CFR Part 5). Under 40 U.S.C. 3702 of the Act, each contractor must be required to compute the wages of every mechanic and laborer on the basis of a standard work week of 40 hours. Work in excess of the standard work week is permissible provided that the worker is compensated at a rate of not less than one and a half times the basic rate of pay for all hours worked in excess of 40 hours in the work week. The requirements of 40 U.S.C. 3704 are applicable to construction work and provide that no laborer or mechanic must be required to work in surroundings or under working conditions which are unsanitary, hazardous or dangerous. These requirements do not apply to the purchases of supplies or materials or articles ordinarily available on the open market, or contracts for transportation or transmission of intelligence.

  • Reference Standards A. Standards, Specifications, Codes, Laws, and Regulations

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