Yahoo.Pipes - a couple of tips, hacks, tips
Unlike some, I do not claim to be the most important pipe expert. However, since I often work with the Yahoo.Pipes service, I dared to share some things, including solving a number of problems that a novice “pipe scientist” (or “paypod”) may face. Well, the main message that prompted me to write this post is, first of all, not to forget about these things myself, and if anything, always be able to consult.
As usual, a small digression. Yahoo.Pipes is an amazing service that allows you to do various useful and interesting things with rss-feeds (rss-streams) (strictly speaking, not only with rss, but also xml-, csv- data, web pages, other Internet services and etc. - the main thing is that they can be accessed via the web). You can combine several rss-channels into one, you can, on the contrary, divide, and then mix again, sort by various ways, add something, subtract something, etc., etc.
The most important thing is that it is implemented through a web interface and in visual form. In other words, you don’t need to program anything and actually invent it yourself. all that is required is to know what modules exist, how to handle them and what they can (RTFM, of course, hasn’t been canceled), and basic knowledge of regular expressions will also help (again, if you want to make complex ", For simple ones, sorry for taftology, everything is much simpler). At the output, you will receive an rss stream or a file in json format, which is also remotely accessible and constantly updated.
')
The advantages of the service are obvious - as I said, you don’t need to program anything, you don’t need to host any scripts, you don’t need to worry about caching and traffic - all this is taken by Yahoo.Pipes
Over the last 2 years of its existence, the service “matured”, new convenient features appeared, and, of course, there are also all sorts of bugs, errors that are poorly documented (therefore the solution is not immediately found), or are simply forced to climb onto the wall (“ I do everything as in the manual, but no, it's buggy ”). Perhaps this arises from the poor reading of my documentation, however, I still share my little discoveries and tips. (I note once again that this article is intended for a less-prepared reader who is familiar with the basic modules of Yahoo.Pipes).
So, to warm up, let's start with a simple one:
1. Often it is required to refer, for example, in a description sub element to another sub element (for example, a link). This happens when you want to insert HTML-text into the description sub-element (for example, the link's url sub-element of the picture, and you want to insert a link to this picture and add a little explanation to it). As a rule, the Regex module is used for this, but the question arises, how to insert a link to another sub-element of item to the line where we write what to change.
To do this, we proceed as follows: put the $ sign, then curly brackets {}, and inside them the name of the subelement without, note the item., I.e.
$ {link}, where link is the name of one of the existing sub-elements of the item element.
Full article on my blog
As usual, a small digression. Yahoo.Pipes is an amazing service that allows you to do various useful and interesting things with rss-feeds (rss-streams) (strictly speaking, not only with rss, but also xml-, csv- data, web pages, other Internet services and etc. - the main thing is that they can be accessed via the web). You can combine several rss-channels into one, you can, on the contrary, divide, and then mix again, sort by various ways, add something, subtract something, etc., etc.
The most important thing is that it is implemented through a web interface and in visual form. In other words, you don’t need to program anything and actually invent it yourself. all that is required is to know what modules exist, how to handle them and what they can (RTFM, of course, hasn’t been canceled), and basic knowledge of regular expressions will also help (again, if you want to make complex ", For simple ones, sorry for taftology, everything is much simpler). At the output, you will receive an rss stream or a file in json format, which is also remotely accessible and constantly updated.
')
The advantages of the service are obvious - as I said, you don’t need to program anything, you don’t need to host any scripts, you don’t need to worry about caching and traffic - all this is taken by Yahoo.Pipes
Over the last 2 years of its existence, the service “matured”, new convenient features appeared, and, of course, there are also all sorts of bugs, errors that are poorly documented (therefore the solution is not immediately found), or are simply forced to climb onto the wall (“ I do everything as in the manual, but no, it's buggy ”). Perhaps this arises from the poor reading of my documentation, however, I still share my little discoveries and tips. (I note once again that this article is intended for a less-prepared reader who is familiar with the basic modules of Yahoo.Pipes).
So, to warm up, let's start with a simple one:
1. Often it is required to refer, for example, in a description sub element to another sub element (for example, a link). This happens when you want to insert HTML-text into the description sub-element (for example, the link's url sub-element of the picture, and you want to insert a link to this picture and add a little explanation to it). As a rule, the Regex module is used for this, but the question arises, how to insert a link to another sub-element of item to the line where we write what to change.
To do this, we proceed as follows: put the $ sign, then curly brackets {}, and inside them the name of the subelement without, note the item., I.e.
$ {link}, where link is the name of one of the existing sub-elements of the item element.
Full article on my blog
Source: https://habr.com/ru/post/59619/
All Articles