The Design of Software (CLOSED)

A public forum for discussing the design of software, from the user interface to the code architecture. Now closed.

The "Design of Software" discussion group has been merged with the main Joel on Software discussion group.

The archives will remain online indefinitely.

Database design for library system that supports MARC?

A simple library designed that doesn't support MARC would be simple. e.g. table books with columns: id, title, author, publisher, etc. But, supporting marc doesn't fit with this design. the fields does varies alot. I think of putting them on rows instead of columns. Do you have any idea? Thanks.
iDevelop
Sunday, August 21, 2005
 
 
May be you can take a look of this project: http://www.koha.org
Carfield Yim Send private email
Monday, August 22, 2005
 
 
You'd need to segment the information into different tables.  MARC identifies (or attempts to) any and all information that a bibliographic database could or would transmit to another system in electronic form.  Treating it as a data transformation mechanism though would be to commit the same faults that UN/EDIFACT did, needlessly overcomplicate the process of data interchange.

Instead you can take the MARC record structures and use those as the fundamental units for organising the database.  So a book would not be a single table with over a thousand columns, nor would it be a single table with over 300 rows per book, instead it would be a single row spanning many tables, at a rough count about 15-20.

Spitting out the MARC compliant data to another system would consist of a query across those tables.
Simon Lucy Send private email
Monday, August 22, 2005
 
 
Punt MARC and go with MODS or Dublin Core.

I worked at the Library of Congress for two years and MARC was specifically designed as a human-readable XML replacement for MARC.
KC Send private email
Monday, August 22, 2005
 
 
KC Send private email
Monday, August 22, 2005
 
 
Stay away from MARC. Really. Import it, maybe store it in tables that mirror your actual, useful tables so that you can export it, but for the love of god don't try to work with it. MARC is a stinking morass of arbitrary data structures (and I use the term loosely) munged together and stomped on.
Eli Naeher Send private email
Wednesday, August 24, 2005
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz