Headlines Plugin

Show headline news in TWiki pages based on RSS and ATOM news feeds from external sites


This plugin displays RSS and ATOM feeds from news sites. Use it to build news portals that show headline news.

Note: Syndic8.com ( http://www.syndic8.com/ ) lists many RSS feeds.

Syntax Rules


Parameter Explanation Default
"..." source of RSS feed; this can be an url (starting with http) or a web.topic location for internal feeds None; is required
href="..." (Alternative to above) N/A
refresh="60" Refresh rate in minutes for caching feed; "0" for no caching Global REFRESH setting
limit="12" Maximum number of items shown Global LIMIT setting
touch="..." Touch (edit/save) topics if the feed has updates. Specify a comma-space delimited list of TopicNames or Web.TopicNames, such as "%TOPIC%, NewsLetter". Useful to send out newsletter using MailerContrib, showing new feeds since last newsletter. To update feeds, visit topics with feeds in regular intervals (using cron with wget or the like). N/A
header Header. Can include these variables: - $channeltitle, $title: title of channel (channel.title)
- $channellink, $link: link of channel (channel.link)
- $channeldescription, $description: description (channel.description)
- $channeldate, $date: publication date of the channel (channel.pubDate)
- $rights: copyrights of the channel (channel.copyright)
- $imagetitle: title text for site (image.title)
- $imagelink: link for site (image.link)
- $imageurl: URL of image (image.url)
- $imagedescription: description of image (image.description)
Global HEADER setting
format Format of one item. Can include these variables:
- $title: news item title (item.title)
- $link: news item link (item.link)
- $description: news item description (item.description)
- $date: the publication date (item.pubDate, item.date)
- $category: the article category (item.category)
Global FORMAT setting

The header and format parameters might also use variables rendering the dc, image and content namespace information. Note, that only bits of interest have been implemented so far and those namespaces might not be implemented fully yet.

Rendering the dc namespace

The following variables are extracting the dc namespace info, that could be used in header and format. Nnote, that some of the variables are already used above. This is done by purpose to use different feeds with the same formating parameters. If there's a conflict the non-dc tags have higher precedence, i.e. a <title> content </title> is prefered over <dc:title> content </dc:title> .

  • $title: channel/article title (dc:title)
  • $creator: channel creator (dc:creator)
  • $subject: subject text; this will also add an image according to the subject hash list, see above (dc:subject)
  • $description: ... (dc:description)
  • $publisher: the channel/article publisher (dc:publisher)
  • $contributor: ... (dc:contributor)
  • $date: ... (dc:date)
  • $type: ... (dc:type)
  • $format: ... (dc:format)
  • $identifier: ... (dc:identifier)
  • $source: ... (dc:source)
  • $language: ... (dc:language)
  • $relation: ... (dc:relation)
  • $coverage: ... (dc: coverage)
  • $rights: ... (dc: rights)

Rendering the image namespace

An image:item is converted into an <img> tag using the following mappings:

  • src: image url (rdf:about attribute of the image.item tag)
  • alt: image title (title)
  • width: image width (image:width)
  • height: image height image:height)

Rendering the content namespace

The variable $content is refering to the <content:encoding> content </content:encoding>.


Slashdot News


