• Use cases

last modified November 22, 2006 by jladage

Inbound Syndication (Feedfeeder)

    √ feedfeeder view (links in feedfolder view should point to the
      feed-items)
    √ add summary to the feedfolder view if it's there.
    √ feeditems view should link to the source content.
    √ Automatic transitionto  a workflow state configurable on a feedfolder

    With regards to the workflow it is required to have direct transitions to each end state which can be selected. Because there's no way to find out a path of multiple transition to get to a end state.

    * extend feed-item which the category field or other optional fields.
    √ navigation on the feed folder view (batches)
    * auto-delete items (configuration of the periode or number and
      enable/disable checkbox)


Outbound Syndication

    √ look into BaseSyndication / FATSyndication for atom output
    * out-going rss/atom configuratable number of items
    * if RSS is coming in and gets republish it as atom, uids should be
      generated for them (look how they did this at: 
      planet.intertwingly.net/code/venus).
    * portal_syndication has to be replaced eventually:
      √ enable on all folder
      - enable, but set individually

Between Plone Sites

    * Allow full read-only content types creation when using feedfeeder and atom between two plones!
      Events is probably most interesting.
    * Or even 'every' AT base type.

Jon Stahl had some notes