Savon WSDL client for WOS SOAP API

[dazza-codes]

Fix #186

This explores using the ruby savon gem for SOAP.

• it can authenticate to the new SOAP API for Web of Science
• it initializes a search SOAP client

Use in rails c

[2] pry(main)> wos = WosClient.new(Settings.WOS.AUTH_CODE);
I, [2017-09-27T08:58:32.938193 #12354]  INFO -- : SOAP request: http://search.webofknowledge.com/esti/wokmws/ws/WOKMWSAuthenticate
I, [2017-09-27T08:58:32.938383 #12354]  INFO -- : Authorization: Basic {{SECRET_SNIPPED}}, SOAPAction: , Content-Type: text/xml;charset=UTF-8, Content-Length: 397
I, [2017-09-27T08:58:33.238701 #12354]  INFO -- : SOAP response (status 200)
[3] pry(main)> wos.session_id
=> "1F28d8jTIRdrY9Oi4aF"
[4] pry(main)> wos.auth.class
=> Savon::Client
[5] pry(main)> wos.search.class
=> Savon::Client
[6] pry(main)> wos.search.operations
=> [:cited_references_retrieve, :related_records, :cited_references, :retrieve, :search, :citing_articles, :retrieve_by_id]
[7] pry(main)> wos.auth.operations
=> [:authenticate, :close_session]

I use this with a config/settings.local.yml file that contains the actual auth-token.

TODO:

• specs on the WosClient.search functionality (see Web of Science queries #223)

Related issues:

• Analysis of work required to use new ScienceWire API #171

[dazza-codes]

My only thoughts on enhancing this client are around how to close the session automatically when the object is detroyed (so it doesn’t leave open sessions dangling). The problem can be pushed up to consumers to explicitly call the close_session. There are some patterns for auto-closing stuff that generally work with class methods, like File.open can take a block and then do stuff after the yield is done to clean up file handlers. I’ll put this commentary in a tech-debt issue, it could be addressed later.

[atz]

Don't need this line because it is done in the .rspec file.