Editors Sample Clauses

Editors. This will confirm agreement between the parties that the Employer may test candidates from outside the Company for the position of Editor by having them perform live copy editing on a pre-employment trial basis for a maximum of twenty (20) working days. It is also agreed that the amount of time spent on the pre- employment trial shall be deducted from the probationary period of that Editor. The manner in which such a person is compensated and the amount of such compensation shall be determined by the Employer but shall not be less than the starting rate of pay for Editor as shown in Appendix C, Editorial, Group 1F when computed on an hourly basis for time worked. Such rate shall also include shift differential and overtime if applicable in accordance with the provisions of Clause (709) and/or Clause (717). It is further agreed that the Employer may not test any more than an average of three (3) candidates per month in any calendar year. The Employer agrees to provide the Guild in advance, in writing when possible, with the name of each candidate and the date of the start and finish of the test. The testing of Editors as described above shall not relieve the Employer of following any of the procedures required under Clause (802). CEP, LOCAL 87-M SOUTHERN ONTARIO NEWSMEDIA GUILD PER: Xxxx Xxxxxxxx Xxxxxxx Xxxxxx Xxxxxxxxx Xxxxxxx Xxxxx Xxxxxx Xxx Xxxxx Xxxxxx Veszlenyi Xxxxx Gjorkes Xxxxxx Xxxxxxx TORONTO STAR NEWSPAPERS LIMITED PER: Xxxx Xxxxx Xxxxxxx Xxxxxxxx Xxxxx Xxxxxxxx Xxxxxx Xxxxxx Xxxxxxxxx Xxxxxxxxxxx SUPPLEMENTAL AGREEMENT TO THE MAIN AGREEMENT (and forming part of the Main Agreement) Between: Toronto Star Newspapers Limited (hereinafter known as the “Employer”) And: CEP, Local 87-M, Southern Ontario Newsmedia Guild (hereinafter known as the “Guild”) Dated this 25th day of January, 2008. Re: Radio Room The radio room in the Editorial Department will be staffed by a pool of roughly a dozen students to be paid the Editorial Trainee rate, working eight (8) hour shifts. Shifts may vary according to staffing needs, with an objective of not more than three (3) shifts per week for any one student. Applications for radio room shifts will be considered from Editorial Assistants and/or other junior newsroom staff seeking opportunities for advancement. Management will use temporary fill-ins on the city clerks’ desk to facilitate the participation of Editorial Assistants on an occasional shift basis. Hours worked by junior staff in the radio room will be paid...
AutoNDA by SimpleDocs
Editors. IIIS and TIDC Publishing have agreed to minimize the intersection between reviewing/accepting the content and editing the form (language and required format). This separation is schematically and briefly described at xxxx://xxx.xxxxxx.xxx/journal/sci/Contents/special-issues-sub.pdf.
Editors. This section concerns the actual editors that user work with to view and modify models. Editor of the core platform Two major kinds of failures were faced when developing industrial sized models: • Failures occurring on Windows platforms, the mostly used system, when reaching the operating system limit number of graphical elements in memory allowed to be displayed at once. This situation used to crash the Rodin platform, and it appeared necessary to control the number of graphical elements needed to display the model elements. Architectures sparing these graphical elements were thus favoured. • Failures due to the high consumption of memory by the heavy graphical elements used by the forms of legacy editor. Moreover, it appeared important to visualize some elements that are not part of the current level of modelling, but are linked to it, for example, the actions in an abstract event, or its guards. Such elements are called the "inherited" elements, or "implicit children". The legacy structured editor being directly interfaced with the underlying Event-B models in database, it was difficult and tricky to modify it in order to display inherited elements. This was one more argument to go for a new editor based on a intermediary representation of the models. Another motivation to go for another editor was to get a more modest and ergonomic way to visualize and edit the models. The models being presented through styled text pretty printing and the edition tightly derived from a textual edition. Xxxxxxx Xxxxxxx was developed as an alternative editor in 2009. In contrast to the existing editor, this was a pure textual editor that supported standard features like copy and paste, auto-completion, color highlighting and many more. In addition, it performed better than the existing structural editor. While successful, Xxxxxxx offered only limited support for models with extended elements contributed by plug-ins. Also, the underlying EMF Compare framework was problematic due to bugs and performance issues.

