Headlines Plugin

Description

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/ ) is a good site listing many RSS feeds.

Syntax Rules

%HEADLINES{"..."}%

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
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>.

Examples

Slashdot News

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

Business Opportunities Weblog

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

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

Mon, 20 Aug 2018 05:13:28 +0000
The original blog about business opportunities and business ideas for small business entrepreneurs
Mon, 20 Aug 2018 05:02:35 +0000 Laurie Bennett

Oracle’s Netsuite is a powerful solution. For example, it enables enterprises to manage various business operations over the cloud.

Organizations will get more value from NetSuite if it is integrated with other applications on a single interface. However, NetSuite integration can be a daunting task. Even teams with advanced competency centers face debilitating errors while developing its integration flows. Moreover, it is difficult to integrate NetSuite with legacy systems and on premise applications.

Nonetheless, many teams still use point-to-point connectivity for integrating NetSuite with other applications. But this approach is time-consuming. Plus, it requires a lot of engineering resources. Moreover, it is not feasible to connect NetSuite with hundreds of legacy systems using this approach. That’s because developers often code something and thereby change the behavior of another application.

Additionally, here are some disadvantages of this point-to-point approach:

 

RELATED ARTICLE: 6 KEY POINTERS FOR RUNNING YOUR VIRTUAL MACHINE SAFELY

 

1. Cost Overheads

Imagine a situation where you need to integrate NetSuite with 500 applications. Hand coding each connection will take several months. Moreover, entities need to invest a huge amount of resources for recruiting and building teams. Costs will expand further because of down times and network breakdowns.

2.Maintenance

Organizations will need to expend enormous efforts to maintain systems and keep up the integration layer. Moreover, the integration layer is disturbed when teams change anything in the ecosystem. Teams have to spend huge cycle runs for incorporating minor changes. These changes keep the IT team busy. They also depreciate the quality of the service.

3. Rigidity

Point-to-point integration is difficult to scale. What’s more, the same coding cannot be used for developing other flows. Therefore, IT teams have to build new codes for accommodating new changes.

4. IT Complexity

Point-to-point connectivity is a good solution where two or three applications are involved. However, it is not a viable solution for an IT ecosystem where several new and old applications run in parallel.

An API-Led Approach for Integrating NetSuite

NetSuite offers several features for integrating with other applications. One feature is Suite Connect. However, there are several things to consider in this approach. Unfortunately, many organizations still view application development in binary. That is, they develop a single code and then send it to maintenance. However, developers generate several lines of coding just to bring data from other applications. Here is a use case of integrating NetSuite with Salesforce for a better understanding:

Step 1

Check remote site settings in Salesforce.

Step 2

Include NetSuite remote URL.

Step 3

Generate a script in NetSuite.

Step 4

Click Document → Files → SuiteScripts → Manual Script.

Step 5

Add a new customer by creating the JavaScript.

NetSuite1a 245w, NetSuite-1-1-768x939.jpg 768w, NetSuite-1-1-837x1024.jpg 837w, NetSuite-1-1-1200x1468.jpg 1200w, NetSuite-1-1-600x734.jpg 600w" sizes="(max-width: 2284px) 100vw, 2284px" />

Step 6

Add a new script with the Add File option.

Step 7

Click Customization → Scripting → Scripts → New.

Step 8

Click Select the type and Name the created script.

Step 9

Click Save. You will have created an endpoint in Salesforce in the form of a URL.

Step 10

Click Add Authentication Request.

Step 11

Use the Rest Call option in Salesforce for data transfer.

NetSuite2a 290w, NetSuite-2-1-768x796.jpg 768w, NetSuite-2-1-988x1024.jpg 988w, NetSuite-2-1-600x622.jpg 600w" sizes="(max-width: 1000px) 100vw, 1000px" />

NetSuite3a 241w, NetSuite-3-1-768x956.jpg 768w, NetSuite-3-1-822x1024.jpg 822w, NetSuite-3-1-600x747.jpg 600w" sizes="(max-width: 1145px) 100vw, 1145px" />

Note: The endpoint will be different for different use cases.

Teams encounter several scale and fail-over issues with this method. For example, the development team develops codes and testing teams validate them. This whole process is repeated several times.

However, teams can overcome all these issues if they can automate NetSuite integration with an end-to-end integration solution. This method thus empowers business teams to build workflows without needing to write a single line of code.

