Background Links Sample Clauses

Background Links. As mentioned in Section 4 we have added the titles of the background links and added new background links to Wikipedia for <dc:creator> and <dcterms:spatial> fields, using the same software as in D2.1. The links to Wikipedia were used to map items directly to related Wikipedia items, with good results, as presented in a conference paper (Agirre et al. 2012)9, and also to produce Wikipedia pages enriched with items from Europeana (Hall et al. 2012). The user studies for the first prototype showed that the interface was showing too many background links, some of which were repeated. Several considerations made us deliver all links and leave the solution at the hands of the interface: • The number of background links could be limited using a threshold on the weight of the link (available at ESEpaths) or showing a fixed number of links. It’s difficult to choose a threshold to eliminate some of the background links in WP2 beforehand (although a threshold of 0.2 was suggested by hand inspection), as the interface might need to show only 5, or 10, or a fixed number. • The repeated links came from the fact that the target term (e.g. London) occurred several times in different fields, or inside the same field at different offsets. All that information is kept in ESEpaths, so the interface can generate hyperlinks in the respective field, so the user can click directly while reading the item information. WP2 will thus serve all links with weight information, and it will be up to the back-end or interface to choose how many and which links to show. In addition I-Sieve is working on the following: • Background links to educational resources, external CH collections, blogs, news, tweets linked to CH resources. • Frequent updates, dynamic links created on the fly based on user profile.
Sample 1
AutoNDA by SimpleDocs
Background Links. In this Section we present intrinsic evaluation of the background links to Wikipedia articles (cf. Section 7). We first evaluated whether the background links to Wikipedia could be used to link Cultural Heritage items automatically to a corresponding Wikipedia article describing the item. This way we are indirectly evaluating the links, although the evaluation is much more strict that just judging whether the background link is relevant for the item. For the later evaluation, the accuracy is around 74%, please refer to (Xxxxx and Xxxxxx, 2008) for further details. In addition, we enriched the queries in the public evaluation CHiC (Cultural Heritage in CLEF). Evaluating correspondence to Wikipedia articles We selected a random subset comprising 400 items from the Scran and Cgrid collections in Europeana. The items were then ordered according to the subcollections they came from, so the annotators had a relatively coherent set of such as “The National Museum Record”11, “The portables Antiquities Scheme”12 or Scran13. Table 5 shows the type of the items in the sample. The majority are photographs, but there are also other types such as paintings or antique coins. Type Count Photographs 276 Coins and Artifacts 57 Books, booklets etc 24 Other 21 Paintings 14 Audio and Video 8 Total 400 Table 5: Types of Europeana items in the sample. The annotators were given the records with all the metadata. They could also access the item as shown in the Europeana interface and they had to return the URL of a single English Wikipedia article matching the item, or NIL if they could not find any matching entry. The definition of a matching entry provided to the annotators was: “the Wikipedia article and the item must describe the same particular object. In the case of photographs, the article must be about the subject of the photograph, e.g a particular person or location.” Note that this definition of matching tries to find equivalent items and articles, and thus does not consider 12 xxxx://xxxxx.xxx.xx/database 13 xxxx://xxx.xxxxx.xx.xx other kinds of relations between item and Wikipedia article, such as for example linking an item to the article about “photography” because it’s a photograph, or linking an item to the article of the author. The random subset of 400 items was independently tagged by two groups of annotators, one in Donostia and another in Sheffield, each one comprising three persons. As a result, the subset was annotated twice and two tags were obtained for e...
Sample 1
Background Links. Reg.31, The Civil Enforcement of Road Traffic Contraventions (Approved Devices, Charging Guidelines and General Provisions) (England) Regulations (s.i. 2022/71) xxxxx://xxx.xxxxxxxxxxx.xxx.xx/uksi/2022/71/contents/made • s.1(2),(3), Pollution, Prevention and Control Act 1999 xxxxx://xxx.xxxxxxxxxxx.xxx.xx/ukpga/1999/24/contents Cross Cutting Issues
Sample 1

