Method of collaboration Sample Clauses

Method of collaboration. OAI-PMH based harvesting of both UNIMARC slim bibliographic records and the MAG structural metadata with subsequent processing and conversions within a BNCF dedicated connector. Data elements are available via a HTTP by calling a script xxxx://xxxx.xxxx.xxxxxxx.xxx.xx/TecaFrontEnd/servlet/readImg with appropriate parameters, for instance xxxx://xxxx.xxxx.xxxxxxx.xxx.xx/TecaFrontEnd/servlet/readImg?RisIdr=BNCF0003471607&amp where RisIdr is a particular image ID and usage is a requested image quality level indicator. The full link to file can be read in the //mag:img/mag:file[@Location=‘URL‘]/xlink:href, e.g. <mag:file Location="URL" xlink:href="xxxx://xxxx.xxxx.xxxxxxx.xxx.xx/TecaFrontEnd/servl et/readImg?RisIdr=BNCF0003465109&amp;usage=3"/> The applicable foliation/pagination can be found in the element //mag:img/mag:nomenclature.
Sample 1
AutoNDA by SimpleDocs
Method of collaboration. Off-line metadata passing (via FTP or other method) with subsequent processing and conversions within a BUTE dedicated connectors. The following diagrams reflect the structure of the METS and the local descriptive metadata used. The mets:fileGrp groups appropriate level quality files which are linked by mets:file/mets:FLocat/@xlink:href. The mets:structMap contains the structural map of the complex digital document including the map of the digitised copy. The applicable pagination is also included and processed. The appropriate files in the file section are referred by mets:div[@TYPE=”DigitalCopy”]/mets:div[TYPE="Page"]/mets:fptr/ @FILEID value which refers to corresponding value in mets:file/@ID. Data elements are available directly via a HTTP.
Sample 1
Method of collaboration. 3.5.2.1 Manuscripts, incunabulas
Sample 1
Method of collaboration. The following diagram shows the preview of structure of the MASTER+. M-Tool enables to produce the msDescription and page elements. DSP will use existing and the newly created M-Tool and M-Can applications. The multiple pgImage elements are allowed inside page element to enable capturing multiple image quality levels. The pgImage/@href contains the URL of the particular image.
Sample 1
Method of collaboration. The following diagram shows the preview of structure of the METS sample. The mets:fileGrp groups appropriate level quality files which are linked by mets:file[@MIMETYPE=“image/jpeg“]/mets:FLocat/@xlink:href. The mets:structMap[@TYPE=“PHYSICAL“] contains the page sequence of the digitised copy. The applicable pagination is not included. The mets:fileGrp[@USE="original“] contains the original DjVu files reference. The particular files in the file section are referred by mets:div[@TYPE=”DigitalCopy”]/mets:div[TYPE="Page"]/mets:fptr/ @FILEID value which refers to corresponding value in mets:file/@ID. Data elements are available directly via a HTTP.
Sample 1
Method of collaboration. Off-line metadata passing (via FTP or other method) with subsequent processing and conversions within a VUL dedicated connectors. The following diagrams reflect the structure of the METS and the local descriptive metadata used: The mets:fileGrp groups appropriate level quality files which are linked by mets:file/mets:FLocat/@xlink:href. The mets:structMap contains the structural map of the document.
Sample 1
Method of collaboration. It is understood that the IBMS needs to interface with the Fire system; To begin with, a preliminary discussion take place between the IBMS supplier and the FIRE SYSTEM supplier. Several discussions are held between IBMS & Fire system supplier to understand the interfacing requirements. IBMS supplier requests for the following information from the VTS supplier: The physical system details Control system architecture & schematics Floor plan equipment location drawings Sequence of operation Command datapoints & data points available to IBMS Communication protocols BOQ Data formats The VTS supplier submits the above information to the IBMS supplier. IBMS supplier reviews the information. A workshop is scheduled. The system information is discussed in detail. The complete list and explanation is given the following sections.
Sample 1
AutoNDA by SimpleDocs
Method of collaboration. Collaboration is the key to success of the Customer / Xxxxx Global support partnership. Xxxxx Global will use Xxxxx Support Portal to record the issues, resource assignment and escalations with target dates and progress notes. Xxxxx Global will use Customer’s Team Foundation Server for source control , but if Customer does not have TFS configured, Xxxxx Global will configure the TFS on Customer’s Environment with access to both team. The four major area and tools which will be critical for this success are as follows: • Issue Assignment & Escalations – Xxxxx Support Portal • Source Code Control - TFS • Configuration Management - TFS • Status Reporting & Documentation - Xxxxx Support Portal & Email
Sample 1

Related to Method of collaboration

  • Scope of Collaboration As part of the collaboration, the Controllers will act as Joint Controller. The roles of the Controller and the associated tasks are specified in more detail in Appendix 1. If one party is solely responsible for a data processing operation, this party will implement all relevant data protection provisions on its own responsibility. However, such data processing procedures are not subject to this Agreement. Joint data processing and the type of Personal Data collected and processed within the framework of collaboration are specified in Appendix 1.

  • Research Collaboration 3.7.1 Aarvik shall carry out the activities of each Work Item and deliver the required Data Package and/or deliverables in accordance with the applicable SOW. Without limiting the generality of the foregoing, Aarvik shall, in accordance with the applicable SOWs and the timeline approved by JRC, apply the Aarvik IP to (i) design and synthesize Collaboration Compounds, and (ii) by itself or through subcontractor(s), [***]. During the Research Term, if any Party identifies any Third Party Patent or Know-How that is necessary or reasonably useful for any activity under the SOWs but has not been included in the Aarvik IP, then such Party shall immediately inform the other Party and the Parties shall discuss in good faith the need of obtaining a license from such Third Party. 3.7.2 No later than [***] ([***]) days after completion of the [***], Aarvik shall, to the extent not already provided to ArriVent, deliver the Data Packages and all other deliverables required under the [***], as well as the results of the Patentability and FTO Analysis as described in Section 3.2.3, to ArriVent. ArriVent shall have the sole discretion to decide whether or not to advance any Collaboration Compound and which Collaboration Compound(s) will be advanced for further studies beyond the [***]. ArriVent shall inform Axxxxx of its decision in writing. If AxxxXxxx decides to advance the Collaboration Program to [***], ArriVent shall make the payment for the [***] pursuant to Section 6.2.1. 3.7.3 If, upon completion of the [***] for the Collaboration Program, AxxxXxxx decides not to advance the Collaboration Program to [***], ArriVent may terminate the Collaboration Program. If AxxxXxxx decides to advance the Collaboration Program to [***], ArriVent shall make the payment for the [***] pursuant to Section 6.2.1. 3.7.4 No later than [***] ([***]) days after completion of the [***], Aarvik shall, to the extent not already provided to ArriVent, deliver all Data Packages and deliverables required under the [***] to ArriVent. ArriVent shall have the sole discretion to decide whether or not to advance any Collaboration Compound and which Collaboration Compound(s) will be advanced for further studies beyond the [***]. ArriVent shall inform Axxxxx of its decision in writing. 3.7.5 No later than [***] ([***]) days after completion of the [***], Aarvik shall, to the extent not already provided to ArriVent, deliver all Data Packages and deliverables required under the [***] to ArriVent. 3.7.6 Within [***] ([***]) days after completion of the [***], Aarvik shall deliver to ArriVent a full report on all key results and findings of the Collaboration Program, and such other data, results and information as ArriVent may deem necessary for it to determine whether or not to exercise the Option (the “Full Report”).

  • Commercialization Intrexon shall have the right to develop and Commercialize the Reverted Products itself or with one or more Third Parties, and shall have the right, without obligation to Fibrocell, to take any such actions in connection with such activities as Intrexon (or its designee), at its discretion, deems appropriate.

  • Commercialization Efforts The RECIPIENT shall, including whether through its own efforts or the efforts of a licensee under a License Agreement allowed by the terms of this Attachment, use diligent and commercially reasonable efforts to commercialize at least one Commercial Product or Commercial Service or otherwise bring to practical application the Project Results in accordance with the commercial development plan submitted with the Application and including any changes to such commercial development plan in accordance with Section D3.01. For the avoidance of doubt, partnering or licensing activities shall be considered to be efforts to commercialize.

  • Development and Commercialization Subject to Sections 4.6 and 4.7, Fibrocell shall be solely responsible for the development and Commercialization of Fibrocell Products and Improved Products. Fibrocell shall be responsible for all costs incurred in connection with the Fibroblast Program except that Intrexon shall be responsible for the following: (a) costs of establishing manufacturing capabilities and facilities in connection with Intrexon’s manufacturing obligation under Section 4.6 (provided, however, that Intrexon may include an allocable portion of such costs, through depreciation and amortization, when calculating the Fully Loaded Cost of manufacturing a Fibrocell Product, to the extent such allocation, depreciation, and amortization is permitted by US GAAP, it being recognized that the majority of non-facilities scale-up costs cannot be capitalized and amortized under US GAAP); (b) costs of basic research with respect to the Intrexon Channel Technology and Intrexon Materials (i.e., platform improvements) but, for clarity, excluding research described in Section 4.7 or research requested by the JSC for the development of a Fibrocell Product or an Improved Product (which research costs shall be reimbursed by Fibrocell); (c) [*****]; and (d) costs of filing, prosecution and maintenance of Intrexon Patents. The costs encompassed within subsection (a) above shall include the scale-up of Intrexon Materials and related active pharmaceutical ingredients for clinical trials and Commercialization of Fibrocell Products undertaken pursuant to Section 4.6, which shall be at Intrexon’s cost whether it elects to conduct such efforts internally or through Third Party contractors retained by either Intrexon or Fibrocell (with Intrexon’s consent).

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK

  • Research Plan The Parties recognize that the Research Plan describes the collaborative research and development activities they will undertake and that interim research goals set forth in the Research Plan are good faith guidelines. Should events occur that require modification of these goals, then by mutual agreement the Parties can modify them through an amendment, according to Paragraph 13.6.

  • Reformulation of Products As of the Effective Date, and continuing thereafter, Products that Xxxxx directly manufactures, imports, distributes, sells, or offers for sale in California shall either: (a) be Reformulated Products pursuant to § 2.2, below; or (b) be labeled with a clear and reasonable exposure warning pursuant to §§ 2.3 and 2.4, below. For purposes of this Settlement Agreement, a “Reformulated Product” is a Product that is in compliance with the standard set forth in

  • Research Program The term “Research Program” shall mean the research program to be undertaken by TSRI under the direction and control of the Principal Investigator as expressly set forth on Exhibit A hereto.

  • Commercialization License Subject to the terms of this Agreement, including without limitation Section 2.2 and Theravance's Co-Promotion rights in Section 5.3.2, Theravance hereby grants to GSK, and GSK accepts, an exclusive license under the Theravance Patents and Theravance Know-How to make, have made, use, sell, offer for sale and import Alliance Products in the Territory.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!