<ul><li>Copyright James Gerencser, Rafael Alvarado, </li></ul><ul><li>Malinda Triller, 2009. This work is the </li></ul><u...
EDUCAUSE Mid-Atlantic  Regional Conference 2009 “ I’ll Have What She’s Having”:  Generating New Reference Questions By Blo...
UNDER THE HOOD
Functional Requirements <ul><li>Internal (Tracking) </li></ul><ul><ul><li>Client profile data (state or nation, purpose, e...
Some Observations <ul><li>Normally separate problems: </li></ul><ul><ul><li>Public vs. Private functions </li></ul></ul><u...
Technical Requirements <ul><li>Simple to build, maintain, and use </li></ul><ul><ul><li>No boutique applications! </li></u...
Also … <ul><li>Reportable data </li></ul><ul><li>Ability to separate public and private functions </li></ul>
Enter Drupal <ul><li>Blog on steroids </li></ul><ul><ul><li>Stories, tags, comments, RSS, etc. </li></ul></ul><ul><ul><li>...
Public and Private Fields
First, adapt a content type
Then create and group fields PRIVATE PUBLIC
…  add field group to access control
Finally, assign role to field group
WORKFLOW
 
 
 
 
Results
 
 
 
 
 
 
 
<ul><li>http://itech.dickinson.edu/archives </li></ul><ul><li>Drupal is  flexible  and  customizable . </li></ul><ul><li>R...
 
Upcoming SlideShare
Loading in …5
×

Dickinson Ref Blog Educause2009

1,527 views

Published on

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

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

No Downloads
Views
Total views
1,527
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
6
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Dickinson Ref Blog Educause2009

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

×