HOPE Persistent Identifier Service Sample Clauses

HOPE Persistent Identifier Service. The HOPE BPN has chosen to require Persistent Identifiers for all metadata records and digital objects submitted to the HOPE system (see HOPE Vision Document). The usage of these PIDs is very important to the maintainability of the HOPE system. Duplicates’ detection and merging has been one of the core problems of large-scale aggregation and unification of heterogeneous sources. The consistent implementation of persistent identifiers by Content Providers will significantly simplify the work-flow and enhance the reliability of the HOPE system. The PIDs submitted to HOPE must be registered at a known persistent identification web- service, such as HANDLE, PURL, DOI, ARK, etc.. WP2 will provide recommendations concerning which PID services conform to the HOPE requirements. The addition of persistent identifiers as resolvable URLs to digital objects will also give Content Providers much flexibility and control over the resolvability of the objects they refer to. For example, when the CP decides to migrate the digital objects to another repository they will only have to change the resolve URL that the PID refers to in the respective web-services. It will not be necessary anymore to issue new URLs for all these objects to all the users and services that are using or have bookmarked these objects. The HOPE system will also provide its own Persistent Identifier Service, because not every Content Provider is able to host its own system. Since there are many PID services available on the web today, the HOPE BPN will choose one of these PID services as its preferred PID mechanism. The HOPE System will host a dedicated resolver for this preferred service. The CP that wants to make use of this HOPE service must first register an institutional PID at this preferred PID service, before they can start using the HOPE PID service. Next to hosting the PID service, HOPE will also provide tools to help CP add PIDs to their objects and metadata records (for example, a small stand-alone command-line tool that will simplify the addition of PIDs to objects/records in the local system with a JDBC compliant database). When the CP adds a dedicated PID field to their metadata, this tool will automatically populate these fields and register the PID at the HOPE Persistent Identifier Service. So due to work-flow concerns the consistent usage of PIDs in the local CP system is deemed preferable. This solves many long-term integration problems for aggregation projects like HOPE. These issue...
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to HOPE Persistent Identifier Service

  • Supplier Diversity Seller shall comply with Xxxxx’s Supplier Diversity Program in accordance with Appendix V.

  • Customer Service A. PRIMARY ACCOUNT REPRESENTATIVE. Supplier will assign an Account Representative to Sourcewell for this Contract and must provide prompt notice to Sourcewell if that person is changed. The Account Representative will be responsible for: • Maintenance and management of this Contract; • Timely response to all Sourcewell and Participating Entity inquiries; and • Business reviews to Sourcewell and Participating Entities, if applicable.

  • Hosting Services 13.1 If Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract Hosts Customer Data in connection with an Acquisition, the provisions of Appendix 1, attached hereto and incorporated herein, apply to such Acquisition.

  • AIN Selective Carrier Routing for Operator Services, Directory Assistance and Repair Centers 4.3.1 BellSouth will provide AIN Selective Carrier Routing at the request of <<customer_name>>. AIN Selective Carrier Routing will provide <<customer_name>> with the capability of routing operator calls, 0+ and 0- and 0+ NPA (LNPA) 555-1212 directory assistance, 1+411 directory assistance and 611 repair center calls to pre-selected destinations.

  • Office of Supplier Diversity The State of Florida supports its diverse business community by creating opportunities for woman-, veteran-, and minority-owned small business enterprises to participate in procurements and contracts. The Department encourages supplier diversity through certification of woman-, veteran-, and minority-owned small business enterprises and provides advocacy, outreach, and networking through regional business events. For additional information, please contact the Office of Supplier Diversity (OSD) at xxxxxxx@xxx.xxxxxxxxx.xxx.

  • Our Service The services that you have selected and the charges for those services are confirmed in Section 9 - Your Consent at the end of this agreement. We agree to provide the services selected and you agree to pay us for those services. Any advice or recommendation that we offer to you, will only be given after we have assessed your needs and considered your financial objectives and attitude to any risks that may be involved. We will also take into account any restrictions that you wish to place on the type of products you would be willing to consider.

  • Customer Service Standards The Franchising Authority hereby adopts the customer service standards set forth in Part 76, §76.309 of the FCC’s rules and regulations, as amended. The Grantee shall comply in all respects with the customer service requirements established by the FCC.

  • Customer Services Customer Relationship Management (CRM): All aspects of the CRM process, including planning, scheduling, and control activities involved with service delivery. The service components facilitate agencies’ requirements for managing and coordinating customer interactions across multiple communication channels and business lines. Customer Preferences: Customizing customer preferences relative to interface requirements and information delivery mechanisms (e.g., personalization, subscriptions, alerts and notifications).

  • Service Levels Annex 1 to this Part A of this Call Off Schedule sets out the Service Levels the performance of which the Parties have agreed to measure. The Supplier shall monitor its performance of this Call Off Contract by reference to the relevant performance criteria for achieving the Service Levels shown in Annex 1 to this Part A of this Call Off Schedule (the Service Level Performance Criteria) and shall send the Customer a Performance Monitoring Report detailing the level of service which was achieved in accordance with the provisions of Part B (Performance Monitoring) of this Call Off Schedule. The Supplier shall, at all times, provide the Services in such a manner that the Service Levels Performance Measures are achieved. If the level of performance of the Supplier of any element of the provision by it of the Services during the Call Off Contract Period: is likely to or fails to meet any Service Level Performance Measure or is likely to cause or causes a Critical Service Failure to occur, the Supplier shall immediately notify the Customer in writing and the Customer, in its absolute discretion and without prejudice to any other of its rights howsoever arising including under Clause 12 of this Call Off Contract (Service Levels and Service Credits), may: require the Supplier to immediately take all remedial action that is reasonable to mitigate the impact on the Customer and to rectify or prevent a Service Level Failure or Critical Service Level Failure from taking place or recurring; and if the action taken under paragraph (a) above has not already prevented or remedied the Service Level Failure or Critical Service Level Failure, the Customer shall be entitled to instruct the Supplier to comply with the Rectification Plan Process; or if a Service Level Failure has occurred, deduct from the Call Off Contract Charges the applicable Service Level Credits payable by the Supplier to the Customer in accordance with the calculation formula set out in Annex 1 of this Part A of this Call Off Schedule; or if a Critical Service Level Failure has occurred, exercise its right to Compensation for Critical Service Level Failure in accordance with Clause 13 of this Call Off Contract (Critical Service Level Failure) (including subject, for the avoidance of doubt, the proviso in Clause 13.1.2 of this Call Off Contract in relation to Material Breach). Approval and implementation by the Customer of any Rectification Plan shall not relieve the Supplier of any continuing responsibility to achieve the Service Levels, or remedy any failure to do so, and no estoppels or waiver shall arise from any such Approval and/or implementation by the Customer. SERVICE CREDITS Annex 1 to this Part A of this Call Off Schedule sets out the formula used to calculate a Service Credit payable to the Customer as a result of a Service Level Failure in a given service period which, for the purpose of this Call Off Schedule, shall be a recurrent period of [one Month] during the Call Off Contract Period (the Service Period).

  • Online Services Microsoft warrants that each Online Service will perform in accordance with the applicable SLA during Customer’s use. Customer’s remedies for breach of this warranty are in the SLA. The remedies above are Customer’s sole remedies for breach of the warranties in this section. Customer waives any breach of warranty claims not made during the warranty period.

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