Family / Person Attachments

[crossan007]

create a way for distributing (semi) private attachment files from the church to persons / families. eg: Recorded words or other media.

I envision this will be an "Attachments" table, with a reference to the family / person ID, the person who created the attachment, and date / time it was uploaded. Also it will store the actual file name of the file on the server so as not to store BLOB data in SQL. This file name will be a (GUID) to reduce possibility of collision.

The person / family, then would be able to see the list of files assigned to them, as well as download / view the files in the browser.

[DawoudIO]

would it be better to do an API integration with dropbox or another service like that? this way you don't have to worry about server file security

[crossan007]

@DawoudIO My thoughts for this primarily are audio files (occasionally we'll have a prophetic word recorded for someone, and we like to deliver them that MP3 excerpt of the service personally).

I'm thinking of keeping everything in a protected directory, and then use an API call to actually deliver the file to the user. That being said, I could build it in a way such that the admin could choose a storage platform (Local Storage, Amazon S3, DropBox, Google Drive, etc). Thoughts?

My priority would be on local storage, but I like the idea of offloading storage of larger files.

We could also transition the family / person image storage to this platform if we build it our correctly.

[DawoudIO]

For that check out soundcloud.com

[DawoudIO]

@rakess70's #350 is a bit more border request, do you guys think we can merge these 2 into 1 issue?

[rakess70]

understandable just thought I would make the suggestion :)

[rakess70]

yes lets merge them how do we do that? :)

[crossan007]

I'll close this, since it's tracked in #350