Pages: [1]
  Print  
Author Topic: Enrich Data by Webservice with HTTP Header  (Read 698 times)
NamSor
Newbie
*
Posts: 12


WWW
« on: April 25, 2014, 03:44:21 PM »

In the tutorial 'RapidMiner to enrich Gender data', the API does not require authentication:
http://namesorts.com/2014/04/23/rapidminer-to-enrich-gender-data/

But (say you would like to use Mashape or some other auth method) how do you specify an API Key HTTP Header in the RapidMiner Webservice operator?

Thanks!
Elian
Logged
JEdward
Full Member
***
Posts: 210


WWW
« Reply #1 on: April 29, 2014, 04:39:25 AM »

If you put the header information in the Request Properties area, that should do the trick. 
Logged

--
RapidMiner China
www.rapidminerchina.com
ighyboo
Newbie
*
Posts: 26


« Reply #2 on: August 27, 2014, 01:13:51 AM »

Has anyone managed to solve this issue?

I found the same/similar question on StackExchange and I wrote a question (specific to mashape) on this forum but no answer yet..
I'm now trying to pass OAuth parameters to the Twitter API but had no luck in passing the right header format despite various different attempts




Logged
ighyboo
Newbie
*
Posts: 26


« Reply #3 on: September 26, 2014, 12:35:24 PM »

Anyone who can help with this? It's driving me crazy!  Angry

HaHaHaHa
Logged
NamSor
Newbie
*
Posts: 12


WWW
« Reply #4 on: June 29, 2015, 06:22:29 PM »

Hi,

You no longer need to worry about HTTP headers, as you can now use NamSor Onomastics Extension (from RapidMiner MarketPlace). Tutorial here
http://blog.namsor.com/2014/09/10/video-tutorial-how-to-extract-the-gender-of-personal-names-using-rapidminer/

There are currently two operators,
Gender : to infer the likely gender of a personal name;
Origin : to infer the likely origin of a personal name.

Best,
Elian
Logged
JEdward
Full Member
***
Posts: 210


WWW
« Reply #5 on: July 23, 2015, 08:37:33 PM »

Looking forward to your talk at RapidMiner world.
Logged

--
RapidMiner China
www.rapidminerchina.com
Pages: [1]
  Print  
 
Jump to: