[Koha-bugs] [Bug 7843] Create RSS for OPAC news

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7843

--- Comment #4 from Viktor Sarge <viktor.sarge at regionhalland.se> ---
(In reply to Owen Leonard from comment #3)
> (In reply to Viktor Sarge from comment #2)
> 
> > * The news items have no individual links since there is no graphical view
> > of individual news items in the way that a blog would have. Is this a
> > problem for RSS-readers?
> 
> I think it could be potentially confusing. Maybe we should add an id to each
> news item header row and link to that as an in-page anchor?
> opac-main.pl#newsitem4

If we use an id that stays unique over time that would work quite well. I would
however like it better if we could create a view where news article are
displayed as single page items. Then we could also create a news archive where
news items are migrated as the time out. 

> > * Should we add additional metadata like author, administrator, publishing
> > dates etc?
> 
> I would add publish date. We don't store author or administrator information
> with individual news items so we can't show anything relevant there.

* I'll look into picking up publish date. I do think that the possibility of
auto displaying author would be great. If you run with that thought you might
even end up with auto created staff pages and a tab for "Our staff" you could
enable. 

> > * Currently the feed will display news for all libraries + your home branch
> > if you access it while logged in. Would only "all libraries" be better? Or
> > maybe all libraries + every item for individual branches?
> 
> I would assume that anyone who was looking at the RSS feed would be doing so
> in a feed reader outside the context of a logged-in session, so I'm not sure
> the home branch items are going to get seen. I don't like that the feed a
> logged-in user would see in their RSS reader would be different from the
> news they see on the site, but I'm not sure there's a better way to handle
> it. A feed for all libraries might be inappropriate or simply too much data.
> One option might be to offer the user a choice?
> 
>  - "All libraries" news plus the user's library
>  - "All libraries" news plus news for all libraries
> 
> I don't know how savvy users are with multiple RSS feeds.

* This is a bit of a problem. The quickest solution might be to only display
news that is for all libraries. But I think the actual problem is that you have
to log in to see news that should be public from the start. If we use the news
to customize the opac to be used as websites for all the different branches
then there should be a public way to navigate between branches. My suggestion
would be to only display "all libraries" in the RSS if we want to push this
functionality quick. Would looking (and searching) another branch than the home
branch you have on your account mess with anything?

-- 
You are receiving this mail because:
You are watching all bug changes.