Dickinson Ref Blog   Educause2009
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Dickinson Ref Blog Educause2009

on

  • 2,093 views

A presentation given at Educause 2009 on the use of Drupal to create a unique blog tracking and making available archival reference questions.

A presentation given at Educause 2009 on the use of Drupal to create a unique blog tracking and making available archival reference questions.

Statistics

Views

Total Views
2,093
Views on SlideShare
2,090
Embed Views
3

Actions

Likes
2
Downloads
4
Comments
0

1 Embed 3

http://www.slideshare.net 3

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

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

Dickinson Ref Blog Educause2009 Presentation Transcript

  • 1.
    • Copyright James Gerencser, Rafael Alvarado,
    • Malinda Triller, 2009. This work is the
    • intellectual property of the author. Permission is
    • granted for this material to be shared for non-
    • commercial, educational purposes, provided
    • that this copyright statement appears on the
    • reproduced materials and notice is given that
    • the copying is by permission of the author. To
    • disseminate otherwise or to republish requires
    • written permission from the author.
  • 2. EDUCAUSE Mid-Atlantic Regional Conference 2009 “ I’ll Have What She’s Having”: Generating New Reference Questions By Blogging Old Ones Jim Gerencser College Archivist Rafael Alvarado Special Projects Coordinator Malinda Triller Special Collections Librarian Library and Information Services Dickinson College
  • 3. UNDER THE HOOD
  • 4. Functional Requirements
    • Internal (Tracking)
      • Client profile data (state or nation, purpose, etc.)
      • Cost tracking for scans, etc.
      • Monthly reports
    • Client-facing (Marketing)
      • SEO to boost site visibility and interaction
        • Aka “Googlability”
      • Transparency: a public record of activity
  • 5. Some Observations
    • Normally separate problems:
      • Public vs. Private functions
    • Solution driven by awareness of affordances
      • Not abstract requirements
      • Would have fallen between the cracks
      • Side-effect of web-as-platform
    • Not only possible to merge, but synergetic
      • A lesson In the value of transparency
  • 6. Technical Requirements
    • Simple to build, maintain, and use
      • No boutique applications!
      • No shoe-horn applications (e.g. ticket systems)
      • KISS for all parties—library staff, clients, coders
    • Flexible metadata
      • Evolvable without breaking the data model
      • Ability to hold public and private fields in the same record
  • 7. Also …
    • Reportable data
    • Ability to separate public and private functions
  • 8. Enter Drupal
    • Blog on steroids
      • Stories, tags, comments, RSS, etc.
      • More flexible than WordPress
    • Available modules to do the job
      • Granular authorization (roles and rights)
      • Sophisticated tagging (taxonomies)
      • Content Construction Kit (CCK)
      • CCK Field Permissions Module
      • PHP nodes
  • 9. Public and Private Fields
  • 10. First, adapt a content type
  • 11. Then create and group fields PRIVATE PUBLIC
  • 12. … add field group to access control
  • 13. Finally, assign role to field group
  • 14. WORKFLOW
  • 15.  
  • 16.  
  • 17.  
  • 18.  
  • 19. Results
  • 20.  
  • 21.  
  • 22.  
  • 23.  
  • 24.  
  • 25.  
  • 26.  
  • 27.
    • http://itech.dickinson.edu/archives
    • Drupal is flexible and customizable .
    • Reference stories are discoverable .
    • Reference stories are searchable .
    • Reference stories are taggable .
    • Reference stories are linkable .
    • Researchers can post comments .
    • Reference statistics are easily obtainable.
    • EMAIL: archives@dickinson.edu
  • 28.