PubDate/Guid 对 RSS 至关重要？ 我如何在 Yahoo! 中创建良好的 RSS 如果源没有为项目提供不同的日期，则通过管道传输？
我正在创建 Yahoo! 通过管道到新闻网站，但是 feedless 来源没有每个项目的日期/时间。 我的 RSS 工作得不太好：每次更新都会使 RSS 阅读器（例如 Google 阅读器）再次将所有已读项目标记为未读。 也许这是因为缺少 pubDate 标签或 guid 标签不正确。
如何在 Yahoo! 上创建“pubDate” 当您的来源不向您提供数据时进行管道传输？
如何避免“guid”标签被覆盖？ （您可以在 YPipes 中设置 guid，但 YPipes 会忽略您的 guid）
解决方案： pudDate 不是必需的。 指导是必不可少的。 即使雅虎！ Pipes 重写了 guid，它会起作用，因为 Yahoo! Pipes 将您的 guid 文本转换为哈希值，在文本被修改之前不会对其进行修改。
I am creating a Yahoo! Pipe to a news site but the feedless source doesn't have a date/time for each item. My RSS doesn't works very well: each update makes the RSS Reader, Google Reader for instance, to mark all readed items as unreaded again. Perhaps that's because of the lack of pubDate tag or incorrect guid tag.
How to create a "pubDate" on Yahoo! Pipes when your source doesn't provide you the data?
How to avoid the "guid" tag overwritting? (you can set the guid in YPipes but then YPipes ignores your guid)
Solution: pudDate isn't necessary. guid is essential. Even if Yahoo! Pipes rewrites the guid, it will work, because Yahoo! Pipes converts your guid text into a hash value, that do not is modified until the text is modified.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（8）
我认为 GUID 是从链接参数生成的。 因此，为每个 feed 项目设置一个唯一的 url 非常重要。 如果所有提要 URL 都具有相同的链接，则它们将具有相同的 GUID。
我希望这有帮助。
我正在努力创建独特的网址。 你有找到实现它的方法吗？
I think the GUID is generated from the link parameter. So it is important to have a unique url for each feed item. If all the feed urls have same link, they will have same GUID.
I hope that helps.
I am struggling myself to create unique url. Have you found anyway to achieve it?
您是否查看过 Feedity - http://feedity.com - 用于创建自定义 RSS 提要。 它类似于 Pipes，但更容易使用，而且实际上在 Pipes 中也能很好地工作。 我已经使用它为那些“无反馈”网页创建 RSS 提要有一段时间了。
Have you looked at Feedity - http://feedity.com - for creating custom RSS feeds. It's like Pipes, but much easier to use, and in fact works well within Pipes as well. I've been using it for a while to create RSS feeds for those "feedless" webpages.
好吧，为了将来参考，可以在此链接中找到解决方案。 它也非常适合约会。 基本上，它的作用是创建一个节点，将所有需要的字段复制为其子节点，然后最后用这个“克隆”子节点替换父节点。
Well, for future reference, the solution can be found in this link. It also serves well for putting a date. Basically what it does is to create a node copying as its subnodes all the needed fields, and then at the end it replaces the parent with this "cloned" child.
我没有给你一个明确的答案，但有趣的是，在过去四年左右的时间里，我一直在维护一个私人提要阅读器。 我接触过很多变幻莫测的 RSS/ATOM，我可以告诉您，很多提要没有与项目相关的日期。 可能是RSS版本问题。
I don't have a definitive answer for you, but anecdotely I have been maintaining a private feed reader for the last 4 years or so. I've been exposed to a lot of vagaries of RSS/ATOM and I can tell you that a lot of feeds don't have dates associated with the items. It might be an RSS version issue.
上次我重建网站时，我在提要方面遇到了很多问题。 按照您描述的方式 - 阅读下次更新时未读的内容，重复的条目。 事实证明，问题更多地与 guid 元素有关，而不是与发布日期有关。 据我记得，只要指导是唯一的，我对日期做了什么（我有一段时间的格式错误）并不重要。
Last time I rebuilt my site, I had a bunch of trouble with the feed. In the way you describe- read things becoming unread on next update, duplicate entries. Turns out the problem was more to do with the guid element than the pubdate. As far as I recall, it didn't matter too much what I did with the date (I had the format wrong for a while) as long as the guid was unique.
对于 Yahoo Pipes，使用“创建 RSS”模块，它似乎使用每个条目的链接（的散列版本）来生成 GUID，正如您所指出的，这对于大多数提要阅读器来说是必要的检测新条目。
我尝试将“创建 RSS”模块的 GUID 字段设置为每个条目唯一的值，但是生成的提要中的 GUID 对于每个条目保持相同。 然后，当我将链接设置为该值时，生成的 GUID 对于每个条目都是唯一的。
我已经通过制作管道的副本并删除（好吧，重命名）链接属性，并且不会生成 GUID（尽管您已经指定了 GUID）。 这已被其他人确认为错误，请参阅tinyurl.com/mxard2。
With Yahoo Pipes, using the 'Create RSS' module, it appears to use (a hashed version of) each entry's link to generate a GUID, which as you point out, is necessary for most feed readers to detect new entries.
I've attempted to set the 'Create RSS' module's GUID field to a value that's unique for each entry, however the GUID in the resultant feed remains identical for each entry. When I then set the link to this value the GUIDs generate were unique for each entry.
I have verified this by making a copy of your pipe and removing (well, renaming) the link attribute and no GUID is generated (although you have specified one). This has been confirmed by others as a bug, see tinyurl.com/mxard2.
问题可能出在您的 Feed 来源上。 如果您使用多个提要，则在管道中的联合操作之后，对 pubdate 执行排序操作，然后将其重定向到输出。
the problem could be with the source of your feed. If you are using mutliple feeds then after the union operation in pipes, do a sort operation on pubdate and then redirect it to the output.
我自己一直在这样做，并且在我用来获取数据的 url 中附加了一个随机数（我正在使用 YQL 进行抓取）。 我通过使用日期生成器生成该随机数并用“今天”填充它以获取当前日期/时间。 然后，我使用 URL 生成器来构建我请求的 url，传递一个额外的“randomnumber”参数，我将其分配给 DateTime.utime 值。
通过查看源代码查看生成的 RSS 提要后，articleId 现在看起来确实是唯一的，但我还没有留下足够长的时间来知道 google reader 等是否认为它不同。
Just been doing this myself, and have resorted to appending a random number to the url that I'm using to get the data from (I'm scraping using YQL). I'm generating that random number by using a Date Builder and populating it with "today" to get the current date/time. I'm then using a URL Builder to build up my url that I'm requesting, passing in an extra parameter of "randomnumber" which I'm assigning to my the DateTime.utime value.
Having looked at the generated RSS feed via view source, the articleId now does appear to be unique, but I haven't left it long enough to know if google reader etc sees it as different.