ELD Liaison Program

Liaison Program Contents

• Reports: 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2001/2002
• Organizational Liaisons Roster
• Description and Charge
• Procedural Clarifications from the Montreal Meeting (June 2002, revised 7/29/2002)
• Guidelines for Cross Posting of Listserv Messages between Liaison Organization servers and ELD-L

Organizational Liaison Roster

Procedural Clarifications from the Montreal Meeting (June 2002)

Below are the decisions and clarifications from the ELD Extended Executive Committee meeting in Montreal that pertain to the Liaison's Program.

1.) What to do when you uncover/discover a chance for collaboration between your group and ELD that you think is worthy of pursuit?

If there is already a corresponding ELD committee or group for that topic/issue, contact the chair of that group and  copy the ELD Liaison Chair. (The ELD Division Chair will remind the other committee chairs that they may be hearing from Liaisons in this context.) If there is not a corresponding ELD group, the talk to the ELD Liaison Chair about the opportunity, and the Chair will consult the ELD Extended Executive Committee (EEC) about that action to take, if any.

2.) What happens after you tell the corresponding ELD chair about the opportunity for collaboration and give them the contact information for the relevant people in your organization?

After contact the chair of the ELD group the ELD liaison's job is done. (we don't expect you to make the collaboration itself happen). The relevant ELD committee will explore the opportunity and the chair of the committee will notify the liaison and the Extended Executive Committee of the outcome (either the results of the collaboration or the reason for the decision not to collaborate).

3.) How do you know what sessions to attend at your conference and/or who to talk to in your organization?

The liaisons charge specifies that you need to attend the business meeting at your annual conference, if it is open. Other suggestions: keep up to date on the activities of ELD (the May/June issue of the ELD newsletter contains the annual reports from the committees and is an excellent summary of ELD activities and interests), look for logical collaborations based on existing ELD groups, but also use your best judgement and follow your instincts. At the Montreal meeting the EEC decided not to provide any particular subject focus for the liaisons.

4.) The EEC recommended that publisher liaisons not be initiated at this time.

5.) Liaisons to non-ELD session at the ASEE Annual Meeting:

While recognizing the value of having a librarian presence at non-ELD sessions at the conference, the EEC did not want to deprive anyone of the chance to attend all of the ELD sessions. So rather than making an official posting of liaisons to the non-ELD sessions, the Division Chair will issue a call for volunteers to attend and report on non-ELD sessions of possible interest to all ELD members. These volunteers will write up a summary of their session for the Listserv and newsletter.

6.) How and when to post your ELD Liaison Reports (updated 3/12/03)

You are expected to post your meeting report within one month of the end of the meeting. The Liaison Chair is happy to review your reports prior to posting, but that is not required. You must post your report in two places in two formats:

• Post the report to the ELD-L Listserv directly (send them to ELD-L@U.Washington.edu). Preferred format is to put the report in the text of the email rather than attaching a file because having to open a file may be a barrier to reading the report.
• Send a WORD version of the report to the ELD Newsletter Editor for posting in the next issue of the newsletter, with a copy to the Liaison Chair. The WORD document must be in New Times Roman 10 pt. font.

Guidelines for Cross Posting of Listserv Messages Between Liaison Organization Listservs and ELD-L (revised 7/29/02)

The first goal of the ELD Liaison's program as stated in the program charge are:

• Improving and increasing the visibility of ELD and its activities within those groups for which they act as liaison [and vice versa]
• Improving awareness of issues and activities of importance to ELD or its members and communicating that information back to ELD

The organization listserv is an important communication mechanism for both ELD and for most of our liaison organizations and would seem to be a useful tool to meet the above goals. When cross posting messages please follow these guidelines:

• Before cross posting a message, obtain permission from the message author/original poster to do so.
• Cross post messages to ELD-L (the members only list) rather than to ELDNET-L (the list open to anyone). To post to ELD-L send a message to ELD-L@U.Washington.edu. Only members can post to this list as well as receive messages on this list.
• Clearly state that the message is a cross posting, with permission, in the subject line so that people subscribed to both lists can delete duplicate messages easily. For example: "From PAMNET: subjectXYZ posted with permission."
• Be selective. If a thread of discussion is particularly rich, consider summarizing the conversation to date to start a similar conversation on our list rather than cross posting all the messages on the topic from the other list. But we do want to know the opinions of the other organization members so be sure that comes through.
• Look for ELD-L messages/conversation/announcements to post to your organization's Listserv (again with permission of the author). We want communication to flow both ways.

Last update 6/5/2006
Liz Mengel