What You're Up Against
Upcoming SlideShare
Loading in...5
×
 

What You're Up Against

on

  • 4,784 views

Given for the PALINET workshop on institutional repositories, 3 December 2007.

Given for the PALINET workshop on institutional repositories, 3 December 2007.

Statistics

Views

Total Views
4,784
Views on SlideShare
2,413
Embed Views
2,371

Actions

Likes
0
Downloads
3
Comments
0

6 Embeds 2,371

http://dsalo.info 2336
http://gavialib.com 23
http://webcache.googleusercontent.com 9
http://www.slideshare.net 1
http://anonymouse.org 1
http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

What You're Up Against What You're Up Against Presentation Transcript

  • What You’re Up Against Dorothea Salo Digital Repository Librarian University of Wisconsin 3 December 2007
  • Let’s start a repository! The Faculty have all their work sof twa just lying around... re is fre they’ll love having a place e! It’s essential to store it! infrastructure! The metadata’s easy, just Dublin Core! xing re fi ly All we have to do is set it up! We’ olar Maybe a little marketing... s ch cation! uni Faculty will do the rest! c omm All we need is a mandate!
  • Reality check The If it’s important, it’s been sof twa published. If it’s not, they re is don’t know where it is, use les Nobody needs s. and don’t care. these things. The word “metadata” scares faculty. ave e rs h with lish ned Faculty won’t hear about it, Pub gun lty. won’t understand it, us out n facu and won’t do anything with it. ou r ow We can’t tell faculty what to do.
  • Fundamental ideology
  • Fundamental ideology I T. .. U I LD U B e! YO co m IF w ill th ey ...
  • Well, we built it. They aren’t coming.
  • Faculty: the few •Peter Suber •Stevan Harnad •Physics and computer science •“Open Access Anthropology” •Editorial revolts •Faculty-senate initiatives
  • Faculty: the many •Worried about their reputations •Worried about their societies •Don’t care about our problems •Unaware how much they’re giving up •Unwilling or unable to change their workflows (and we’re not helping much)
  • Keystrokes?! (you expect them to type actual keystrokes?) • Faculty have never preserved their work before. Why should they have to do it now? • Do they know where their work is? • Do they own rights to it? Do they care? • Our interfaces are horrible. All of them. • Do they trust us to do this? Do they know we do it? • What’s in it for them?
  • The basic problem is... ve n t. . . h a wa n’t t y do u l W fe ac t, ng an yt hi lt yw a n cu e . f a av at ’t h h n d w e do an w ... THE IDEOLOGY HAS FAILED.
  • Pernicious effects “Resources? Staff? But faculty are “Training? doing all the work, Encouragement? right?” Mediated deposit? Bah, a deposit only takes ten minutes!” “We did all the planning. So everything will be just fine.”
  • Pernicious effects “Resources? Staff? But faculty are “My publisher will hate me “Training? doing all the work, and I’ll never get tenure and no one Encouragement? right?” will respect me again and I’ll Mediated deposit? Bah, a throw myself off a bridge...” deposit only takes ten “Of course I minutes!” own the rights! I wrote it, didn’t I?” “We did all the planning. So everything will be just fine.”
  • Pernicious effects “Resources? Staff? But faculty are “My publisher will hate me “Training? doing all the work, and I’ll never get tenure and no one Encouragement? right?” will respect me again and I’ll Mediated deposit? Bah, a throw myself off a bridge...” deposit only takes ten “Of course I minutes!” own the rights! I “Customization? wrote it, didn’t It works out of the I?” box!” “Versioning in the software? All we want is the final product!” “We did all the planning. So everything will be just fine.”
  • Pernicious effects ... *poke* *poke*... “Resources? Staff? But faculty are “My publisher will hate me “Training? doing all the work, and I’ll never get tenure and no one Encouragement? right?” will respect me again and I’ll Mediated deposit? Bah, a throw myself off a bridge...” deposit only takes ten “Of course I minutes!” own the rights! I “Customization? wrote it, didn’t It works out of the I?” box!” “What’s that thing “Versioning got to do with me?” in the software? All we want is the final product!” “We did all the planning. So everything will be just fine.”
  • Pernicious effects ... *poke* *poke*... “Resources? Staff? But faculty are “My publisher will hate me “Training? doing all the work, and I’ll never get tenure and no one Encouragement? right?” will respect me again and I’ll Mediated deposit? Bah, a throw myself off a bridge...” deposit only takes ten “Of course I minutes!” own the rights! I “Customization? “How dare you wrote it, didn’t It works out of the take in student projects I?” box!” (learning objects, images, digitized special collections, etc.)? Repositories are about the “What’s that thing “Versioning got to do with me?” PEER-REVIEWED in the software? All LITERATURE!” we want is the final product!” “We did all the planning. So everything will be just fine.”
  • Pernicious effects ... *poke* *poke*... “Resources? Staff? But faculty are “My publisher will hate me “Training? doing all the work, and I’ll never get tenure and no one Encouragement? right?” will respect me again and I’ll Mediated deposit? Bah, a throw myself off a bridge...” deposit only takes ten “Of course I minutes!” own the rights! I “Customization? “How dare you wrote it, didn’t It works out of the take in student projects I?” box!” (learning objects, images, digitized special collections, etc.)? Repositories are about the “What’s that thing “Versioning got to do with me?” PEER-REVIEWED in the software? All LITERATURE!” we want is the final product!” Why is it so empty? “We did all the planning. So Where did we go wrong? everything will be just fine.” Where did I go wrong?
  • The simple fact is... ... nobody’s coping well with the ideology failure. Not in the United States, anyway.
  • Two choices • You can make your service valuable to faculty on FACULTY TERMS... • ... which means a lot of design and development work, because repository software is so hopelessly bad... • ... or hooking the repository to a sturdier bandwagon... • Or you can do the deposit work on their behalf... • ... which means a lot of software and workflow development, as well as ongoing costs.
  • Two choices • You can make your service valuable to faculty on FACULTY TERMS... • ... which means a lot of design and development work, because repository software is so hopelessly bad... • ... or hooking the repository to a sturdier bandwagon... • Or you can do the deposit work on their behalf... • ... which means a lot of software and workflow development, as well as ongoing costs. • NOTHING ELSE WORKS. • If you can’t commit to one or the other, get out of this business (or don’t get into it in the first place).
  • The software • If you have the choice, go for EPrints. • Arrange a customization workflow with IT up-front. • You will have to customize it. Repeatedly. • If IT won’t let you or help you, forget it. • Think now about how to integrate with other campus content-creation services. • Pay attention to SWORD. Close attention. • Got webspace? Build in an “Archive It!” button.
  • The service model • The repository by itself is useless. • But it can form part of useful services: • Research assessment and faculty bibliographies. • Retirement archiving. • Publishing and copyright consulting or assistance. • Collaboration and other cyberinfrastructure spaces. • Conference capture and archival. Small-journal archival. • ETDs. • Figure out the services you can offer that fit your faculty’s needs and your goals.
  • You and your colleagues • You need to win Most Collegial awards. • Your colleagues won’t help the IR, but they might help you. • You need your library administrators’ ear. And their help. • You can’t get a mandate. • You can’t require ETDs. • You can’t allocate library staff time or funding. • You can’t even talk to provosts and deans and IT brass. • Start beating the drum now, and don’t stop.
  • You and me • We do not have a community of practice. • No journals, just “special issues.” • No regular conferences (in the US), just random workshops. • No professional associations, or even SIGs. • Not even a lousy mailing list! • We are not sharing... ed at. • ... policies. g talk not re bein rtainly • ... code. t , we’ and ce hing d to, d to. • ... ideas. If any alke tene N ot t lis • ... the burden. • I can’t fix this one alone. I’ve tried.
  • Credits • http://flickr.com/photos/jacobrask (Cover) • http://flickr.com/photos/purpleslog (Let’s start) • http://flickr.com/photos/bossco (Reality check) • http://flickr.com/photos/laffy4k (Fundamental ideology) • http://flickr.com/photos/oneservant2go (We built it, The basic problem, The simple fact) • http://flickr.com/photos/rickabbott/ (Faculty: the many) • http://flickr.com/photos/DeclanTM (Keystrokes) • http://flickr.com/photos/anonfx (Two choices) • http://flickr.com/photos/alex-photos (The software) • http://flickr.com/photos/myklroventine (Service models) • http://flickr.com/photos/richardsummers (You and your colleagues) • http://flickr.com/photos/kazk (You and me)
  • Thank you! ... and good luck! dsalo@library.wisc.edu AIM: mindsatuw This work is licensed under a Creative Commons Attribution 3.0 License.