Preparing recommendations for the District Sample Clauses

Preparing recommendations for the District. 1.12. Conduct a telephonic and correspondence campaign to attempt to increase interest among qualified bidders.
AutoNDA by SimpleDocs

Related to Preparing recommendations for the District

  • Manufacturer's Recommendations All work or materials shall be installed in accordance with the manufacturer's recommendations and requirements. The Contractor shall obtain the manufacturer’s recommendations and requirements, for its use at the Site in executing the Work, copies of bulletins, circulars, catalogues, or other publications bearing the manufacturer’s titles, numbers, editions, dates, etc. If the manufacturer’s recommendations and requirements are not available, the Contractor shall request installation instructions from the Design Professional.

  • Representations and Recommendations Unless otherwise stated in writing, neither Xxxxxxxx Realty Inc, nor its brokers or licensees have made, on their own behalf, any representations or warranties, express or implied, with respect to any element of the Property including but not limited to, the legal sufficiency, legal effect, or tax consequences of this transaction. Any information furnished by either party should be independently verified before that party relies on such information. Xxxxxxxx Realty Inc. recommends that Buyer consult its attorneys and accountants before signing this Agreement regarding the terms and conditions herein and that Seller satisfy itself as to the financial ability of Buyer to perform.

  • Conclusion and Recommendations D. Evaluations for Offenders without a sex offense conviction shall answer the following additional referral questions in the evaluations:

  • Conclusions and Recommendations The demonstration and evaluation process provided an opportunity to test community specific tools with a range of end users from the memory institution domain and to gain greater insight into both the current and future evolution of the SHAMAN prototypes for preservation, access and re-use. Xxxx et al. (2000) in their user evaluation study of the Alexandria Digital Library which incorporated the evaluation of a Web prototype by earth scientists, information specialists and educators raised four key questions in relation to their findings that SHAMAN may be well advised to consider, they are paraphrased here with our conclusions from the investigations. What have we learned about our target organizations and potential users?  Memory institutions are most definitely not a homogenised group; their needs and requirements differ greatly across the domain.  Representatives of the archives community are agreed on the benefits of SHAMAN‟s authenticity validation function.  The representatives of government information services remained unconvinced as to the need or benefit of grid technologies or distributed ingest while librarians saw the value of grid access as an asset of the framework. What have we learned about the evaluation approach for digital preservation?  Within the limits of the exercise, in terms of time-frame and resources, the approach adopted has generated useful information for the further development of demonstrators and for the development of the SHAMAN framework overall. What have we learned about the SHAMAN ISP1 demonstrator?  Respondents to the evaluation questionnaires and the focus groups indicate that, overall, the presentation of the demonstrator worked effectively and that, in general, participants in the demonstration and evaluation events were able to understand the intentions of the demonstration and to apply the ideas presented to their own context. What have we learned about the applicability of the SHAMAN framework to memory institutions?  Respondents to the questionnaires and participants in the focus groups readily identified the value of the SHAMAN framework to their own operations. The majority had not yet established a long-term digital preservation policy, but recognized the need. Generally, the concepts of distributed ingest and grid operations found favour.  Virtually all practitioners in the focus groups, however, drew attention to need of a lower level demonstration that would be closer to their everyday preservation troubles, especially for digital preservation to be applied to non-textual materials, such as film, photographs and sound archives. In addition to the criteria suggested by Xxxx et al., we can add a further project-related question: What have we learned that has implications for the training and dissemination phase of the Project?  It was not part of the remit of the demonstration and evaluation specifically to discover information of relevance to the training and dissemination function. However, a number of factors will affect the efficacy of any training programme in particular. o First, no common understanding of digital preservation can be assumed of the potential target audiences for training. Consequently, it is likely that self-paced learning materials will be most effective in presenting the SHAMAN framework. o Secondly, the aims of SHAMAN as a project must be conveyed clearly: specifically, that it is a kind of „proof-of-concept‟ project and is not intended to deliver a package of programs capable of being implemented by institutions. o Thirdly, it needs to be emphasised that the SHAMAN framework is not limited to text documents; it can be applied to materials of all kinds. However, the demonstrations relate to bodies of material that were actually available for use. o Fourthly, the existing presentation materials are capable of being adapted for use in training activities. o Finally, the target audiences will appreciate the possibility of online access to the demonstrator, which will need to have very great ease of access in order that people with diverse backgrounds are able to use it with equal facility. We believe that, overall, WP14 has met its aims and objectives in this demonstration and evaluation of ISP1. Valuable lessons have been learnt by all parties involved, which will be transferred to the evaluation of ISP2 in the coming months.

  • Public Access to Meetings and Records If the Contractor receives a cumulative total per year of at least $250,000 in City funds or City-administered funds and is a non-profit organization as defined in Chapter 12L of the San Francisco Administrative Code, Contractor shall comply with and be bound by all the applicable provisions of that Chapter. By executing this Agreement, the Contractor agrees to open its meetings and records to the public in the manner set forth in §§12L.4 and 12L.5 of the Administrative Code. Contractor further agrees to make-good faith efforts to promote community membership on its Board of Directors in the manner set xxxxx xx §00X.0 of the Administrative Code. The Contractor acknowledges that its material failure to comply with any of the provisions of this paragraph shall constitute a material breach of this Agreement. The Contractor further acknowledges that such material breach of the Agreement shall be grounds for the City to terminate and/or not renew the Agreement, partially or in its entirety.

  • Notification and Public Notice If either party desires to alter or amend this Agreement, it shall, not less than one hundred and twenty (120) days prior to the termination date set forth under the Duration Article, provide written notice and a proposal to the other party of said desire and the nature of the amendments, and cause the public notice provisions of law to be fulfilled.

  • NOTIFICATION OF PUBLIC EVENTS AND MEETINGS 2 A. CONTRACTOR shall notify ADMINISTRATOR of any public event or meeting funded in 3 whole or in part by the COUNTY, except for those events or meetings that are intended solely to serve 4 clients or occur in the normal course of business.

  • Audit of Existing Content and Functionality By May 1, 2017, the District will propose for OCR’s review and approval the identity and bona fides of an Auditor (corporation or individual) to audit all content and functionality on its website, including, but not limited to, the home page, all subordinate pages, and intranet pages and sites, to identify any online content or functionality that is inaccessible to persons with disabilities, including online content and functionality developed by, maintained by, or offered through a third party vendor or an open source. The Auditor will have sufficient knowledge and experience in website accessibility for people with disabilities to carry out all related tasks, including developing a Proposed Corrective Action Plan. The Audit will use the Benchmarks for Measuring Accessibility set out above, unless the District receives prior permission from OCR to use a different standard as a benchmark. During the Audit, the District will also seek input from members of the public with disabilities, including parents, students, employees, and others associated with the District, and other persons knowledgeable about website accessibility, regarding the accessibility of its online content and functionality.

  • We provide Message Boards for the use of Our Website users The Message Boards may not be used to promote Websites or any commercial or business activity. We are not responsible for any of the opinions expressed in the Message Boards. By posting a message to the message board You agree to take full legal responsibility and liability for your comments, including for offensive or defamatory statements. Feedback: Feedback is provided for the purpose of facilitating trading by You on Our Website. Feedback provided on other parties must not contain offensive, defamatory, retaliatory or inappropriate language or content. We may remove any feedback that is considered to be offensive, defamatory, retaliatory or inappropriate. You may only give feedback that relates to a specific transaction. You must not post feedback on a transaction that does not relate to that specific transaction. You must not post feedback about Yourself or include any contact details or Personal Information in Your feedback.

  • Public Access to Nonprofit Records and Meetings If Contractor receives a cumulative total per year of at least $250,000 in City funds or City-administered funds and is a non-profit organization as defined in Chapter 12L of the San Francisco Administrative Code, Contractor must comply with the City’s Public Access to Nonprofit Records and Meetings requirements, as set forth in Chapter 12L of the San Francisco Administrative Code, including the remedies provided therein.

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