| http://libguides.caltech.edu |
7225 |
| http://repositoryman.blogspot.com |
393 |
| http://www.proyectoagrega.es |
88 |
| http://tallerciencia20.blogspot.com |
44 |
| http://courseresources.derby.ac.uk |
23 |
| https://courseresources.derby.ac.uk |
13 |
| http://bbapp01-tst.derby.ac.uk |
13 |
| https://bbapp01-tst.derby.ac.uk |
11 |
| http://bbapp03.derby.ac.uk |
10 |
| http://bbapp04 |
7 |
| https://crtest.derby.ac.uk |
7 |
| http://tallerciencia20.blogspot.com.ar |
6 |
| https://bbapp02-tst.derby.ac.uk |
5 |
| http://bbapp01.derby.ac.uk |
5 |
| http://bbapp04.derby.ac.uk |
4 |
| http://repositoryman.blogspot.co.uk |
4 |
| https://bbapp01.derby.ac.uk |
4 |
| http://translate.googleusercontent.com |
3 |
| http://libguides.mountainviewcollege.edu |
3 |
| http://bbapp01-tst |
3 |
| http://bbapp02.derby.ac.uk |
3 |
| http://131.253.14.98 |
2 |
| http://derbyresearchrepository.pbwiki.com |
2 |
| http://www.slideshare.net |
2 |
| https://ubb-app.derby.ac.uk |
2 |
| http://ubb-app.derby.ac.uk |
2 |
| http://0-libguides.caltech.edu.innopac.up.ac.za |
2 |
| https://derbyresearchrepository.pbworks.com |
1 |
| http://agrega.avanzo.com |
1 |
| http://tallerciencia20.blogspot.ru |
1 |
| http://repositoryman.blogspot.nl |
1 |
| http://tallerciencia20.blogspot.mx |
1 |
| http://tallerciencia20.blogspot.com.es |
1 |
| https://bbapp03.derby.ac.uk |
1 |
| http://bbapp02-tst.derby.ac.uk |
1 |
| http://urban-spoken.blogspot.com |
1 |
| http://repositoryman.blogspot.de |
1 |
| http://static.slidesharecdn.com |
1 |
| http://ubb-app-tst.derby.ac.uk |
1 |
| http://repositoryman.blogspot.com.au |
1 |
Subscribing to the repositoryman blog as we speak. 4 years ago
I think there's a complementary presentation that would fit with this - ways to get things *in to* repositories that don't look like the conventional (ineffectual) user-driven, forms-driven upload models, e.g. what would a repository that actually existed within a syndicated, web 2.0 landscape look like. This preso does a good job illustrating the ways content can flow and be promoted once in a repository. That one would illustrate how a repository can respect and harness the ways in which people are already publishing. Together, they might show a repository that finally serviced it's owner's ends (ultimately the 'institution,' much as we might regret it) while not forcing the *actual end users* to be the ones to pay for this. <end of rant? anyways, nice job. 4 years ago