Preservica Sample Clauses

Preservica. Preservica uses a workflow system and, as such, does not require any specific SIP structure. Hence, it can receive SIPs that are ingested in a variety of structures (e.g., national standards like ARELDA in Switzerland, EDIAKT in Austria or SAHKE2 in Finland). However, it is most efficient to convert whatever SIP is received into a standard Preservica-defined SIP structure. This allows existing ingest workflows to be reused. The standard Preservica-defined SIP structure has exactly one root or top-level directory. The name of the root directory is the string representation of a randomly generated (version 4) UUID as seen in Figure 15. The root directory contains a subdirectory named content, and the associated metadata in a file called metadata.xml. The content subdirectory contains all the physical files that make up the SIP; any arbitrary directory / file hierarchy is allowed within the content subdirectory. Figure 15: Structure of a Submission Information Package in Preservica The metadata must conform to the XIP schema and it must include a protocol file. Preservica provides also a locally installable (optional) “SIP Creator” to • Build submission packages from locally held files; • Assign descriptive metadata from fragments created elsewhere or by using a GUI; • Select where in the hierarchy to place the submission; • Upload content to Preservica. The minimum set of steps which are required to transfer digital records into the archive are to copy the records into Preservica’s working area, ensure that the metadata etc. is correctly formed and then to store the files in Preservica’s storage area(s) and the metadata in Preservica’s metadata store database. However, this does not carry out all of the quality checks on the records being submitted that should be expected in a long-term repository, nor does it characterise the content files. Characterisation needs to be carried out because the information it provides is needed in order to be able to preserve the ingested information objects; however, such information objects can be characterised post-ingest, so it does not have to be included in an ingest workflow. Preservica includes workflow steps which implement both these additional processes, and standard workflows that incorporate them. An example of such a workflow is shown in Figure 16. Figure 16: Ingest workflow in Preservica • Pre-Ingest - SIPs must be created in or transformed into defined format. • Receive Submission - Once a suitable SIP has bee...
Sample 1
AutoNDA by SimpleDocs

Related to Preservica

  • Preservation Fail to use reasonable efforts to preserve intact in any material respect their business organizations and assets and maintain their rights, franchises and existing relations with customers, suppliers, employees and business associates.

  • Media preservation and protection When a Contractor discovers a cyber incident has occurred, the Contractor shall preserve and protect images of all known affected information systems identified in paragraph (c)(1)(i) of this clause and all relevant monitoring/packet capture data for at least 90 days from the submission of the cyber incident report to allow DoD to request the media or decline interest.

  • Preservation of Evidence Both Parties will take action to protect and preserve the fire origin area and evidence pertaining to the fire cause.

  • Historic Preservation Subrecipient agrees to comply with the Historic Preservation requirements set forth in the National Historic Preservation Act of 1966, as amended (16 U.S.C. 470) and the procedures set forth in 36 CFR 800, Protection of Historic Properties, insofar as they apply to the performance of this Contract. In general, this requires concurrence from the State Historic Preservation Officer for all rehabilitation and demolition of historic properties that are fifty years old or older or that are included on a Federal, State, or local historic property list.

  • Industrial cooperation The aim of cooperation shall be to:

  • Preservation of Existence, Etc (a) Preserve, renew and maintain in full force and effect its legal existence and good standing under the Laws of the jurisdiction of its organization except in a transaction permitted by Section 7.04 or 7.05; (b) take all reasonable action to maintain all rights, privileges, permits, licenses and franchises necessary or desirable in the normal conduct of its business, except to the extent that failure to do so could not reasonably be expected to have a Material Adverse Effect; and (c) preserve or renew all of its registered patents, trademarks, trade names and service marks, the non-preservation of which could reasonably be expected to have a Material Adverse Effect.

  • Fair Use For the avoidance of doubt, nothing in this Agreement shall restrict or limit either Party’s right to make any use of any term or trademark that constitutes fair use under Applicable Law or factual use for historical or reference purposes.

  • Cooperation with Economic Studies If ICANN initiates or commissions an economic study on the impact or functioning of new generic top-­‐level domains on the Internet, the DNS or related matters, Registry Operator shall reasonably cooperate with such study, including by delivering to ICANN or its designee conducting such study all data related to the operation of the TLD reasonably necessary for the purposes of such study requested by ICANN or its designee, provided, that Registry Operator may withhold (a) any internal analyses or evaluations prepared by Registry Operator with respect to such data and (b) any data to the extent that the delivery of such data would be in violation of applicable law. Any data delivered to ICANN or its designee pursuant to this Section 2.15 that is appropriately marked as confidential (as required by Section 7.15) shall be treated as Confidential Information of Registry Operator in accordance with Section 7.15, provided that, if ICANN aggregates and makes anonymous such data, ICANN or its designee may disclose such data to any third party. Following completion of an economic study for which Registry Operator has provided data, ICANN will destroy all data provided by Registry Operator that has not been aggregated and made anonymous.

  • Preservation of Privilege Nothing contained in this Agreement or any Consent Judgment, and no act required to be performed pursuant to this Agreement or any Consent Judgment, is intended to constitute, cause, or effect any waiver (in whole or in part) of any attorney-client privilege, work product protection, or common interest/joint defense privilege, and each Party and Participating Subdivision agrees that it shall not make or cause to be made in any forum any assertion to the contrary.

  • COOPERATION WITH THIRD PARTIES The Contractor shall be responsible for fully cooperating with any third party, including but not limited to other Contractors or Subcontractors of the Authorized User, as necessary to ensure delivery or performance of Product.

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