diff --git a/_includes/data.js b/_includes/data.js index 44015ffd..57065512 100644 --- a/_includes/data.js +++ b/_includes/data.js @@ -1,9 +1,9 @@ var data = [ - {id: 0, date: '2011-01-01', x: 1, y: 2, z: 3, country: 'DE', label: 'first', lat:52.56, lon:13.40}, - {id: 1, date: '2011-02-02', x: 2, y: 4, z: 24, country: 'UK', label: 'second', lat:54.97, lon:-1.60}, - {id: 2, date: '2011-03-03', x: 3, y: 6, z: 9, country: 'US', label: 'third', lat:40.00, lon:-75.5}, - {id: 3, date: '2011-04-04', x: 4, y: 8, z: 6, country: 'UK', label: 'fourth', lat:57.27, lon:-6.20}, - {id: 4, date: '2011-05-04', x: 5, y: 10, z: 15, country: 'UK', label: 'fifth', lat:51.58, lon:0}, - {id: 5, date: '2011-06-02', x: 6, y: 12, z: 18, country: 'DE', label: 'sixth', lat:51.04, lon:7.9} + {id: 0, date: '2011-01-01', x: 1, y: 2, z: 3, country: 'DE', geo: {lat:52.56, lon:13.40} }, + {id: 1, date: '2011-02-02', x: 2, y: 4, z: 24, country: 'UK', geo: {lat:54.97, lon:-1.60}}, + {id: 2, date: '2011-03-03', x: 3, y: 6, z: 9, country: 'US', geo: {lat:40.00, lon:-75.5}}, + {id: 3, date: '2011-04-04', x: 4, y: 8, z: 6, country: 'UK', geo: {lat:57.27, lon:-6.20}}, + {id: 4, date: '2011-05-04', x: 5, y: 10, z: 15, country: 'UK', geo: {lat:51.58, lon:0}}, + {id: 5, date: '2011-06-02', x: 6, y: 12, z: 18, country: 'DE', geo: {lat:51.04, lon:7.9}} ]; diff --git a/_includes/example-backends-gdocs.js b/_includes/example-backends-gdocs.js index 72fa38fd..555d6a2c 100644 --- a/_includes/example-backends-gdocs.js +++ b/_includes/example-backends-gdocs.js @@ -1,10 +1,8 @@ // Create a dataset with a Google Docs backend and a url to the Google Doc var dataset = new recline.Model.Dataset({ - url: 'https://docs.google.com/spreadsheet/ccc?key=0Aon3JiuouxLUdGZPaUZsMjBxeGhfOWRlWm85MmV0UUE#gid=0' - }, - // backend name or instance - 'gdocs' -); + url: 'https://docs.google.com/spreadsheet/ccc?key=0Aon3JiuouxLUdGZPaUZsMjBxeGhfOWRlWm85MmV0UUE#gid=0', + backend: 'gdocs' +}); // Optional - display the results in a grid // Note how we can set this up before any data has arrived @@ -15,14 +13,9 @@ var grid = new recline.View.Grid({ $('#my-gdocs').append(grid.el); // Now do the query to the backend to load data -dataset.fetch().done(function() { - dataset.query().done(function(data) { - // The grid will update automatically - // Log some data as an example - if (console) { - console.log(data); - console.log(dataset.currentDocuments); - } - }); +dataset.fetch().done(function(dataset) { + if (console) { + console.log(dataset.currentDocuments); + } }); diff --git a/_includes/tutorial-basics-ex-1.js b/_includes/tutorial-basics-ex-1.js new file mode 100644 index 00000000..067a1f1b --- /dev/null +++ b/_includes/tutorial-basics-ex-1.js @@ -0,0 +1,24 @@ +// (for convenience) assume availability of jquery +// must have div with class="ex-1" +var $el = $('.ex-1'); + +// we will define this function display so we can reuse it below! +function display(dataset) { + // total number of records resulting from latest query + $el.append('Total found: ' + dataset.recordCount + '
'); + $el.append('Total returned: ' + dataset.currentRecords.length); + + $el.append('
'); + + // dataset.currentRecords is a Backbone Collection of Records that resulted from latest query (hence "current") + // Get the first record in the list - it returns an instance of the Record object + var record = dataset.currentRecords.at(0); + + // Use the summary helper method which produces proper html + // You could also do record.toJSON() to get a hash of the record data + $el.append(dataset.recordSummary(record)); +} + +// now display our existing dataset ... +display(dataset); + diff --git a/_includes/tutorial-basics-ex-2.js b/_includes/tutorial-basics-ex-2.js new file mode 100644 index 00000000..79b937ae --- /dev/null +++ b/_includes/tutorial-basics-ex-2.js @@ -0,0 +1,13 @@ +// must have a div with class="ex-1" +var $el = $('.ex-2'); + +// query with text 'UK' - this will attempt to match any field for UK +// Also limit the query to return a maximum of 2 results using the size attribute + +// query function has asynchronous behaviour and returns a promise object +// (even for the case of in memory data where querying in fact happens synchronously) +// On completion the display function will be called +dataset.query({q: 'UK', size: 2}).done(function() { + display(dataset); +}); + diff --git a/_includes/tutorial-basics-ex-events.js b/_includes/tutorial-basics-ex-events.js new file mode 100644 index 00000000..a9a78ebe --- /dev/null +++ b/_includes/tutorial-basics-ex-events.js @@ -0,0 +1,13 @@ +function onChange() { + $('.ex-events').append('Queried: ' + dataset.queryState.get('q') + '. Records matching: ' + dataset.recordCount); + $('.ex-events').append('
'); +} + +dataset.currentRecords.bind('reset', onChange); + +dataset.query({q: 'DE'}); +dataset.query({q: 'UK'}); +dataset.query({q: 'US'}); + +dataset.unbind('reset', onChange); + diff --git a/_includes/tutorial-basics-ex-fields-2.js b/_includes/tutorial-basics-ex-fields-2.js new file mode 100644 index 00000000..0559abc8 --- /dev/null +++ b/_includes/tutorial-basics-ex-fields-2.js @@ -0,0 +1,10 @@ +var $el = $('.ex-fields-2'); + +dataset.fields.models[6] = new recline.Model.Field({ + id: 'geo', + label: 'Location', + type: 'geo_point' +}); +var rec = dataset.currentRecords.at(0); +$el.append(dataset.recordSummary(rec)); + diff --git a/_includes/tutorial-basics-ex-fields.js b/_includes/tutorial-basics-ex-fields.js new file mode 100644 index 00000000..d6cc38eb --- /dev/null +++ b/_includes/tutorial-basics-ex-fields.js @@ -0,0 +1,20 @@ +var $el = $('.ex-fields'); + +// Now list the Fields of this Dataset (these will have be automatically extracted from the data) +$el.append('Fields: '); +// Dataset.fields is a Backbone collection of Fields (i.e. record attributes) +dataset.fields.each(function(field) { + $el.append(field.id + ' || '); +}); + +$el.append('
'); + +// Show all field info +var json = dataset.fields.toJSON(); +$el.append( + $('
')
+    .append(
+      JSON.stringify(json, null, 2)
+    )
+);
+
diff --git a/docs/backends.markdown b/docs/backends.markdown
index a7af4a04..72e22069 100644
--- a/docs/backends.markdown
+++ b/docs/backends.markdown
@@ -11,11 +11,19 @@ root: ../
   
 
 
