Update the corresponding metadata Sample Clauses

Update the corresponding metadata. No direct connection to ESAP. In short, all aspects of this use case which are of relevance to ESAP are addressed in the project’s vision (§2), although further work is required to complete delivery of these capabilities.
AutoNDA by SimpleDocs

Related to Update the corresponding metadata

  • Schedule Updates the Contractor agrees to maintain the Work duration schedule updates on an ongoing basis and, when the County requests it, include the updates in its payment request. The Contractor may be required to submit a narrative report with each monthly update which shall include a description of current and anticipated problem areas, delaying factors and their impact, and an explanation of corrective action taken or proposed. Failure to do so may be considered a material breach of the Contract. Any additional or unanticipated costs or expense required to maintain the schedules shall be solely the Contractor’s obligation and Contractor agrees not to charge the County.

  • Paid Claims without Supporting Documentation Any Paid Claim for which Practitioner cannot produce documentation shall be considered an error and the total reimbursement received by Practitioner for such Paid Claim shall be deemed an Overpayment. Replacement sampling for Paid Claims with missing documentation is not permitted.

  • DOES THE SPR NEED TO BE UPDATED IF INFORMATION CHANGES Yes. It remains a continuing obligation of the principal or his/her authorized agent to update the SPR whenever any of the information provided on the initial form changes. WHERE DO THE SPR AND ANY UPDATES NEED TO BE FILED? The SPR needs to be filed with the County Department or County Division processing the application or matter. If and when an additional expenditure is incurred subsequent to the initial filing of the SPR, an amended SPR needs to be filed with the County Department or County Division where the original application, including the initial SPR, was filed. WHEN DO THE SPR AND ANY UPDATES NEED TO BE FILED? In most cases, the initial SPR needs to be filed with the other application forms. The SPR and any update must be filed with the appropriate County Department or County Division not less than seven (7) days prior to the BCC hearing date so that they may be incorporated into the BCC agenda packet. (See Section 2-354(b), Orange County Code.) When the matter is a discussion agenda item or is the subject of a public hearing, and any additional expenditure occurs less than 7 days prior to BCC meeting date or updated information is not included in the BCC agenda packet, the principal or his/her authorized agent is obligated to verbally present the updated information to the BCC when the agenda item is heard or the public hearing is held. When the matter is a consent agenda item and an update has not been made at least 7 days prior to the BCC meeting or the update is not included in the BCC agenda packet, the item will be pulled from the consent agenda to be considered at a future meeting.

  • Two-­‐character labels All two-­‐character ASCII labels shall be withheld from registration or allocated to Registry Operator at the second level within the TLD. Such labels may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator, provided that such two-­‐character label strings may be released to the extent that Registry Operator reaches agreement with the related government and country-­‐code manager of the string as specified in the ISO 3166-­‐1 alpha-­‐2 standard. The Registry Operator may also propose the release of these reservations based on its implementation of measures to avoid confusion with the corresponding country codes, subject to approval by ICANN. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such labels that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Registry Operator may self-­‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.

  • Updates and Upgrades Contractor grants to the Department a non-exclusive, non-transferable license to use upgrades and updates provided by Contractor during the term of the Contract. Such upgrades and updates are subject to the terms of the Contract. The Department shall download, distribute, and install all updates as released by Contractor during the length of the Contract, and Contractor strongly suggests that the Department also downloads, distributes, and installs all upgrades as released by Contractor during the length of the Contract. Contractor shall use commercially reasonable efforts to provide the Department with work-around solutions or patches to reported software problems that may affect the Department’s use of the software during the length of the Contract.

  • RIGHTS TO BID, PROPOSAL AND CONTRACTUAL MATERIAL All material submitted by the Contractor to the City shall become property of the City upon receipt. Any portions of such material claimed by the Contractor to be proprietary must be clearly marked as such. Determination of the public nature of the material is subject to the Texas Public Information Act, Chapter 552, and Texas Government Code.

  • Reference Materials The Board agrees to continue to make available to employees the reference materials maintained by the district. Principals are encouraged to provide additional reference materials of high use in schools where feasible.

  • Drawings Submitted During the Contract Term Where required to develop maintain and deliver diagrams or other technical schematics regarding the scope of work, Contractor shall do so on an ongoing basis at no additional charge, and must, as a condition of payment, update drawings and plans during the Contract term to reflect additions, alterations, and deletions. Such drawings and diagrams shall be delivered to the Authorized User’s representative.

  • Updates “Updates” are changes that do not require a change to the established Centralized Contract terms and conditions. Updates may include: Centralized Contract changes and updates made in accordance with the previously approved pricing formula (e.g. discount from list price); adding new products or services within the established, previously approved pricing structure; lowering pricing of products or services already on Contract, deleting products or services available through the Centralized Contract, adding product or service that do not fall under the previously established price structure or discounts under the Contract, re-bundled products, and other updates not listed above that are deemed to be in the best interest of the State and do not result in a change to the established Centralized Contract terms and conditions. Updates must be submitted to OGS for review, and must be accompanied by a justification of reasonableness of price if the change results in a change in pricing methodology. OGS will notify Contractor in writing if approved.

  • PRICE LISTS AND PRODUCT INFORMATION Contractors should provide an electronic version of the proposed price list in an Excel format or pdf on a jump drive. Also provide a dealer list, if applicable in an Excel format with "read and write" capabilities on the same jump drive. No costs or expenses associated with providing this information in the required format shall be charged to the State of Arkansas. At the time of contract renewal contractor will furnish OSP with an updated dealer list and published price list.

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