Talk:Meeting Bulletin Application
Please sign your comments with four tildes (
1. Right now, one cannot use the official Church logo, although many units do that anyway on printed programs, but the official name of the Church can be included. Church logo use policies are in Handbook 2.
2. A way for a nonmember who might come into the building with a smartphone to be able to access the basic program with most of the information without the app may be desirable. I recommend this be made a subset of the 'Newsletter' feature, but also have a path so anyone walking into the building with a smartphone is able to view the meeting bulletin, if it is a public meeting like sacrament or priesthood, can see it with little additional effort. This access will be important in missionary efforts, so those who are not members who come into the meetings that are more general in nature can feel more a part of the meeting.
3. Another idea with the music is a way to, after the meeting is done, to reference the hymn's music download (where available) so members can use it right away. For choirs, if the music is available on lds.org or something that was submitted via create.lds.org, a link can be used to help them prepare for presenting the special musical number if that number exists on pages of music eventually posted from create.lds.org music selections. Some choral music (maybe even some with sheet music) has been submitted to create.lds.org, for future inclusion in what was known as the Media Library part of lds.org, now called something longer although the music portion has not been activated yet. We don't even know how much of the submitted recordings to create.lds.org are of solo and choral music appropriate for sacrament or similar meetings as of this writing.
- Hi James, Thanks for the feedback. I'll incorporate these ideas into the outline. David Bailey (talk) 07:48, 8 August 2012 (MDT)
Started on my own for my own ward
I've started working on this for my local ward and am using this outline as the basis. Here's the initial hard-coded HTML page that I have been using as a starting point. This Sunday I'll be starting work on the backend.
Initially I'll work out the mobile piece, then work on the PDF generation of the printed program. I've created working code that takes the LDS Account login/password and pull a JSON string of the calendar items for your ward (with the intention that you can pick which items should show up on the bulletin). I've also create database tables with a collection of hymns, Priesthood lessons and Sunday School lessons that all link to the corresponding online version - so when creating the bulletin you only need to enter the hymn #, lesson #, etc., and the system will pull the title and link. -- Epoulin 14:24, 14 May 2013
- Please note that the code you've created that uses LDS Account is contrary to Church policy. We read in Third-party API for gospel content: "... third-party developers are restricted from using LDS Account, which could give access to membership data. This restriction protects the privacy of membership data (a legal requirement in many countries) and safeguards how membership data is viewed and used."
- I know you're just trying to help, and it's great that you are innovating, but it's essential that we follow Church policy. So you'll need to figure out how to create your app without using LDS Account. It appears that the proposal by David Bailey is for a Church-sponsored project, which would be able to use LDS Account, but since your effort is not an official Church project, you don't have that option. Thanks. -- Aebrown (talk) 08:34, 15 May 2013 (MDT)
- Tks Aebrown - that's too bad - especially since I found the technique for using the LDS Account calls here on LDS Tech :) Without LDS Account access, people will need to manually enter calendar items which makes the app very painful... but I suppose no less painful than creating a Ward Program in MS Word. I realize the proposal is for a potential church project - was just taking initiative to fill a need and using this well thought-out design outline. Epoulin 14:24, 15 May 2013
- Is there a way that we can turn this app into an LDS project? The Sunday Bulletin is a constant hassle and it would be a real blessing if we could find ways to automate and streamline the process of creating them. I think what Epoulin has done is a marvelous start - how do we now move it into a project using church-approved technologies and methods so that we can get the benefits of this GREAT IDEA? I'm interested in working on the project (and recruiting others) and helping to move it to the LDS Stack and adopt corresponding app standards. Please advise. Rhusted (talk) 10:50, 24 June 2015 (MDT)