+Backends connect Dataset and Documents to data from a specific 'Backend' data
+source. They provide methods for loading and saving Datasets and individuals
+Documents as well as for bulk loading via a query API and doing bulk transforms
+on the backend.
+
 Backends come in 2 flavours:
 
 1. Loader backends - only implement fetch method. The data is then cached in a Memory.Store on the Dataset and interacted with there. This is best for sources which just allow you to load data or where you want to load the data once and work with it locally.
 2. Store backends - these support fetch, query and, if write-enabled, save. These are suitable where the backend contains a lot of data (infeasible to load locally - for examples a million rows) or where the backend has capabilities you want to take advantage of.
 
+
+# Backend API
+
 Backend modules must implement the following API:
 
 {% highlight javascript %}
diff --git a/docs/index.html b/docs/index.html
index caadbff8..432e7b54 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -52,53 +52,17 @@ root: ../
   
-

Twitter Example

-
-
-
-
-
-
-

Customing Display and Import using Fields

-
-
-
-
-

Listening to events

-
-
-
-
-

Setting and Getting State

-
-
-
- -

Extending Recline

-
-
-
-

Create a new View

-
-
-
-
-

Create a new Backend

-
-
-
-
-

Create a Custom Record Object

+

Views Quickstart - Grids, Graphs, Maps and more

