Versioning of files and documents Sample Clauses

Versioning of files and documents. In all instances, all new files in the repository should be notified promptly and no change or versioning should take place without previous or short notice. Versioning of files will be used, with interested parties initially responsible for documents, via email or any other agreed method. All documents, documentation, proposals must be shared via the repository with all partners for discussion with a clear deadline before entering into force and being deposited in the repository for future reference. Documents should be drafted initially by one or more people and then shared to the general mailing list with a link to their repository location. This discussion of documents at the level of Work Packages should be via a two-tiered approach. The first discussion and versioning should be internal to the WP and the second one extended to the all the partners, both of them with a clear deadline.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Versioning of files and documents

  • Quality control records and Documents The Contractor shall hand over a copy of all its quality control records and documents to the Authority’s Engineer before the Completion Certificate is issued pursuant to Clause 12.2. The Contractor shall submit Road Signage Plans to the Authority Engineer for approval at least 6 (six) months prior to expected completion of Project Highway.

  • Inspection of Goods 8.1 The Buyer shall inspect the goods upon delivery.

  • Records and Documentation The Sub-Recipient agrees to make available to AAAPP staff and/or any party designated by the AAAPP any and all contract related records and documentation. The Sub-Recipient shall ensure the collection and maintenance of all program related information and documentation on any such system designated by the AAAPP. Maintenance includes valid exports and backups of all data and systems according to AAAPP standards.

  • Processing of Deposit files The use of compression is recommended in order to reduce electronic data transfer times, and storage capacity requirements. Data encryption will be used to ensure the privacy of registry escrow data. Files processed for compression and encryption will be in the binary OpenPGP format as per OpenPGP Message Format -­‐ RFC 4880, see Part A, Section 9, reference 3 of this Specification. Acceptable algorithms for Public-­‐key cryptography, Symmetric-­‐key cryptography, Hash and Compression are those enumerated in XXX 0000, not marked as deprecated in OpenPGP IANA Registry, see Part A, Section 9, reference 4 of this Specification, that are also royalty-­‐free. The process to follow for the data file in original text format is:

  • Public Records Request (09/17) Contractor acknowledges that the City of Portland is subject to the Oregon Public Records Act and Federal law. Third persons may claim that the Confidential Information Contractor submitted to the City hereunder may be, by virtue of its possession by the City, a public record and subject to disclosure pursuant to the Oregon Public Records Act. The City’s commitments to maintain certain information confidential under this Contract are all subject to the constraints of Oregon and federal laws. All information submitted by Contractor is public record and subject to disclosure pursuant to the Oregon Public Records Act, except such portions for which Contractor requests and meets an exemption from disclosure consistent with federal or Oregon law. Within the limits and discretion allowed by those laws, the City will maintain the confidentiality of information.

  • Delivery and Documents 13.1 Subject to GCC Sub-Clause 33.1, the delivery of the Goods and completion of the Related Services shall be in accordance with the List of Goods and Delivery Schedule specified in the Supply Requirements. The details of shipping and other documents to be furnished by the Supplier are specified in the SCC.

  • Inspection of Records Upon reasonable notice to the Administrative Trustees and the Property Trustee, the records of the Trust shall be open to inspection by Securityholders during normal business hours for any purpose reasonably related to such Securityholder's interest as a Securityholder.

  • Inspections, Records, and Cooperation The Owner agrees to provide any information pertinent to this Contract which the Program Administrator, PJ, or HUD may reasonably require. Further, upon reasonable notice to the Owner, Owner agrees to provide access to the Program Administrator, PJ, HUD, or their representatives to the Unit, the property on which the Unit is located, and the Owner’s records (wherever located) relevant to this Contract and compliance with Program requirements. The Owner further agrees to provide access to such records to the Comptroller General of the United States (commonly known as the Government Accountability Office or “GAO”). The Owner must grant access to relevant computerized or other electronic records and to any computers, equipment, or facilities containing such records, and must provide any information or assistance needed to access the records. Such rights to inspect and review will not expire until five (5) years after the date of expiration or termination of this Contract.

  • Inspection of construction records The Authority shall have the right to inspect the records of the Contractor relating to the Works.

  • Public Records Requests If the Department receives a public records request for materials designated by the Contractor as trade secret or otherwise confidential under Florida or federal law, the Contractor will be responsible for taking the appropriate legal action in response to the request. If the Contractor fails to take appropriate and timely action to protect the materials designated as trade secret or otherwise confidential, the Department will provide the materials to the requester.

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