Better yet, correct them in MLS. If you're not the guy, then make a list of changes and get it to the Membership clerk.RussellHltn wrote:I'd suggest editing the file with a text editor such as notepad. It's ugly, but it works.
Use this forum to discuss issues that are not found in any of the other clerk and stake technology specialist forums.
Many questions are already answered on the LDSTech wiki. Check it out!
lajackson wrote:Another training opportunity on the importance of accuracy in membership records. [grin]
And another opportunity to lament the fact that MLS provides no tools for validating and standardizing addresses.
And he probably wants to get his map sometime this month.boomerbubba wrote:His problem is that he is a stake clerk. All such edits must be made in ward MLS. (I suppose he could send the files to the ward clerks to make corrections.)
Long term, that is the right way to do things.
This may be more trouble than it's worth, but if you open the unedited file in WardMap, then click on the offending addresses, you can place them on the map yourself. Look up the locations with whatever geocoder you prefer, find out where they are, and point them out on the map. WardMap will remember these locations, so you'll never have to do the same address twice (unless you move to a different computer).robm wrote:So in the short term I was opened the membership.csv file in excel and hand tweaked and fixed most of the problems with the addresses. However, after I save the file and try to load it into WardMap, it just sits there trying to import and does nothing.
This is a problem I experience regularly with work. My solution is to use a program called R to read in the Excel CSV, then export it to a new file. R will write the csv file in the format WardMap is looking for. As long as you don't open it in Excel, you should be okay.robm wrote:Oh...boy, gonna make me write a perl script -- hmm, seems like this could be a problem someone else has already solved. Maybe Google has my answer...
Thanks for the info--
It's an extra step, but it let's me use the convenience of Excel spreadsheets while still getting the format that I need.
R Foundation for Statistical Computing
Sample code to import data
Import <- read.table( [FILENAME], header=TRUE, sep=",")
Sample code to export data
write.table( Import, [FILENAME], quote=TRUE, sep=",", row.names=FALSE)
I'm having a similar problem with a Singles Branch. I've exported the membership.csv file and loaded it into WardMap (twice). Both times it counts the correct number of members - around 80, but every address except one is not mapped. During the mapping process 79 of the 80 addresses are noted as errors.robm wrote:I am a stake clerk and am trying to use the WardMap program -- I noticed that we had a large number of addresses that could not be mapped and this was mostly due to spelling errors, abbreviations, and missing information in the address fields in the membership.csv file......
I've checked the csv file and the addresses appear to be correct, although they are scattered around a bit - perhaps by a few miles instead of a few blocks. The single address that's mapped is no different than any of the 79 addresses that are not mapped.
I've had no problems at all installing the program for the wards in our stake.
One more thing....I've not edited in any way the CSV file that's exported from MLS.
Suggestions? Is a branch csv file different from a wards??
Have you read the Code of Conduct?
Who is online
Users browsing this forum: No registered users