Skip to content

Tag Archives: howto

Anatomy of the Zotero Library to RSS Feed Pipe

Note! A new feature on the Zotero website does away with the need to use this Yahoo! Pipe. RSS feeds are now generated by the Zotero website itself. Read more about it on the Zotero blog.

Last week I posted about a Yahoo Pipes construct that turns a Zotero website library into an RSS feed. As Dan Cohen noted in a twitter response to the posting, the Zotero team is planning to add an RSS capability in a future release of the website, so this pipe will ultimately be usurped by that capability, but in the meantime it is a handy tool. It was my first full-scale foray into creating a Yahoo Pipes construct from scratch, so I thought it would be useful to document how it works (in case I need to do something similar again). You might find this useful, too; especially the part about how to put a pubDate element into the RSS feed.

This is a preview of Anatomy of the Zotero Library to RSS Feed Pipe. Read the full post (1099 words, 2 images, 4:24 minutes estimated reading time)
Also tagged , ,
2009 03 06 Comments (1)

HOWTO Deal With Spam as a Mailman List Owner

Dealing with SPAM e-mail is a real hassle. Dealing with SPAM e-mail as a mailing list owner is an even bigger hassle. Here are some tips for dealing with SPAM e-mail on mailing lists using the Mailman software package.

The Symptoms


Unless you are making your users as well as yourself miserable, you’ve probably set the “Action to take for postings from non-members for which no explicit action is defined” to “Hold”. I believe this is the default setting for new lists.

\"Hold Nonmember\" Setting in Mailing list administration -> Privacy Options -> Sender filters

Hold Nonmember setting in Mailing list administration, Privacy Options, Sender filters

This is a preview of HOWTO Deal With Spam as a Mailman List Owner. Read the full post (628 words, 2 images, 2:31 minutes estimated reading time)
Also tagged ,
2008 07 16 Comments (1)

Fronting Tomcat with Apache HTTPD to Remove Ports and Context Paths

In this How-To guide, I show a combination of software and configuration to clean up URLs by removing the port numbers of the Java servlet engine (Tomcat) and the context path of the application. The goal is to create “cool URLs” that are are short (removing the unnecessary context path) and follow conventions (using the default port “80″ rather than “8080″). OhioLINK also uses a custom access control module — built for Apache HTTPD — which makes the fronting of Apache HTTPD for Tomcat even more desirable.

This is a preview of Fronting Tomcat with Apache HTTPD to Remove Ports and Context Paths. Read the full post (560 words, 2:14 minutes estimated reading time)
Also tagged , , , ,
2007 09 19 Comments (10)
From the Disruptive Library Technology Jester (http://dltj.org/), printed on Thursday the 2nd of September 2010 at 8:15:08 PM UTC (+0000). The URL to this page is http://dltj.org/tag/howto/

[Creative Commons Logo] This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 United States License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/us/ or send a letter to Creative Commons, 543 Howard Street, 5th Floor, San Francisco, California, 94105, USA.