Difference between revisions of "Talk:PubMan Web Syndication Feeds"

From MPDLMediaWiki
Jump to navigation Jump to search
 
Line 43: Line 43:
<channel>
<channel>
<title>FACES</title>
<title>FACES</title>
<link>http://faces.mpdl.mpg.de/resources/images/Faces/mpi_hd.png</link>
<link>http://www.mpib-berlin.mpg.de/</link>
<description>A database of facial expressions in younger, middle-aged, and older women and men</description>
<description>A database of facial expressions in younger, middle-aged, and older women and men</description>
<logo url="http://www.mpib-berlin.mpg.de/" />
<logo url="http://faces.mpdl.mpg.de/resources/images/Faces/mpi_hd.png" />




Line 63: Line 63:
</pre>
</pre>


Feed link will presented on the pictures browsing pages for complete collection with the concerned sorting.
Feed link will presented on the browsing page for the complete collection (no pagination!)  with the concerned sorting.  


Feed URL:
Feed URL:

Latest revision as of 15:01, 20 November 2009

Feed for search results[edit]

  • each advanced search for the logged in user
Question: Why restricting this functionality to logged in users? --Inga 14:41, 17 September 2008 (UTC)
Vlad : Agree, can be extended for the case.

Naming[edit]

feedermanager sounds somewhat weird to my ears. wouldn't syndication_manager be better? Robert 11:21, 23 September 2008 (UTC)

Agree --Makarenko 15:37, 13 November 2008 (UTC)

Interfaces[edit]

Implementation[edit]

  • must the structured export manager be redesigned to deal with feed information?
    • the idea is - this to be done in SyndicationManager and the structured export manager to only deal with feed-entries transformation i.e. like mapping to any metadata format --Natasa 14:00, 13 November 2008 (UTC)
      • agree --Makarenko 14:39, 13 November 2008 (UTC)
    • StructuredExportManager should distinguish the context (e.g. Faces, PubMan, VIRR) to be able to apply correct transformations since MD sets are different for applications. Possible solutions:
      • XSLT parses the item list and applies appropriate transformation for the item
        • Advantages: the only XSLT should be changed and not the service.
        • Disadvantages: a) lack of functionality for string processing in XPATH (but, probably, enough for the purpose); b) no way to use ROME
      • move transformation functionality from XSLT to the ROME
        • Advantages: a) simple and standardized approach to generate WSF of all supported formats, b) java string processing, c) fast development, d) JBOSS integration
        • Disadvantages: StructuredExportManager should be redesigned to adopt ROME
--Makarenko 15:39, 13 November 2008 (UTC) On my opinion, the ROME has more advantages against XSLT.

--Makarenko 16:49, 14 November 2008 (UTC) Decision: all functionality should be presented only in the syndication manager to avoid complexity.

Media RSS Module (mrss)[edit]

Media RSS specifications is here. MRSS to be implemented as RSS 2.0 module. Cooliris delivers the 3D presentation of the pictures with the FF addon.

At the first stage the module will be implemented for the Faces / Diamonds projects. Next to be implemented for PubMan and VIRR for all attached components of types: jpg, png, gif.

Start up mapping for Faces:

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:media="http://search.yahoo.com/mrss/">
	<channel>
<title>FACES</title>
<link>http://www.mpib-berlin.mpg.de/</link>
<description>A database of facial expressions in younger, middle-aged, and older women and men</description>
<logo url="http://faces.mpdl.mpg.de/resources/images/Faces/mpi_hd.png" />



	   <item>
		   <title>file_name</title>
<!-- 			   (i.e. Face item metadata compressed) -->
		   <media:description>Face expression: <emotion>, <age-group>, <gender>, <picture-set>, <age>, <person-id></media:description>
                   <guid>escidoc.objid</guid>
		   <link>coreservice-url to face item</link>
		   <media:thumbnail url="coreserviceurl to thumbnail"/>
		   <media:content url="coreservice-url to web resolution"/>
                   <content:encoded>escidocItem encoded</content:encoded>
	   </item>
	</channel>
</rss>

Feed link will presented on the browsing page for the complete collection (no pagination!) with the concerned sorting.

Feed URL:

http://faces.mpdl.mpg.de/syndication/feed/${feedType}/${firstSortGroup}/${firstSortGroupOrder}/${secondSortGroup}/${secondSortGroupOrder}/${thirdSortGroup}/${thirdSortGroupOrder}

For example:

http://faces.mpdl.mpg.de/syndication/feed/rss_2.0/escidoc.face-item.picture-group/desc/escidoc.face-item.age/desc/escidoc.face-item.identifier/desc

TODO: