Functionality and Features Sample Clauses

Functionality and Features. Not all of the same functionality or features may be accessible or available at all times for all Services or Electronic Channels.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
Functionality and Features. ‌ The following infrastructure (hardware, firmware, database, interfaces to other systems etc.) shall be provided to service recipients within the ETH web core area for content publication purposes: • An authoring system which is monitored on an ongoing basis • Two (geo-redundant) publication systems deployed at two different locations which are monitored on an ongoing basis • Systems updates at all levels (operating system, development environment, applications) by implementing patches and upgrades • Systems backup to ensure recovery in the event of a crash The ETH web core area provides the following software to service recipients: • Web content management system • Webpage templates that are consistent with the Corporate Design • Additional components and functions within the web CMS that comply with ETH specifications • Interfaces for displaying data from ETH applications and databases (e.g. Course Catalogue, Operational Information System, eCitations, Addresses and Personal Data). • Integrated full text search for non-protected areas (Google) • Authorisation and role concept The following support services shall be provided to service recipients within the ETH web core area: • Author training: Corporate Communications • Advice to authors on website design and structure: Corporate Communications • First level support: the IT Service Desk shall always be the first point of contact for service recipients. The IT Service Desk is responsible for performing triage and escalating incidents to second level support. • Second level support: Corporate Communications is responsible for providing second level support in respect of content-related, structural or design issues. ITS User Services is responsible for providing second level support in relation to technical incidents or problems. • Third level support: any issues that cannot be resolved through first or second level support shall be passed on either to ITS Software Services (ITS SWS) or to Adobe. • Corporate Communications shall gather, assess and define the requirements for developing new functions for ETH or specific organisational units. ITS shall determine the relevant specifications and develop the new functions on behalf of CC. • Maintaining the community of authors: Corporate Communications • Documentation and guides: Corporate Communications IT Services shall provide a separate “web archiving” service for websites that are no longer required. IT Services shall provide a separate “web statistics” se...
Sample 1
Functionality and Features. The Official CAS support is obsolete as Liferay is still using CAS Protocol 2 whereas neuGRID is using CAS Protocol version 3 and the XXXX assertions that are extensively used in the neuGRID SSO architecture to provide access to the users' attributes to the different neuGRID services. It required the development of a custom authentication handler based on the existing CAS integration, using the features provided by Liferay. It was updated to handle the CAS 3 protocol. This step required to create the class neuGRIDAutoLogin which implements com.liferay.portal.security.auth.AutoLogin. This class is responsible for extracting the user's attributes from the XXXX assertion that are returned by CAS once the user has been successfully authenticated. A Liferay user is created using these attributes if it does not already exist into the local Liferay database. The Distinguished Name (DN) of the user is normalized and used as the screen name. A Liferay hook was also developed in order to be able to customise the terms of use page. A new portal user has to accept these terms before being able to use the neuGRID portal. The former neuGRID portal developed using Ruby On Rails has been completely migrated to Liferay. The design has been migrated as a Liferay theme. The neuGRID menu has been ported into a portlet including the Grid load glowing brain that is updated using Ajax and the resource serving facility of the JSR 286. The portal is now ready to receive the neuGRID portlets.
Sample 1
Functionality and Features. The neuGRID pseudonymization Java library allows one to keep or remove a selected list of fields from DICOM images. The library is being implemented into the org.healthgrid.neuGRID.pseudonymize.Pseudonymization class providing the following public methods: boolean Pseudonymize(String inputFile, String outputFile, int[] headers, int operation) FileInputStream Pseudonymize(FileInputStream imageStream, int[] headers, int operation) (not yet implemented) boolean RemoveHeaders(DicomObject dcmObj, int[] headers) ArrayList<Integer> KeepHeaders(DicomObject dcmObj, int[] headers) (not yet implemented) The pseudonymization applet will allow users to select one or more local files and pseudonymize them in a manner configured for the neuGRID needs. It will take a list of images as input and will either output pseudonymized images into one chosen repository or send them to the neuGRID infrastructure according to the user's choice. The applet will also be handling the manual upload of files at the DACS level. Due to its applet nature when new features, bugs fixes or new pseudonymization rules are implemented, they will be immediately available for use. When running in standalone mode the applet will have an update facility allowing it to update itself and to apply automatically any possible new pseudonymization rules. In order to be able to create a nice and responsive applet that could live outside a browser, the JavaFX SDK has been used. JavaFX is a client platform developed by Sun allowing the creation of rich user interfaces for Internet applications. It is one of the main RIA (Rich Internet Application) frameworks. It allows reusing any existing Java library, and it is also capable of creating applets that could be deployed on a user's desktop just by dragging them from the browser.
Sample 1
Functionality and Features. Not all of the same functionality or features may be accessible or available for all Accounts or other Services or Electronic Channels, or at all times. At the Customer’s request, Royal Bank will provide the Customer with more information about these limitations.
Sample 1
Functionality and Features. XRM Tokens uses, purpose, attributes, functionalities or features, express or implied are solely must be seen as a facilitating mechanism for building Aerum community and providing its members with a sample of delegated cross-chain proof of stake governance mechanism.
Sample 1

