Skip to end of metadata
Go to start of metadata

key:
non-trivial
done
useful outside this project

Process:  for non trivial improvements, start with discussion on forums, to ensure code well written to CiviCRM standards, etc.

Project management

Combine all comments, etc., into draft specification and publish on Wiki

Identify and prioritise usability interface improvements and additional functionality for this project below

Complete LINks functionality

Usability / interface improvements and additional functionality

Improvements to CSS

  • Headers more visible with better collapsible layout
  • Borders more visible
  • Tabs better looking and more compact
  • Upload new CSS to production site

Layout improvements

  • Membership status and expiry shown on summary page
  • Data quality warning shown in colour on summary page
  • Custom fields shown separately in search
  • Remove 'strike through' and 'clean up messy code' buttons from WYSIWYG editor

Contacts and relationships

  • Individuals inherit organisations address by default
  • Individual's organizations are shown with the individual wherever necessary (search results, mailing labels, event attendees, activities?)
  • Activities delivered employees and trustees of organisations can be / are shown on organisation pages
  • Primary contact for organisations (already exists for households?)
  • Organisations can only have one address - always primary and billing address and of type 'office'.
  • Desirable: view/edit an individual's relationships on the individual summary/edit page
  • Faith organisation - check yes no to select

Address stuff

  • Address field for county
  • Automatic capitalisation of postcode field

Activities

  • Change default activity status to completed

Events

  • indicates when no free places are remaining, and prohibits additional free place bookings (http://civicrm.org/node/380)
  • event display page to show participants' organisations, and charge for their course booking.
  • Event price based on membership and organisational income (use hook http://civicrm.org/node/380*)*

Payment

  • Daniel: decide on brackets congruent with organisational income field for membership and events
  • Add option for invoice
  • Check the spelling of cheque

Membership

  • Membership price based on organisational income (use hook http://civicrm.org/node/380)
  • Ability to record who the membership was delivered to
  • Add contribution type for VAW membership and change VAW membership to this type

Access control

  • Soft deletion of contacts by adding to ACL group?
  • Ask on the forums about the best way to hide sensitive LINk data

Mailing

  • Important:  "Quick mail" functionality - someone can choose a mailing list from a dropdown and be shortcutted to the compose mail screen

General / global / other

  • Daniel - please clarify this requirement: can the Contact Dashboard be set as the home page for the database (displaying the user's groups, events, etc).  Is it possible to add a display of outstanding scheduled tasks assigned to the user to this page?
  • The use of the term "group" anywhere on the database is confusing.  Could we replace with "list"?
  • Change CiviCRM language to en_GB on live site
  • Change Drupal menu language to en_GB
  • Add added field to changelog search tab

Desirable / good ideas / alternative approaches

  •  Custom field for mailings

Bugs

Can't delete some of the unneeded custom fields

Javascript tab doesn't appear for employer

Data import

Import LINk membership data

Hosting and domain transfer

  • Get confirmation on new DNS set up
  • Transfer to new name servers 
  • Investigate slowness of site

Staff training and ongoing involvement

Go through database session notes to pull out all the ways that you can make the database living and breathing

Staff training on the following key concepts

  • Advanced search
  • Profiles - a way of making all data input systematic. You can choose what information you want to collect from people at different types of events and have it always linked back to the right database table. (see "use every opportunity, e.g. after training sessions, health checks etc, but always use the same form that relates to the database" in Database Session 170708.doc)
  • Fields
    • where you can add fields (and where you can't)
    • Consquences of adding and deleting fields
Labels
  • None

Creative Commons License
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-Share Alike 3.0 United States Licence.