Configuring Pundit Sample Clauses

Configuring Pundit. ‌ Once our Pundit vocabularies were online and reachable at a stable URL, we created a new Pundit configuration to include them by simply adding the following lines: vocabularies: [ "xxxxx://xx.xxxxxxxxxxxxxxxxxx.xxx/u/769042/pundit-demo-philosophers.json", "xxxxx://xx.xxxxxxxxxxxxxxxxxx.xxx/u/769042/pundit-demo-philosophers-predicates.json”] In addition to configuring the vocabularies, the Pundit configuration allows to tune in other features of the annotation UI. The following is the configuration (with comments) that we used for this demo. punditConfig = { // Set debug to true to see debugging messages in your browser javascript consolle. debugAllModules: false, // The url of the Pundit server that will be used to store and retrieve annotations annotationServerBaseURL : 'xxxx://xx.xxxxxxx.xx:8080/annotationserver/', // The vocabularies (Relations Sets and Entities Taxnonomies) to be included vocabularies: [ "xxxxx://xx.xxxxxxxxxxxxxxxxxx.xxx/u/769042/pundit-demo-philosophers.json", "xxxxx://xx.xxxxxxxxxxxxxxxxxx.xxx/u/769042/pundit-demo-philosophers-predicates.json" ], // Set this one to “true” if you want to include the default Relations Set useBasicRelations: false, // The modules parameter allows you to turn on/off and configure specific UI modules modules: { // With this module you can provide to your users an introduction or help page 'xxxxxx.Xxxx': { introductionFile: 'xxxx://xxxxxxx.xx/bm/demo-philosophers/demo-introduction.html', introductionWindowTitle: 'Welcome to Pundit Philosopher DEMO! :)', showIntroductionAtLogin: true }, // The following configures the contact form, where users can enter feedback or feature requests, etc. The “list” parameter is an identifier for a set of mail addresses to which the user messages will be forwarded. It can be configured from the Pundit server admin panel. 'pundit.ContactHelper': { instances: [{ title: 'Contact us!', comment: 'Drop us a line, give us some feedback!', list: 'demophilosophers' }]}, // The notebook manager allows users to see and edit notebooks properties from Pundit, as well as to create new notebooks 'pundit.NotebookManager': { active: true, notebookSharing: false, askBaseURL: 'xxxx://xxx.xx.xxxxxxx.xx/#/myNotebooks/'}, // Turn on/off the image fragments annotation 'pundit.ImageFragmentHandler': { active: false }, 'pundit.ImageAnnotationPanel': { active: false }, // Turn on/off annotation of the full page 'pundit.PageHandler': { active: false }, // Turn on/off the automatic entity extraction...
Sample 1
AutoNDA by SimpleDocs
Configuring Pundit. ‌ Once the simple Relation Set was created, we included it in the Pundit configuration that we can see at xxxx://xxxxxxxxx.xxxxx.xxxxxx.xx/timelinejs/pundit_conf/pundit-conf.js. To read more about Pundit configuration the users shouldrefer to the “Deploying the annotation environment” tutorial.‌
Sample 1
Configuring Pundit. ‌ Once you created a set of vocabularies, they have to be put online and resolvable via a stable URL. Then, to include them in a specific Pundit deployment you just have to edit the Pundit configuration accordingly. The configuration is a Javascript file like the following: var punditConfig = { debugAllModules: false, annotationServerBaseURL : 'xxxx://xx.xxxxxxx.xx:8080/annotationserver/', vocabularies: [ 'xxxx://xxxxxxx.xxx/xx-xxxxxxxx-xxxxxxxx.xxxxx', 'xxxx://xxxxxxx.xxx/xx-xxxxxxxxx-xxx.xxxxx' ], useBasicRelations: false, }; Where the vocabulary attribute contains a number of URLs pointing to some vocabularies. By setting the useBasicRelations attribute to true, you can include the default relations set built-in in Pundit. The configuration includes a number of other settings, the most important being the annotationServerBaseURL, which tells Pundit which instance of the Pundit Server annotations will be read from and written to. At xxxx://xx.xxxxxxx.xx:8080/annotationserver/ you can find a public Pundit Server installation, feel free to use it for testing or prototyping, but keep in mind that persistence of annotations is not guaranteed! If you want to set up a production environment, you can download the Pundit Server from GitHub (xxxx://xxxxxx.xxx/net7/pundit-server) and install it into your own server, following the instructions that you can find at xxxx://xxx.xxxxxxx.xx/documentation/deploy-and-configure-the-pundit-server/. A complete set of configuration parameters can be found in the client documentation at xxxx://xxxx.xxxxxxx.xx/classes/pundit.Configuration.html.‌
Sample 1

Related to Configuring Pundit

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

  • System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades.

  • 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.

  • Provisioning of High Frequency Spectrum and Splitter Space 3.2.1 BellSouth will provide <<customer_name>> with access to the High Frequency Spectrum as follows:

  • Developer Attachment Facilities Developer shall design, procure, construct, install, own and/or control the Developer Attachment Facilities described in Appendix A hereto, at its sole expense.

  • CONTRACTOR PORTABLE DEVICES Contractor shall not place Data on any portable Device unless Device is located and remains within Contractor’s CONUS Data Center. For Authorized Users subject to ITS policies, the Data, and/or the portable device containing the Data, shall be destroyed in accordance with applicable ITS destruction policies (ITS Policy S13-003 Sanitization/Secure Disposal and S14-003 Information Security Controls or successor) when the Contractor is no longer contractually required to store the Data. TRANSFERRING OF DATA General Except as required for reliability, performance, security, or availability of the services, the Contractor will not transfer Data unless directed to do so in writing by the Authorized User. All Data shall remain in CONUS. At the request of the Authorized User, the Contractor will provide the services required to transfer Data from existing Databases to physical storage devices, to facilitate movement of large volumes of Data. The Authorized User may require several Cloud providers to share or transfer Data for a period of time. This will be provided for in the Authorized User Agreement or shall be assumed to be limited to a six month duration. Transfer of Data at End of Contract and/or Authorized User Agreement Term At the end of the Contract and/or Authorized User Agreement term, Contractor may be required to facilitate transfer of Data to a new Contractor. This transfer must be carried out as specified by the Authorized User in the Authorized User Agreement. Transfer of Data; Charges Contractor cannot charge for the transfer of Data unless the charges are provided for in response to an Authorized User RFQ. Transfer of Data; Contract Breach or Termination Notwithstanding Section 3.6.3, in the case of Contract breach or termination for cause of the Contract, all expenses for the transfer of Data shall be the responsibility of the Contractor.

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

  • 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

  • Technical Specifications and Drawings a) The Goods and Related Services supplied under this Contract shall conform to the technical specifications and standards mentioned in Section VI, Schedule of Requirements and, when no applicable standard is mentioned, the standard shall be equivalent or superior to the official standards whose application is appropriate to the Goods' country of origin.

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