Problem/Motivation

The GSA provides an API for administrative tasks and in particular for handling keymatchs.
Integrating this API in Drupal would allow users (e.g. content editors, support staff, communications) to create/read/update/delete keymatchs from the Drupal interface without granting access to the Admin Console.

Proposed resolution

Setting the credentials could be achieved from the regular settings page.
Keymatchs could show up in a separate tab with 3 sub-pages: one for editing keymatchs, one for viewing them and one for adding them.
Authentication is based on tokens which we could store in the user's session.
Attached is a proposed patch.

Remaining tasks

Review & opinions welcome.

User interface changes

Screenshots attached.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

iamEAP’s picture

This is really fantastic!

I was unable to do an end-to-end test on my end (due to some oddities in how we have our GSA configured within our network), but this looks promising. Full review forthcoming.

fengtan’s picture

FileSize
27.76 KB
2.07 KB
73.68 KB

OK -- it might also be convenient to be able to search for keymatchs rather than just listing them.
Here is a new patch that allows to do that on the 'view' tab. Screenshot attached.

fengtan’s picture

FileSize
50.43 KB

Added support for Related Queries and Onebox modules.
It is possible this could be refactored but the functionality seems to work.

fengtan’s picture

It might also be interesting to integrate Query Suggestions.

mausolos’s picture

How close is this to being added to dev or released with a module version?

iamEAP’s picture

Thanks for the interest, @mausolos. I'm excited to include this featureset, but could use help reviewing and testing @fengtan's patch in #4. Our GSA and Drupal installation are not networked in a way that makes testing this easy.