Share object persists Share is a temporary metadata object that persists the state of the application when using the Share function.
This function is available by clicking the Menu button () in the top left of the map window, and selecting Share. The state of the application (including all dashboard settings, filters, map position, visualizations and much more) is persisted and a link is generated. After clicking this link, anyone with access to the project will be able to recover the saved application state and see the exact view as the creator of the share link. The link looks like this:
...
language | text |
---|---|
title | Share link example |
How Share MD objects differ from other MD object types
Share MD object is a temporary object which is valid only until any change in correspondent metadata hierarchy is made and after that is invalidated and deleted. For more details refer to Shares invalidation section of this article.
Share MD objects can be considered internal i.e. these MD objects themselves are not exposed to a user in any way and are only used internally for computing shared versions of MD objects such as view, dashboards, etc
Share MD objects cannot be created, retrieved, modified or deleted using REST API for standard CRUD operations
Share MD objects cannot be dumped from a project using CleverMaps Shell
Life cycle of Share metadata objects
Creating shares
This function is available by clicking the Menu button () in the top left of the map window, and selecting Share. The state of the application (including all dashboard settings, filters, map position, visualizations and much more) is persisted and a link is generated. After clicking this link, anyone with access to the project will be able to recover the saved application state and see the exact view as the creator of the share link. The link looks like this:
Share link example
Code Block | ||
---|---|---|
| ||
https://secure.clevermaps.io/#/yufqzxkbiecj7jot/map/catchment_area_view?shareId=exb9g8wi9606ziyk |
It's a link to a specific view in a specific CleverMaps project, followed by the ?shareId={shareId}
parameter, which contains the ID of the share - exb9g8wi9606ziyk
.
Each shared link can consist of 5 share objects, which extend these share link can reference multiple Share MD objects with the same shareId
. Each of these Share MD objects represents persisted state of a single MD object of one of these MD object types:
Please note that there NOTES:
There can be more than one indicator
...
and more than one indicator drill. Or there can be no indicator or no dashboard. This depends on the settings of your dashboard
...
Syntax
This is a share object applied on catchment_area_view
view of the Retail Solution Demo. The diff array contains these changes:
- it adds default values of (
histogram
) filter at 10th position to 50 and 90 - it sets the map window center to 52.42325659892287,-1.9569396972656254 and zoom to level 12
- it adds the default visualization setting -
areas
- it adds the default compare type setting -
dominance
- it sets the default compare type to dominance
- it sets default spatial query to settings
- it adds default measure type -
isoline
- it sets the
defaultSelected
property to the feature with id "6" from datasetshops
All these properties and paths are described in detail in the Views article.
...
title | Share object syntax |
---|
...
View
MD object is the main MD object from which all subordinate MD objects (which are subjects to sharing) are referenced by (directly or associatively, refer to this article for details of MD objects hierarchy). This relation is used for determining whether share link is still valid; if a Share MD object exists for the view then the share link is valid, otherwise the share link is not valid. Following are the rules for creating and using share links which are the result of this design:When creating a new share link
Share MD object must always be created for a
View
even though there would be no difference between original and shared viewShare MD object does not have to be created for MD object types other than
View
if there would be no difference between original and shared MD object
When opening a share link
in case of
View
when Share MD object exists for a
View
then shared version of given view is returned from REST APIwhen Share MD object does not exist for a
View
then an error (404) is returned from REST API
in case of MD object types other than
View
when Share MD object exists for MD object then shared version of given MD object is returned from REST API
when Share MD object does not exist for MD object then given MD object without any modifications is returned from REST API
Shares invalidation
A state of the application persisted using a share link is defined by configuration of View
MD object and all subordinate MD objects referenced by it (directly or associatively) except for MD objects of types Dataset
and Export
, namely:
(Refer to this article for details of MD objects hierarchy.)
That being said a share link must be invalidated and all relevant Share MD objects must be deleted in case of any change (update or delete) of any MD object in the View
hierarchy which is of one of MD object types listed above. This happens automatically in MD service when request for updating of deleting for such MD object is made.
Shares REST API
Share MD objects are stored in MD service but cannot be created, retrieved, updated nor deleted directly via REST API. Creating of Share MD objects is done using endpoints for updating individual MD object types while providing shareId
request parameter. Getting of shared versions for MD objects is done using endpoints for getting individual MD object types while providing shareId
request parameter.
Code Block | ||||
---|---|---|---|---|
### Create a Share [PUT /rest/projects/{projectId}/md/{mdObjectType}/{mdObjectId}?shareId={shareId}] Creates a new Share MD object for given MD object which represents its state in the moment of creation of the Share MD object. #### Response statuses * 200 - OK * 403 - Forbidden * 404 - Not Found + Parameters + projectId: `vb2b3d8v91jao331` (string) - ID of an actual project + mdObjectType: `view` (string) - Type of MD object to create share for + mdObjectId: `o31q6691gdtj3vng` - ID of MD object to create share for + shareId: `m1nfjgsglwlcxvlf` - ID of Share MD object to be created + Request + Headers Accept: "itemId": "ee2069d8ebd36700690adbf9875111f1"application/json Authorization: Bearer {{accessToken},} { + Body "op": "replace", "path": "/content/mapOptions/center/lat", { "value": 52.42325659892287 "id": "td9uijp62o8sa27b", }, { "name": "catchment_area_view", "optype": "replaceview", "pathtitle": "/content/mapOptions/center/lngCatchment Area Analysis", "valuedescription": -1.9569396972656254 }, { "op": "replace","Identify areas with the biggest and smallest shares of your customers. Find out what turnover these customers generate. Evaluate store rankings and identify the pick-up partners used by customers from different regions. You can also compare the catchment areas for two different stores.", "pathcontent": "/content/mapOptions/zoom",{ "valueicon": 12"performance_method", }, "order": 1, { "opdashboard": "add",/rest/projects/qkn86k5upo4m9b27/md/dashboards?name=catchment_area_dashboard", "pathmarkerSelector": "/content/defaultVisualizationrest/projects/qkn86k5upo4m9b27/md/markerSelectors?name=shops_marker_selector", "valuedefaultGranularity": "areas"/rest/projects/qkn86k5upo4m9b27/md/datasets?name=ward", }, "defaultVisualization": "areas", { "opdefaultCompareType": "adddominance", "path": "/content/defaultCompareType", "defaultSelected": { "value": "dominance" }, "dataset": "/rest/projects/$projectId/md/datasets?name=shops", { "opids": "add",[ "path": "/content/spatialQuery/profile", 6 "value": "air" }, ] { "op": "add" }, "path": "/content/spatialQuery/unit", "value"filterGroup": [ "distance" }, { "op": "add", "pathtype": "/content/spatialQuery/amountglobalDate", "value": 500 }"property": "baskets.date_iso", { "opdefaultValues": "add",{ "path": "/content/measure/type", "valuestartDate": "isoline"{ }, { "op""value": "add2019-02-03", "path": "/content/defaultSelected/dataset", "value": "/rest/projects/$projectId/md/datasets?name=shops"}, }, { "endDate": { "op": "add", "path": "/content/defaultSelected/ids/0", "value": "62019-02-09" } ], "breakingChanges": [], } "forcedRebaseCount": 0 } } | ||||
Code Block | ||||
| ||||
{ "url": "/rest/projects/yufqzxkbiecj7jot/md/shares/m1nfjgsglwlcxvlf", "dumpTime": "2020-12-08T08:06:10Z", } "version": "1", "content": { "id": "m1nfjgsglwlcxvlf", "name": "catchment_area_view_m1nfjgsglwlcxvlf",}, "type": "share", "content": { { "shareId": "m1nfjgsglwlcxvlf", "objectId": "o31q6691gdtj3vng", "objectNametype": "catchment_area_viewhistogram", "diff": [ {"property": "baskets.amount", "op": "add", "format": { "path": "/content/filterGroup/10/defaultValues/values/0", "valuetype": 50"number", "itemId": "d13d5b44990292a6c1b051c018410053" "fraction": }0, { "opsymbol": "add£", "path": "/content/filterGroup/10/defaultValues/values/1", }, "value": 900, "itemIddefaultValues": "ee2069d8ebd36700690adbf9875111f1"{ }, { "values": [ "op": "replace", "path": "/content/mapOptions/center/lat"100.0, "value": 52.42325659892287 },500.0 { ], "op": "replace", "path": "/content/mapOptions/center/lng", "value"nullFiltered": -1.9569396972656254true }, } { "op": "replace" }, "path": "/content/mapOptions/zoom", { "value": 12 "type": "multiSelect", }, { "property": "baskets.on_off_name", "op": "add", "pathorderBy": "/content/defaultVisualization",[ "value": "areas" { }, { "opproperty": "addbaskets.on_off_name", "path": "/content/defaultCompareType", "valuedirection": "dominanceasc" }, { } "op": "add", ] "path": "/content/spatialQuery/profile", }, "value": "air" }, { { "optype": "addmultiSelect", "path "property": "/content/spatialQuery/unitbaskets.courier", "value": "distance" "orderBy": [ }, { { "op": "add", "pathproperty": "/content/spatialQuery/amountbaskets.courier", "value": 500 }, "direction": "asc" { } "op": "add", "path": "/content/measure/type", ] "value": "isoline" }, { { "op": "add", "pathtype": "/content/defaultSelected/datasetmultiSelect", "value "property": "/rest/projects/$projectId/md/datasets?name=shops"clients.sex_name", }, "orderBy": [ { "op": "add", { "path": "/content/defaultSelected/ids/0", "valueproperty": "6clients.sex_name", } ], "breakingChanges": [],"direction": "asc" "forcedRebaseCount": 0 }, "accessInfo": { } "createdAt": "2020-12-07T15:35:51Z", ] "createdBy": "/rest/accounts/00ubfu7fdyIoFKxXm0h7" }, "links": [ { { "rel": "self", "hreftype": "/rest/projects/yufqzxkbiecj7jot/md/shares/m1nfjgsglwlcxvlf"multiSelect", } ] } } |
Additional syntax examples
Code Block | ||||
---|---|---|---|---|
| ||||
{ "property": "clients.age_name", "id": "exb9g8wi9606ziyk", "name": "turnover_indicator_drill_on_exb9g8wi9606ziyk", "type": "share", "content": { "shareIdorderBy": "exb9g8wi9606ziyk",[ "objectId": "iir539klh29s9mvo", "objectName": "turnover_indicator_drill_on", "diff": [ { { "op": "add", "pathproperty": "/content/blocks/3/visualizedclients.age_cat", "value": false, "itemIddirection": "9403698a1ed0cc2e55fcc27762faa1a3"asc" }, } { "op": "add", ] "path": "/content/blocks/3/displayValues/0/Offline", "value": "Offline", }, "itemId": "9403698a1ed0cc2e55fcc27762faa1a3" { }, { "optype": "addmultiSelect", "path": "/content/blocks/4/visualized", "valueproperty": false"dim_dates_day_of_week.day_of_week_name_en", "itemId": "ccf504abece40ed0bbe992f4931ddae3" }, "orderBy": [ { "op": "add", { "path": "/content/blocks/5/visualized", "value": false, "itemId"property": "d13d5b44990292a6c1b051c018410053"dim_dates_day_of_week.order_en", }, { "op": "add","direction": "asc" } "path": "/content/blocks/6/visualized", "value": false, ] "itemId": "8d053723cb9372574ceeae9bd0c360ba" }, ], "breakingChanges": [], { "forcedRebaseCount": 0 } } |
This share object is applied on indicator drill. You can see it contains explicit disabled visalization of drill blocks. But mainly, for block 3 (categories
) there is an displayValues
setting which means we selected "Offline" category from the block.
Code Block | ||||
---|---|---|---|---|
| ||||
{ "id": "exb9g8wi9606ziyk", "name": "shops_marker_selector_exb9g8wi9606ziyk", "type": "shareindicator", "content": { "shareId": "exb9g8wi9606ziyk", "objectId": "nl3porml3fmg4o0a", "objectNameindicator": "shops_marker_selector",/rest/projects/qkn86k5upo4m9b27/md/indicators?name=turnover_indicator" "diff": [ { }, "op": "add", { "path": "/content/keepFiltered/granularity", "value": false "type": },"indicator", { "opindicator": "add",/rest/projects/qkn86k5upo4m9b27/md/indicators?name=customers_indicator" "path": "/content/keepFiltered/markers", }, "value": true }, { { "op "type": "addindicator", "path "indicator": "/content/showIndicatorValuesOnMap",/rest/projects/qkn86k5upo4m9b27/md/indicators?name=purchases_customer_indicator" "value": false } }, { ], "op": "add", "mapOptions": { "path": "/content/clusterMarkers", "valuecenter": false{ } ], "breakingChangeslat": []52.42325659892287, "forcedRebaseCount": 0 } } |
This share object is applied on marker selector. You can see it contains three marker selector settings - keepFiltered
, showIndicatorValuesOnMap
and clusterMarkers
set to false.
Key description
content
...
Status | ||||
---|---|---|---|---|
|
...
id of the share (present in share link)
...
Status | ||||
---|---|---|---|---|
|
...
id of metadata object on which the share is applied
...
Status | ||||
---|---|---|---|---|
|
...
diff
...
Status | ||||
---|---|---|---|---|
|
...
Status | ||||
---|---|---|---|---|
|
...
Status | ||||
---|---|---|---|---|
|
...
content.diff
content.breakingChanges
Each diff
and breakingChanges
array element follows the JSON Patch standard.
...
Status | ||||
---|---|---|---|---|
|
...
type of the operation
...
Status | ||||
---|---|---|---|---|
|
...
string
integer
number
boolean
...
Status | ||||
---|---|---|---|---|
|
...
value applied to the path
value
is polymorphic - it can be of any type available in the JSON standard
...
Status | ||||
---|---|---|---|---|
|
...
Generated ID for an item from the most outer array in the path - itemId
is used while rebasing share diffs to match existent diffs with corresponding items within master metadata object content which might have been reordered within arrays after metadata object update.
e.g. for path /content/filterGroup/10/defaultValues/values/0
the itemId
is generated for the item at path /content/filterGroup/10
There are cases when item for which diff is applied does not exists in master metadata object (only in shared metadata object) - in such cases itemId attribute is not present in share diff as it is not supposed to match anything in the master metadata object.
IMPORTANT: itemId
is not supposed to be modified manually via REST API.
NOTE: Mechanism described above does not cover all the cases, for example reordering items within a nested array currently produces breaking changes - the implementation is likely to improve in the future to store item IDs in share diff for items within all arrays in the path (the most outer and nested arrays instead of just the most outer one).
...
"lng": -1.9569396972656254
},
"zoom": 12,
"minZoom": 0,
"maxZoom": 18,
"tileLayer": "mapbox"
},
"exports": [
{
"export": "/rest/projects/qkn86k5upo4m9b27/md/exports?name=administrative_units_export"
},
{
"export": "/rest/projects/qkn86k5upo4m9b27/md/exports?name=customer_ids_export"
},
{
"export": "/rest/projects/qkn86k5upo4m9b27/md/exports?name=transaction_ids_export"
},
{
"export": "/rest/projects/qkn86k5upo4m9b27/md/exports?name=grid_export"
}
],
"excludeDatasets": [
"gb2_district",
"gb2_ward",
"gb2_postcodes_dwh",
"gb2_msoas_dwh",
"gb2_lsoas_dwh",
"postcodes_dwh"
],
"spatialQuery": {
"profile": "air",
"unit": "distance",
"amount": 500
},
"measure": {
"type": "isoline"
}
},
"accessInfo": {
"createdAt": "2019-03-21T11:37:55Z",
"modifiedAt": "2020-04-27T12:00:43Z",
"createdBy": "/rest/accounts/00ufp0zalagOjXrmb0h7",
"modifiedBy": "/rest/accounts/00ufp0zalagOjXrmb0h7"
},
"version": 13,
"links": [
{
"rel": "self",
"href": "/rest/projects/qkn86k5upo4m9b27/md/views/td9uijp62o8sa27b"
}
]
}
+ Response 200 (application/json)
{
"id": "m1nfjgsglwlcxvlf",
"name": "catchment_area_view_m1nfjgsglwlcxvlf",
"type": "share",
"content": {
"shareId": "m1nfjgsglwlcxvlf",
"objectId": "o31q6691gdtj3vng",
"objectName": "catchment_area_view",
"diff": [
{
"op": "add",
"path": "/content/filterGroup/1/defaultValues",
"value": {
"values": [
100,
500
],
"nullFiltered": true
}
},
{
"op": "replace",
"path": "/content/mapOptions/center/lat",
"value": 52.42325659892287
},
{
"op": "replace",
"path": "/content/mapOptions/center/lng",
"value": -1.9569396972656254
},
{
"op": "replace",
"path": "/content/mapOptions/zoom",
"value": 12
},
{
"op": "add",
"path": "/content/defaultVisualization",
"value": "areas"
},
{
"op": "add",
"path": "/content/defaultCompareType",
"value": "dominance"
},
{
"op": "add",
"path": "/content/spatialQuery",
"value": {
"profile": "air",
"unit": "distance",
"amount": 500
}
},
{
"op": "add",
"path": "/content/measure",
"value": {
"type": "isoline"
}
},
{
"op": "add",
"path": "/content/defaultSelected",
"value": {
"dataset": "/rest/projects/$projectId/md/datasets?name=shops",
"ids": [
"6"
]
}
}
]
}
}
### Get shared version for MD object [GET /rest/projects/{projectId}/md/{mdObjectType}/{mdObjectId}?shareId={shareId}]
Computes and returns share version for given MD object by share ID.
#### Response statuses
* 200 - OK
* 404 - Not Found
+ Parameters
+ projectId: `vb2b3d8v91jao331` (string) - ID of an actual project
+ mdObjectType: `view` (string) - Type of MD object to compute and get shared version for
+ mdObjectId: `o31q6691gdtj3vng` - ID of MD object to compute and get shared version for
+ shareId: `m1nfjgsglwlcxvlf` - ID of Share MD object use for computing shared version for MD object
+ Request
+ Headers
Accept: application/json
Authorization: Bearer {{accessToken}}
+ Response 200 (application/json)
{
"id": "m1nfjgsglwlcxvlf",
"name": "catchment_area_view_m1nfjgsglwlcxvlf",
"type": "share",
"content": {
"shareId": "m1nfjgsglwlcxvlf",
"objectId": "o31q6691gdtj3vng",
"objectName": "catchment_area_view",
"diff": [
{
"op": "add",
"path": "/content/filterGroup/1/defaultValues",
"value": {
"values": [
100,
500
],
"nullFiltered": true
}
},
{
"op": "replace",
"path": "/content/mapOptions/center/lat",
"value": 52.42325659892287
},
{
"op": "replace",
"path": "/content/mapOptions/center/lng",
"value": -1.9569396972656254
},
{
"op": "replace",
"path": "/content/mapOptions/zoom",
"value": 12
},
{
"op": "add",
"path": "/content/defaultVisualization",
"value": "areas"
},
{
"op": "add",
"path": "/content/defaultCompareType",
"value": "dominance"
},
{
"op": "add",
"path": "/content/spatialQuery",
"value": {
"profile": "air",
"unit": "distance",
"amount": 500
}
},
{
"op": "add",
"path": "/content/measure",
"value": {
"type": "isoline"
}
},
{
"op": "add",
"path": "/content/defaultSelected",
"value": {
"dataset": "/rest/projects/$projectId/md/datasets?name=shops",
"ids": [
"6"
]
}
}
]
}
}
|
Syntax
NOTE: As the first section of this article states Share MD objects are internal MD objects and thus are not exposed to a user in any way. That being said following syntax examples serves only as an illustration of how these MD objects look when being created or used by MD service.
This is a share object applied on catchment_area_view
view of the Retail Solution Demo. The diff array contains these changes:
it adds default values of (
histogram
) filter at index 1 to 100 and 500it sets the map window center to 52.42325659892287,-1.9569396972656254 and zoom to level 12
it adds the default visualization setting -
areas
it adds the default compare type setting -
dominance
it sets default spatial query settings
it adds default measure type -
isoline
it sets the
defaultSelected
property to the feature with id "6" from datasetshops
All these properties and paths are described in detail in the Views article.
Share object syntax
Code Block |
---|
{
"id": "m1nfjgsglwlcxvlf",
"name": "catchment_area_view_m1nfjgsglwlcxvlf",
"type": "share",
"content": {
"shareId": "m1nfjgsglwlcxvlf",
"objectId": "o31q6691gdtj3vng",
"objectName": "catchment_area_view",
"diff": [
{
"op": "add",
"path": "/content/filterGroup/1/defaultValues",
"value": {
"values": [
100,
500
],
"nullFiltered": true
}
},
{
"op": "replace",
"path": "/content/mapOptions/center/lat",
"value": 52.42325659892287
},
{
"op": "replace",
"path": "/content/mapOptions/center/lng",
"value": -1.9569396972656254
},
{
"op": "replace",
"path": "/content/mapOptions/zoom",
"value": 12
},
{
"op": "add",
"path": "/content/defaultVisualization",
"value": "areas"
},
{
"op": "add",
"path": "/content/defaultCompareType",
"value": "dominance"
},
{
"op": "add",
"path": "/content/spatialQuery",
"value": {
"profile": "air",
"unit": "distance",
"amount": 500
}
},
{
"op": "add",
"path": "/content/measure",
"value": {
"type": "isoline"
}
},
{
"op": "add",
"path": "/content/defaultSelected",
"value": {
"dataset": "/rest/projects/$projectId/md/datasets?name=shops",
"ids": [
"6"
]
}
}
]
}
} |
Additional syntax examples
Example of a share object on indicator drill
Code Block |
---|
{
"id": "exb9g8wi9606ziyk",
"name": "turnover_indicator_drill_on_exb9g8wi9606ziyk",
"type": "share",
"content": {
"shareId": "exb9g8wi9606ziyk",
"objectId": "iir539klh29s9mvo",
"objectName": "turnover_indicator_drill_on",
"diff": [
{
"op": "add",
"path": "/content/blocks/3/visualized",
"value": false
},
{
"op": "add",
"path": "/content/blocks/3/displayValues",
"value": [
"Offline"
]
},
{
"op": "add",
"path": "/content/blocks/4/visualized",
"value": false
},
{
"op": "add",
"path": "/content/blocks/5/visualized",
"value": false
},
{
"op": "add",
"path": "/content/blocks/6/visualized",
"value": false
}
]
}
} |
This share object is applied on indicator drill. You can see it contains explicit disabled visalization of drill blocks. But mainly, for block 3 (categories
) there is an displayValues
setting which means we selected "Offline" category from the block.
Example of a share object on marker selector
Code Block |
---|
{
"id": "exb9g8wi9606ziyk",
"name": "shops_marker_selector_exb9g8wi9606ziyk",
"type": "share",
"content": {
"shareId": "exb9g8wi9606ziyk",
"objectId": "nl3porml3fmg4o0a",
"objectName": "shops_marker_selector",
"diff": [
{
"op": "add",
"path": "/content/keepFiltered",
"value": {
"granularity": false,
"markers": true
}
},
{
"op": "add",
"path": "/content/showIndicatorValuesOnMap",
"value": false
},
{
"op": "add",
"path": "/content/clusterMarkers",
"value": false
}
]
}
} |
This share object is applied on marker selector. You can see it contains three marker selector settings - keepFiltered
, showIndicatorValuesOnMap
and clusterMarkers
set to false.
Key description
content
Key | Type | Optionality | Description | Constraints | ||||||
---|---|---|---|---|---|---|---|---|---|---|
shareId | string |
| id of the share (present in share link) |
| ||||||
| string |
| id of metadata object on which the share is applied |
| ||||||
objectName | string |
| name of metadata object on which the share is applied |
| ||||||
| array |
| list of changes applied on the metadata object |
content.diff
Each diff
array element follows the JSON Patch standard.
Key | Type | Optionality | Description | Constraints | ||||||
---|---|---|---|---|---|---|---|---|---|---|
| string |
| type of the operation |
| ||||||
| string |
| path in the json on which the operation is applied |
| ||||||
| string integer number boolean |
| value applied to the
|
Visual representation
Shares themselves do not have a visual representation in the application. However, the Share function is available in Menu:
...
Then, a popup window with the generated link is shown:
...