Broaden project scope: Storing and editing board meeting protocols (pöytäkirjat)

[jssmk]

Board members could add, edit, store and browse meeting protocols (written in Markdown) in member registry system with following benefits:

• centralised repository for stored documents
• information about non-handled member applications already available from the same system (helps when writing a new meeting protocol)

Proposed features:

• data model for protocols template, for quicker writing and recurring content
• agenda data model for open issues to be handled in future meetings
• search function

[jautero]

Will the protocols be stored as a document or individual items? If as documents, is sql database right place to store documents? If we store individual items and compose document on demand, are we going to extend it to fully blown meeting system?

[rambo]

I was first thinking of something like storing a Jinja (or Django Template Engine but Jinja is more powerful) template in DB rendered a form with checkboxes for board members present. Membership applications to be approved would be autofilled (checkboxes autofilled but could be unchecked), start time again as a form field, defaulting to now and end-time from submitting, after submitting we have a rendered HTML document that can be stored somewhere (probably should be stored with some metadata but SQL is not the best for document storage, OTOH setting up a separate document db is plenty of extra work)

Searching is either naive (LIKE "%word%" in SQL) or complicated to set up (Elasticsearch with or without dedicated document database, or some document database with built in search)

[rambo]

JSONField https://docs.djangoproject.com/en/1.9/ref/contrib/postgres/fields/#jsonfield would work for metadata storage and querying quite cleanly.