Table of Contents
News articles in Plone are instances of the 'News Item' content type: they can contain a title, a description, a body text, an image and some basic metadata. If you publish a couple of items from time to time, this is fine.
But suppose you have to publish dozens of items everyday... How do you tell your readers who they are about? What do they cover? Where do they took place? And, more important, how do you classify them? How do you organize them? How do you tell your readers which ones are newsworthy?
To solve these, and other issues, the IPTC developed XML standards to define the content and structure of news articles. NITF, NewsML and NewsCodes are among these standards and they support the classification, identification and description of a huge number of news articles characteristics.
NITF is intended to structure independent news articles and this package aims to implement a content type inspired by the specification.
Got an idea? Found a bug? Let us know by opening a support ticket.
To enable this product in a buildout-based installation:
Edit your buildout.cfg and add
collective.nitfto the list of eggs to install:
[buildout] ... eggs = collective.nitf
After updating the configuration you need to run ''bin/buildout'', which will take care of updating your system.
Go to the 'Site Setup' page in a Plone site and click on the 'Add-ons' link.
Check the box next to
collective.nitf and click the 'Activate' button.
You may have to empty your browser cache and save your resource registries in order to see the effects of the product installation.
This package includes a behavior called
By applying it to a Dexterity-based content type you will get a new field called
All news articles provide @@nitf and @@newsml views that are available although are not registered.
You can validate the output of the those views using services like XML validation.
collective.nitf uses Cycle2 slideshow plugin for jQuery and it can load its resources from the Plone JS registry if they are present there.
If you're using
collective.nitf with other packages that use Cycle2 also (like sc.photogallery or covertile.cycle2),
it is highly recommended that you register those resources to load them once and avoid conflicts.
You can use a
jsregistry.xml file that includes the following: