I have a client that has a lending library of approx 600 publications. They have all of the publication information in an Access db. Does anyone have a suggestion as to what module would work to handle the information text fields (about 20) and what would be the best method to export the data from the Access db into the suggested DNN module? The only additional field needed would a "check-out" option when viewing a publication detail page.

It was easy enough to use UDT to create a table / grid to handle the data, but the "check-out" button has me stumped. When pressed the user should get the option to enter a name, email address and phone number. Then the resulting information should be emailed to the librarian along with enough descriptive information to identify the document. And, of course, what would be the best method to import the data into the UDT module from the Access db.

Thanks for any suggestions.

Jim

Thanks for the reply and the offer. I've emailed you via the provided address.

Jim

Jim

First the logic:
1)I would only show REGISTERED users the checkout option
2)Publics could see an alternative "register to check-out this item"
Why? registered users will have all the data (tokens) available to you inherintly which can be easily drawn from.

3)Additionally, either the registered user button or the public button should be conditional displayed based on whether an item is currently checkout or not, if item is checked out then button (null) displays as 'currently checked out' You could even offer a 'reserve when available' button but perhaps save for later revision
4-a) Checkout button emails librarian requesting item. Librarian acknowledges and edits the database marking item 'checked out'
4-b) Checkout queries database to mark item as checked out and emails (notifies) librarian

Implementation:
Simple logic, maybe not so simple implementation
1) DATABASE - Add checkout toggle field in mdb file (as you stated) yes/no type would suffice
2) DATABASE - you could (recommend) add a table to store borrower's info and item reference (there can be more than one way to accomplish this, as well even relinguish the need for the checkout field)
3) create the additional interface(s) for managing the database which could be a checkbox for checked out and a dropdown list (populated from DNN registered user list) for selecting borrower and apply

Pulling it all together will depend on your resources to write code and/or mashup. Alternatively is to look for an already developed module specific to library business logic. 

while not specific to library business the SQLGridSelectedView module from Tressleworks.ca could be essential to your app.

It's not really complex, but often there is no such thing as a 'little job' even though it is .. it's all relative.

Making it simple at the UI (always key) usually means degrees of complexity in the back end. Could be a good project to 'teeth on' if you are so inclined.

Long winded, but hopefully somewhat useful
B

"Good development is like looking both ways on a one-way street" - unknown