Related to Editors

  • Editorial Control The Licensee shall be permitted only to exercise editorial control over programming to the extent permitted by federal law.

  • Project Managers The JBE’s project manager is: [Insert name]. The JBE may change its project manager at any time upon notice to Contractor without need for an amendment to this Agreement. Contractor’s project manager is: [Insert name]. Subject to written approval by the JBE, Contractor may change its project manager without need for an amendment to this Agreement.

  • Librarians The normal work week for librarians is 35 hours per week. The maximum for reference desk coverage is 20 hours per week. Individual faculty members may elect to exceed this maximum. Where librarians are involved in instructional modes listed in Article 12.03, these shall be pro-rated. For part-time regular and non-regular type 2 librarians, part of their assignment shall be scheduled as non reference desk duties as agreed upon by the librarian and the administrator responsible. Scheduling work shall follow past practices and shall be delivered in cooperation with the administrator responsible.

  • Programming (a) Pursuant to Section 624 of the Cable Act, the Licensee shall maintain the mix, quality and broad categories of Programming set forth in Exhibit 4, attached hereto and made a part hereof. Pursuant to applicable federal law, all Programming decisions, including the Programming listed in Exhibit 4, attached hereto, shall be at the sole discretion of the Licensee.

  • Directory Publication Nothing in this Agreement shall require Verizon to publish a directory where it would not otherwise do so.

  • Scientific Publications During the Research Program Term, neither Party shall first publish or first present in a public forum the scientific or technical results of any activity performed pursuant to this Agreement without the opportunity for prior review and comment by the other Party. Each Party agrees to provide the other Party with the opportunity to review any proposed abstract, manuscript or scientific presentation (including any verbal presentation) that relates to its activities performed pursuant to this Agreement during the Research Program Term, at least [**] days prior to its intended submission for publication and agrees, upon request, not to submit any such abstract or manuscript for publication until the other Party is given a reasonable period of time up to [**] to secure patent protection for any material in such publication that it believes to be patentable. Both Parties understand that a reasonable commercial strategy may require delay of publication of information or filing of patent applications first with respect to activities performed or results obtained pursuant to this Agreement during the Research Program Term, or not to publish at all if necessary to preserve trade secrets. The Parties agree to review and decide whether to delay publication of such information to permit filing of patent applications. Neither Party shall have the right to publish or present any Confidential Information of the other Party, except as provided in Section 9.2. After the Research Program Term, each Party and its Affiliates may publish or present results, data or scientific findings of any of their activities without the prior review of the other Party, provided that such publication or presentation does not disclose any of the other Party’s Confidential Information. Nothing contained in this Section 9.3 shall prohibit the inclusion of information necessary for a patent application; provided that the non-filing Party is given a reasonable opportunity to review the information to be included prior to submission of such patent application in accordance with Section 8.2. Nothing contained in this Section 9.3 shall prohibit either Party from disclosing the results, data or scientific findings of any activity performed by the other Party or its Affiliates pursuant to this Agreement without prior review and prior written consent of the other Party, where required, as reasonably determined by the disclosing Party’s legal counsel, by applicable law; provided that if a Party is required by law to make any such disclosure, to the extent it may legally do so, it will give reasonable advance notice to the other Party of such disclosure and will use its reasonable efforts to secure confidential treatment of such information prior to its disclosure (whether through protective orders or otherwise).

  • Contract Managers Each party will designate a Contract Manager during the term of this Agreement whose responsibility shall be to oversee the party’s performance of its duties and obligations pursuant to the terms of this Agreement. As of the Effective Date, Citizens’ and Firm’s Contract Managers are as follows: Citizens’ Contract Manager Xxxx Xxxxxxx, VP of Legal Services 0000 Xxxxxxxx Xxxxxx Xxxxxxxxxxx, XX 00000 000-000-0000 Xxxx.Xxxxxxx@xxxxxxxxxxx.xxx Firm’s Contract Manager Xxxxx Xxxxxxxx, Partner 000 Xxxxx Xxxxxx Xxx., Xxxxx 0000 Xxxxxxx, XX 00000 000-000-0000 xxxxxxxxx@xxxxxx.xxx Citizens and Firm shall provide written notice to Citizens of any changes to the Contract Manager; provided, such changes shall not be deemed contract amendments.

  • RESEARCH AND PUBLICATION 34 CONTRACTOR shall not utilize information and/or data received from COUNTY, or arising out 35 of, or developed, as a result of this Agreement for the purpose of personal or professional research, or 36 for publication. 37 //

  • JOB FAMILY: APPLICATIONS DEVELOPMENT‌ Job Title: Director, Systems and Programming Job#: 1200 General Characteristics Responsible for the full systems development life cycle management of projects/programs. Provides direction for technical and business resources. Actively participates in long-range strategy planning and manages policy development to address complex business issues, provides leadership to cross-functional teams. Serves as the primary point of contact from project/program inception to delivery. Defines and develops project management infrastructure, manages a methodology driven quality plan, monitors and controls the quality of the deliverable, as well as manages the project completion process through customer acceptance. Works with business unit managers and forms alliances on projects, operational decisions, scheduling requirements/conflicts and vendor contract clarification.

  • Media No media releases, public announcements or public disclosures relating to this Agreement or its subject matter, including but not limited to promotional or marketing material, shall be made by the Contractor without the prior written consent of the Client.

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