Skip to main content

Customizable RSS Feeds

Do you use RSS feeds? Then you know how useful they can be when you want alerts to newly published online information that applies to you: professionally or personally. This kind of targeted, agile publishing is exactly what Tizra is all about and, as you'd expect, we offer simple yet flexible features that let you get the most relevant updates out to your most interested users.

In case you're unfamiliar with RSS, it's basically a way of formatting information so that people can subscribe to and view it in feed reading software (Details from Wikipedia).  RSS means users save time because they're notified of anything new at their favorite sites without needing to visit them.
Tizra RSS feeds can be linked to from the homepage of your Tizra site, or any other web page.
By default, Tizra sites include an RSS feed that updates subscribers every time any new Document is added.  For example, here's a feed that'll update you any time Columbia University Press adds a book to the CUPOLA site they run on Tizra...

http://cupola.columbia.edu/~rss

The recipe for this is simple: Just take the domain name for the site (cupola.columbia.edu) and add ~rss at the end.

Customizing RSS Feeds:
You can customize the default feed just by adding a few parameters at the end of its URL.  Following are a few examples.

Collection Feed
Say you're only interested in Columbia's Business and Economics collection.  You'd start with the URL for the collection (http://cupola.columbia.edu/tdprp/) and add the ~rss to get...

http://cupola.columbia.edu/tdprp/~rss

Excerpt Feed
One of the really interesting things about the way Tizra lets you work with content is that you can unbundle Documents into shorter chunks called Excerpts, which can then be rebundled with other content.  These Excerpts can be the basis of feeds, too.  For example, The Association of Research Libraries breaks up each issue of its publication Research Library Issues into Excerpts—one for each article—and generates a feed like this...

http://publications.arl.org/all_rli_articles/~rss?metaTypeName=PageRange

By adding ?metaTypeName=PageRange at the end, the feed is switched to list Excerpts, rather than whole Documents.  This makes sense in a lot of cases like this, where users will probably find it more interesting to see the titles of each article in their feed reader, rather than just being informed that a new issue has come out.  Note: It's also possible to generate an Excerpt feed by using the Collection approach above.  Just configure the Collection to include Excerpts (or a combination of Excerpts & Documents) and the feed that's created by adding ~rss to the URL will include whatever's in the Collection.

Tag-Based Feed
You can also create a more free-form feed that will update users any time you apply a certain tag to your content.  For example, here's a feed containing everything with the "Automotive" tag on the Goodheart-Willcox Online Textbooks site...

http://www.g-wonlinetextbooks.com/~rss?AdminTags=Automotive

These are just a few examples...by no means comprehensive.  You could also do things like generate a feed with all the works of a particular author, update conference participants any time new items are added to a particular session, limit the number of items in a feed.  Drop us a note, and we'll be glad to discuss in more detail.

Comments

Popular posts from this blog

Technical Podcasts

If there is something the web as surely changed, it was the way that software engineers need to work. It is now a crucial aspect of our work to be able draw from the huge internet knowledge base out there in an efficient way to get to the right answers. Part of that information extraction is related to the keeping-up-to-date effort that every developer is required to accomplish to continue to be productive. While previous a software engineer could rely mostly on print material, nowadays we need to rely as well on content available on the net. Podcasts are such a source that can bring an amazing amount of information to the mix of knowledge one needs these days. If you are a software engineer and have not jumped into the podcast wagon yet, I suggest you do so. Here is a list some technical podcasts that we hear at Tizra: The Java Posse : a fantastic podcast on Java development. Containing news info update, analysis of tools, overall software development discussions. Software as She Dev...

Using XML to Create a Better Online Reading Experience for the American Payroll Association

Congrats to the American Payroll Association on their recent launch of XML-based publications on Tizra!  Thanks to this collaboration, APA's authoritative books for payroll professionals are now available in crisp, reflowable HTML, creating a user experience that feels like a truly digital native product, rather than a conversion from print. XML-based publishing also creates a better mobile reading experience, supports more precise search and navigation, and opens the door to better accessibility for users with low vision and other disabilities. Our partners at  Scribe  did a great job supporting APA through the process of producing the XML for loading into Tizra, and we’d definitely recommend them to anyone interested in such a transition. It’s hard to overstate what a big step forward this is for Tizra as a platform and a company. XML has long been planned for in the product's architecture, but now for the first time, we have a working example that demonstrates t...

The importance of continuous integration

Leading a team of developers in the effort of building a robust, quality software product should involve the establishment of some process and tools to assist the team effort and serve as a safety net for the errors of getting people to work together. Continuous integration is, I believe, a crucial element of that process. Introduced by Martin Fowler and Matt Foemmel (see article Continuous Integration ), continuous integration establishes the practice of frequent integration of work developed by the several team members verified by automated build and testing of integrated code within a clean sandbox. This practice is valuable for several reasons: It promotes the development of a clear process of building/deployment independent of any specificity of developer's platforms. Code that exists on a single platform only is bound to become dependent on specific aspects of that platform without anyone really noticing the dependencies until trying to port to other platforms. The existence ...