Skip to content
Snippets Groups Projects
Select Git revision
  • main default protected
  • 1.25.x
  • 1.95.x
  • issue_141
  • 132-symfony-component-eventdispatcher-event-is-deprecated-consider-using-civi-core-event
  • 1.56.x
  • 1.46.x
  • 1.24.x
  • issue_114
  • 1.11.x
  • 1.9.x
  • 1.3.x
  • 1.2.x
  • 1.1.x
  • 1.0.x
  • 1.120
  • 1.119
  • 1.118
  • 1.117
  • 1.116
  • 1.25.8
  • 1.25.7
  • 1.25.6
  • 1.115
  • 1.114
  • 1.113
  • 1.112
  • 1.111
  • 1.110
  • 1.109
  • 1.108
  • 1.107
  • 1.106
  • 1.105
  • 1.104
35 results
Compare
erik's avatar
use_case_tokens
erikbrouwer authored
df606c3b
History
erik's avatar df606c3b
History
Name Last commit Last update
..
dev
images
CustomizePdfTemplate.md
HowToAddAPIDataOutput.md
HowToDevelopACsvDataSource.md
add_your_own_datasource.md
basic-concept.md
hooks.md
how_to_create_search.md
how_to_create_test.md
index.md
uc-mailtokens.md
uc-members-online.md
index.md

Introduction

Data Processor is an extension originally developed by CiviCooP, mainly funded by Velt, Barnekreftforeningen, Zorg om Boer en Tuinder, NIHR BioResource, Civiservice.de and CiviCooP themselves.

The aim of the extension is to create an engine to quickly create data overviews without coding that can be used within CiviCRM but also outside of CiviCRM, like on the public website.

And without the requirement of having CiviCRM installed on the same server. So I could have my public website on server A and CiviCRM installed on server B and still show data from CiviCRM on my public website using the Data Processor extension.

The configuration we had in mind when developing is a CiviCRM installation on a different server than the public website and communication with CiviCRM using the CiviMRF framework (see the CiviMRF GitHub repo).

!!! Note "About CiviMRF" CiviMRF is a framework that enables communication between a public website and CiviCRM on a separate server. It contains a generic core, a Drupal 7 specific implementation, a Wordpress specific implementation, a Drupal 8 specific implementation etc.

This is not required, you can just as well use the Data Processor extension to communicate with a CiviCRM installation on the same server as the public website.

Contents

This guide is an attempts to explain the basic concept of the Data Processor and a few examples on how to use the data processor.

In some examples other related extensions are required as well, we will mention that in the examples.

The basic concepts of the Data Processor are explained on:

This guide also contains a few examples of use cases:

And some technical information on how to add your own data sources:

CiviCRM versions

The Data Processor extension has initially been developed with CiviCRM 4.7 and has been tested with CiviCRM 5.x on various sites.

!!! Note If you want the Data Processor updated to a newer version you can do so. Alternatively, if you want us to do it and have some funding, contact Jaap Jansma (jaap.jansma@civicoop.org) or Erik Hommel(erik.hommel@civicoop.org). You can also find them on the CiviCRM Mattermost Channel using the handles jaapjansma or ehommel.

Screen prints

In this guide you will find a number of screenshots. These were all taken from an installation with the Shoreditch theme.