TubeNet

I'm about to start cataloging the sheet music for a community band. They have a fairly good sized library, and will (RealSoonNow) have all the information they think they need in an Excel spreadsheet (gnomes have been slaving away for a month of stolen Saturdays). I'd like to move that information to a proper database.

There are several constraints:
a) it must run on a Mac - all data entry/searches/everything will be done
on a MacBookPro (currently running Tiger...soon perhaps Leopard)
b) it should be possible to export to Microsoft Access for use by students
learning how to do simple database tasks
c) it should be as simple as possible (but no simpler) - this is just the card
catalog for the band librarian (not me!)
d) it should be possible to do most of the initial data entry directly from
the existing (RealSoonNow) spreadsheet.
e) assume that I can hack through just about any technical hurdle during
the initial set-up - but that the ultimate user(s) will have minimal
training.


I know there are a few band librarians out there - any suggestions?

I'm primarily interested in opinions on:

a) DO NOT use XXX [because...]
b) DO use YYY [because...]
c) I've already solved this problem - here's my design.

Feel free to reply directly to <KennethRSloan@gmail.com> If there is any interest, I'll summarize the results here in a few months.

I use MS-Access for both The Old Dam Community Band library and my own personal collection of march folios and tunes. I don't know how that equates to a MAC but I would think that any db4 database or comma delimited database would import/export just fine.

Many high school band directors use a database product from Pyware. I have a demo copy and it is not very flexible and cannot be expanded beyond the range of parts it comes with. There are other 'off-the-shelf' products our there but none with the flexibility of a true relational database.

I have my database set up so I can record the tune number, title, composer, arranger, type of tune, publisher, play time, columns for all parts (expandable), cost, date purchased, location, list of performances, date of last performance, notes, .... etc.... expandable to add new fields as the need comes up.

As both an Ensemble Librarian and tubist, I recommend FileMaker Pro. Designed to operate with Macs. Very user friendly. NOT nearly as fluid (in a good way) as comparable MS application. Also, it is very easy to customize your layout, and easy to import from MS Excel. I've used it to convert several databases already with great sucess.

Good luck.

T. Hendra
Ensemble Libraian
University of Kansas

I'm librarian (and tubist/tubaist/tuber) for a community band with about 800 titles in our files. I agree with TubaTinker regarding the flexibility of a common database program. We include almost the same info that he lists except for the performance dates which the conductor keeps separately. But it sounds like a good idea to add that info.

We categorize the tunes into 8 or 10 categories (marches, big band, patriotic, Christmas, etc) and it helps to sort by category when planning a program.

hendra_tuba wrote:As both an Ensemble Librarian and tubist, I recommend FileMaker Pro. Designed to operate with Macs. Very user friendly. NOT nearly as fluid (in a good way) as comparable MS application. Also, it is very easy to customize your layout, and easy to import from MS Excel.

And export. A good solid program!

I second (or third?) FileMaker Pro. It really is the standard when it comes to relational databases and I've used it on many projects (sheet music, students, moving, etc) and it's worked well and it pretty easy to use.