diff --git a/docs/models.markdown b/docs/models.markdown index 05ec1976..676dbcb2 100644 --- a/docs/models.markdown +++ b/docs/models.markdown @@ -21,7 +21,7 @@ holding summary information about a Field (or multiple Fields). All the models are Backbone models, that is they extend Backbone.Model. Note, however that they do not 'sync' (load/save) like normal Backbone models. -## Dataset +

Dataset

A Dataset is *the* central object in Recline. Standard usage is: @@ -159,7 +159,6 @@ field's value (if any) and the current record. It's signature and behaviour is the same as for renderer. -

Query

Query instances encapsulate a query to the backend (see

Loading data from different sources using Backends +
+ These set of examples will show you how you can load data from different +sources such as Google Docs or the DataHub using Recline

-These set of examples will show you how you can load data from different -sources such as Google Docs or the DataHub using Recline.

Note: often you are loading data from a given source in -order to display it using the various Recline views. However, you can also -happily use this data with your own code and app and this is a very common -use-case.

-

Moreover, Recline is designed so you need only include the -backend and its dependencies without needing to include any of the dependencies -for the view portion of the Recline library.

+order to load it into a Recline Dataset and display it in a View. However, you can also +happily use a Backend to load data on its own without using any other part of the Recline library as all the Backends are designed to have no dependency on other parts of Recline.

## Overview @@ -30,20 +28,18 @@ source. They provide methods for loading and saving Datasets and individuals Documents as well as for bulk loading via a query API and doing bulk transforms on the backend. -You can instantiate a backend directly e.g. +You can use a backend directly e.g. {% highlight javascript %} -var backend = recline.Backend.ElasticSearch(); +var backend = recline.Backend.ElasticSearch.fetch({url: ...}); {% endhighlight %} But more usually the backend will be created or loaded for you by Recline and all you need is provide the identifier for that Backend e.g. {% highlight javascript %} var dataset = recline.Model.Dataset({ - ... - }, - 'backend-identifier' -); + backend: 'backend-identifier' +}); {% endhighlight %}
@@ -53,7 +49,6 @@ How do you know the backend identifier for a given Backend? It's just the name o ### Included Backends -* [memory: Memory Backend (local data)](docs/backend/memory.html) * [elasticsearch: ElasticSearch Backend](docs/backend/elasticsearch.html) * [dataproxy: DataProxy Backend (CSV and XLS on the Web)](docs/backend/dataproxy.html) * [gdocs: Google Docs (Spreadsheet) Backend](docs/backend/gdocs.html) @@ -63,7 +58,7 @@ Backend not on this list that you would like to see? It's very easy to write a n ## Preparing your app -This is as per the [quickstart](example-quickstart.html) but the set of files is much more limited if you are just using a Backend. Specifically: +This is as per the [quickstart](tutorial-views.html) but the set of files is much more limited if you are just using a Backend. Specifically: {% highlight html %} @@ -71,8 +66,6 @@ This is as per the [quickstart](example-quickstart.html) but the set of files is - - @@ -110,5 +103,5 @@ a bespoke chooser and a Kartograph (svg-only) map. ## Writing your own backend Writing your own backend is easy to do. Details of the required API are in the -[Backend documentation](docs/backend/base.html). +[Backend documentation](docs/backends.html). diff --git a/docs/tutorial-basics.markdown b/docs/tutorial-basics.markdown new file mode 100644 index 00000000..2705c814 --- /dev/null +++ b/docs/tutorial-basics.markdown @@ -0,0 +1,170 @@ +--- +layout: container +title: Tutorial - Dataset Basics +recline-deps: true +root: ../ +--- + + + +## Preparations + +1. [Download ReclineJS]({{page.root}}download.html) and relevant dependencies. + +2. Include the core dependencies for the Dataset model + + {% highlight html %} + + + + +{% endhighlight %} + +## Creating a Dataset + +Here's the example data We are going to work with: + +{% highlight javascript %} +{% include data.js %} +{% endhighlight %} + +In this data we have 6 records / rows. Each record is a javascript object +containing keys and values (values can be 'simple' e.g. a string or float or arrays or hashes - e.g. the geo value here). + + + +We can now create a recline Dataset object from this raw data: + +{% highlight javascript %} +var dataset = new recline.Model.Dataset({ + records: data +}); +{% endhighlight %} + + + +## Records, Fields and more + +Now that we have created a Dataset, we can use it. + +For example, let's display some information about the Dataset and its records: + +
You can find out more about Dataset and Records in the reference documentation
+ +{% highlight javascript %} +{% include tutorial-basics-ex-1.js %} +{% endhighlight %} + +Here's the output: + +
 
+ + + +Note how the last geo attribute just rendered as `[object Object]`. This is because the Dataset is treating that field value as a string. Let's now take a look at the Dataset fields in more detail. + +### Fields + +In addition to Records, a Dataset has Fields stored in the `fields` attribute. Fields provide information about the fields/columns in the Dataset, for example their id (key name in record), label, type etc. + +The Dataset's fields will be automatically computed from records or provided by the backend but they can also be explicitly provided and configured. Let's take a look at the fields on the dataset at present using the following code: + +{% highlight javascript %} +{% include tutorial-basics-ex-fields.js %} +{% endhighlight %} + +Running this results in the following: + +
 
+ + + +As can be seen all fields have the default type of 'string'. Let's change the geo field to have type geo\_point and see what affect that has on displaying of the dataset (for good measure we'll also set the label): + +{% highlight javascript %} +{% include tutorial-basics-ex-fields-2.js %} +{% endhighlight %} + +
 