%HEADLINES{ "http://slashdot.org/slashdot.rdf" 
  header="*[[$link][$title]]:* $description" 
  format="$t* [[$link][$title]]"
to get the latest Slashdot news as a bullet list format:

Business Opportunities Weblog


%HEADLINES{ "http://www.business-opportunities.biz/feed" limit="2" }%

to get the latest postings on the "Business Opportunities" weblog:

Fri, 11 Jun 2021 16:45:33 +0000
The original blog about business opportunities and business ideas for small business entrepreneurs
Fri, 11 Jun 2021 00:53:26 +0000 Carrol Strain
Featured image by National Cancer Institute on Unsplash

Thanks to recent advancements in technology, healthcare providers are now turning to ERP software instead of relying exclusively on paper records. Patients and healthcare providers alike enjoy impressive benefits as a result.


Recent research predicts that by 2025, the US healthcare system will reach a market size of $2.1 billion. The rapid growth of this sector makes the use of ERP software in healthcare essential, as traditional record-keeping is insufficient to the task at hand. But ERP software efficiently and reliably gathers and consolidates data while keeping it confidential.

Eight Benefits of ERP in Healthcare

1. ERP Software Gives Easier Access to Medical Records

Until recently, healthcare providers kept patients’ medical records in paper files stored in filing cabinets that took up enormous space in the office. When a patient arrived, they were sometimes forced to wait while staff members searched for their files. Then, unless they possessed prodigious memories, doctors and other healthcare professionals had to search through these sometimes massive paper files to learn what they needed to know in order to properly treat the patient.

But with ERP software every patient’s records reside in a single platform. There, any information the healthcare provider might need is just a click away. This minimizes the time providers need for pulling up and researching patient files.

ERP software really came into its own during the pandemic. Practically everything in the world came to a screeching halt, and most businesses had to close. But healthcare was on the front lines in the war against the virus. ERP software gave clinics and hospitals the ability to provide remote care, even monitoring patients’ vital signs remotely. Because they could easily access patients’ electronic records, they were able to keep in-person visits to a minimum.

2. Patients' Records Remain Confidential

Medical records must be kept confidential, and confidentiality is less likely to be compromised with ERP software, as only authorized individuals are able to access patient records. Moreover, even if a breach does occur, it is often traceable. In other words, it can be a fairly simple matter to determine who illegally accessed electronic records.

3. Clinics Benefit from Smarter Business Intelligence

If you own a healthcare clinic, ERP software will give you an advantage when it comes to overseeing your facility’s business operations. You will be able to access information about your clinic’s performance, its budget, and more. Therefore, you will be better able to make smart decisions about running your business.

4. Healthcare Providers Can More Accurately Monitor Costs

Every industry needs to have proper financial monitoring to accurately account for both income and expenses. The healthcare industry is no exception.

ERP software easily monitors income and outgo. It gives authorized members of your staff effortless access to salaries, operational expenditures, and patient payments. It also minimizes the effects of human error, as much of the process is automated.

5. ERP Software Simplifies Industry Compliance

Every healthcare provider must comply with regulatory requirements, and this is where ERP software truly shines. While regulatory compliance is never a simple matter, having the right software will definitely make this part of running your facility much easier.

6. ERP Software Reduces Operational Costs

Consolidating all of your facility’s data within a single platform will reduce operational costs. You’ll be able to leave billing, inventory, and other operations in the hands of a few trained individuals, thereby minimizing costs for labor.


7. It Streamlines Process Integration

When your facility uses ERP software, its various processes will be streamlined. This will improve efficiency, collaboration, and communication.

8. Patient Safety Improves

The patient puts his or her trust in their healthcare provider, and it is up to the provider to safeguard that trust by using a system that’s transparent with financial transactions as well as with communications about patient care. ERP software protects both the patient and the healthcare provider in these matters.


The post The Benefits of ERP Software in Healthcare appeared first on Business Opportunities.

Thu, 10 Jun 2021 17:36:36 +0000 Carrol Strain
Featured image by Eak sikgun

The internet of things (IoT) has transformed our world. A mere concept just a few years ago, it’s a reality now, with billions of smart devices interconnected all around the world, sharing and receiving data with each other. Let’s take a look at how all this interconnectivity shapes our homes, our businesses, and our lives.


A multitude of connectivity technologies make the internet of things possible. These technologies provide the infrastructure and communication capabilities so that IoT devices can exchange data over the internet. Because they do, we can now remotely monitor and control the “things” in our lives.

The technologies that make this possible currently include Bluetooth, Wi-Fi, and mesh network technologies like Zigbee. Additionally, cellular data connectivity with the help of IoT SIM cards remains one of the most popular connectivity technologies today.


What Is an IoT SIM Card?

Most of us are familiar with the concept of SIM cards. Chances are, in fact, you have used SIM cards in your smartphones and other mobile devices. A SIM card allows a device such as a smartphone to send and receive information wirelessly, over a cellular data network.

Traditional SIM cards actually were first launched in 1991. Since then, they have enabled more than 7 billion smartphones and other devices to connect with cellular networks all around the world.

However, IoT connectivity between IoT devices demands more than the standard cellular connectivity features in our smartphones. This is where IoT SIM cards come in. Below are some unique needs of IoT connectivity that create the demand for IoT SIM cards.

1. Remote SIM Provisioning

Typical SIM cards in our smartphone are locked into a single network provider. If we want to switch between providers, such as when we’re traveling internationally, we must physically also switch to another SIM card.

The reason for this is that an internet of things SIM card is able to connect with multiple network carriers all around the world. This has important implications for global implementations of IoT devices. For example, it is essential for connecting IoT devices that are located in different countries.

This feature is also useful for mobile IoT devices, such as autonomous vehicles that operate across international borders.

IoT data plans offer global coverage in more than 100 countries. Meanwhile, some also allow users to remotely configure SIM cards to access specific networks. This gives users for more versatility with regard to network control.

2. Durability

Some IoT devices might need to be deployed in extreme environments. But IoT SIMs are extremely durable. For example, neither massive vibrations nor wide variances in temperature affect the hardiest of them. This is basically because IoT SIM cards are much more durable than standard SIM cards such as the ones in our smartphones. They can endure for as long as a decade under extreme conditions that include powerful vibrations and temperatures that range from -40 degrees to 105 degrees Celsius.

3. Remote Monitoring and Management of the Internet of Things

In an IoT deployment, users must be able to monitor and manage IoT SIMs remotely. Typically, the IoT data plan provider will provide dedicated management software that allows business users to remotely manage their IoT devices in bulk.

4. Data Aggregation on the Internet of Things

IoT SIMs typically have lower data requirements than traditional ones. However, different IoT devices in the network may consume different levels of data.

An IoT data plan that allows data aggregation is very important in such cases. This type of plan allows users to incur lower charges when some of their devices are overusing data while others are underusing data.

How Do SIM Cards Engage with the Internet of Things?

1. Casual IoT Hobbies

Cellular IoT connectivity by way of IoT SIM cards is one of the most accessible and cost-effective IoT connectivity solutions for hobbyists. Users can simply purchase an SIM card and use it in their devices. This instantly adds cellular connectivity to their IoT projects.

2. Wearables

Apple with the Apple Watch and Samsung with its Galaxy Watch pioneered the use of eSIM for wearables. These are programmable SIM cards that are embedded directly into devices. In the near future, we can expect new wearable technologies to adopt the IoT SIM card. This will provide even more innovative features far beyond today's typical health and sports applications.

3. Home Automation

Most smart home IoT devices rely on Wi-Fi and other short-range connectivity options like Bluetooth or Zigbee. However, there are smart home devices that can benefit from using IoT SIM cards to get cellular IoT connectivity. For example, alarm systems, outdoor smart cameras, and so on have more functionality when they’re connected to the internet of things.

4. Industrial IoT Deployment

Industrial sensors can be deployed in remote and environmentally harsh locations. These locations typically require the IoT SIM card's durability and longevity, as well as its remote provisioning capabilities. IoT SIM cards can provide businesses the ability to monitor and control these devices in real time, even when two or more devices are separated by thousands of miles.

5. As Backup for Other Connectivity Options

In a smart home setting, Wi-Fi or even hardwire internet might be fast and reliable enough. But in cases of network failure due to poor infrastructures and/or natural disasters, cellular IoT connectivity can act as a reliable backup.

Why is this so? As we all know, cellular towers are virtually everywhere. Therefore, so cellular IoT connections offer more flexibility and reliability than traditional Wi-Fi connectivity.


IoT SIM Cards and the Internet of Things Connect Our World

IoT SIM cards help to make cellular IoT connectivity possible. What’s more, they provide more durability and longevity than traditional SIM cards like the ones in our smartphones. Also, IoT SIM cards allow more unique features that cater to the unique needs of IoT deployments, like remote provisioning and dedicated device management solutions.

The post How the Internet of Things Is Transforming Our World appeared first on Business Opportunities.

Plugin Settings

Plugin settings are stored as preferences variables. To reference a plugin setting write %<plugin>_<setting>%, for example, %HEADLINESPLUGIN_SHORTDESCRIPTION%. Note: Don't modify the settings here; copy and customize the settings in Main.TWikiPreferences. For example, to customize the USERAGENTNAME setting, create a HEADLINESPLUGIN_USERAGENTNAME setting in Main.TWikiPreferences.

  • One line description, shown in the TextFormattingRules topic:
    • Set SHORTDESCRIPTION = Show headline news in TWiki pages based on RSS and ATOM news feeds from external sites

  • Refresh rate in minutes for cached feeds. Disable caching: 0, default: 60
    • Set REFRESH = 60

  • Maximum number of items shown. Default: 100
    • Set LIMIT = 100

  • Use LWP::UserAgent, or fallback to TWiki's internal getUrl() method. Default: yes

  • Timeout fetching a feed using the LWP::UserAgent. Default: 20

  • Name of user agent. Default: TWikiHeadlinesPlugin/2.21
      * Set USERAGENTNAME = TWikiHeadlinesPlugin/2.21

  • Default header: (variables are explained in the syntax rules)
      * Set HEADER = <div class="headlinesChannel"><div class="headlinesLogo"><img src="$imageurl" alt="$imagetitle" border="0" />%BR%</div><div class="headlinesTitle">$n---+!! <a href="$link">$title</a></div><div class="headlinesDate">$date</div><div class="headlinesDescription">$description</div><div class="headlinesRight">$rights</div></div>

  • Default format of one item: (variables are explained in the syntax rules)
      * Set FORMAT = <div class="headlinesArticle"><div class="headlinesTitle"><a href="$link">$title</a></div>$n<span class="headlinesDate">$date</span> <span class="headlinesCreator"> $creator</span> <span class="headlinesSubject"> $subject </span>$n<div class="headlinesText"> $description</div></div>

  • Values taken from configure: (only supported if CPAN:LWP is installed)
    • $TWiki::cfg{PROXY}{HOST} - proxy host, such as "proxy.example.com";
    • $TWiki::cfg{PROXY}{PORT} - proxy port, such as "8080";
    • $TWiki::cfg{PROXY}{SkipProxyForDomains} - domains excluded from proxy, such as "intra.example.com, bugs.example.com";

Style Sheets

The default HEADER and FORMAT settings use the following styles. See the style.css file defining the default CSS properties (indentation illustrates enclosure).

  • headlinesRss: output of the HeadlinesPlugin (div)
    • headlinesChannel: channel header (div)
      • headlinesLogo: channel logo (div)
      • headlinesTitle: channel title (div)
      • headlinesDate: channel date (div)
      • headlinesDescription: channel description (div)
      • headlinesRight: channel copyright (div)
    • headlinesArticle: one news item (div)
      • headlinesTitle: article title (div)
      • headlinesDate: article date (span)
      • headlinesCreator: author of article (span)
      • headlinesSubject: subect category of the article (span)
      • headlinesText: article text (div)

Plugin Installation Instructions

  • Download the ZIP file.
  • Unzip it in your twiki installation directory. Content:
    File: Description:
    data/TWiki/HeadlinesPlugin.txt plugin topic
    pub/TWiki/HeadlinesPlugin/style.css default css
    lib/TWiki/HeadlinesPlugin.pm plugin perl module
    lib/TWiki/HeadlinesPlugin/Core.pm plugin core
    Check if above examples show a news feed instead of variable.
  • Optionally, run HeadlinesPlugin_installer.pl to automatically check and install other TWiki modules that this module depends on. You can also do this step manually.
  • Alternatively, manually make sure the dependencies listed in the table below are resolved.
    Digest::MD5>=2.33Required. Download from CPAN:Digest::MD5
    LWP::UserAgent>=5.803Optional. Download from CPAN:LWP::UserAgent

Plugin Info

Plugin Author: TWiki:Main.PeterThoeny, TWiki:Main.MichaelDaum
Copyright: © 2002-2010, Peter Thoeny, Twiki, Inc.; 2005-2007, Michael Daum http://wikiring.de
License: GPL (GNU General Public License)
Plugin Version: v2.6 - 2010-05-16
Change History:  
2010-05-16: TWikibug:Item6433 - more doc improvements
2010-04-25: TWikibug:Item6433 - doc fix: Changing TWIKIWEB to SYSTEMWEB
2010-02-27: TWikibug:Item6313 - fixed bug in ATOM feed with <link ...></link> instead of <link ... /> -- Peter Thoeny
2009-09-30: fixed bug in lastBuildDate of feeds affecting touch parameter functionality -- Peter Thoeny
2009-08-29: added touch parameter -- Peter Thoeny
12 Feb 2009: {PROXY}{HOST} supports domain with and without protocol -- Peter Thoeny
06 Feb 2009: added {PROXY}{SkipProxyForDomains} configure setting, added USERAGENTNAME plugin setting -- Peter Thoeny
11 Dec 2008: added {PROXY}{HOST} and {PROXY}{PORT} configure settings -- Peter Thoeny
13 Sep 2007: fixed parsing of content:encoded
23 Jul 2006: improved atom parser; if a posting has no title default to 'Untitled'
26 Apr 2006: added lazy compilation
10 Feb 2006: packaged using the TWiki:Plugins/BuildContrib; minor fixes
03 Feb 2006: off-by-one: limit="n" returned n+1 articles; make FORMAT and HEADER format strings more robust
23 Jan 2006: released v2.00
05 Dec 2005: internal feed urls must be absolute
02 Dec 2005: added web.topic shorthand for internal feeds
29 Nov 2005: fixed CDATA handling
21 Nov 2005: added ATOM support; extended RSS support; added dublin core support; added content support; optionally using LWP to fetch feeds to follow redirections; corrected CPAN dependencies ; recoding special chars from html integer to entity encoding to increase browser compatibility; added css support; use getWorkArea() if available
11 May 2005: TWiki:Main.WillNorris: added DevelopBranch compatability
31 Oct 2004: Fixed taint issue by TWiki:Main.AdrianWeiler; small performance improvement
29 Oct 2004: Fixed issue of external caching if mod_perl or SpeedyCGI is used
02 Aug 2002: Implemented caching of feeds, thanks to TWiki:Main/RobDuarte
11 Jun 2002: Initial version (V1.000)
Perl Version: 5.8
TWiki:Plugins/Benchmark: GoodStyle 100%, FormattedSearch 99.5%, HeadlinesPlugin 94%
Plugin Home: http://TWiki.org/cgi-bin/view/Plugins/HeadlinesPlugin
Feedback: http://TWiki.org/cgi-bin/view/Plugins/HeadlinesPluginDev
Appraisal: http://TWiki.org/cgi-bin/view/Plugins/HeadlinesPluginAppraisal

Related Topics: TWikiPlugins, AdminDocumentationCategory, TWikiPreferences

Topic revision: r1 - 2010.05.17 - TWikiContributor
This site is powered by the TWiki collaboration platformCopyright © 1999-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
Note: Please contribute updates to this topic on TWiki.org at TWiki:TWiki.HeadlinesPlugin.