Metadata gateway Sample Clauses

Metadata gateway. This is the user interface to be used by content providers for the ingestion [month 12] Schedule of relevant Milestones Milestone number 59 Milestone name Lead benefi- ciary number Delivery date from Annex I 60 Comments MS7 ▇▇▇▇▇▇▇▇ ready for delivery of content to Europeana 7 12 this is the starting point for the beginning of mapping and delivery of metadara records to Europeana Project Number 1‌ 270905 Project Acronym 2 Linked Heritage One form per Work Package Work package number 53 WP6 Work package title Coordination of Content Start month 6 End month 30 Lead beneficiary number 55 17 Objectives • To gather feedback for the refinement and improvement of the environment and the system as a whole, in order to support tier-one countries and others who have not yet contributed large amounts of content to Europeana • To provide support to the content providers for the mapping of their metadata formats to the Linked Heritage format • To contribute large amounts of enhanced content to Europeana, including private sector content Description of work and role of partners
View Source
Metadata gateway. This is the user interface to be used by content providers for the ingestion [month 12] Schedule of relevant Milestones Milestone number 59 Milestone name Lead benefi- ciary number Delivery date from Annex I 60 Comments MS7 ▇▇▇▇▇▇▇▇ ready for delivery of content to Europeana 7 12 this is the starting point for the beginning of mapping and delivery of metadara records to Europeana Project Number 1 270905 Project Acronym 2 Linked Heritage Work package number 53 WP6 Work package title Coordination of Content Start month 6 End month 30 Lead beneficiary number 55 17 • To gather feedback for the refinement and improvement of the environment and the system as a whole, in order to support tier-one countries and others who have not yet contributed large amounts of content to Europeana • To provide support to the content providers for the mapping of their metadata formats to the Linked Heritage format • To contribute large amounts of enhanced content to Europeana, including private sector content
View Source

Related to Metadata gateway

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

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store County 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 County Information Security Office.

  • Workstation Encryption Supplier will require hard disk encryption of at least 256-bit Advanced Encryption Standard (AES) on all workstations and/or laptops used by Personnel where such Personnel are accessing or processing Accenture Data.

  • End User This agreement shall bind the ordering activity as end user but shall not operate to bind a Government employee or person acting on behalf of the Government in his or her personal capacity.