User Profiles Sample Clauses

User Profiles. You may designate User Profiles equal in number to the number of seats set forth on the applicable Order Form. Your designated administrator (“Power User”) is responsible for the timely addition, removal, and designation of user profiles. If the employment of any of your employees with a User Profile terminates during the Term, such employee’s access to Priority Engine shall be revoked by the Power User immediately and without any action by us. In any event, you shall promptly notify us and take all reasonable steps necessary to ensure that such former employee ceases accessing Priority Engine. You may, however, reassign user profiles at any time subject to the number of license seats provided on the Order Form. If you would like to change your Power User, you must inform your TechTarget client service representative at least two (2) business days prior to the date upon which you wish to implement this change.
View SourceView Similar (3)
User Profiles. You may have the opportunity to create a profile, which consists of information about you, and may include Personal Information, photographs, information on work previously performed via the Service and outside the Service, skills, earnings information, feedback/rating information and other information, including your username (“Profile”). The information in your Profile will be visible to all Pinion Users. If, in any case, you believe that an unauthorized profile has been created about you, you can request for it to be removed by contacting us. Before user can complete registration on the Service, or at any time thereafter, we may request or re-request identity verification. Without limiting the manner in which we request identify verification, we may require the user to participate in a video call after submitting their government issued ID to enable us to confirm that the user is indeed the individual in the ID or the appointed company representative. We may record such video calls and take screenshots of the user during the call. Pinion may use the information obtained from Identity Verification for purposes of verifying your identity, enforcing our Terms of Service and other agreements, and preventing fraud.
View SourceView Similar (2)
User Profiles. The ways of working to exploit the potential of creating added value based on bigger exposure, re-use and enrichment of cultural heritage by aggregation and collaboration are still in their infant stages. From the experiences so far it is clear that it is no easy undertaking. It requires fundamental changes to the administration and management of collections under stewardship, based on large investments in knowledge and new technical skills. Exchanging rich data, as it might be called, needs skilled human effort, advanced ICT infrastructure and sophisticated tools to map from source to target data. Many institutions within the Europeana Network share the vision that this is the way forward. However, at the moment their limited resources result in a limitation of the effort needed for exchanging data through Europeana or other aggregators. Initially the DoW stated that the profiles for the use cases would be: a small institution, a large institution and an aggregator. However, during the first specification task, the requirement analysis showed no clear distinction between small and large institutions or rather institutions with small collections or big collections in relation to their potential for exchanging digital information. What it did show was that it is not the size of an institution or the size of the digital collection that matters, but that it is a question of resource investment, in-house expertise (or the willingness to invest in it) and ambition or expectations. Furthermore, it showed that aggregators’ needs in the user scenarios were not different from content providers’ needs within the different scenarios. Even though an aggregator can act as a local point of contact for Europeana, can take care of the registration process of the museum and can enrich the metadata before passing it on to Europeana, it still has the same requirements as a content providing institution who would take all these organisational and technical steps themselves. As a result, the intended structuring of the use cases from the description of work was replaced with an alternative approach. It was decided to differentiate use case descriptions on (technical) capabilities, wishes and needs of content providers, based on the quality of their infrastructure and their digital strategy. Based on these findings, the two main profiles were identified:
View Source

Related to User Profiles

  • Workstation/Laptop encryption All workstations and laptops that process and/or store County PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the County Information Security Office.

  • THIRD-PARTY CONTENT, SERVICES AND WEBSITES 10.1 The Services may enable You to link to, transfer Your Content or Third Party Content to, or otherwise access, third parties’ websites, platforms, content, products, services, and information (“Third Party Services”). Oracle does not control and is not responsible for Third Party Services. You are solely responsible for complying with the terms of access and use of Third Party Services, and if Oracle accesses or uses any Third Party Services on Your behalf to facilitate performance of the Services, You are solely responsible for ensuring that such access and use, including through passwords, credentials or tokens issued or otherwise made available to You, is authorized by the terms of access and use for such services. If You transfer or cause the transfer of Your Content or Third Party Content from the Services to a Third Party Service or other location, that transfer constitutes a distribution by You and not by Oracle. 10.2 Any Third Party Content we make accessible is provided on an “as-is” and “as available” basis without any warranty of any kind. You acknowledge and agree that we are not responsible for, and have no obligation to control, monitor, or correct, Third Party Content. We disclaim all liabilities arising from or related to Third Party Content. 10.3 You acknowledge that: (i) the nature, type, quality and availability of Third Party Content may change at any time during the Services Period, and (ii) features of the Services that interoperate with Third Party Services such as Facebook™, YouTube™ and Twitter™, etc., depend on the continuing availability of such third parties’ respective application programming interfaces (APIs). We may need to update, change or modify the Services under this Agreement as a result of a change in, or unavailability of, such Third Party Content, Third Party Services or APIs. If any third party ceases to make its Third Party Content or APIs available on reasonable terms for the Services, as determined by us in our sole discretion, we may cease providing access to the affected Third Party Content or Third Party Services without any liability to You. Any changes to Third Party Content, Third Party Services or APIs, including their unavailability, during the Services Period does not affect Your obligations under this Agreement or the applicable order, and You will not be entitled to any refund, credit or other compensation due to any such changes.

  • Protocols Each party hereby agrees that the inclusion of additional protocols may be required to make this Agreement specific. All such protocols shall be negotiated, determined and agreed upon by both parties hereto.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central ▇▇▇▇▇▇ Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Contract Sales Reporting. Contractor shall report total Contract sales quarterly for this Cooperative Purchasing Agreement to Enterprise Services, as set forth below. Contract Sales Reporting System. Contractor shall report quarterly Contract sales in Enterprise Services’ Contract Sales Reporting System. Enterprise Services shall provide Contractor with a login password and a vendor number. The password and vendor number shall be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized Purchasers specified herein during the term of the Contract. If there are no Contract sales during the reporting period, Contractor must report zero sales. Due dates for Contract Sales Reporting. Quarterly Contract Sales Reports must be submitted electronically by the following deadlines for all Contract sales invoiced during the applicable calendar quarter: Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 1.25 percent on the purchase price for all Cooperative Purchasing Agreement sales (the purchase price is the total invoice price less applicable sales tax) under this Cooperative Purchasing Agreement. The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Contract sales invoiced (not including sales tax) x .0125. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services shall invoice Contractor quarterly based on Contract sales reported by Contractor. Contractor is not to remit payment until Contractor receives an invoice from Enterprise Services. Payments must be received within thirty (30) calendar days of the invoice issue date from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference the invoice number. Contractor’s VMF payment to Enterprise Services must reference this Contract number, the year and quarter for which the VMF is being remitted, and Contractor’s name as set forth in this Contract, if not already included on the face of the check. Contractor’s failure to report accurate total net Contract sales, to submit a timely Contract sales report, or to remit timely payment of the VMF to Enterprise Services, shall be cause for Enterprise Services, at its discretion, to suspend Contractor or terminate this Contract or exercise remedies provided by law. Without limiting any other available remedies, the parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums, the sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) calendar days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing. Annual Contract Sales Report. Contractor shall provide to Enterprise Services a detailed annual Contract sales report. Such report shall include, at a minimum, the following: The Goods and/or Services sold and provided (including, as applicable, category or another identifier); Services purchased by Purchaser; and Contract price. This report must be provided in an electronic format that can be read by Microsoft (MS) Excel. Such report is due within thirty (30) calendar days of the annual anniversary of the effective date of this Contract.