{
  "title": "Collective Feature Purchasing for CiviCRM and FOSS: Alternative to MIH",
  "sections": [
    {
      "id": "section-1",
      "title": "Collective Feature Purchasing for CiviCRM and FOSS: Alternative to MIH",
      "level": 2,
      "headingHtml": "Slide 1",
      "html": "<h3>Collective Feature Purchasing for CiviCRM and FOSS: Alternative to MIH</h3><p>Dominik Lukes, Learning Technologist</p><p>@techczech</p><p>training.dyslexiaaction.org.uk</p><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=1\">View original slide 1</a></p>"
    },
    {
      "id": "section-2",
      "title": "With contributions and advice from",
      "level": 2,
      "headingHtml": "Slide 2",
      "html": "<h3>With contributions and advice from</h3><p><img src=\"/readers/collective-feature-purchasing-for-civicrm-and-foss/media/img-74d8589d1936533c.png\" alt=\"Logo of the Association for Learning Technology: the words Association for Learning Technology beside a green diamond containing the letters ALT.\" loading=\"lazy\"></p><p><a href=\"http://www.alt.ac.uk\" target=\"_blank\" rel=\"noopener noreferrer\">http://www.alt.ac.uk</a></p><ul><li>Maren Deepwell, Operations and Services Manager</li><li>Seb Schmoller, CEO</li></ul><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=2\">View original slide 2</a></p>"
    },
    {
      "id": "section-3",
      "title": "Tweet comments @techczech with #civicrm",
      "level": 2,
      "headingHtml": "Slide 3",
      "html": "<h3>Tweet comments @techczech with #civicrm</h3><p><img src=\"/readers/collective-feature-purchasing-for-civicrm-and-foss/media/img-5bfc94eadf504a7d.jpeg\" alt=\"The historical Twitter logo: a white lowercase letter t on a glossy light-blue rounded square.\" loading=\"lazy\"></p><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=3\">View original slide 3</a></p>"
    },
    {
      "id": "section-4",
      "title": "Outline",
      "level": 2,
      "headingHtml": "Slide 4",
      "html": "<h3>Outline</h3><p><img src=\"/readers/collective-feature-purchasing-for-civicrm-and-foss/media/img-1fc272a7ecfec13e.jpeg\" alt=\"Silhouette of two monkeys sitting close together against a white background, one touching the other&#x27;s head.\" loading=\"lazy\"></p><p><a href=\"http://www.flickr.com/photos/vijo/1231276186\" target=\"_blank\" rel=\"noopener noreferrer\">http://www.flickr.com/photos/vijo/1231276186</a></p><ul><li>Options for sponsoring development</li><li>Pros and Cons of MIH</li><li>Collective purchasing</li><li>Some practical ideas</li><li>Discussion</li></ul><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=4\">View original slide 4</a></p>"
    },
    {
      "id": "section-5",
      "title": "How do new features get into CiviCRM?",
      "level": 2,
      "headingHtml": "Slide 5",
      "html": "<h3>How do new features get into CiviCRM?</h3><p>Somebody pays for them or contributes time via SYOI (Scratch Your Own Itch) or during Code Sprint</p><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=5\">View original slide 5</a></p>"
    },
    {
      "id": "section-6",
      "title": "Sponsoring custom development in CiviCRM Now",
      "level": 2,
      "headingHtml": "Slide 6",
      "html": "<h3>Sponsoring custom development in CiviCRM Now</h3><ul><li>Custom code developed</li><li>Sponsor release of custom code to public</li><li>Contribute to MIH (Make it Happen)</li></ul><p><img src=\"/readers/collective-feature-purchasing-for-civicrm-and-foss/media/img-7da8893203766480.png\" alt=\"Screenshot of a CiviCRM Make it Happen project box titled &quot;Discount codes for events and memberships&quot;: a progress bar from $0 to $4,500.00 at 24%, &quot;Raised $1,060.00 of $4,500.00&quot;, 4 donors, a description that the project will allow administrators to create discount codes for events and membership, &quot;Campaign is ongoing&quot; and a &quot;Learn more&quot; link.\" loading=\"lazy\"></p><p><a href=\"http://civicrm.org/mih\" target=\"_blank\" rel=\"noopener noreferrer\">http://civicrm.org/mih</a></p><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=6\">View original slide 6</a></p>"
    },
    {
      "id": "section-7",
      "title": "Custom code developed",
      "level": 2,
      "headingHtml": "Slide 7",
      "html": "<h3>Custom code developed</h3><p><strong>Pros</strong></p><ul><li>Quick</li><li>Running site with code implemented</li></ul><p><strong>Cons</strong></p><ul><li>Expensive</li><li>Difficult to maintain (upgrade)</li><li>No shared expertise benefit</li><li>No public code review</li><li>Often hardcoded options to save cost = low customizability</li><li>Variable documentation</li></ul><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=7\">View original slide 7</a></p>"
    },
    {
      "id": "section-8",
      "title": "Sponsoring sharing of code",
      "level": 2,
      "headingHtml": "Slide 8",
      "html": "<h3>Sponsoring sharing of code</h3><p><strong>Pros</strong></p><ul><li>Long-term support</li><li>Benefit of public review / shared expertise</li><li>More customizable / generic interface</li><li>Better documentation</li><li>Easier maintenance / upgrading</li></ul><p><strong>Cons</strong></p><ul><li>More expensive (more development needed)</li><li>Benefit of public review limited if no support offered (for modules not core)</li><li>Possibly less flexible</li></ul><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=8\">View original slide 8</a></p>"
    },
    {
      "id": "section-9",
      "title": "Contribute to an MIH",
      "level": 2,
      "headingHtml": "Slide 9",
      "html": "<h3>Contribute to an MIH</h3><p><strong>Pros</strong></p><ul><li>Cheap</li><li>Long-term support</li><li>Benefit of public review / shared expertise</li><li>More customizable / generic interface</li><li>Better documentation</li><li>Easier maintenance / upgrading</li></ul><p><strong>Cons</strong></p><ul><li>No precise control over features</li><li>Functionality only available with upgrade cycle</li><li>Difficult to fit in with organizational accounting</li></ul><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=9\">View original slide 9</a></p>"
    },
    {
      "id": "section-10",
      "title": "Alternative: Collective Feature Purchasing",
      "level": 2,
      "headingHtml": "Slide 10",
      "html": "<h3>Alternative: <strong>Collective Feature Purchasing</strong></h3><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=10\">View original slide 10</a></p>"
    },
    {
      "id": "section-11",
      "title": "Collective Feature Purchasing (CFP)",
      "level": 2,
      "headingHtml": "Slide 11",
      "html": "<h3>Collective Feature Purchasing (CFP)</h3><p>Several organizations get together around specific feature (feature set) that they identify as having in common, contract with a developer (company) who will implement the features taking into account specific implementation needs of individual contributors.</p><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=11\">View original slide 11</a></p>"
    },
    {
      "id": "section-12",
      "title": "Collective Feature Purchasing (CFP)",
      "level": 2,
      "headingHtml": "Slide 12",
      "html": "<h3>Collective Feature Purchasing (CFP)</h3><p>A CFP collective can also work with the Civi Core team to determine roadmap synergies and needs for future maintenance. E.g. will the features be modules or rolled into core code base?</p><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=12\">View original slide 12</a></p>"
    },
    {
      "id": "section-13",
      "title": "Collective Feature Purchasing (CFP)",
      "level": 2,
      "headingHtml": "Slide 13",
      "html": "<h3>Collective Feature Purchasing (CFP)</h3><p>CFP collectives can be ad hoc or more permanent. Members can join or opt out of specific CFP rounds.</p><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=13\">View original slide 13</a></p>"
    },
    {
      "id": "section-14",
      "title": "Collective Feature Purchasing (CFP)",
      "level": 2,
      "headingHtml": "Slide 14",
      "html": "<h3>Collective Feature Purchasing (CFP)</h3><p>Key difference between CFP and MIH is greater transparency and accountability on both sides. A successful CFP round would end up with all contributors running actual code on their website.</p><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=14\">View original slide 14</a></p>"
    },
    {
      "id": "section-15",
      "title": "CFP – Pros / Cons",
      "level": 2,
      "headingHtml": "Slide 15",
      "html": "<h3>CFP – Pros / Cons</h3><p><strong>Pros</strong></p><ul><li>MIH &lt; Cost &lt; others</li><li>Control over features</li><li>Benefit of shared expertise</li><li>New features translate to immediate site functionality</li><li>Easier maintenance / upgrading</li><li>Easier accounting (hopefully)</li></ul><p><strong>Cons</strong></p><ul><li>Potential contractual framework complexity</li><li>Agreement on features among CFP partners</li></ul><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=15\">View original slide 15</a></p>"
    },
    {
      "id": "section-16",
      "title": "CFP Spec Framework (Uservoice)",
      "level": 2,
      "headingHtml": "Slide 16",
      "html": "<h3>CFP Spec Framework (Uservoice)</h3><p><img src=\"/readers/collective-feature-purchasing-for-civicrm-and-foss/media/img-a900508948171d51.png\" alt=\"Screenshot of the Dropbox Votebox page, &quot;Votebox lets you decide what we work on next!&quot;, with red boxes and arrows marking the In Progress and Completed tabs, the &quot;6 votes left&quot; counter, and the vote counts (131662, 95124, 86060) and comment counts of the ideas &quot;Watch any folder&quot;, &quot;Sharing permissions&quot; and &quot;Better (more affordable) storage prices&quot;.\" loading=\"lazy\"></p><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=16\">View original slide 16</a></p>"
    },
    {
      "id": "section-17",
      "title": "Anybody wants to work on Events?",
      "level": 2,
      "headingHtml": "Slide 17",
      "html": "<h3>Anybody wants to work on Events?</h3><p><strong>http://bit.ly/civieventwishlist</strong></p><p><strong>CiviEvent Wishlist (#CiviCRM)</strong></p><p>Posted on <a href=\"http://techczech.net/2011/09/01/civievent-wishlist-civicrm/\" target=\"_blank\" rel=\"noopener noreferrer\">September 1, 2011</a> by <a href=\"http://techczech.net/author/dominik-lukes/\" target=\"_blank\" rel=\"noopener noreferrer\">Dominik Lukeš</a></p><p>We have been using <a href=\"http://civicrm.org/\" target=\"_blank\" rel=\"noopener noreferrer\">CiviCRM</a> for event management for over a year. This list covers the sort of things that might be needed by an organization running a wide range of events and courses of different types.</p><p>Event management</p><ol><li><strong>Easier search</strong>: There should be an equivalent of the quick search bar for contacts for events. We run close to a hundred events at any one time and it would be nice if we could access them from the front screen. The workaround using Views/Finder works but doesn’t provide access to all the event functionality.</li><li><strong>Configurable event dashboard</strong>: The dashboard as it is now is pretty much useless for us since it only shows about a dozen events (we need a quick overview of many more) without any clear indication which events make it there. Also, it would be nice to be able to choose the columns displayed. E.g. event type is irrelevant to most admins but they would appreciate more granular registration count display. This could be built in Views in <a href=\"http://www.drupal.org/\" target=\"_blank\" rel=\"noopener noreferrer\">Drupal</a> except, Views don’t seem to have access to counts of users. Plus the links provided by views to event configuration and participant listing appear to be broken.</li><li><strong>Multiple changes to event configuration</strong>: Often we have lots of events that need to have a small change made to them – e.g. the event price or location or default profile. It would be nice to be able to make those changes at once. Also, it would be nice to be able to edit event dates and things like registration status inline without having to go to the whole edit interface.</li><li><strong>Participant info</strong>: Better access to participant info would be really great. It would be great to be able to configure what is visible at a glance or have the participant profile expand similarly to what happens on case listings.</li></ol><p>Event functionality</p><ol><li><strong>Multiple registration paths</strong>: We need to register tutors, volunteers and students for the same event and it would be nice if we could have a different registration page for each. Particularly for paid events where only internal staff get to attend free. Showing a free option on the registration page is unprofessional and confusing.</li><li><strong>Internal/hidden prices</strong>: At the very least, it would be nice if we could have internal/hidden prices for events. At the moment, if we want to give somebody a special price we have no way of accounting for it in the database. Some of this could be accomplished by CiviEvent discount <a href=\"http://drupal.org/project/civievent_discount\" target=\"_blank\" rel=\"noopener noreferrer\">http://drupal.org/project/civievent_discount</a></li><li><strong>Post registration contributions/Partial payments</strong>: We have a number of events where the participants have to go through an approval process before they are asked to pay. It would be nice if we could associate contribution pages with specific events and have those show up as fees. Even better, it would be nice if multiple associated contributions would add up to an event’s fee (for instance, deposit and full payment).</li></ol><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=17\">View original slide 17</a></p>"
    },
    {
      "id": "section-18",
      "title": "Anybody wants to work on Events?",
      "level": 2,
      "headingHtml": "Slide 18",
      "html": "<h3>Anybody wants to work on Events?</h3><p><strong>http://bit.ly/civieventwishlist</strong></p><p><strong>4.</strong> <strong>Internal/external event titles</strong>: This is a small but annoying feature. We would like to be able to refer to events with internal titles that would be used for internal listings and long descriptive titles that would be displayed to students. This way, managing events is cumbersome within the existing interface.</p><p><strong>5.</strong> <strong>CiviAdmissions</strong>: Many of our events require the student to go through an admissions process. We use CiviCase for this at the moment but it is a big too big of an overkill for the job. It would be nice to have some sort of an event admissions workflow to manage event status. Perhaps per event type event status list with notes on each status and a record of event status changes on the event screen. Or an integration with CiviCase where a case status would trigger an event status.</p><p>Profile behavior</p><ol><li><strong>Multi step profiles</strong>: This has been mooted elsewhere before. Here’s a nice way of how this can be accomplished but it would be nice to have this as core functionality: <a href=\"http://civicrm.org/blogs/kurund/using-civicrm-profile-survey\" target=\"_blank\" rel=\"noopener noreferrer\">http://civicrm.org/blogs/kurund/using-civicrm-profile-survey</a></li><li><strong>Private profile titles</strong>: The profile titles show up on the registration form as is which makes it impossible for us to manage over 100 profiles effectively since we can’t name them in a descriptive way: “Short event initial info – Version 2 since May 11″</li><li><strong>Profile field logic</strong>: This has also been discussed. But we could really use “If you check X, Y becomes available/compulsory” kind of logic on profiles.</li><li><strong>Multi value fields in profiles</strong>: This is also not new and is standard functionality on most forms. <a href=\"http://forum.civicrm.org/index.php?topic=11563.0\" target=\"_blank\" rel=\"noopener noreferrer\">http://forum.civicrm.org/index.php?topic=11563.0</a></li><li><strong>Contribution/participant fields on non-event related profiles</strong>: Very often we want to have participants submit additional details that we want associated with their participant profile and/or a contribution. It would be nice to be able to associate specific profiles with particular events and their related contributions.</li></ol><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=18\">View original slide 18</a></p>"
    },
    {
      "id": "section-19",
      "title": "Discussion",
      "level": 2,
      "headingHtml": "Slide 19",
      "html": "<h3>Discussion</h3><p><img src=\"/readers/collective-feature-purchasing-for-civicrm-and-foss/media/img-328fd5c4193f6b22.jpeg\" alt=\"Photo of three white geese standing on ground covered with fallen autumn leaves.\" loading=\"lazy\"></p><p><a href=\"http://www.flickr.com/photos/ktylerconk/3045268759\" target=\"_blank\" rel=\"noopener noreferrer\">http://www.flickr.com/photos/ktylerconk/3045268759</a></p><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=19\">View original slide 19</a></p>"
    },
    {
      "id": "section-20",
      "title": "Tweet comments @techczech with #civicrm",
      "level": 2,
      "headingHtml": "Slide 20",
      "html": "<h3>Tweet comments @techczech with #civicrm</h3><p><img src=\"/readers/collective-feature-purchasing-for-civicrm-and-foss/media/img-5bfc94eadf504a7d.jpeg\" alt=\"The historical Twitter logo: a white lowercase letter t on a glossy light-blue rounded square.\" loading=\"lazy\"></p><p><a href=\"/collective-feature-purchasing-for-civicrm-and-foss?mode=originals&amp;page=20\">View original slide 20</a></p>"
    }
  ],
  "pages": [
    {
      "number": 1,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-01.png",
      "text": "Collective Feature Purchasing for CiviCRM and FOSS: Alternative to MIH\nDominik Lukes, Learning Technologist\n@techczech\ntraining.dyslexiaaction.org.uk"
    },
    {
      "number": 2,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-02.png",
      "text": "With contributions and advice from\nhttp://www.alt.ac.uk\nMaren Deepwell, Operations and Services Manager\nSeb Schmoller, CEO"
    },
    {
      "number": 3,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-03.png",
      "text": "Tweet comments @techczech with #civicrm"
    },
    {
      "number": 4,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-04.png",
      "text": "Outline\nhttp://www.flickr.com/photos/vijo/1231276186\nOptions for sponsoring development\nPros and Cons of MIH\nCollective purchasing\nSome practical ideas\nDiscussion"
    },
    {
      "number": 5,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-05.png",
      "text": "How do new features get into CiviCRM?\nSomebody pays for them or contributes time via SYOI (Scratch Your Own Itch) or during Code Sprint"
    },
    {
      "number": 6,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-06.png",
      "text": "Sponsoring custom development in CiviCRM Now\nCustom code developed\nSponsor release of custom code to public\nContribute to MIH (Make it Happen)\nhttp://civicrm.org/mih"
    },
    {
      "number": 7,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-07.png",
      "text": "Custom code developed\nPros\nQuick\nRunning site with code implemented\nCons\nExpensive\nDifficult to maintain (upgrade)\nNo shared expertise benefit\nNo public code review\nOften hardcoded options to save cost = low customizability\nVariable documentation"
    },
    {
      "number": 8,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-08.png",
      "text": "Sponsoring sharing of code\nPros\nLong-term support\nBenefit of public review / shared expertise\nMore customizable / generic interface\nBetter documentation\nEasier maintenance / upgrading\nCons\nMore expensive (more development needed)\nBenefit of public review limited if no support offered (for modules not core)\nPossibly less flexible"
    },
    {
      "number": 9,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-09.png",
      "text": "Contribute to an MIH\nPros\nCheap\nLong-term support\nBenefit of public review / shared expertise\nMore customizable / generic interface\nBetter documentation\nEasier maintenance / upgrading\nCons\nNo precise control over features\nFunctionality only available with upgrade cycle\nDifficult to fit in with organizational accounting"
    },
    {
      "number": 10,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-10.png",
      "text": "Alternative: Collective Feature Purchasing"
    },
    {
      "number": 11,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-11.png",
      "text": "Collective Feature Purchasing (CFP)\nSeveral organizations get together around specific feature (feature set) that they identify as having in common, contract with a developer (company) who will implement the features taking into account specific implementation needs of individual contributors."
    },
    {
      "number": 12,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-12.png",
      "text": "Collective Feature Purchasing (CFP)\nA CFP collective can also work with the Civi Core team to determine roadmap synergies and needs for future maintenance. E.g. will the features be modules or rolled into core code base?"
    },
    {
      "number": 13,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-13.png",
      "text": "Collective Feature Purchasing (CFP)\nCFP collectives can be ad hoc or more permanent. Members can join or opt out of specific CFP rounds."
    },
    {
      "number": 14,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-14.png",
      "text": "Collective Feature Purchasing (CFP)\nKey difference between CFP and MIH is greater transparency and accountability on both sides. A successful CFP round would end up with all contributors running actual code on their website."
    },
    {
      "number": 15,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-15.png",
      "text": "CFP – Pros / Cons\nPros\nMIH < Cost < others\nControl over features\nBenefit of shared expertise\nNew features translate to immediate site functionality\nEasier maintenance / upgrading\nEasier accounting (hopefully)\nCons\nPotential contractual framework complexity\nAgreement on features among CFP partners"
    },
    {
      "number": 16,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-16.png",
      "text": "CFP Spec Framework (Uservoice)"
    },
    {
      "number": 17,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-17.png",
      "text": "Anybody wants to work on Events?\nhttp://bit.ly/civieventwishlist\nCiviEvent Wishlist (#CiviCRM)\nPosted on September 1, 2011 by Dominik Lukeš\nWe have been using CiviCRM for event management for over a year. This list covers the sort of things that might be needed by an organization running a wide range of events and courses of different types.\nEvent management\n1. Easier search: There should be an equivalent of the quick search bar for contacts for events. We run close to a hundred events at any one time and it would be nice if we could access them from the front screen. The workaround using Views/Finder works but doesn’t provide access to all the event functionality.\n2. Configurable event dashboard: The dashboard as it is now is pretty much useless for us since it only shows about a dozen events (we need a quick overview of many more) without any clear indication which events make it there. Also, it would be nice to be able to choose the columns displayed. E.g. event type is irrelevant to most admins but they would appreciate more granular registration count display. This could be built in Views in Drupal except, Views don’t seem to have access to counts of users. Plus the links provided by views to event configuration and participant listing appear to be broken.\n3. Multiple changes to event configuration: Often we have lots of events that need to have a small change made to them – e.g. the event price or location or default profile. It would be nice to be able to make those changes at once. Also, it would be nice to be able to edit event dates and things like registration status inline without having to go to the whole edit interface.\n4. Participant info: Better access to participant info would be really great. It would be great to be able to configure what is visible at a glance or have the participant profile expand similarly to what happens on case listings.\nEvent functionality\n1. Multiple registration paths: We need to register tutors, volunteers and students for the same event and it would be nice if we could have a different registration page for each. Particularly for paid events where only internal staff get to attend free. Showing a free option on the registration page is unprofessional and confusing.\n2. Internal/hidden prices: At the very least, it would be nice if we could have internal/hidden prices for events. At the moment, if we want to give somebody a special price we have no way of accounting for it in the database. Some of this could be accomplished by CiviEvent discount http://drupal.org/project/civievent_discount\n3. Post registration contributions/Partial payments: We have a number of events where the participants have to go through an approval process before they are asked to pay. It would be nice if we could associate contribution pages with specific events and have those show up as fees. Even better, it would be nice if multiple associated contributions would add up to an event’s fee (for instance, deposit and full payment)."
    },
    {
      "number": 18,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-18.png",
      "text": "Anybody wants to work on Events?\nhttp://bit.ly/civieventwishlist\n4. Internal/external event titles: This is a small but annoying feature. We would like to be able to refer to events with internal titles that would be used for internal listings and long descriptive titles that would be displayed to students. This way, managing events is cumbersome within the existing interface.\n5. CiviAdmissions: Many of our events require the student to go through an admissions process. We use CiviCase for this at the moment but it is a big too big of an overkill for the job. It would be nice to have some sort of an event admissions workflow to manage event status. Perhaps per event type event status list with notes on each status and a record of event status changes on the event screen. Or an integration with CiviCase where a case status would trigger an event status.\nProfile behavior\n1. Multi step profiles: This has been mooted elsewhere before. Here’s a nice way of how this can be accomplished but it would be nice to have this as core functionality: http://civicrm.org/blogs/kurund/using-civicrm-profile-survey\n2. Private profile titles: The profile titles show up on the registration form as is which makes it impossible for us to manage over 100 profiles effectively since we can’t name them in a descriptive way: “Short event initial info – Version 2 since May 11″\n3. Profile field logic: This has also been discussed. But we could really use “If you check X, Y becomes available/compulsory” kind of logic on profiles.\n4. Multi value fields in profiles: This is also not new and is standard functionality on most forms. http://forum.civicrm.org/index.php?topic=11563.0\n5. Contribution/participant fields on non-event related profiles: Very often we want to have participants submit additional details that we want associated with their participant profile and/or a contribution. It would be nice to be able to associate specific profiles with particular events and their related contributions."
    },
    {
      "number": 19,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-19.png",
      "text": "Discussion\nhttp://www.flickr.com/photos/ktylerconk/3045268759"
    },
    {
      "number": 20,
      "image": "/readers/collective-feature-purchasing-for-civicrm-and-foss/pages/page-20.png",
      "text": "Tweet comments @techczech with #civicrm"
    }
  ],
  "pageKind": "PowerPoint slides rendered with LibreOffice · local format pilot"
}