Automating NetSuite Integration

Automation augments the orchestration of technologies. Moreover, it allows teams to bring in data from any source. Therefore, teams can get a 360-degree view of data and integrate apps in simple steps. Also, teams can monitor and resolve IT complexity. This can prevent network breakdowns. Plus, they can access a number of business benefits by addressing pervasive integration needs.

A Simple Way to Integrate Cloud-Based Applications with an Enterprise-Class Integration Solution

Step 1

Log into the platform and click “Projects” on the interface. The Projects page displays.

Step 2

Click “Data Interface'' to create flows for any-to-any integration.

Step 3

Click “Create Interface.” Specify elements such as Name, Source Schema Name, Source Type, Source Name, Target Type, Target Schema Name, Data Mapping, etc.

Step 4

Drag and drop data. This will allow you to map data between the source and target elements.

Here is a video tutorial where you can get a more detailed integration approach.

In this way, organizations can beat back the challenges of IT complexity in an enterprise. Then, the IT teams can focus on other important issues. Additionally, business users can build integration flows for addressing unique customer needs.

Conclusion

A manual approach to NetSuite Integration is cumbersome, error-prone, and resource-intensive. Therefore, make use of automation instead.

The post NetSuite Integration: Replacing Point-to-Point Connectivity with Automation appeared first on Business Opportunities.

Mon, 20 Aug 2018 04:54:49 +0000 Laurie Bennett
Photo by ELEVATE from Pexels

Whether you're running a high-hazard factory or a roster of remote inspectors, you're supposed to pay careful attention to your workers’ welfare. That's why maintaining a rigorous schedule of safety due diligence can mean the difference between a near-miss and an expensive legal battle. This is where safety automation software can help.

Think of safety due diligence as a safety net for passing the liability litmus test. Essentially, it involves taking reasonable precautions to prevent injuries or accidents in the workplace. In the event of an accident, proving that you took preventive steps can protect you from lawsuits and fines.

On the other hand, not keeping on top of it can be costly. Between 2016 and 2017, 19 fines of 1 million or higher were issued in the UK for failure to control serious risks and hazards. Moreover, the top 20 fines cost businesses a total of 38.6 million.

 

RELATED ARTICLE: SAFETY WORKWEAR: YES, YOU CAN GIVE EMPLOYEES STYLISH OPTIONS

 

Do You Keep a Health and Safety Diary?

Recording a health and safety diary is the easiest (and most instantly available) way to demonstrate due diligence. A safety log should note specific issues and corrective actions you took. This can help show compliance. It’s true that filling up a safety diary can be tedious. However, gaps in accountability will only demonstrate your company’s negligence. This is especially true if you don’t keep your log up to date.

This is where safety inspection software comes in. Instead of entering every detail and scheduling every inspection manually, you can automate the process with automation software.

A safety inspection app with workflow automation software can keep all your data organized. This will allow you to note any findings in your log. Also, you can automatically schedule follow-up tasks from the same central interface.

Moreover, it's important that you maintain a rolling slate of inspections, too. For example, health and safety experts recommend that these sorts of inspections be carried out at least once a week:

  • General inspections of the workplace
  • Sampling of processes, activities, and areas
  • General inspections of dangerous processes, activities, and areas
  • Incident inspections following an accident that caused injury, fatality, or a near-miss

Your workforce should conduct these regular inspections. Further, supervisors should perform safety audits every three months. Moreover, your company must conduct full annual audits to review safety as a whole.

However, since completing a diary often involves filling out the same data over and over again, the process can become monotonous. This is where automation software can make a huge difference in efficiency, clarity, and even liability.

 

Maintain Compliance with Safety Automation Software

There's no room for cutting corners in health and safety due diligence. A lax attitude would put employees at risk- and their employers at the full mercy of the law. Companies must maintain compliance. But that doesn't mean it has to be difficult.

Safety inspection automation software like Form.comhelps companies move away from traditional paper-based health and safety diaries. Instead, these companies use slick mobile interfaces where processes can be automated. The whole idea behind health and safety automation software is to make performing due diligence easier. Plus, it saves time and reduces headaches.

By creating workflows, you’ll be able to assign tasks to the correct personnel. You’ll even be able to automate repetitive tasks. For example, you can streamline data fields by creating pre-filled forms. Then the automation software will schedule new tasks based on specific responses. Those are not the only benefits, though.

