Powered By IdeaScale - try it free Login/Signup

Repositories - communicating the idea

« Back To JISC Repositories
The repository should have more "web 2.0" features
Posted by c.rusbridge 07/14/2008 07:00 AM GMT+00:00
Again, the Andy Powell idea. This one, I think, more about sharing, embedding, mashups. Think Flickr. Think sneep.
Idea # 18Category/Tags : Repository functions (10)  (9)  
Comments
a.mcgregor
07/14/2008
I agree with this but the term Web 2.0 covers a lot of ground. Is it worth being a bit more specific about what parts of web 2.0 are the most important?

e.g.
The network effect - concentrating users in one place and using that concentration of users to provide useful services.

Social networks around research outputs or learning objects - providing services that help academics manage the various social interactions around their content?
Paul Walk
07/17/2008
Chris,
This is the one I really disagree with I think!

The repository should be able to participate in an interactive Web. It should be entirely possible for someone else to build a remote Web 2.0 service around resource exposed in my repository. This does not preclude me building such a service - if I think I have sufficient mass of interested users etc. but if I *need* to do this because only I can, then I have probably just built another silo.

This is what I meant by my assertion that, in general, Technorati offers us a better model than Slideshare. Someone can build a better, more focussed, domain specific etc. version of Technorati if there is demand for this, without needing to move or copy the resources in their 'source repositories' (blogs, in this case).

Paul Walk
dorothea.salo
07/18/2008
Paul scooped me. That's more or less what I wanted to say.
Richard Davis
07/18/2008
It may be possible to agree with Paul, who disagrees with Chris, without disagreeing with Chris (who may even agree with Paul)!

IMO, ideally a repo would be susceptible to all sorts of Flickrish RSS, Web API type manipulation - SWORD-like and who knows what else - leading to total personalisation potential of the user experience.

OTOH, providing implementers and users with an acceptable out-of-the-box UI, that might include basic implementations of some voguish features, and widgety ways to configure them - cf. Flickr or Wordpress - is no bad thing either.

I don't much like the default UIs for Eprints or DSpace, or most of the variants they end up as. It must be possible to provide something better - otherwise the developers might as well abdicate all responsibility for a UI and just ship a bunch of libraries/APIs...

The Wordpress model of contributed, open source themes appeals - does anything like this go on in repository land - with Fedora or Manakin maybe?
Richard Davis
07/18/2008
Sorry should have said agree with the proposal rather than personalising it, I realise Chris is facilitating :)
Files/Attachments
Related Topics/Ideas
Title

Category/Tags : Repository functions (10)  (9)  

Category/Tags : Repository functions (10)  (9)  

Category/Tags : Repository functions (10)  (9)  

Category/Tags : Repository functions (10)  (9)  

Category/Tags : Repository functions (10)  (9)  

Category/Tags : Repository functions (10)  (9)  

Category/Tags : Repository functions (10)  (9)  

Activity Chart
Track/Publish/Promote
  • Users Tracking (3)
Privacy Policy   |   Terms of Use
Idea Management