[Ldsoss] Re: HT and VT Tool

[Big Daddy]

>From what I understand the Membership Record "can" contain other confidential information.
 
Richard Butt
4796 S. Linoln Ridge Drive
Tucson, AZ 85730
 
Richard.Butt at yahoo.com


 



----- Original Message ----
From: Manfred Riem <mriem at manorrock.org>
To: LDS Open Source Software <ldsoss at lists.ldsoss.org>
Sent: Tuesday, May 22, 2007 11:17:44 AM
Subject: RE: [Ldsoss] Re: HT and VT Tool


Hi Tom,
 
Having dealt with an issue in the past concerning the Membership record I can say that
really depends on the country of residence. At the time I was in Holland and there an 
individual can request access to any record pertaining to them or minors in their care.
The law there even goes as far as allowing access to the other spouse record if the
individual is mentioned on it. Note that I say ACCESS, so handing out is not really the
issue.
 
How it is here I do not know. I guess it comes down to the privacy policy the church
has in place for each country ;)
 
Manfred
 



From: ldsoss-bounces at lists.ldsoss.org [mailto:ldsoss-bounces at lists.ldsoss.org] On Behalf Of Thomas Haws
Sent: Tuesday, May 22, 2007 12:09 PM
To: LDS Open Source Software
Subject: Re: [Ldsoss] Re: HT and VT Tool


I have heard it called confidential, but for the life of me I can't fathom why.  Maybe like the Social Security number, some people are just touchy about such things.

On that subject, I recently got a message on MLS pointing out that the Individual Ordinance Summary is for handing out to a member, but the Membership record is NOT.  But again, for the life of me, I haven't yet discerned any difference between them.  And I certainly can't figure out any moral justification for keeping information on people that they aren't permitted to access.  Does anybody have any insight on this? 

Tom


On 5/22/07, Slide <slide.o.mix at gmail.com> wrote: 
On 5/22/07, Bill Pringle <wrp103 at psu.edu> wrote:
> The CSV files from MLS also contain the membership IDs, which is a
> permanent identification.  That is what you can use and never 
> change.  The internal ID value seems fairly stable, but I only use it
> to match up the HT/VT and Organization records with the Membership
> records.  I have defined an auxiliary file that I use for my 
> program.  This file contains the membership ID along with any other
> information I want to keep (like cell phones and e-mail for each
> member)  By comparing the auxiliary file with the import, I can tell 
> who is new and who is no longer on the records.
>


Isn't the MRN confidential information though? That is why I wasn't
storing it or using it.

slide
_______________________________________________ 
Ldsoss mailing list
Ldsoss at lists.ldsoss.org
http://lists.ldsoss.org/mailman/listinfo/ldsoss




-- 
Tom Haws 480-201-5476
Have a beautiful day. 
_______________________________________________
Ldsoss mailing list
Ldsoss at lists.ldsoss.org
http://lists.ldsoss.org/mailman/listinfo/ldsoss


       
____________________________________________________________________________________Pinpoint customers who are looking for what you sell. 
http://searchmarketing.yahoo.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ldsoss.org/pipermail/ldsoss/attachments/20070522/561dec21/attachment-0001.html