Here are seven more ways inspection automation software can grease the wheels of safety workflow:

#1: Predefined Processes

Task assignment ensures everyone follows the same inspection and audit process. Inspections in the field are often carried out by different health and safety personnel. One shared process prevents data inconsistencies and provides one version of the truth.

#2: Reduced Risk of Noncompliance

Automated workflows allow managers to oversee operations and create individual checklists for inspections. Approvals, comments, and changes are all documented. Further, managers can make them subject to review. Therefore, nothing will be signed off without supervisor approval. This keeps data organized and compliant with company and regulatory standards.

#3: No More Duplicate Data Entry

Safety inspection software can automate repetitive tasks. For instance, when workers need to enter the same data needs with each inspection, the fields can be pre-filled. This avoids duplication, eliminates confusion, and saves time.

#4: Key Dates Identified

Digitally tracking compliance will prevent missed deadlines. That is, the automation software will send alerts and warnings when important dates draw near. Where daily checks are necessary, this functionality is essential in ensuring that safety records are maintained.

#5: Dynamically Assigned Tasks

Task automation software allows department leads to assign safety personnel new tasks based on their specialty. From a central interface, management provides field inspectors with the necessary documentation to complete tasks and safety inspection checklists. Individuals can log into their account via a mobile app at any time and from anywhere in the world to view and check off jobs.

#6: Real Time Access to Information

Safety inspection software erases piles of paperwork. It thus eliminates the need for task completion updates by email or fax. This means that managers can view data in real time. This will hasten the decision-making process. If inspectors identify a health and safety risk factor, supervisors can quickly arrange corrective and preventive action. This keeps employees safe and downtime at bay.

#7: Simple Reporting Managed Simply

With automation software, historical data remains in one place. Therefore, overseers can easily examine reports for quarterly and annual safety audits. Data visualization makes information easier to analyze and explain in presentations. Every business should keep a health and safety diary. However, using pen and paper to do that is just begging for complications.

 

Automation Software Streamlines Health and Safety Compliance

In the end, workflow automation software simplifies inspections. It makes it easy to record your data for a safer, smarter workplace. So, think about ditching the calendar-and the calendar app-for something a lot more reliable.

About the Author

Alex Brown is a technical content writer forForm.com. He writes informative tech articles for various publications as well as content related to digital distribution, branding, IT, and more.

The post Ditching the Calendar: How Automation Software Creates a Safer Workplace appeared first on Business Opportunities.

Mon, 20 Aug 2018 04:27:17 +0000 Laurie Bennett
Photo by Britta Jackson from Pexels

In an age when digital content is omnipresent, there's actually tremendous value in print publications. Not only does print cut through the noise, but it also commands a certain level of value that its online counterparts cannot. If you're interested in launching a print magazine, read on to discover what it looks like to be successful in the midst of the digital age.

 

RELATED ARTICLE: 4 WAYS YOU CAN MAKE MONEY WITH YOUR LOVE FOR PHOTOGRAPHY

 

The Secrets to Being Successful with a Print Magazine

If the year were 1988, the idea of starting a print magazine would seem totally sane and normal. But it's 2018, and you'd be crazy to even think about launching a print magazine venture&hellipright? Well, maybe not.

There's no question that print magazines have taken a huge nosedive over the last decade and a half. While the staples of the industry-publications such as Better Homes and Gardens, Good Housekeeping, Reader's Digest, National Geographic, and People magazine-are still doing quite well, the smaller ones have dropped like flies. It's for this reason that the notion of launching a new magazine with no history or existing reputation seems so crazy.

But perhaps it's just crazy enough to work.

Half of this business is about attracting eyeballs, and the other half is about moving people to action. In a world where thousands of new blogs and online publishing platforms are launched on a weekly basis, trying to make it in traditional digital circles is extremely challenging. You have to publish so much content and invest in so much marketing and promotion that you have very little time to actually focus on the quality and message of the content you're creating. As you can guess, this is highly problematic.

Print magazines are different. They offer something tangible in a digitized marketplace that's predicated on virtual experiences. They stand out-and for all the right reasons.

By no means is it easy to start a successful magazine, but the opportunity exists for those who are willing to put in the energy and effort. If you think you're that person, here are some tips for success:

1. Determine Your Timeline

