Evangelical Lutheran Church in Canada
Directory   Search  

Who was Rasmus?

This project is named after Rasmus Jensen, the first Lutheran pastor in North America.

Pastor Jensen was the chaplain of an expedition sent in the spring of 1619 by King Christian IV of Denmark and Norway to search for the Northwest Passage to India. The expedition landed on the shore of Hudson Bay at the present day site of Churchill Manitoba in the fall of 1619.

His commemoration date is February 20.

Home » Project Rasmus » Event Comments Send to a friend     print

Project Rasmus

Event Registration Application - Comments Summary

This is a summary of the discussion of the event registration application by the bishops, the representatives of the synod offices, and the representatives of congregations who met in Winnipeg June 16-18. Comments in italics have been added by Tony Kwok, the IBM representative who has been working closely with the ELCIC to develop the requirements for the applications.

  1. Attendee Data
  2. Billet Data
  3. Statements
  4. Payment Data
  5. General Functionality Comments

Attendee Data

  • Congregation data has been added to the contact record in the contact database, so those fields can be copied into this form when the person picks their name off of the contact list at event registration time.
  • We need to define which fields are mandatory and prevent people from submitting incomplete forms. This should be checked when the person finalizes their session choices and tries to save their document.
  • Add field to record accommodations confirmation number and add this field to mail merge
  • Add field to record travel confirmation number and add this field to mail merge
  • Need some way to identify oddball situations
  • The two miscellaneous categories can be used to enter in any textual attribute you need to tie to an individual. You can then bring up a list of all individuals that have that attribute assigned to them. This would work for things like table assignments or anything else where you need to group people by a common attribute
  • The RoomMate assignment allows you to enter any textual description to group people together by rooms. If some rooms have weird requirements (e.g. bring your own pillow) then this should be included as part of the textual description of that room grouping (e.g. Delta03 - Bring Pillows)
  • If people specify a roommate and that person has not registered yet, then give the first person a textual roommate grouping that implies that (e.g. Waiting for Bill Smith)

Billet Data

  • Add a form to track billeting information
  • How many people can they billet?
  • Do they have any pets or other things that people could have allergies to?
  • Can they provide daily transportation to/from the event site


  • Add a field for late payment fees. The event setup document could have a field for defining the fee amount.
    COMMENT - If the fee is applied to all statements not paid up by a certain date, then this date can be captured in the setup form so that all late fees are automatically applied and those statements would change status so that the registrar knows they need to be reprinted and sent out again. Otherwise, it will likely be a checkbox where the registrar checks this checkbox for all people who should be charged the late fee.
  • Each session that a person is being charged for should be itemized on the statement
  • The setup document should allow you to define if certain lines of the statement will print if the line amount is zero.

Payment Data

  • A new form needs to be designed for capturing payments made by an attendee. When the Statements get refreshed, the total of all payments should be deducted from the total amount owing to give the outstanding balance.
  • This form should capture payment type, date of payment, cheque number, etc.

General Functionality Comments

  • There were several requests for the ability to turn off unused features and/or development of a light weight version that could be used by any congregation or group for managing smaller events
  • Mail merge button should capture additional fields of data to facilitate the production of quick reference cards that can be used during the event if a computer is not available
  1. Attendee Data
  2. Billet Data
  3. Statements
  4. Payment Data
  5. General Functionality Comments

We appreciate your comments and suggestions about Rasmus at this e-mail.

In full communion with The Anglican Church of Canada
© Copyright 2007 Evangelical Lutheran Church in Canada