MLS -> Outlook + photos -> Blackberry?

[bstein]

As for the source data, I assume you would not use a custom report but one of the standard MLS export formats.
. . .
Do they want a set of contacts structured as one record per member, or as one record per family?
. . .
As far as I can tell, Microsoft does not advertise that Outlook can "sync" such a data import derived from an external source.

We'll be using Outlook 2007 on the ward computer (XP) when we upgrade to 2007. Until then, I'm hammering out the process on my computer. The guidelines contained in the wiki will indeed be followed.

Because the standard MLS exports do not contain all the desired fields, a custom report is necessary, as the goal is to duplicate and extend the information contained in individual membership records (it's for a YSA ward), which extended information would most likely be inputted into Outlook--after a member record is received, is exported and converted to a .vcf and imported.

So far, I have found and modified a shell script to split a multi-record .vcf into individual .vcf's, but it needs refinement. So, if it is possible to create a .vcf, with custom fields and hopefully a photo, that can be imported into Outlook 2007, all with (win32 ports of) GNU utils, then I can probably figure out the parsing, but I would need to find code to convert a JPG to VCF PHOTO data.

That's too bad Outlook can't sync a contact, but it's okay because MLS says when membership data has changed, which would alert when a record needs to be exported, converted, and imported again (or just edited manually).

[mkmurray]

...but I would need to find code to convert a JPG to VCF PHOTO data.

I have C# code for this if you are interested. I won't have access to that code though for a few days.

[RossEvans]

It's up to you, but to me that process sounds like an administrative nightmare with a large amount of duplicated manual work and opportunity for error.

I still don't really understand what you are describing. Do you plan to create custom fields in Outlook that would be populated by keying data into the Outlook screen interface? Is a custom field allowed? Or does Outlook have standard fields that MLS can't populate, but the user would key their content into the Outlook? Or do you mean you will create, populate and export custom fields in MLS via a custom report? If you do a custom report from MLS, I think its output format would be csv, not vcf.

Edit: I see that Outlook does provide for user-defined fields.

If you are prepared to do programming, Microsoft exposes quite a rich software object to drive Outlook by most any language, which would enable a program to update the contacts field-by-field with as much granular control as you want. A programmer could effectively build an automated sync process that would handle new records, revised records and deleted records. The overall task obviously would entail some complexity, but it appears doable. A weakness would be a lack of unique keys. Are you capturing DOB? A combination of DOB and full name is pretty reliable for linking programatically.

[RossEvans]

The scope of this idea turns out to be bigger than just merging photos onto a Blackberry. It seems wise to test several proof-of-concept matters before proceeding too far down this development path:

• On your personal test machine, interactively create a few test records in Outlook, complete with photos and any user-defined fields. Then install the free Blackberry Desktop utility and verify that all this data does sync to the bishopric's Blackberry devices.
• Make sure the bishopric members are informed of the policy guidance against uploading MLS data to third-party servers, so each of them can test whether his own Blackberry can be configured not to propagate this data to his employer's enterprise server. The bishop then can judge whether this plan complies with Church policy.
• Secure the approval of the stake president, who must approve any special software installations on the ward computer, to okay the installation of Outlook, Blackberry Desktop and any conversion utilities you might need. (BTW, to comply with pollcy you also should configure Outlook and other utilities to keep the contacts data files on a flash drive that is locked away when not in use, rather than the hard disk.)

Because a "No" on any of these issues could be a hard stop, better to find out before investing a lot of development time.

[mkmurray]

• Secure the approval of the stake president, who must approve any special software installations on the ward computer, to okay the installation of Outlook, Blackberry Desktop and any conversion utilities you might need. (BTW, to comply with pollcy you also should configure Outlook and other utilities to keep the contacts data files on a flash drive that is locked away when not in use, rather than the hard disk.)

Installing Blackberry Desktop on the ward computer may not help more than 1 person. If the software is anything like how syncing works with the iPhone, you can only sync one device to the software.

[RossEvans]

Installing Blackberry Desktop on the ward computer may not help more than 1 person. If the software is anything like how syncing works with the iPhone, you can only sync one device to the software.

That is one more proof-of-concept test that ought to be run.

Also, does Blackberry Desktop do a one-way sync between Outlook and the Blackberry, or a two-way sync?

[russellhltn]

Secure the approval of the stake president, who must approve any special software installations on the ward computer, to okay the installation of Outlook, Blackberry Desktop and any conversion utilities you might need.

Since Outlook is payware, it will be required for the ward to obtain the necessary licensing to place it on the ward computer. The 2009 Policy and Guidelines states "Privately owned software should not be installed on Church computers."

[RossEvans]

Since Outlook is payware, it will be required for the ward to obtain the necessary licensing to place it on the ward computer. The 2009 Policy and Guidelines states "Privately owned software should not be installed on Church computers."

Yes, the ward would have to pay for it out of Budget funds. My point is that the stake president still would have to approve it, just has he would have to approve any freeware installed on the ward's PC (except those few applications that are pre-approved such as OpenOffice).

[russellhltn]

Yes, the ward would have to pay for it out of Budget funds. My point is that the stake president still would have to approve it, just has he would have to approve any freeware installed on the ward's PC (except those few applications that are pre-approved such as OpenOffice).

I see nothing against donating software to the ward. The guidelines say "properly licensed". I had it in my mind that it had to be owned by the ward. I don't see it as part of the current policy, but I'd feel much more comfortable if it was. Otherwise it might be difficult to show that it is "properly licensed".

I agree with the Stake President's approval. My point was that there is a significant cost as well. Something in the ballpark of $80. (The version chosen will affect the cost - but it can also affect the development.)

And I agree with the idea of getting approval for everything before starting development. I'm just adding another factor.

[RossEvans]

I see nothing against donating software to the ward. ...

I agree with the Stake President's approval. My point was that there is a significant cost as well. Something in the ballpark of $80. (The version chosen will affect the cost - but it can also affect the development.)

In the case at hand, I suspect that -- especially since this project is the bishop's brainchild -- he could find $80 in the ward budget to fund it. Getting the stake president's approval may (or may not) be a more significant barrier.

It had never occurred to me that there could be an in-kind donation of commercial software. I really don't know what the policy is about in-kind donations of any type of property to a unit. If there is a general policy about that issue, it is probably covered in the handbook, not just the letter defining computer policy. That computer policy does prohibit donation of computers.