Sometimes the Board or the Executive Committee will discuss changes in policy or in reports that will mean design changes that the Database Committee and, possibly, the Membership Committee would need to make. The Database Committee should provide input to the Board discussion on feasibility and timing. Examples:
- A different combination of membership fee and membership renewal period or date will require a new Membership Level. A new level would be set up by the Database Committee, which would also make changes in Saved Searches and in the Membership Report to deal with the new level appropriately. Associated new Membership Enrollment forms and new membership drive notices would be the responsibility of the Membership Committee, with help and/or consultation from the Database Committee.
- Collecting new data will require adding a new field or fields to the database. This is relatively easy. WildApricots' help is very extensive. Help could be searched for "Adding and modifying database field" if needed. Any new fields will probably also need to be added to the Membership Enrollment forms, and to the notices that are sent when a renewal is completed. These are the responsibility of the Membership Committee, but the Database Committee members may need to assist.
- New committees would mean new Volunteer opportunities, which are fields in the database and on the Enrollment forms. Analysis should be done of how best to present those to members. The new committees will also need to be reflected appropriately on the websites, which is the responsibility of the Websites Committee.
Sometimes ASU changes data that ASURA imports and uses. Occasionally that means changes in the import process or the database and associated processes, saved searches, and forms. The most likely to impact would be:
- A new campus or a new campus name.
- A new Employment Category, or a deleted category.
