0
Le IR, c’est mort.

                Dorothea Salo
             Repository Fringe
                 31 July 2008
!
Le IR, c’est I
               R
        le
    v e
             mort.
  i
V               Dorothea Salo
             Rep...
We thought...
                 IT...
          U I LD
      U B                       e!
    YO                       om
I...
We thought...                                “Resources? Staff?
                                          It’ll mostly run...
We thought...                                 “Resources? Staff?
                                            It’ll mostly ...
We thought...                                      “Resources? Staff?
                                                 It’...
We thought...                                      “Resources? Staff?
                                                 It’...
And so we built it.

 They didn’t come.
My job timeline
           June 2007:
        Repository budget
      slashed by one-third.



                      Octob...
Hey, wait up!
 “How do I cite                  “What is the           “Will someone
    this?”                   authorita...
Hey, wait up!
 “How do I cite                  “What is the           “Will someone
    this?”                   authorita...
The other downer

The top two words I utter about the software
     platform the repository is based on:




            “...
it y?
                    u n
                o $
             o #
     Deathfthroes
         o
      a pe
     quot;
 e
!
Software hammerlock
Our software made the same bad assumptions
we did!
So now we’re stuck with...
 ... workflows that don’t...
Hey, get with the program!
  We are on the Web, but not of it.
  We are not mashuppable. Not even with
  other library ser...
What are we, anyway?
                                                       Systems
     Researcher
                      ...
What are we, anyway?
                                                         Systems
     Researcher
                    ...
Let’s take a step back.
d !
                 o n
               eyb
               s
             ep back.
Let’s take a%step
           o
        ...
Beyond “green OA”
Self-archiving will not save us.
Peer-reviewed research is not all we care
about.
  Useful research prod...
Beyond silos
All of this is about more than where the
stuff resides! That’s the least of our worries.
We have to get stuff...
Beyond eternal demos

          I’m tired of watching
          good code fly by!
          How do we share
          innov...
My job timeline
           June 2007:
        Repository budget
      slashed by one-third.



March 2007:           Octob...
My job timeline
                                March 2008:
           June 2007:          WG makes radical
        Reposi...
Variations on a theme in
H
Variations on a theme in
Harvesting
The content is out there. We just have to
get our hands on it.
APIs? (What if they won’t use ours?)
Rights?
Rel...
Healing
Contused metadata
 If we’re swapping metadata and whole items,
 why aren’t we correcting each other?

Dislocated s...
Helping
Idealism isn’t enough. We have to make
ourselves useful.
 ... to our administrations
 ... to our faculty

How?
 Ea...
Hope
Funders are on the move.
Faculty have trailblazers to consider.
Librarians are taking note of process,
not product.
P...
Starting to fit in
y!
             &
           a in
  Startingn fit
       fi
   .
          to

..
Imperial College, London
                                                     of this
                                    ...
ePrints:
             Usability Counts!
“We... apply a Spock approach—the needs
 of the many outweigh the needs of the few...
il!
                ePrints:
                                                      a
                                     ...
Chris Rusbridge:
-ve clicks, +ve value!
Andy Powell:
       Communicating




Andy Powell, “Web 2.0 and repositories: have we got
                our repository a...
Paul Walk:
        Fitting in with the Web
                                “I wonder if the user-
                        ...
SPARC, DRIVER and JISC
                                     “... joint
                            commitment to promote
 ...
SPARC, DRIVER and JISC
                                                    “... joint
                    SWAP            ...
SPARC, DRIVER and JISC
                                                    “... joint
                    SWAP            ...
We can do this.

    Have sense!
    Have fun!
    Have at it!
s!
 We can do this.

           n  *
       s-
    n fun!
  o
  Have sense!

 &Have at it!
A
  Have
Credits
http://flickr.com/photos/laffy4k (We thought...)

http://flickr.com/photos/oneservant2go (We built it)
http://flickr....
Upcoming SlideShare
Loading in...5
×

Le IR, c'est mort. Vive le IR!

5,072

Published on

