Newsdesk Enhancements to Newsletters, Rich Atom, and Layout
April 11, 2013 Leave a Comment
We’ve been hard at work improving Newsdesk to bring our clients more of what they need. Here’s a rundown of what’s new in the April 11th update.
Table of Contents Options in Newsletter Templates
You now have a new way to customize your newsletters templates more fully. The Table of Contents is automatically generated and included at the top of email Newsletters.
You may choose from:
-
Table of contents (default)
-
No table of contents (new)
-
Table of Contents with article headlines (new)
Clean Layout
To make it easier to scan through the search results, the headline now appears below the source, author, and publish time.
The Twitter and Yammer icons have been updated and extraneous lines have been replaced by whitespace.
Rich Atom
For our “Rich Atom” feed format, we will now include a link to an XSD file that you can use to validate the returned XML. This brings us in line with industry standards.
If calls are made too frequently, a 429 “Too many requests” error will be returned. Calls for content should be spaced at least 60 seconds apart.
Enhancements to the “Add Articles” Feature
Articles that you manually add yourself can be translated directly from saved searches and Newsletters using Google Translate.
The language is set after clicking “Add Article” from a saved search’s drop-down menu.
Other Enhancements
-
To help manage large source lists, in the Advanced Sources tab, we have made the selection area larger and added sources are sorted alphabetically.
-
Further improvements to duplicate detection for similar articles.
-
Wildcards now work with case sensitive searching and Power Searches.
Log in to Newsdesk to see them for yourself and tell us what you think.
Filed under: Newsdesk features



Leave a Comment
XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
TrackBack URL | RSS feed for comments on this post.