1 / 11

Project Barcode: Simplifying Inventory Process in the Art Library at UMD

INFM 603 Jaydeep Yelne Shelton Roberts Jr. Project Barcode: Simplifying Inventory Process in the Art Library at UMD. Over 82,000 books ALEPH developed by ExLibirs Part of USMAI (16 libraries) 12 Student Assistants, 3 Supervisors, 1 Reference Librarian. The Art Library.

betrys
Download Presentation

Project Barcode: Simplifying Inventory Process in the Art Library at UMD

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. INFM 603 JaydeepYelne Shelton Roberts Jr. Project Barcode:Simplifying Inventory Process in the Art Library at UMD

  2. Over 82,000 books ALEPH developed by ExLibirs Part of USMAI (16 libraries) 12 Student Assistants, 3 Supervisors, 1 Reference Librarian The Art Library

  3. Could take up to 6 months • Things checked: • Where • Condition • Status • Logs maintained The Inventory Process

  4. Two separate systems Aleph + Paper logs Look up book / user Planning The problems

  5. www.artlibinventorycp.info • We created a site that allows inventory functions to be completed electronically in one place. • Look up functionality by barcode • Scan history by barcode • Scan history by username • Schedule viewing (students) and entry (supervisors) The Solution

  6. Speeds up the inventory process Clean interface Intuitive advantages

  7. Access to the dynamic database Time constraint User testing Limitations

  8. Sorting by date Enabling flow of books Integrated mailing system Schedule request system Possible Improvements

  9. Used a “tag-team” approach to coding. Jaydeep – Direct link to customer, gathered and verified all requirements, gave customer project updates & demo. Shelton – Secured hosting spot, installed Drupal and modules onto site, translated & wrote initial requirements into functions / code. Benefitted from having two perspectives to solving the same problem How / What we Did

  10. Drupal – Not very intuitive. • Lack of documentation • “Hit or Miss” with modules • Did not always do what was advertised • Stability was a concern • Modules stopped working • Frustrating when trying to pinpoint problems • Is it the code? Or is it Drupal? What we learned

  11. Thank you! Questions???

More Related