Membership and Meeting database guidelines

This section is still under development. If you need further information, contact the Quakers Australia Coordinator.

Restrict Access: 
Public

Members, Attenders and Children

This page is not complete - there are simply some preliminary notes for your information.

Child of the Meeting

A 'Child of the Meeting' is automatically marked as Active and has access to sign in to the website if they have an email address. They will also appear in the printable lists. Individual items of their data (address, email, phone number) can be suppressed if their parent / guardian request it.

There is to be a revised 'Web enabled' field which will give the following options for all Contacts:

  • ‘Default’ (which would be controlled by their membership status),
  • ‘Force web enabled’ (for those who would otherwise be excluded – e.g. those overseas or special cases), or
  • ‘Force web disabled’ to exclude those who would otherwise be automatically included.

This then enables a Membership Secretary to exclude a Child of the Meeting from the web and Find a Friend if their guardian requests it.

There is an issue of Children of the Meeting who are still shown as contacts but are over 18 or have no date of birth. We are looking in to the possibility of flagging these for correction by the Membership Secretaries.

 

Restrict Access: 
All Site Members

No email address and Different postal address

No email address

The information below is no longer correct. A person does not have to have an email address in Salesforce. However, they do need one if they want to log in to the website. Their email address must also be unique to them and not shared with anyone else.

If a person wants to use an email address they need to contact their RM Membership Secretary for it to be recorded on their Salesforce record.

Where a Friend has no email address (e.g. a child) we need to enter a 'dummy' address. In order to identify these addresses (for example, to exclude them from a mailout or from a listing) they should be in a particular format. The format is also designed to identify which RM they belong to. The format is as follows:

Friend's initials/@/RM initial/.coma

Examples would be:

George Michael in Qld RM: GM@Q.coma

Frances Anne Webb in Victoria RM: FAW@V.coma

Note that each email address needs to be unique and if there is a possibility of two that are the same (e.g. Frank Arthur Williams in Victoria) either change the initials or add a number. E.g. FW@V.coma or FW1@V.coma.

The .coma extension identifies it as a 'dummy' address and also ensures that if by chance an email is sent it will 'bounce'.

If such a Friend wanted to access the website they could do so using this email address but they would have to contact the AYM Website Coordinator web@quakersaustralia.info to obtain a password.

Postal address different from street address

The "mailing address" fields are used for mail-outs. Hence they should show a PO Box address if there is one or the street address if not.

Where there is a PO Box address in the "mailing address" fields, the street address should be shown in the "Other address" fields.

Restrict Access: 
All Site Members

Meetings for Worship

These instructions are not complete, and only give basic information. More detail is available from the AYM Membership Secretary membership@quakersaustralia.info.

Information about Meetings for Worship are controlled by each Regional Meeting Membership Secretary through the Salesforce database. Information entered there automatically populates the website pages where Meetings are listed. Each Meeting automatically has its own website page.

All Meetings also have a generic email address here. Those email address are controlled by the AYM Website Coordinator web@quakersaustralia.info.

Entries in Salesforce

All Meetings should have a 'Physical address' in order to appear correctly on the Google map. The postal address is optional.

The email address is the generic address for that Meeting and is not alterable by the Membership Secretary but is there for information. Difficulties with the email address should be referred to the AYM Website Coordinator web@quakersaustralia.info.

The Meeting abbreviation is used for the printed lists of Meetings, Members, Attenders and Children. These can be found under Find A Friend on the website. It can only be changed by an Administrator but is shown for information.

 

 

Restrict Access: 
All Site Members

Add a new Meeting for Worship

This section is not yet finalised. To establish a new Meeting in Salesforce consult the AYM Membership Secretary.

When putting in the address of the Meeting the Google map should show the correct spot. A suburb and postcode are usually the minimum.

Remember that a new Meeting for Worship needs to have an email address for the "Contact" button on its web page. This can be established by contacting the AYM Website Coordinator. There also needs to be a Contact person who will monitor the new email address.

Restrict Access: 
All Site Members

New contact person for a Meeting

When the contact information for a Meeting for Worship changes it may be necessary to change the person who monitors the email address. This process is described here.

If there are difficulties, contact the AYM Website Coordinator.

Restrict Access: 
All Site Members

Change of Meeting name or place

Where a Meeting changes its name or place of worship it may be necessary to consider the generic email address associated with that Meeting. Examples are:

  • If it is simply a new address for Meetings for Worship no other changes may be needed.
  • If the Meeting changes its name there will need to be consideration of the email address. Should it be changed or is it OK for the old address to continue even though the Meeting name is different? Bear in mind that Friends may have a record of the existing email address and changing it may cause confusion. If a change is necessary, contact the AYM Website Coordinator. (see also "Laying down a Meeting")
  • If the changes involve a change in the Contact Person for that Meeting there may also need to be a change in the person who monitors the Meeting's generic email address. Instructions for that can be found here.