+ + + +As can be seen the rendering of the field has changed. This is because the `recordSummary` method uses the Record.getFieldValue function which in turn renders a record field using the Field's renderer function. This function varies depending on the type and can also be customized (see the Field documentation). + + +## Querying + +The basic thing we want to do with Datasets is query and filter them. This is very easy to do: + +{% highlight javascript %} +{% include tutorial-basics-ex-2.js %} +{% endhighlight %} + +This results in the following. Note how recordCount is now 3 (the total number of records matched by the query) but that currentRecords only contains 2 records as we restricted number of returned records using the size attribute. + +
 
+ + + +Full details of the query structure and its options can be found in the reference documentation. + +Also worth noting is that the last run query is stored as a Query instance in the `queryState` attribute of the Dataset object. Modifying `queryState` will also resulting in a query being run. This is useful when building views that want to display or manage the query state (see, for example, Query Editor or Filter Editor widgets). + + +## Listening for Events + +Often you'll want to listen to events on Datasets and its associated objects rather than have to explicitly notify. This is easy to do thanks to the use of Backbone model objects which have a [standard set of events](http://backbonejs.org/#FAQ-events). + +Here's an example to illustrate: + +{% highlight javascript %} +{% include tutorial-basics-ex-events.js %} +{% endhighlight %} + +
 
+ + + +Here's a summary of the main objects and their events: + +* Dataset: + + * Standard Backbone events for changes to attributes (note that this will **not** include changes to records) + * *query:start / query:end* called at start and completion of a query + +* Dataset.currentRecords: Backbone.Collection of "current" records (i.e. those resulting from latest query) with standard Backbone set of events: *add, reset, remove* + +* Dataset.queryState: queryState is a Query object with standard Backbone Model set of events + +* Dataset.fields: Backbone Collection of Fields. + diff --git a/example-quickstart.markdown b/docs/tutorial-views.markdown similarity index 70% rename from example-quickstart.markdown rename to docs/tutorial-views.markdown index 2e470e50..7e22f018 100644 --- a/example-quickstart.markdown +++ b/docs/tutorial-views.markdown @@ -2,13 +2,14 @@ layout: container title: Library - Example - Quickstart recline-deps: true +root: ../ --- @@ -16,7 +17,7 @@ recline-deps: true Before writing any code with Recline, you need to do the following preparation steps on your page: -1. [Download ReclineJS](download.html) and relevant dependencies. +1. [Download ReclineJS]({{page.root}}download.html) and relevant dependencies. 2. Include the relevant CSS in the head section of your document: {% highlight html %} @@ -33,16 +34,11 @@ Before writing any code with Recline, you need to do the following preparation s {% endhighlight %} -4. Create a div to hold the Recline view(s): - {% highlight html %} -
{% endhighlight %} - You're now ready to start working with Recline. ### Creating a Dataset @@ -60,37 +56,62 @@ no reason you cannot have objects as values allowing you to nest data. We can now create a recline Dataset object (and memory backend) from this raw data: {% highlight javascript %} -var dataset = recline.Backend.Memory.createDataset(data); +var dataset = new recline.Model.Dataset({ + records: data +}); {% endhighlight %} -Note that behind the scenes Recline will create a Memory backend for this dataset as in Recline every dataset object must have a backend from which it can push and pull data. In the case of in-memory data this is a little artificial since all the data is available locally but this makes more sense for situations where one is connecting to a remote data source (and one which may contain a lot of data). - ### Setting up the Grid -Let's create a data grid view to display the dataset we have just created, binding the view to the `
` we created earlier: + +Let's create a data grid view to display the dataset we have just created. We're going to use the SlickGrid-based grid so we need the following: + +{% highlight html %} + + + + + + + + + +{% endhighlight %} + +Now, let's create an HTML element to for the Grid: + +{% highlight html %} +
+{% endhighlight %} + +Now let's set up the Grid: {% highlight javascript %} var $el = $('#mygrid'); -var grid = new recline.View.Grid({ - model: dataset +var grid = new recline.View.SlickGrid({ + model: dataset, + el: $el }); -$el.append(grid.el); +grid.visible = true; grid.render(); {% endhighlight %} And hey presto: -
 
