Forum .LRN Q&A: Contacts for community membership management

I might have the need for users to provide additional information upon signing up into a .LRN community (so not only during the registration per se, as has been TIPped, but in general).

Furthermore, mailings should be send to users based on this information and not just for all users.

Knowing contacts, I know that I could just add contacts to the community, do some integration in the "join / apply" page and replace bulk mail with the more sophisticated mass mailing available in contacts.

The question I have though: Am I the only one with such a need? How do you send mass mailings to a subset of your students based on additional information you have about them?

Or am I strange in using .LRN for Communities in general and should I just switch to using Subsites, though this would probably disable the nice portal interface (and benefiting from the good UI work done on .LRN).

Collapse
Posted by Caroline Meeks on
Hi Malte,

Solution Grove is moving more and more towards using subsites for any new site that isn't exactly the use case the dotLRN infrastructure was built for.

We are still supporting an number of existing dotLRN infrastructure based sites. For several of those clients contacts might be a far more useful to them then Bulk Mail. However, everyone has their agendas, priorities and budgets and I don't see this as an area of investment for our dotLRN infrastructure clients in the near future.

One problem barrier to adoption is the variation in the collection of user data. One of the features of contacts over bulk mail is being able to do a search based on user data and sending mail to the results of that search. My understanding is that contacts uses AMS for user data.

Contacts - AMS
Sloan - PhotoBook
MGH - Assessment
KSG - extensions to the user table

My assumption is that these variations means that contacts as a replacement for Bulk Mail for dotLRN will not be plug and play for our clients.

Let me know if I'm understanding the challenges and advantages correctly.

Thanks

Collapse
Posted by Malte Sussdorff on
When it comes down to bulk mail vs. contacts for existing installations, nothing would change. Bulk Mail goes out to group members only anyway, so replacing it with contacts would do no harm (you would just use contacts to send the message to the group, along with the mail tracking and the ability to attach files to it. Also you would get more variables that are auto replaced to include in your mail. And did I mention mail templates?).

Once you store additional data in contacts (apart from the mandatory first name, last name and email), you would be able to make more customized emails, though before that would be a good time to think about the permission for attributes a little bit more (I mean it works and I have a pretty good idea how to solve this elegantly if you have one contacts instance but multiple communities), but still, it needs some talk.

As for the amount of work involved in actually moving from e.g. photobook to contacts, that will differ from client to client. Steps involved:

a) Create the attributes which are needed per default for a person and an organization
b) For each community add the additional attributes (all using the contacts admin page).
b1) If you have attributes which are only readable for a certain group of people, add a group for these attributes. This is a little bit hard to understand, but is part of the setup process which can begin once the initial data collection has been analysed.
c) Export your existing data in CSV.
d) Use the newly (to be released) general import functionality that allows you to match the Headers in the CSV to the attributes in the groups (see a) and b))

As you described your existing customers, they are using different approaches which should probably not be adopted nowadays by new .LRN users.

The benefit of contacts is not the storage in AMS (though this is a plus). What is best about it is the good combination of AMS lists (a list of attributes bundled together) with linking it to groups and permissions, giving you greater flexibility (and reuse ability). Apart from the CRM functionality you get on top.