Restrict Access: 
All Site Members

Laying down a Meeting

The policy in relation to Meetings that are laid down is as follows:

  • The Meeting remains in the database and on the website for twelve months with information to say that it is no longer meeting. It may have a phone number for people to ring for more information.
  • At the end of twelve months the Meeting is 'archived' so it no longer appears on the website. If it is to be deleted, then click the arrow to the right of the Meeting in SalesForce and click 'Delete'.
  • Similarly, the generic email address for the Meeting is forwarded to the Regional Meeting clerk for twelve months. Normally it would then be deleted.

Details of the Meeting are controlled in Salesforce by the Regional Meeting Membership Secretary; details of the email address can be controlled by the AYM Website Coordinator.

Restrict Access: 
All Site Members

Reports

These pages are still under construction.

There are suggestions for producing reports:

  • Listing all Friends in a Regional Meeting
  • Listing all Meetings in a Regional Meeting

Reports can be exported to Excel (via the down arrow at the right), but note that if you alter the report and 'save' it you may need to run it again before downloading (otherwise it does not download the latest version).

Restrict Access: 
All Site Members

List of Friends

Basic reports have been produced for each RM using the following criteria:

  • Show all Households and Organisations.
  • Filter by "Aust RM associated with" (use, for example, 'greater than v' and 'less than w' for Victoria - this ensures you don't have to have the exact RM name).
  • Group by "Household or Organisation name".
  • Sort by Household name.
  • Don't include subtotals.

The order of the fields can be changed by dragging them in the list on the Edit screen.

The fields included are:

  • Household or Organisation Name

  • First Name

  • Middle Name

  • Last Name

  • Mailing Address Line 1

  • Mailing Address Line 2

  • Mailing Address Line 3

  • Mailing City

  • Mailing State/Province

  • Mailing Zip/Postal Code

  • Mailing Country

  • Other Street

  • Other City

  • Other State/Province

  • Other Zip/Postal Code

  • Other Country

  • Phone

  • Fax

  • Mobile

  • Email

  • Quaker Status

  • Birthdate

Restrict Access: 
All Site Members

List of Meetings

Basic reports have been produced for each RM using the following criteria:

  • Show all Households and Organisations.
  • Household or Organisation Record Type equals "Local Meeting".
  • Filter by "Aust RM associated with" (use, for example, 'greater than v' and 'less than w' for Victoria - this ensures you don't have to have the exact RM name).
  • Don't include subtotals.

The order of the fields can be changed by dragging them in the list on the Edit screen.

The fields included are:

  • Parent Household or Organisation

  • Household or Organisation Name

  • Shipping/Worship Street

  • Shipping/Worship City

  • Shipping/Worship State/Province

  • Shipping/Worship Zip/Postal Code

  • Primary Contact

  • Phone

  • Worship Time and Day

Restrict Access: 
All Site Members

Rename a report

To rename a report, go to the Edit screen and click Save > Properties

Restrict Access: 
All Site Members

AYM Membership Secretary only

This page contains information for the AYM Membership Secretary only.

An update of information on the website can be forced for the dev site or the live site.

Michael: I have added things below gleaned from our various conversations.

Adding a field to Salesforce

Here's the Salesforce documentation on how to add "Field-Level Help" text: https://help.salesforce.com/articleView?id=customhelp_defining_field_level_help.htm&type=5

If a field is added to the Salesforce file it is added to all types of record and is available in all, but can be suppressed so it does not appear in any of them. To restrict its appearance to a particular type of record (e.g. Meetings) it needs to then be ‘un-suppressed’ in those records. The field can then be made alterable only by an Administrator or by a Membership Secretary on the basis of another option.

In June 2019 Jeff gave the following explanation for making the "Deceased" field visible to Membership Secretaries:

  • Go to contacts tab or a contact record
  • Hit the setup icon (gear) in the upper right
  • Select "edit object" in the setup menu
  • Select "Fields and Relationships" in the admin sidebar menu
  • Find the "Deceased" in the field list (I used the search filter at the top) and click on the linked label
  • Clicked the "Set Field Level Security" button at the top.
  • Clicked the "visible" checkbox next to RM Secretary profile and save.

Logging in as a Membership Secretary

RM Membership Secretaries log in with a different level of access so don’t see as much as an Administrator’s log in. You can see their experience by going Setup (Cog) > Users > Users and choosing to log in as one of them. The layout of records is very different.

Find a Friend and printable lists

The Find a Friend list comes from Salesforce on the basis that the Contact:

  1. has a Salesforce ID (i.e, is not a Developer)
  2. is not "inactive"
  3. is not "deceased",
  4. AND either has:
    1. a Quaker Status of Member, Attender, Child of the Meeting or Member of Overseas Meeting or
    2. the field Force Web Enabled checked.

We are working on a similar basis for the printable lists, which at present are prepared by David Parris.

 

Restrict Access: 
All Site Members