It would seem that the issue of copying the ward list for maps and maintaining changes in the membership directory could be (partially) addressed by providing some type of programmatic (e.g. web service) interface to the membership directory. Is this a good idea? Would it be permissible for calling applications to act as a pass-thru for the name/password?
(Right now I think you can log onto lds.org/units "normally," which caches your session and would allow a subsequent website to access the URL to the CSV file on lds.org/units once you've authenticated. In other words, you can still have a map application that uses the membership directory without copying it. However, I haven't been successful in doing this without the web browser.)
Programmatic access to the membership directory
-
- New Member
- Posts: 1
- Joined: Mon Feb 12, 2007 5:01 am
- Location: Houston, TX
- Contact:
- WelchTC
- Senior Member
- Posts: 2085
- Joined: Wed Sep 06, 2006 8:51 am
- Location: Kaysville, UT, USA
- Contact:
I'm working with the various departments that control data to see if this is feasible.qslewis wrote:It would seem that the issue of copying the ward list for maps and maintaining changes in the membership directory could be (partially) addressed by providing some type of programmatic (e.g. web service) interface to the membership directory. Is this a good idea? Would it be permissible for calling applications to act as a pass-thru for the name/password?
Tom
- thedqs
- Community Moderators
- Posts: 1042
- Joined: Wed Jan 24, 2007 8:53 am
- Location: Redmond, WA
- Contact:
-
- New Member
- Posts: 8
- Joined: Tue Apr 03, 2007 1:29 pm
- Location: Logan, Utah
API Access to membership directory
I would personally love API access to membership information. I'm working through some programming project ideas and allowing a user to supply their ward website username and password would reduce the complexity of maintaining two databases significantly.
-David Ernstrom
-David Ernstrom
- thedqs
- Community Moderators
- Posts: 1042
- Joined: Wed Jan 24, 2007 8:53 am
- Location: Redmond, WA
- Contact:
I know the church is looking into this. As for my project it still is on the back burner until after finals. This API that I am personally creating has no affiliation to any church sponsered project and it really is so additional projects that I plan on implementing for my own or community purposes can have easy access into the LUWS system.
Since this project is not sponsered or affiliated with the church and really relys on the current implementation of LUWS it will only work until LUWS is updated or the HTML format of information is changed. (Thus the reason why the community wanted a XML formatted API into LUWS)
Since this project is not sponsered or affiliated with the church and really relys on the current implementation of LUWS it will only work until LUWS is updated or the HTML format of information is changed. (Thus the reason why the community wanted a XML formatted API into LUWS)
- David