Contributed Modules

This is a space for contributed modules related to RESTful web services to put their documentation.

Feeds JSONPath Parser

1) Identify the json URL, and look at it using this tool: http://jsonviewer.stack.hu/ (or, if you know the json well, identify what you want to import.

2) Download jsonpath php file here: https://code.google.com/archive/p/jsonpath/downloads (jsonpath-0.8.1.php) and place inside sites/all/modules/feeds_jsonpath_parser

3) Create a new parser using feeds, with the jsonpath parser selected

4) Example json:


{
  "tumblelog": {
    "title": "Tumblr Blog",
    ..... (other global fields)
  },
  "posts": [
    {
      "id": "46252144726",
      "url": "http://whatever.com",
      "type": "regular",
      "date": "Mon, 25 Mar 2013 10:45:38",
      "regular-title": "Test Blog Entry",
      "regular-body": "Body text goes here",
      "tags": [
        "tag1",
        "tag2",
      ]
    },
   {
      "id": 46249331035,
.... rest of posts

OK, so now is where I'm getting unclear, and need help.

5) In the jsonpath parser settings page:admin/structure/feeds/rss_feed_importer/settings/FeedsJSONPathParser there are two elements, "Context" and "Title". In the Context field, if you want to map the variables in post, to fields in a blog content type, for example, you need to let jsonpath parser know where to start. So in this case, the context would be:

$.tumblelog.posts.*

RESTful Web Services

RESTWS exposes Drupal resources (e.g. entities) as RESTful web services. The module makes use of the Entity API and the information about entity properties (provided via hook_entity_property_info()) to provide resource representations.

It aims to be fully compliant to the REST principles.

Installing the Module

  • Copy the whole restws directory to your modules directory (e.g. DRUPAL_ROOT/sites/all/modules) and activate the RESTful Web Services module.
  • Use Drush commands: drush dl restws & drush en restws
  • There is no user interface to configure.

Usage / Testing

To obtain the JSON representation of an entity use your browser to visit: http://example.com/<entity type name>/<entity id>.json
For example: http://example.com/node/1.json or http://example.com/user/1.json would resolve as a JSON dump to client. There are no "service endpoints" to configure as resources are just available at uniform paths like "node/1", "user/1". One can use a client in the form of a browser plugin to test out the different CRUD functions.

Permissions

Views GeoJSON Example Use Case

In this example use case, Druplicon the blogger travels around the world and blogs about the awesome stuff he encounters on his travels.

What's Views GeoJSON for?

Druplicon's blog-site will collect location information for each post. Views GeoJSON allows using Views to provide a GeoJSON feed of this locative data that can be added to a map, or that another site can collect (maybe with the Feeds module) and utilize.

Setting up Views GeoJSON

Download and install Views GeoJSON.

In this example we'll use Geofield to store geospatial data. We could do so as well with the Location module, or via any content type that maintains latitude & longitude or WKT data.

  • Add a geofield to a content type, in this example basic page
  • Geofield depends on geoPHP

Pages

Subscribe with RSS Subscribe to RSS - json