After both participants kill a convo it remains in that participants convo's list. Is this beneficial or determental?

When a broadcast is created it is sent as a singleton message to all users, also pinging them

Data

• recepients: [Groups] || null(all)
• title: String
• message: String
• isNotification: Boolean
• syncs: enum(all, events, convos, singups, messages, talks)
• createdBy: User

Applies to talks and events

Render if loaded in browser, json if not.

Possibly render if get request but return json error message if post/put request?

Fail if one field left empty of required fields
Talk:

• topic
• author
• date
• reference
• outline

Msg:

• subject
• author
• msg

The problem here is that broadcasts will create and use a message to show user's the message text, how will this work for older clients? They just don't get to see the option?

Will create a spreadsheet for a signup and add data to it

Makes use of google docs

Implementations

• Add google auth code to User
• Add refresh token to User
• Add Worksheet id to Signup
• Add Spreadsheet key to Signup
• Create get auth key utility function
  • uses refresh token to get auth token

For following functions: if auth key fails then use utility to get new refresh

• When creating a new signup - async F() below
  • create spreadsheet
  • get spreadsheet
  • get worksheets
  • add worksheet Id to Signup
  • add spreadsheet key to signup
  • add header cells
• When member adds to signup
  • create row with worksheet id and key

Will close issue #5 when complete

If I am user1, with broadcasts 1 and 2, and I try to kill broadcast 1, both die.

After fixing, need to retest remove users broadcast on test-deploy server

• all of the user ones
• add signups (if permission)
• add events (if permission)
• add talks (if permission)
• inbox (if minister)
• ios
• android

If Req.body.address, line 39 of events controller

• server
• android
• ios
• some sort of printable data page

• name
• time of event
• members
• member count
• location
• related event

Schema for "Conversations"

Goal

• This data is designed to represent a series of back and forth communications between two parties.
• The document should keep track of whether the data has been read by one party

Fields

Opted out of participant array for using static group ministers
Ministers can see all conversations

Compatability

Messages end-points that must stay:

• [GET] messages/mine
• [POST] messages/
• [DELETE] messages/

Messages fields that must stay:

• _id
• from
• simpleFrom
• simpleTo
• subject
• date
• message
• version
• topic
  • _id

Fields to be added to Messages

• Added
• conversation
• sender_id

Note: essentially conversation will 'replace' the "to" fields and sender_id will replace the "from" fields, conversation now will also hold the relevant data for subject, version(because individual messages are nonmutable), and topic.

Changes in Messages endpoints

• Changed
• [POST] messages/
  • will create two things:
    • message object: just like normal
    • conversation object
      • singleton: true
      • add a new message object to the conversation like a new conversation

Creates two types to fully support backwards compatability between senders and ministers

Scenarios:

• Old Sender -> Old Receiver
  • will come as normal message
• Old Sender -> New Receiver
  • will come as singleton conversation
• New Sender -> Old Receiver
  • not supported, idea is that an old receiver should be upgraded before new receiver
• New Sender -> New Receiver
  • will come as conversation
• [DELETE] messages/
  • will only work if message does not have conversation field

Fields to be added to Users

• Added
  • active_conversations - all conversations that the user is a participant of that are still globally alive
  • [array of objects]
  • object:
    • id of conversation
    • considered alive
    • sender_id

Fields to be added to Groups:

• Added
• can create conversations - users
• can read conversations - ministers only

Paths for Conversations

Consider which ones, fields to determine which ones, authentication needed

• Gets
  • (/) - gets all conversations(for dev reasons)
    • need to be admin
  • (/minister) gets all conversations still alive
    • need readConvo group permission
  • (/mine) gets any conversations that user has that are still alive
• Posts
  • (/) - create new conversation, see here
    • needs "createConvo" group permission
• Puts
  • (/send) - adds a new message to an exisiting conversation
    • authenticated()
    • will make the conversation alive again for all parties(and check that it's globally alive)
    • will set readLast to false for all parties except the sender

Create New Conversations

Follow table below

• android
• ios

• android
• ios

• related signups

• send a message
• refresh
• ios
• android

Only the minister should get an original notification

Minister also get notification when he updates

If I send a broadcast to all groups, and user1 is in groupA and groupB he will receive the broadcast twice.

After fixing, need to test sending broadcasts on test-deploy server

will allow better connection between maps programs

All of the convo functions seem to fail on the gcm send function.

Need to restest, send, respond, and kill convos on test-deploy