Configuration for SemanticProxy?

Hey @malukalu, how are things?

To enable SemanticProxy go to the Calais Node Settings, for a particular content type you can turn on SemanticProxy to evaluate either the FeedAPI Original URL (if you use FeedAPI) or to take a URL from any CCK Link or Textfield and use that for submission. If you like you can also save the full text that is returned to another CCK textarea on the same node (this part is totally optional). The short of it is that you have to tell Calais which URL to submit to SemanticProxy. Keep in mind that currently using SP means that no node content itself will be submitted, only the configured URL.

Give that a whirl and let me know how it goes. Good luck.

Thanks for posting these instructions, but I am having a little trouble following them to enable SemanticProxy. I've looked at Calais Node Settings and do not see anything there related to SemanticProxy. Then I checked through the Content Types, and find nothing there either. Could you please provide more detail on where I supply a URL for Calais to submit to SemanticProxy?

Thanks for all the help.

Do you have any Content Types enabled as FeedAPI Node items? (You'll need FeedAPI and FeedPI Node enabled) Do any of your content types have a text field (besides title) or a link field (You'll need the Link module enabled for this)?

Those are the 2 (or 3) requirements to be able to use SemanticProxy on a Node. If you have any of those setup, SementicProxy configuration appears as a fieldset below the Calais processing section and provides a dropdown listing your options of which field to use as the URL to submit to SemanticProxy. If you dont see anything you may not have the proper field configured on your content types.

Thanks for all the extra info. I think I almost got it, but still missing something.

I now see the SemanticProxy section for the node type in the Calais Configuration section:

Field to send to SemanticProxy:(i've set this to) Field Item Original URL

Then below it there is a drop down

Field to save document text: (set to) Dont store document text

Now, when I go back to a blog (feedapi enabled) content type entry, I still only see the summary of the feed item. Is there another step I need to take to have it pull in the whole article from the original URL?

Really appreciate all the help you've provided.

thanks

To get the full body that was parsed by SemanticProxy you will need to add a textarea to your feeditem, then under the "Field to save document text" select the field you have added. Right now you are telling the Calais module to not save that text.

The SemanticProxy configuration was appearing as a fieldset in the Calais processing section, but now it is gone. Do you know the correct way to configure a link field for a blog entry type, so that it will automatically reference the feeds original URL without it having to be manually entered per article.

To further explain, for the content type field, I pick 'link' for type, then the only option showing for operation is 'Text Fields for Title and URL'. But before, in the Calais processing section, there was a semanticproxy fieldset option to auto reference the original URL of the article.

Not sure how to set it to do that again.

The error message I now receive when processing an article is "URL for SemanticProxy is invalid:"

nevermind, figured it out. I apologize. Looks as though my Blog Entry type had been un-enabled as a feed type.
I think that did it.

Thanks

Yep, that would do it. Glad you figured it out.

Is it working well for you otherwise?

Something seems to be acting a little strange.

When I add a new feed, now I get this error:
SemanticProxy processing error: URL http://us.rd.yahoo.com/dailynews/rss/search/aapl/SIG=126s172rj/*http%3A/... is invalid

Also, in the Calais node configuration, the SemanticProxy configuration has dissapeared for blog types even though the blog type is still enabled as a feed content type.

I don't have the SimpliePie Parser enabled. Should that be on? Right now, I just have the feedapi_node parser on.

Hey Rob,

First off, if I'm not mistaken, you need A parser turned on, either SimplePie or Common Syndication. FeedAPI Node itself is not a parser.

Now for your real question, the way the SemProx integration works is that if you want to specify which field to submit to SemProx on a blog entry, then you have to have Blog Entry specified as a FeedAPI Node Content Type (node to be made from a feed item) for a content type that is specified as a Feed, not as a Feed type itself. So, is your Feed type configured (under FeedAPI Node) to make Blog Entries?

Great, this cleared it up. Took me a few moments to really digest your reply; I was misunderstanding(crossing) some of the terms.

Glad it worked out. Thanks for sticking with it.

I also have problems with getting the full body that was parsed by SemanticProxy in to my text field. In the "Feed" content type, which is auto created from feedAPI, I have under the field set >> "FeedAPI Node - create nodes from feed items" >> " Node type of feed items: " entered my feed node type "Calais Feed". In the "Calais Feed" I have added a text field called "Save Feed".

Next I went to admin/settings/calais/calais-node and under the field set >> "Calais Feed" >> "Semantic Proxy" >> Field to send to SemanticProxy: Feed item Original URL, but under the dropdown below, the "Field to save document text:" there is no option. Isn't this where I would be able to choose the "Save Feed"-field? Why doesn't it work, am I missing something?

I guess I should set it to active. Read above.

that seems right to me. did you follow the instructions rob had up in #10?

Your 'Save Feed' field has to be a multiple row (text area) Text field.
Change it in the Manage Fields settings, by doing a 'change basic settings' for that field.