Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
What's new
10
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Open sidebar
Michael McAndrew
GSoC 2018
Commits
de3c742d
Commit
de3c742d
authored
Jan 25, 2018
by
bgm
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
projects.md: removed i18n project, add pluggable data export formats for reports.
parent
4535bd9c
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
14 additions
and
13 deletions
+14
-13
projects.md
projects.md
+14
-13
No files found.
projects.md
View file @
de3c742d
...
...
@@ -9,20 +9,21 @@ GSoC students are free to propose projects that are not on this list, but will n
find a qualified mentor for the project.
## Improve multi-lingual scalability
Themes: Translation, Internationalisation, Database architecture
Potential Mentor: Mathieu Lutfy (primary), Xavier Dutoit (for client testing)
When organisations operate in multiple languages and have public-facing forms available in multiple languages,
CiviCRM has to be switched to "multi-lingual mode". This makes it possible to translate custom field labels,
contribution page titles, etc, into more than one language. However, the current database model is made in a
way that only makes it possible to use up to 3 languages. We are looking to change the database model to a
more scalable one.
Technically, the current database model uses one big table per entity, with an extra column for each language
(ex: civicrm_contribute.title_en_US). A MySQL "view" is then created to simplify database queries
(civicrm_contribute_en_US.title). The model needs to be flipped around: an extra table for each language. We
also need to provide an upgrade mechanism for existing sites.
## Pluggable data export formats for reports
Potential Mentor: Mathieu Lutfy (Coop SymbioTIC)
CiviCRM currently supports exporting reports to CSV and PDF format. Some
extensions make it possible to export to other formats, such as for exporting to
Excel (xlsx), but they have to implement odd hacks to get around the lack of
pluggable data export formats in CiviCRM.
This project would therefore aim to provide a clean set of 'hooks' so that
extensions can support other export formats. It would also aim to propose
changes to some of the extensions, to provide examples. Since this is a change
to CiviCRM's core, it would require writing a unit test, documentation and
interacting with other developers to gather other potential use-cases for this
hook.
## Mosaico for transactional emails
Themes: UI, responsive html5
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment