General platform design Sample Clauses

General platform design. A Citizen Science platform for the analysis of iMars data called Mars in Motion was developed with the project builder at xxx.xxxxxxxxxx.xxx that launched in 2015. Building a project requires an account on Xxxxxxxxxx.xxx. The project builder presents several sections, accessible via a menu on the left hand side (Figure 2.1), which closely correspond to the different pages of the live site (Figure 2.2). The names of these pages are fixed by the project builder and cannot be changed without independently downloading the project builder code from GitHub and then requesting the Zooniverse team to launch the project to the public.
AutoNDA by SimpleDocs

Related to General platform design

  • Trading Platform 22.5.1 Subject to clause 22.6 all warranties, express and implied, as to the description, quality, performance or fitness of the purposes for you of the Trading Platform or any component of such Trading Platform are disclaimed and excluded. 22.5.2 We do not warrant or forecast that the Trading Platform or any component of any Trading Platform or any services performed in respect of any such Trading Platform will meet the requirements of any user, or that the operation of the Trading Platform will be uninterrupted or error-free, or that any services performed in respect of the Trading Platform will be uninterrupted or error-free.

  • The Platform THE PLATFORM IS PROVIDED “AS IS” AND “AS AVAILABLE.” THE AGENT PARTIES (AS DEFINED BELOW) DO NOT WARRANT THE ACCURACY OR COMPLETENESS OF THE BORROWER MATERIALS OR THE ADEQUACY OF THE PLATFORM, AND EXPRESSLY DISCLAIM LIABILITY FOR ERRORS IN OR OMISSIONS FROM THE BORROWER MATERIALS. NO WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR STATUTORY, INCLUDING ANY WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT OF THIRD PARTY RIGHTS OR FREEDOM FROM VIRUSES OR OTHER CODE DEFECTS, IS MADE BY ANY AGENT PARTY IN CONNECTION WITH THE BORROWER MATERIALS OR THE PLATFORM. In no event shall the Administrative Agent or any of its Related Parties (collectively, the “Agent Parties”) have any liability to the Borrower, any Lender, the L/C Issuer or any other Person for losses, claims, damages, liabilities or expenses of any kind (whether in tort, contract or otherwise) arising out of the Borrower’s or the Administrative Agent’s transmission of Borrower Materials through the Internet, except to the extent that such losses, claims, damages, liabilities or expenses are determined by a court of competent jurisdiction by a final and nonappealable judgment to have resulted from the gross negligence or willful misconduct of such Agent Party; provided, however, that in no event shall any Agent Party have any liability to the Borrower, any Lender, the L/C Issuer or any other Person for indirect, special, incidental, consequential or punitive damages (as opposed to direct or actual damages).

  • Program Design The County Human Resources Department will operate a Catastrophic Leave Bank which is designed to assist any County employee who has exhausted all paid accruals due to a serious or catastrophic illness, injury, or condition of the employee or family member. The program establishes and maintains a Countywide bank wherein any employee who wishes to contribute may authorize that a portion of his/her accrued vacation, compensatory time, holiday compensatory time or floating holiday be deducted from those account(s) and credited to the Catastrophic Leave Bank. Employees may donate hours either to a specific eligible employee or to the bank. Upon approval, credits from the Catastrophic Leave Bank may be transferred to a requesting employee's sick leave account so that employee may remain in paid status for a longer period of time, thus partially ameliorating the financial impact of the illness, injury, or condition. Catastrophic illness or injury is defined as a critical medical condition, a long-term major physical impairment or disability which manifests itself during employment.

  • File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

  • Project Design Applicants must design a project that provides access to health services to enable eligible women and men experiencing health needs to secure and maintain safe and accessible quality screening and diagnostic services, comprehensive family planning, and/ or other women’s health services. A. Applicants are encouraged to emphasize the following components in the design of their projects. Projects must: 1. Use a collaborative approach to maximize existing community resources and avoid duplication of effort; 2. Enhance systems and local processes to make it easier for people to transition to, from, and between services; 3. Address barriers to ensure services are accessible to people regardless of setting or location; and 4. Promote improvement and positively impact health and well-being through coordinated service delivery. B. To be effective, services and activities provided or made available as part of the Proposed Project should have policies and procedures in place and include with the application as an attachment that: 1. Delineate the timely provision of services; 2. Deem Client eligibility and service provision as soon as possible and no later than 30 calendar days from initial request; 3. Require staff to assess and prioritize Client needs; 4. Implement with model fidelity to an evidence-based program or based upon best available research; 5. Plan in partnership with the person and are inclusive; 6. Provide in an environment that is most appropriate and based on a person’s preference including reasonable clinic/reception wait times that are not a barrier to care; 7. Provide referral sources for Clients that cannot be served or receive a specific service; 8. Are culturally and linguistically sensitive; 9. Tailor services to a person’s unique strengths and needs; 10. Manage funds to ensure established Clients continuity of care throughout budget year; 11. Continue to provide services to established Clients after allocated funds are expended; 12. Have processes to identify and eliminate possible barriers to care; 13. Do not deny services due to inability to pay; 14. Have appropriate key personnel and required staff to meet the medical and health needs of Clients; 15. Bill services appropriately and timely through TMHP; 16. Effectively communicate and document information related to health care needs with next steps available to Client; 17. Establish outreach and education plan for the community; and 18. Outline successful delivery of direct clinical services to Clients By submitting an Application under this RFA, the Applicant certifies that Applicant has or will have at time of grant award services, policies, or procedures that conform with the requirements in this section as applicable. HHSC, in its sole discretion, may request to review relevant documentation during the project period as necessary to ensure program fidelity.

  • Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.

  • Linking to the Website and Social Media Features You may link to our homepage, provided you do so in a way that is fair and legal and does not damage our reputation or take advantage of it, but you must not establish a link in such a way as to suggest any form of association, approval, or endorsement on our part. This Website may provide certain social media features that enable you to: • Link from your own or certain third-party websites to certain content on this Website. • Send emails or other communications with certain content, or links to certain content, on this Website. • Cause limited portions of content on this Website to be displayed or appear to be displayed on your own or certain third-party websites. You may use these features solely as they are provided by us, and solely with respect to the content they are displayed with, and otherwise in accordance with any additional terms and conditions we provide with respect to such features. Subject to the foregoing, you must not: • Establish a link from any website that is not owned by you. • Cause the Website or portions of it to be displayed on, or appear to be displayed by, any other site, for example, framing, deep linking, or in-line linking. • Link to any part of the Website other than the homepage. • Otherwise take any action with respect to the materials on this Website that is inconsistent with any other provision of these Terms of Use. The website from which you are linking, or on which you make certain content available, must comply in all respects with the Content Standards set out in these Terms of Use. You agree to cooperate with us in causing any unauthorized framing or linking immediately to stop. We reserve the right to withdraw linking permission without notice. We may disable all or any social media features and any links at any time without notice in our discretion.

  • Platform (a) The Borrower agrees that the Agent may, but shall not be obligated to, make the Communications (as defined below) available to the Lenders by posting the Communications on the Platform. (b) The Platform is provided “as is” and “as available.” The Agent Parties (as defined below) do not warrant the adequacy of the Platform and expressly disclaim liability for errors or omissions in the Communications. No warranty of any kind, express, implied or statutory, including any warranty of merchantability, fitness for a particular purpose, non-infringement of third-party rights or freedom from viruses or other code defects, is made by any Agent Party in connection with the Communications or the Platform. In no event shall the Agent nor any of its directors, officers, agents, employees, advisors, shareholders, attorneys or Affiliates (collectively, the “Agent Parties”) have any liability to any Borrower, any Lender or any other Person or entity for damages of any kind, including direct or indirect, special, incidental or consequential damages, losses or expenses (whether in tort, contract or otherwise) arising out of the Borrower’s or the Agent’s transmission of communications through the Platform, unless it is determined by a final and nonappealable judgment or court order that the damages were the result of acts or omissions constituting gross negligence or willful misconduct of the Agent Party. “Communications” means, collectively, any notice, demand, communication, information, document or other material provided by or on behalf of the Borrower pursuant to any Loan Document or the transactions contemplated therein that is distributed to the Agent or any Lender by means of electronic communications pursuant to this Section, including through the Platform.

  • General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:

  • Customer Materials Subject to Section 4(a), all right, title and interest (including all Intellectual Property Rights) in and to the Customer Materials are owned by Customer or Customer’s suppliers.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!