Keynote at Repository Fringe 2008 in Edinburgh, Scotland.

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
5,072
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
8
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Transcript of "Le IR, c'est mort. Vive le IR!"

  1. 1. Le IR, c’est mort. Dorothea Salo Repository Fringe 31 July 2008
  2. 2. ! Le IR, c’est I R le v e mort. i V Dorothea Salo Repository Fringe 31 July 2008
  3. 3. We thought... IT... U I LD U B e! YO om I F il lc w th ey ...
  4. 4. We thought... “Resources? Staff? It’ll mostly run itself.” “Everybody wants open access!” “All we’ll take is the peer-reviewed research literature.” “We did all the planning. So everything will be just fine.”
  5. 5. We thought... “Resources? Staff? It’ll mostly run itself.” “Customization? It works out of the “Oh, come on, box!” they can just hack it to do that!” “Everybody wants open access!” “All we’ll take is the peer-reviewed research literature.” “We did all the planning. So everything will be just fine.”
  6. 6. We thought... “Resources? Staff? It’ll mostly run itself.” “Customization? “Dublin Core is It works out of the plenty good enough.” “Oh, come on, box!” they can just hack it to do that!” “Everybody wants open access!” “All we’ll take is the peer-reviewed research literature.” “We did all the planning. So everything will “Document versioning? be just fine.” But all we want is the final version, right?”
  7. 7. We thought... “Resources? Staff? It’ll mostly run itself.” “Customization? “Dublin Core is It works out of the plenty good enough.” “Oh, come on, box!” they can just hack it “Sure, they’ll type to do that!” “Everybody wants open access!” keystrokes!” is the “All we’ll take peer-reviewed research literature.” “We did all the planning. So everything will “Document versioning? be just fine.” But all we want is the final version, right?”
  8. 8. And so we built it. They didn’t come.
  9. 9. My job timeline June 2007: Repository budget slashed by one-third. October 2007: March 2007: I am asked to chair WG I start. on repository future. Part of WG charge: “Figure out how we’ll fund you.”
  10. 10. Hey, wait up! “How do I cite “What is the “Will someone this?” authoritative version plagiarize me?” of record?” “Will my “Will I be publisher be upset?” “Will someone sued for violating violate my copyright or copyright?” steal my idea?” “Will I get “Is my credit toward tenure institution trying to be “What do I and promotion?” Big Brother?” put here?”
  11. 11. Hey, wait up! “How do I cite “What is the “Will someone this?” authoritative version plagiarize me?” of record?” “Will my “Will I be publisher be upset?” “Will someone sued for violating “I don’t understand.” violate my copyright or copyright?” steal my idea?” “Will I get “Is my credit toward tenure institution trying to be “What do I and promotion?” Big Brother?” put here?”
  12. 12. The other downer The top two words I utter about the software platform the repository is based on: “I’m sorry.”
  13. 13. it y? u n o $ o # Deathfthroes o a pe quot; e !
  14. 14. Software hammerlock Our software made the same bad assumptions we did! So now we’re stuck with... ... workflows that don’t work... ... defaults and designs that make no sense... ... protocols that don’t do enough... ... services we want to offer but can’t... ... stunning, appalling amounts of redundant effort aimed at redressing these problems.
  15. 15. Hey, get with the program! We are on the Web, but not of it. We are not mashuppable. Not even with other library services! We are ugly and unusable. We’re not 2.0. We’re not even 1.0b. We are missing opportunity because of this! How much more can we afford?
  16. 16. What are we, anyway? Systems Researcher administrator ETD coordinator Systems analyst Liaison librarian Research programmer Scholarly communication Repository librarian coordinator Data curator Metadata librarian Grant administrator
  17. 17. What are we, anyway? Systems Researcher administrator ETD coordinator Systems analyst How doprogrammer Research we work Liaison librarian together? communication Scholarly Repository librarian coordinator Data curator Metadata librarian Grant administrator
  18. 18. Let’s take a step back.
  19. 19. d ! o n eyb s ep back. Let’s take a%step o tw en !
  20. 20. Beyond “green OA” Self-archiving will not save us. Peer-reviewed research is not all we care about. Useful research products happen long before publication! Who will care for them? Open access as byproduct, not end-product If we’re part of the process, we have better claim to the results.
  21. 21. Beyond silos All of this is about more than where the stuff resides! That’s the least of our worries. We have to get stuff, give stuff, mash up stuff, expose stuff, manage stuff, help with stuff. No matter where it lives! The self-archiving paradigm didn’t have a management component, much less offer any cogent help.
  22. 22. Beyond eternal demos I’m tired of watching good code fly by! How do we share innovations more widely? How do we mainstream them? Not just about code!
  23. 23. My job timeline June 2007: Repository budget slashed by one-third. March 2007: October 2007: I start. I am asked to chair WG on repository future. Part of WG charge: “Figure out how we’ll fund you.”
  24. 24. My job timeline March 2008: June 2007: WG makes radical Repository budget suggestion: slashed by one-third. “Le IR, c’est mort.” March 2007: October 2007: July 2008: I start. I am asked to chair WG WG report suggests on repository future. “Vive le IR!” Part of WG charge: “Figure out how we’ll AS A SUITE OF fund you.” SERVICES AND SOLUTIONS.
  25. 25. Variations on a theme in
  26. 26. H Variations on a theme in
  27. 27. Harvesting The content is out there. We just have to get our hands on it. APIs? (What if they won’t use ours?) Rights? Relations with commercial services? With disciplinary repositories? Compiled statistics for duplicate deposits? (We know they want ’em!)
  28. 28. Healing Contused metadata If we’re swapping metadata and whole items, why aren’t we correcting each other? Dislocated silos Paper plus data Your institution, my institution, their discipline IR, digital library, research storage... Again: are we of the Web, or just on it? Bruised egos We haven’t covered ourselves with glory here. It’s time to mend some fences.
  29. 29. Helping Idealism isn’t enough. We have to make ourselves useful. ... to our administrations ... to our faculty How? Early intervention? Add-on services? Or maybe we just don’t know yet—so let’s turn people loose to help others!
  30. 30. Hope Funders are on the move. Faculty have trailblazers to consider. Librarians are taking note of process, not product. Programmers are moving toward flexibility. We are all rethinking our initial assumptions.
  31. 31. Starting to fit in
  32. 32. y! & a in Startingn fit fi . to ..
  33. 33. Imperial College, London of this tion g the crea ddin g the mbe king ly rin by e or du ’s w ificant tive option itution ign jec ad s ob re inst were ipal ensu in the ion rinc s to y pt .” nes he p wa “T ive epl to ado moved de rs har d Jo e Ric h arc ositor t b y so arrie if not r and p ha wered, ari re tice s, t lo Afsh c teh pra Fe resh —
  34. 34. ePrints: Usability Counts! “We... apply a Spock approach—the needs of the many outweigh the needs of the few. So end-users are most important, followed by depositors, followed by editors, followed by librarians, etc.” “EPrints 3.1 is a little different... to make administering it easier. We've introduced web-based configuration editing, many more configuration files... reload if changed (saving restarts), and... an issue discovery system (duplicate titles etc).” —Christopher Gutteridge
  35. 35. il! ePrints: a tm Usability Counts! o H rr “We... apply a Spock approach—the needs a a n C of the many outweigh the needs of the few. ' ) So end-users are most important, followed L s by depositors, followed by editors, followed l' by librarians, etc.” — s ck configuration editing, many more “EPrints 3.1 is a little different... to make u administering it easier. We've introduced S s: web-based t configuration files... reload if changed (saving n ( restarts), and... an issue discovery system eP (duplicate titles etc).” —Christopher Gutteridge
  36. 36. Chris Rusbridge: -ve clicks, +ve value!
  37. 37. Andy Powell: Communicating Andy Powell, “Web 2.0 and repositories: have we got our repository architecture right?”
  38. 38. Paul Walk: Fitting in with the Web “I wonder if the user- centric/institutional/ global debate around repositories is just symptomatic of a tension about to become apparent all over the (institutional) Web?” Paul Walk, —Paul Walk “Repository Architecture #83”
  39. 39. SPARC, DRIVER and JISC “... joint commitment to promote a European network of repositories... across institutional and national boundaries....” “... a common lobby at a national and international level to leverage change...”
  40. 40. SPARC, DRIVER and JISC “... joint SWAP commitment to promote SWORD a European network of ePrints repositories... across SHERPA/RoMEO institutional and national boundaries....” SPECTRa RepoMMan Common Repositories CLADDIER Interface Group “... a common lobby at a national and OpenDOAR international level to leverage change...” EThOS
  41. 41. SPARC, DRIVER and JISC “... joint SWAP commitment to promote SWORD a European network of ePrints repositories... across SHERPA/RoMEO institutional and national boundaries....” SPECTRa RepoMMan Common Repositories CLADDIER Interface Group “... a common OpenDOAR lobby at a national and international level to Repository leverage change...” EThOS Fringe 2008
  42. 42. We can do this. Have sense! Have fun! Have at it!
  43. 43. s! We can do this. n * s- n fun! o Have sense! &Have at it! A Have
  44. 44. Credits http://flickr.com/photos/laffy4k (We thought...) http://flickr.com/photos/oneservant2go (We built it) http://flickr.com/photos/emdot (Software hammerlock) http://flickr.com/photos/philon (Hey, wait up!) http://flickr.com/photos/moriza (Hey, get with the program!) http://flickr.com/photos/peasap (Beyond eternal demos) http://flickr.com/photos/annia316 (Beyond green OA) http://flickr.com/photos/darynbarry (Beyond silos) http://flickr.com/photos/cyron (Harvesting) http://flickr.com/photos/gaetanlee (Helping) http://flickr.com/photos/erkcharlton (Healing) http://flickr.com/photos/wetsun (Hope) http://flickr.com/photos/archie4oz (Imperial College, London) http://flickr.com/photos/kevincollins (ePrints) This work is licensed under a Creative Commons Attribution 3.0 License.
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×