Library

Modules · Content Construction Kit (CCK)

jastraat - August 8, 2008 - 23:28

To current users of this module:

I am considering a re-write of this module that simplifies the current structure by removing patrons as node objects and simply using Drupal users instead. There have been a number of issues in the cue that indicate that most users of this module are setting patrons as users and that the patron wrapper is sometimes getting in the way of integrating this module with other applications/modules.

I am also considering reducing the flexibility regarding library actions and just offering a pre-set selection of (rename-able) options: check-in, check-out, renew, request, and hold. These options would be events that tie into the rules module and could be configured through that interface. (For those of you who haven't used the rules module - it's fantastic.) Making these changes would reduce some flexibility in the library module but would greatly increase how much users could configure what exactly happens on a checkout/check-in/hold (in addition to severely reducing the complexity of the module which is currently a bit of a monster).

If you have an opinion regarding these potential changes, I would really like to hear from you. My contact form is http://drupal.org/user/105111/contact Thanks!

Description

The library module allows users to manage the availability of nodes as assets. You can create custom content types using CCK and then add those content types to the library.

The module supports multiple copies of a library item associated with one node, and each copy may be individually made available or unavailable.

The module allows administrators to define their own library actions. Library actions may make an item available, unavailable, or not change an item's status. Every transaction is associated with a library patron. If you use the trigger module (part of core) with the library module, each library action generates a trigger that you can assign further actions to. The module includes a few built-in actions (send an email, extend the due date of an item).

The library module is intended to be very flexible and comes with a number of options. You may use unique identifiers on item instances (e.g. barcodes), have library patrons as users, and configure what fields display in the custom library search.

To get the full functionality of the module, you should have CCK installed and Triggers (part of core in Drupal 6) enabled. The module also integrates with views.

Note: this module is for Drupal 6 and is not intended for production use yet. Also, while I am happy to accept suggestions for improvement, I may not have time in the future for many enhancements. If other folks are interested in contributing though, they are more than welcome!

Example of this module in use: http://library.cenhum.artsci.wustl.edu