+
 
@@ -106,7 +127,7 @@ library and the Recline Graph view: - + {% endhighlight %} Next, create a new div for the graph: @@ -115,35 +136,15 @@ Next, create a new div for the graph:
{% endhighlight %} -Now let's create the graph, we will use the same dataset we had earlier: +Now let's create the graph, we will use the same dataset we had earlier, and we will need to set the view 'state' in order to configure the graph with the column to use for the x-axis ("group") and the columns to use for the series to show ("series"). -{% highlight javascript %} -var $el = $('#mygraph'); -var graph = new recline.View.Graph({ - model: dataset -}); -$el.append(grid.el); -graph.render(); -{% endhighlight %} - -And ... we have a graph view -- with instructions on how to use the controls to -create a graph -- but no graph. Go ahead and play around with the controls to -create a graph of your choosing: - -
 
- - - -But suppose you wanted to create a graph not a graph editor. This is -straightforward to do -- all we need to do is set the 'state' of the graph -view: +
+State: The concept of a state is a common feature of Recline views being an object +which stores information about the state and configuration of a given view. You +can read more about it in the general Views +documentation as well as the documentation of individual views such as the +Graph View. +
{% highlight javascript %} var $el = $('#mygraph'); @@ -158,12 +159,12 @@ $el.append(graph.el); graph.redraw(); {% endhighlight %} -We would get this rendered graph: +The result is the following graph: -
 
+
 
-
-State: The concept of a state is a common feature of Recline views being an object -which stores information about the state and configuration of a given view. You -can read more about it in the general Views -documentation as well as the documentation of individual views such as the -Graph View. -
- ### Creating a Map Now, let's create a map of this dataset using the lon/lat information which is diff --git a/download.markdown b/download.markdown index fd8d381c..412715b5 100644 --- a/download.markdown +++ b/download.markdown @@ -9,9 +9,10 @@ title: Download
-Besides the library itself, the download package contains full source code, -unit tests, files for debugging and a build system. The production files -(included the same way as in the code above) are in the dist folder. +Besides the library itself, the download package contains full source +code, unit tests, external vendor libraries and documentation. The +production files (included the same way as in the code above) are in the +dist folder.

Download Recline v0.5 (master) (in-progress version)