Related to Background Links

  • Background Data The Disclosing Party's Background Data, if any, will be identified in a separate technical document.

  • Background Screening VENDOR shall comply with all requirements of Sections 1012.32 and 1012.465, Florida Statutes, and all of its personnel who (1) are to be permitted access to school grounds when students are present, (2) will have direct contact with students, or (3) have access or control of school funds, will successfully complete the background screening required by the referenced statutes and meet the standards established by the statutes. This background screening will be conducted by SBBC in advance of VENDOR or its personnel providing any services under the conditions described in the previous sentence. VENDOR shall bear the cost of acquiring the background screening required by Section 1012.32, Florida Statutes, and any fee imposed by the Florida Department of Law Enforcement to maintain the fingerprints provided with respect to VENDOR and its personnel. The parties agree that the failure of VENDOR to perform any of the duties described in this section shall constitute a material breach of this Agreement entitling SBBC to terminate immediately with no further responsibilities or duties to perform under this Agreement. VENDOR agrees to indemnify and hold harmless SBBC, its officers and employees from any liability in the form of physical or mental injury, death or property damage resulting from VENDOR’s failure to comply with the requirements of this section or with Sections 1012.32 and 1012.465, Florida Statutes.

  • Background Check The Department or Customer may require the Contractor to conduct background checks of its employees, agents, representatives, and subcontractors as directed by the Department or Customer. The cost of the background checks will be borne by the Contractor. The Department or Customer may require the Contractor to exclude the Contractor’s employees, agents, representatives, or subcontractors based on the background check results. In addition, the Contractor must ensure that all persons have a responsibility to self-report to the Contractor within three (3) calendar days any arrest for any disqualifying offense. The Contractor must notify the Contract Manager within twenty-four (24) hours of all details concerning any reported arrest. Upon the request of the Department or Customer, the Contractor will re-screen any of its employees, agents, representatives, and subcontractors during the term of the Contract.

  • Background Checks The State may require that the Contractor and Contractor Parties undergo criminal background checks as provided for in the State of Connecticut Department of Emergency Services and Public Protection Administration and Operations Manual or such other State document as governs procedures for background checks. The Contractor and Contractor Parties shall cooperate fully as necessary or reasonably requested with the State and its agents in connection with such background checks.

  • Background 1.1. The “Work” is the research article, review article, letter, clinical trial study, report, article, or other copyright work, as identified in the Copyright Letter and further detailed in Schedule 1: Details of the Work (including such form of the copyright work submitted to Xxxxxxx Science for publication pursuant to clause 4, below), but excluding (except where context otherwise requires) any diagrams, figures or illustration specifically identified to Xxxxxxx Science pursuant to clause 3.2, below.

  • Project Background 6.1.1. Brief description of Contracting Agency’s project background and/or situation leading to this Project

  • Background Intellectual Property ‌ Notwithstanding and superseding anything to the contrary in this ARTICLE 14, each Party retains title to all Intellectual Property Rights owned or possessed by it or any of its affiliates prior to or independent of performance of this Agreement and used by it in fulfilling its obligations under this Agreement, as well as any modifications or improvements made thereto in the course of performing this Agreement (“Background IP”). To the extent that one Party acquires any right, title, or interest in and to any aspect of the modifications or improvements to the Background IP of the other Party, such first Party shall assign such right, title, and interest to the second Party, immediately following such acquisition. If any of the Supplier’s Background IP is included in or required to use the Documentation provided by the Supplier to the City, the Supplier hereby grants to the City an irrevocable, perpetual, fully paid-up, royalty-free, worldwide, transferable and non-exclusive licence (including the right to sub-licence only to members of the City’s Group) to, itself and through contractors and agents, use, copy, amend, reproduce, modify, create derivative works of, use, commercialize, and otherwise exploit the Supplier’s Background IP but only to the extent required to use such Documentation for the purpose (or any reasonably inferred purpose) for which it has been provided or for the provision of the Supply under this Agreement (excluding any software source code).

  • Background and Context 1.1 Objectives of this Agreement The purpose of this Agreement is to define, in the context of the resource inputs provided, the targets by which the performance of Forensic Science Ireland (FSI) will be measured in 2021. The ongoing supports that the Department of Justice will provide to FSI in this regard, and the mechanisms for monitoring and appraising performance, form part of the overall governance arrangements between the two parties and as such are set out in the separate but complementary Oversight Agreement 2020-22.

  • Background Investigations OSC policy requires that background investigations be conducted on Contractor Staff who will have access to OSC’s IT systems, access to OSC confidential information/data, or routine access to any OSC facility. For purposes of this policy, “routine access” is defined as access to an OSC facility for five consecutive business days or 10 business days over the annual term of the engagement. Accordingly, with the signing of this Agreement, the Contractor certifies that it has or will conduct a background investigation on Staff to whom the policy applies within the 12 months prior to the Staff commencing Services under this Agreement. The Contractor agrees to undertake a background investigation of any new/replacement Staff during the term of the Agreement. At a minimum, background investigations shall include a review/evaluation of the following: • identity verification, including Social Security Number search; • employment eligibility, including verification of U.S. citizenship or legal immigration status where appropriate; • criminal history/court records (Federal, State and local for the past five years); • work experience/history for the past five years; • pertinent skills, qualifications, and education/professional credentials; and • references. The Contractor must obtain the consent of its Staff to allow OSC, upon request: (i) to review the background investigation records, including all supporting documentation, and (ii) to conduct its own background investigation. Only Staff who have passed the background investigation, and provided such consent shall be assigned to provide Services to OSC under this Agreement. During the term of the Agreement, and in accordance with Appendix A (Section 10, Records), the Contractor must maintain records related to the background investigations performed.

  • 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

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