1. Cornell University – March 20, 2009 BIBAPP: A CAMPUS RESEARCH GATEWAY AND EXPERT FINDER SARAH L. SHREEVES UNIVERSITY OF ILLINOIS AT URBANA-CHAMPAIGN

2. BibApp developed by…. -- Still Under Development -- University of Wisconsin at Madison ================= Eric Larson Dorothea Salo University of Illinois at Urbana-Champaign =============== Tim Donohue Bill Ingram Sarah Shreeves

3. So what are the issues?

4. Libraries  Talk to faculty about archiving and scholarly communication issues  Market institutional repositories and look for ways to easily deposit  Faculty want something that gives access to ALL publications not just what is available in repository  Faculty are not motivated to archive, but if the library can help do this, "that's probably the right thing to do..."

5.  Don’t keep track of their publications and responsibility is typically passed to someone else  Need lists of their publications for easy import into grant applications and other reports  Comprehensiveness may be unnecessary for tenured faculty, but is extremely important for untenured faculty. Currency is important to everyone.  Citation re-use is extremely important; faculty often have to contribute publication lists to multiple places.  Faculty want to be able to highlight certain publications over others. Faculty

6. Departments / Centers  Publication lists are very important for recruiting new grad students and for research centers  Organizing publications is often the hardest part of a departmental annual report.

7. Universities  Often do not understand collaborations across campus  Often do not understand shifts in scholarly publishing patterns over time (obvious implications for librarians as well)

8. Faculty directory information + Publication lists + Sherpa / Romeo archival database + OpenURL resolver + SWORD (for repository connection) = ----------------------------------------------- BibApp

9. Demo http://bibapp.mbl.edu/ http://www.library.uiuc.edu/bibapp/

10. HistorySpeech Communication

11. HistorySpeech Communication

12. Metadata Issues….  Inconsistency across A&I services (example below from three)

14. ? ?

15. Author Disambiguation Also see http://code.google.com/p/bibapp/wiki/AuthorAuthorities http://www.gliffy.com/publish/1371131/

16. Rudimentary Authority Control Example with Publishers

17. Other metadata issues… Althaus, S. L. (2001). Who's voted in when the people tune out? Information effects in congressional elections. In Hart, R. P. and Shaw, D. R. (Eds.), Communication in U.S. elections: new agendas. Lanham, MD: Rowman & Littlefield Publishers: 33- 53. Book chapters in social sciences and humanities hard to find as the primary entry. Conferences can also be hard to find.

18. Other metadata issues  Not displaying or sharing:  Subject terms  Abstract  Working on updating via RSS feed but inconsistent across A&I services

19.  Open author identifiers that can be used across publishers, libraries, A&I services, grant making agencies, etc.  Better consistency from A&I services  Better awareness of what’s available and what’s not via A&I services  Better support of API’s, RSS feeds, and other sharing mechanisms by A&I services We need:

20. Technology Stack  Ruby on Rails  Lucene / Solr  Sherpa Romeo API  Google Books API  OpenURL  FOAF  Accepts RIS, RefWorks XML, Medline  Runs on MySQL or PostgreSQL

21. Where are we?  BibApp 1.0  Easy to get citations in from multiple venues  Easy to get citations out in multiple formats  Straightforward authorization for editing citation lists  Maintain focus on publication analysis  Maintain pushing material in and out of the institutional repository  BibApp 2.0  Tag clouds  Collaboration network visualization  Publication patterns

22. When is BibApp 1.0 coming?  Aimed for late spring / early summer 2009  See http://www.bibapp.org/ for more information or to download code (0.7 available)http://www.bibapp.org/

23. Contact Information Sarah Shreeves Coordinator, IDEALS http://www.ideals.illinois.edu/ 217-244-3877 sshreeve@illinois.edu