''Magazines are typically released monthly, quarterly or annually,'' the Issuu blog explains. ''How much time will each issue need for content to come together? How frequently should this content be shared? In the strive for quality and quantity, it is important to ensure that one does not sacrifice the other.''

You want to give yourself enough time to produce quality content, but you don't want to spend so much time between issues that your audience forgets about you. Monthly or bi-quarterly is a good starting point.

2. Understand How the Supply Chain Works

Most people enter the magazine industry with an improper understanding of how the supply chain works. You don't print copies and sell them to distributors, who in turn sell them to your readers. It's not quite that easy.

''The first hard truth is that nearly all retailers stock your title on commission, meaning they only pay the distributor when they sell a copy, meaning the distributor only pays you at that time, meaning you take on 100% of the risk of printing,'' industry insider Steve Daniels writes.

You're also going to have trouble getting space in most major stores. This is prime real estate, and those stores are going to reserve that space for publications with high circulation.

Keeping both of these issues in mind, strategic partnerships become very important. You need inside access. Otherwise, you'll suffer through anonymity.

3. Find a Reliable Print Partner

There's no sense in going to a massive magazine printing company right off the bat. Your circulation numbers will be low on the front end. And there are really only a few things you're looking for: good prices, reliability, and hands-on customer service.

Smaller companies like Printing Center USA offer magazine printing services that the bigger guys don't. For instance, they offer one-stop printing, quick proof approvals, and fast turnarounds.

4. Accept Criticism with an Open Mind

You'll never last in this industry if you aren't willing to accept criticism. In fact, it'll take a while before you consistently receive positive feedback. Until then, it's imperative that you buckle down and apply the criticisms you receive. This is the best way to optimize and improve.

Never Say Never

At first, the idea of a print magazine seems crazy. However, as you think about it more, you may realize this is the opportunity you've been looking for. Give it a shot and see what happens. It could be incredibly rewarding.

The post 4 Tips for Launching a Successful Print Magazine in the Digital Age 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 SitePreferences. For example, to customize the USERAGENTNAME setting, create a HEADLINESPLUGIN_USERAGENTNAME setting in Main.SitePreferences.

  • One line description, shown in the TextFormattingRules topic:
    • Set SHORTDESCRIPTION = Show headline news in Foswiki 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 Foswiki's internal getUrl() method. Default: yes
    • Set USELWPUSERAGENT = yes

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

  • Name of user agent. Default: FoswikiHeadlinesPlugin/2.21.2
      * Set USERAGENTNAME = FoswikiHeadlinesPlugin/2.21.2

  • 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)
    • $Foswiki::cfg{PROXY}{HOST} - proxy host, such as "proxy.example.com";
    • $Foswiki::cfg{PROXY}{PORT} - proxy port, such as "8080";
    • $Foswiki::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

You do not need to install anything in the browser to use this extension. The following instructions are for the administrator who installs the extension on the server.

Open configure, and open the "Extensions" section. Use "Find More Extensions" to get a list of available extensions. Select "Install".

If you have any problems, or if the extension isn't available in configure, then you can still install manually from the command-line. See http://foswiki.org/Support/ManuallyInstallingExtensions for more help.

Check if above examples show a news feed instead of variable.

Plugin Info

Plugin Author: TWiki:Main.PeterThoeny, Foswiki:Main.MichaelDaum (2005-2007)
Copyright: © 2002-2009, Peter Thoeny, TWIKI.NET; 2005-2007, Michael Daum http://wikiring.de
License: GPL (GNU General Public License)
Release: 2.21.2
Version: 6822 (2010-03-21)
Change History:  
09 Mar 2010: can now use 0 properly with HEADLINESPLUGIN_REFRESH, HEADLINESPLUGIN_LIMIT, HEADLINESPLUGIN_USERAGENTTIMEOUT
08 Mar 2009: Ported without changes to Foswiki namespace by Kenneth Lavrsen and put under "Feel Free To Modify" in Foswiki context.
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.008
Home: Foswiki:Extensions/HeadlinesPlugin
Support: Foswiki:Support/HeadlinesPlugin
Topic revision: r1 - 13 Feb 2009, ProjectContributor
 

This site is powered by FoswikiCopyright © by the contributing authors. All material on this site is the property of the contributing authors.
Ideas, requests, problems regarding Wiki-Colivre? Send feedback