ChurchCRM / CRM

ChurchCRM is an OpenSource Church CRM & Management Software.
https://ChurchCRM.io
MIT License
616 stars 434 forks source link

File Upload and management #350

Closed rakess70 closed 1 month ago

rakess70 commented 8 years ago

This could be used for many purposes

Common forms and files needed for events (parental authorization, confidential forms, reimbursement) Sheet music File downloads

It could also be used to make a form of worship planning system.

dschwen commented 8 years ago

I remember a discussion about this from a few weeks back. I think the consensus was to use existing solutions that have been developed for these purposes. Correct me if I'm wrong.

DawoudIO commented 8 years ago

correct, services like dropbox etc support api to upload files...

DawoudIO commented 8 years ago

@crossan007 requested it via https://github.com/ChurchCRM/CRM/issues/122

crossan007 commented 8 years ago

@dschwen You're not wrong; although I still want to build it into ChurchCRM so that files can be easily associated with families, and so that families can access the files published to them.

I don't really care what the storage back end is. In fact, It'd be great it we let the admin choose the back end with the ability to automatically migrtate files between whatever backends we support (Local [my preferred choice], Backblaze, S3, Dropbox, Google Drive, etc), and present the files to the users in the ChurchCRM UI.

crossan007 commented 8 years ago

From #122 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 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.

crossan007 commented 8 years ago

+1 Another request for this

MrClever commented 4 years ago

This has been asked again recently. There are ways to work around the lack of feature in the notes editor (by linking to a URL/image) but this is a clunky solution. Having the ability attach files to both families and individuals would be a useful feature to many I think.

crossan007 commented 4 years ago

I've been thinking more and more about implementing this. Let's keep it open.

github-actions[bot] commented 2 months ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] commented 1 month ago

This issue was closed because it has been stalled for 15 days with no activity.