Ticket #1504 (closed defect: fixed)

Opened 12 years ago

Last modified 11 years ago

Description in RSS feed is not human-readable

Reported by: hans Owned by: jukka
Priority: critical Milestone:
Component: generic Version:
Keywords: Cc:
Time planned: Time remaining:
Time spent:

Description (last modified by hans) (diff)

Description in "What's going on?" RSS feed is not human-readable:

<item rdf:about="http://lemill.net/content/social-networking-tools-for-learning">
    <link>http://lemill.net/content/social-networking-tools-for-learning</link>
    <title>[LR] Social networking tools for learning</title>
    <description>28044400ed5429300b69eed6b85dc3fc</description>
    <dc:creator>Hans</dc:creator>        
    <dc:rights></dc:rights>                
    <dc:date>2007-08-26T22:20:26Z</dc:date>  
</item>

In RSS reader it looks like this:

http://lemill.org/trac/attachment/ticket/1504/whats_going_on_rss_feed.png?format=raw

Human-readable description should be:

<a href="http://lemill.net/content/social-networking-tools-for-learning">Social networking tools for learning</a> was changed by <a href="http://lemill.net/community/Hans">Hans Põldoja</a>

Attachments

whats_going_on_rss_feed.png (15.3 KB) - added by hans 12 years ago.

Change History

Changed 12 years ago by hans

comment:1 Changed 12 years ago by hans

  • Description modified (diff)

comment:2 Changed 12 years ago by pjotr

This one seems to be all about the getRSSDescription method.

It seems to be defined for MemberFodler?, but in all the other cases the system seems to be using the getBody method (that one is giving out that unreadable line) or nothing.

For GroupBlog it does not return anything, so I suppose we will also need to define that method there to use (return self.getDescription()). Or something like that.

comment:3 Changed 12 years ago by pjotr

I think that the easiest is to just populate the Description of the portal_catalog entry for the object (We have it there anyway).

Some of the objects (like Piece) have the description already. Some (like PILOT) have a suitable field where to take that description from (shortDescription). For others we will have to think of something.

Or this is not a good solution?

Then we should anyway have some place to take it from. This will also be good for Exporting the Metadata into other places. As we will not have so many just empty Descriptions.

comment:4 Changed 11 years ago by jukka

  • Owner changed from anonymous to jukka
  • Status changed from new to assigned

comment:5 Changed 11 years ago by jukka

  • Status changed from assigned to closed
  • Resolution set to fixed

Looks like this is fixed, as I couldn't find any place where description can be given such values.

Note: See TracTickets for help on using tickets.