Related to Functionality and Features

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • Antivirus software All workstations, laptops and other systems that process and/or store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY must have installed and actively use comprehensive anti-virus software solution with automatic updates scheduled at least daily.

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • CONTENT UPDATES If You purchase a Symantec maintenance/support offering consisting of or including Content Updates, as indicated on Your Support Certificate, You are granted the right to use, as part of the Licensed Software, such Content Updates as and when they are made generally available to Symantec’s end user customers who have purchased such maintenance/support offering and for such period of time as indicated on the face of the applicable Support Certificate. This License Agreement does not otherwise permit You to obtain and use Content Updates.

  • Customer Content As part of the Services provided under this Agreement, Customer Data will be stored and processed in the data center region specified in the applicable Ordering Document. Axway shall not access Customer Content except in response to support or technical issues where Customer provides Axway with prior Customer’s written authorization required to access such Customer Content. Axway is not responsible for unauthorized access, alteration, theft or destruction of Customer Content arising from Customer’s own or its authorized users’ actions or omissions in contravention of the Documentation. Customer’s ability to recover any lost data resulting from Axway’s misconduct is limited to restoration by Axway from the most recent back-up.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • User Content Certain areas of the Platform may enable you to post comments, send messages, correspond with others and/or otherwise post content (“User Content”) in connection with various features that Spectra may elect to offer, such as information libraries, e-mail service, bulletin boards, chatrooms, electronic postcards, chats with special guests, e-mails, and forums to communicate with others (“Message Features”). You must use the Message Features in a responsible manner and you are fully responsible for all User Content that you provide to us or others. Your License to Us. By submitting User Content, you grant us and our designees a royalty-free, irrevocable, perpetual, non-exclusive, worldwide, fully sub-licensable, transferable, license to publish, reproduce, distribute, display, perform, edit, adapt, modify, translate, create derivative works, make, sell, offer for sale, export, and otherwise use and exploit your User Content (or any portion thereof) in any way that we want and in any form, media, or technology now known or later developed. You hereby waive any moral rights you may have in your User Content in favor of Spectra and any of its designees. You represent that you have obtained all necessary permissions necessary to grant us those rights, including from any person identified in or implicated by your submission (including those shown in photographic content), and, in the case of minors, also from their parents or legal guardians, as appropriate. No Obligation to Publish. We are not obligated to publish, transmit or use your User Content. Spectra is not in any manner endorsing any User Content that it may publish or post on the Platform and cannot, and will not, vouch for its reliability. Spectra is not responsible for any User Content and has no duty to monitor User Content. You use any information contained in User Content at your own risk. Spectra and its designees have the right, in their sole discretion, to monitor, review, edit, remove, delete, disable, refuse, restrict, or terminate access to your User Content or the Platform (in whole or in part) at any time, without prior notice and in our sole discretion, for any or no reason. The obligations that you have to us under these Terms shall survive termination of the Platform, any use by you of the Platform, any User Content on the Platform, or these Terms. You will not continue to post any User Content that Spectra has previously advised you not to post.

  • Contract Database Metadata Elements Title: Whitesville Central School District and Whitesville Central School Educational Support Staff Association (2003) Employer Name: Whitesville Central School District Union: Whitesville Central School Educational Support Staff Association Local: Effective Date: 07/01/2003 Expiration Date: 06/30/2006 PERB ID Number: 10699 Unit Size: Number of Pages: 23 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ AGREEMENT BETWEEN WHITESVILLE CENTRAL SCHOOL EDUCATIONAL SUPPORT STAFF ASSOCIATION AND THE WHITESVILLE CENTRAL SCHOOL DISTRICT JULY 1, 2003 THROUGH JUNE 30, 2006 TABLE OF CONTENTS ARTICLE TITLE PAGE Preamble 1 I Recognition 1 II Collective Bargaining U n i t 1 III Dues/Agency Fee Ckoffand Payroll Deduction 1 IV Rights of Employees 2 V Rights of Employer ------------- 2 VI Personnel F i l e 2 VII Employee Definitions 3 VIII Permanent Status/Seniority 4 IX Wages 5 X Overtime 7 XI Vacation 7 XII Holidays 8 XIII Sick Leave and Leavesof A b s e n c e 8 XIV Conference, Workshops,Required Courses 10 XV Meal Allowance and M i l e a g e 11 XVI Retirement 11 XVII Insurance 12 XVIII Cafeteria P l a n 14 .XIX Uniform Allowance------------------ 14 XX Hours of W o r k 14 XXI Transfers/Promotions 15 XXII Job Descriptions 15 XXIII Grievance Procedure 15 XIV Copies of the Contract 18 XV Zipper C x x x x x 18 XXVI Legislative Clause 18 XXVII Duration 19 SIGNATURES 19 APPENDIX A Grievance F o r m 20 APPENDIX B Dues Authorization F o r m 21

  • Software Updates XXXXX agrees to keep current with software licensed from Skyward and will install new versions on a timeline approved by XXXXX governance. This timeline will be communicated by NWRDC to the Districts. School District Workstations Configuration requirements for devices and their software that school district personnel use to access WSIPC’s software modules can be found on our website: xxxxx://xxx.xxxxx.xxx/technology‐team/. State Reports XXXXX will provide, at no additional fee, all data reports required by the state that impact 50% or more of the school districts in the state. WSIPC and NWRDC will work with state agencies to gather requirements on the required data. WSIPC will inform NWRDC staff of any mandated changes to state reports and NWRDC will communicate the information to the District. Appendix B NWRDC FTE Fees Fiscal Only NWRDC Software Support Services XXXXX Software Licensing Total FTE Fee $13.63 $20.34 $33.97 $15.56 $13.08 $28.64 $24.52 $20.34 $44.86 Student Only Full Service

  • Upgrades and Updates Customer shall be entitled to receive all upgrades and updates Philips makes generally commercially available during the term of the Agreement, subject to the same usage rights, limitations, and restrictions applicable to the originally provided version of InfoView. Custom Modules may need additional modifications to be compatible with the Software upgrades and are, subject to resource availability and may be subject to an additional cost. Updates including bug fixes, shall be prioritized by Philips based on the needs and impact such bugs are having on the total customer base using the InfoView Software.

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