diff --git a/src/backend.dataproxy.js b/src/backend.dataproxy.js index ac3eeab3..58f537d7 100644 --- a/src/backend.dataproxy.js +++ b/src/backend.dataproxy.js @@ -6,6 +6,9 @@ this.recline.Backend.DataProxy = this.recline.Backend.DataProxy || {}; my.__type__ = 'dataproxy'; // URL for the dataproxy my.dataproxy_url = 'http://jsonpdataproxy.appspot.com'; + // Timeout for dataproxy (after this time if no response we error) + // Needed because use JSONP so do not receive e.g. 500 errors + my.timeout = 5000; // ## load // @@ -48,12 +51,11 @@ this.recline.Backend.DataProxy = this.recline.Backend.DataProxy || {}; // a crude way to catch those errors. var _wrapInTimeout = function(ourFunction) { var dfd = $.Deferred(); - var timeout = 5000; var timer = setTimeout(function() { dfd.reject({ - message: 'Request Error: Backend did not respond after ' + (timeout / 1000) + ' seconds' + message: 'Request Error: Backend did not respond after ' + (my.timeout / 1000) + ' seconds' }); - }, timeout); + }, my.timeout); ourFunction.done(function(arguments) { clearTimeout(timer); dfd.resolve(arguments); diff --git a/src/model.js b/src/model.js index 50721278..1651559d 100644 --- a/src/model.js +++ b/src/model.js @@ -27,7 +27,7 @@ my.Dataset = Backbone.Model.extend({ creates: [] }; this.facets = new my.FacetList(); - this.docCount = null; + this.recordCount = null; this.queryState = new my.Query(); this.queryState.bind('change', this.query); this.queryState.bind('facet:add', this.query); @@ -178,7 +178,7 @@ my.Dataset = Backbone.Model.extend({ this.trigger('query:start'); if (queryObj) { - this.queryState.set(queryObj); + this.queryState.set(queryObj, {silent: true}); } var actualQuery = this.queryState.toJSON(); @@ -197,7 +197,7 @@ my.Dataset = Backbone.Model.extend({ _handleQueryResult: function(queryResult) { var self = this; - self.docCount = queryResult.total; + self.recordCount = queryResult.total; var docs = _.map(queryResult.hits, function(hit) { var _doc = new my.Record(hit); _doc.bind('change', function(doc) { @@ -220,11 +220,13 @@ my.Dataset = Backbone.Model.extend({ toTemplateJSON: function() { var data = this.toJSON(); - data.docCount = this.docCount; + data.recordCount = this.recordCount; data.fields = this.fields.toJSON(); return data; }, + // ### getFieldsSummary + // // Get a summary for each field in the form of a `Facet`. // // @return null as this is async function. Provides deferred/promise interface. @@ -250,6 +252,19 @@ my.Dataset = Backbone.Model.extend({ return dfd.promise(); }, + // ### recordSummary + // + // Get a simple html summary of a Dataset record in form of key/value list + recordSummary: function(record) { + var html = ''; + this.fields.each(function(field) { + if (field.id != 'id') { + html += '
' + field.get('label') + ': ' + record.getFieldValue(field) + '
'; + } + }); + return html; + }, + // ### _backendFromString(backendString) // // See backend argument to initialize for details @@ -344,16 +359,6 @@ my.Record = Backbone.Model.extend({ return val; }, - summary: function(fields) { - var html = ''; - for (key in this.attributes) { - if (key != 'id') { - html += '
' + key + ': '+ this.attributes[key] + '
'; - } - } - return html; - }, - // Override Backbone save, fetch and destroy so they do nothing // Instead, Dataset object that created this Record should take care of // handling these changes (discovery will occur via event notifications) @@ -404,6 +409,9 @@ my.Field = Backbone.Model.extend({ object: function(val, field, doc) { return JSON.stringify(val); }, + geo_point: function(val, field, doc) { + return JSON.stringify(val); + }, 'float': function(val, field, doc) { var format = field.get('format'); if (format === 'percentage') { diff --git a/src/view.map.js b/src/view.map.js index daa27f96..143a935f 100644 --- a/src/view.map.js +++ b/src/view.map.js @@ -35,7 +35,7 @@ my.Map = Backbone.View.extend({ // If not found, the user will need to define the fields via the editor. latitudeFieldNames: ['lat','latitude'], longitudeFieldNames: ['lon','longitude'], - geometryFieldNames: ['geojson', 'geom','the_geom','geometry','spatial','location'], + geometryFieldNames: ['geojson', 'geom','the_geom','geometry','spatial','location', 'geo', 'lonlat'], initialize: function(options) { var self = this; diff --git a/src/view.multiview.js b/src/view.multiview.js index ccadc046..3168689b 100644 --- a/src/view.multiview.js +++ b/src/view.multiview.js @@ -83,7 +83,7 @@ my.MultiView = Backbone.View.extend({ \ \
\ - {{docCount}} records\ + {{recordCount}} records\
\