Peer production cycle Sample Clauses

Peer production cycle. Within the QMPP project we have developed a metaphor for the effective management of quality in peer production. It includes two important elements - these are the “peer production cycle” and the “supporting activities”. The “peer production cycle” includes the following phases: ♦ benchmarking – identifying of good cases and practices, identifying of good digital resources, identifying areas of lacking content, sharing learning experiences by sharing learning (b)logs etc. ♦ creating – (shared) authoring of texts and other resources; creating images, audio materials, video materials; creating wikis etc. ♦ validating – validating content with subject matter experts, validating content with peers, rating the validity of the content etc. ♦ editing – sharing editing responsibilities (from proof-reading to translation), undertaking peer reviews, creating alternative navigational routes etc. ♦ enriching – creating additional content materials, publishing individual works and team works, sharing or learning (b)logs, adding library links, social bookmarking, creating wikis etc. ♦ updating – monitoring existing content, updating existing content, adding specific area content etc. However, as stated previously, it is obvious that organizations favoring peer production must also have enabling and supporting structures. These should include the following: ♦ enabling policies – organizational opportunities for peer production of content (such as time resources allocated for peer production), management support for peer production, access to various digital resources to be used in content production etc. ♦ enabling procedures – organizational support for peer production, guidelines for peer production and peer reviews, guidelines of intellectual property rights, agreement on compensation policies etc. ♦ enabling processes – practical support of peer production, agreed and supported processes and workflows for peer production ♦ enabling tools – joint and shared tools to be used in peer production to provide effective and fluent collaborative work. These essential elements are summarized in picture 3. Picture 3 Updating Benchmarking Enablliin g polliiciies Enabling procedures Enriching CRreaatitningg Enabling processes Enabling tools Ediittiin g VCarelidaatintingg At this stage it should also be emphasized that in real life these stages are not linear or directly sequencial. In the creation phase there is naturally authoring, re-authoring etc. – thus it can rather be seen ...
AutoNDA by SimpleDocs

Related to Peer production cycle

  • Annual Production Program document describing the forecasts for Production and handling of Oil, Gas, water, special fluids, and waste arising from the Production process of each Development Area or Field.

  • RE-WEIGHING PRODUCT Deliveries are subject to re- weighing at the point of destination by the Authorized User. If shrinkage occurs which exceeds that normally allowable in the trade, the Authorized User shall have the option to require delivery of the difference in quantity or to reduce the payment accordingly. Such option shall be exercised in writing by the Authorized User.

  • Program Components Activities and services delivered under this Program Element align with Foundational Programs and Foundational Capabilities, as defined in Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf) as well as with public health accountability outcome and process metrics (if applicable) as follows:

  • Development Milestones In addition to its obligations under Paragraph 7.1, LICENSEE specifically commits to achieving the following development milestones in its diligence activities under this AGREEMENT: (a) (b).

  • Interconnection Product Options Interconnection Customer has selected the following (checked) type of Interconnection Service:

  • Product ACCEPTANCE Unless otherwise provided by mutual agreement of the Authorized User and the Contractor, Authorized User(s) shall have thirty (30) days from the date of delivery to accept hardware products and sixty (60) days from the date of delivery to accept all other Product. Where the Contractor is responsible for installation, acceptance shall be from completion of installation. Failure to provide notice of acceptance or rejection or a deficiency statement to the Contractor by the end of the period provided for under this clause constitutes acceptance by the Authorized User(s) as of the expiration of that period. The License Term shall be extended by the time periods allowed for trial use, testing and acceptance unless the Commissioner or Authorized User agrees to accept the Product at completion of trial use. Unless otherwise provided by mutual agreement of the Authorized User and the Contractor, Authorized User shall have the option to run testing on the Product prior to acceptance, such tests and data sets to be specified by User. Where using its own data or tests, Authorized User must have the tests or representative set of data available upon delivery. This demonstration will take the form of a documented installation test, capable of observation by the Authorized User, and shall be made part of the Contractor’s standard documentation. The test data shall remain accessible to the Authorized User after completion of the test. In the event that the documented installation test cannot be completed successfully within the specified acceptance period, and the Contractor or Product is responsible for the delay, Authorized User shall have the option to cancel the order in whole or in part, or to extend the testing period for an additional thirty (30) day increment. Authorized User shall notify Contractor of acceptance upon successful completion of the documented installation test. Such cancellation shall not give rise to any cause of action against the Authorized User for damages, loss of profits, expenses, or other remuneration of any kind. If the Authorized User elects to provide a deficiency statement specifying how the Product fails to meet the specifications within the testing period, Contractor shall have thirty (30) days to correct the deficiency, and the Authorized User shall have an additional sixty (60) days to evaluate the Product as provided herein. If the Product does not meet the specifications at the end of the extended testing period, Authorized User, upon prior written notice to Contractor, may then reject the Product and return all defective Product to Contractor, and Contractor shall refund any monies paid by the Authorized User to Contractor therefor. Costs and liabilities associated with a failure of the Product to perform in accordance with the functionality tests or product specifications during the acceptance period shall be borne fully by Contractor to the extent that said costs or liabilities shall not have been caused by negligent or willful acts or omissions of the Authorized User’s agents or employees. Said costs shall be limited to the amounts set forth in the Limitation of Liability Clause for any liability for costs incurred at the direction or recommendation of Contractor.

  • Contract Year A twelve (12) month period during the term of the Agreement commencing on the Effective Date and each anniversary thereof.

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • SHOP DRAWINGS, PRODUCT DATA AND SAMPLES 4.12.1 Shop Drawings are drawings, diagrams, schedules and other, data specially prepared for the Work by the Contractor or any Subcontractor, manufacturer, supplier or distributor to illustrate some portion of the Work.

  • Contract Quarterly Sales Reports The Contractor shall submit complete Quarterly Sales Reports to the Department’s Contract Manager within 30 calendar days after the close of each State fiscal quarter (the State’s fiscal quarters close on September 30, December 31, March 31, and June 30). Reports must be submitted in MS Excel using the DMS Quarterly Sales Report Format, which can be accessed at xxxxx://xxx.xxx.xxxxxxxxx.xxx/business_operations/ state_purchasing/vendor_resources/quarterly_sales_report_format. Initiation and submission of the most recent version of the Quarterly Sales Report posted on the DMS website is the responsibility of the Contractor without prompting or notification from the Department’s Contract Manager. If no orders are received during the quarter, the Contractor must email the DMS Contract Manager confirming there was no activity.

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