[Koha] inconsistencies in acquisition.simple process

Joshua Ferraro jferraro at alma.athenscounty.lib.oh.us
Fri Sep 26 14:58:54 NZST 2003


Stephen et al,

There was an interesting article by Roy Tennant a while back in Library 
Journal that outlined the latest recasting of the bibliographic record
in terms of hierarchical dimensions very similar to the Koha database.

Here's the rundown:

+In 1998, the International Federation of Library Associations and Institutions
+(IFLA) published a report on the Functional Requirements of Bibliographic
+Records (FRBR)?a revolutionary recasting of the bibliographic record on behalf
+of library users. It defined such principles as the hierarchical dimensions of
+a creative product: work (distinct creation), expression (realization of a
+work), manifestation (physical embodiment), and item (a single exemplar). The
+revolutionary aspect is best understood as it is being applied by OCLC and RLG
+to their catalogs. When a user searches for a book in a catalog, they are faced
+with the variations of that work as multiple, separate records. Which one to
+choose? With FRBR, all manifestations can be collapsed into one virtual record,
+with methods for users to narrow in on the items (e.g., language, form, etc.).
+Draft screen designs for RLG's new system are compelling evidence of the
+benefit of "FRBRizing." One screenshot shows a list of search
 results. Under the title and author of an item is the notation "19 editions
+published between 1916?2001 in 5 languages." The full record for that item
+provides a way for the user to see only editions in a specific language or the
+two audio versions.

If the link survives my paste attempt you can read the whole article at:

http://libraryjournal.reviewsnews.com/index.asp?layout=article&articleid=CA2891
90&display=Digital+LibrariesNews&industry=Digital+Libraries&industryid=3760&ver
ticalid=151&publication=libraryjournal

if not, just do a search on google for "not your mother's union catalog".

Cheers,

Joshua 

On Fri, Sep 26, 2003 at 11:42:03AM +1200, Chris Cormack wrote:
> >  
> > >But I think the form has been designed in a way so that it looks like
> > >we'd need 3 biblios for the above example .. which is not right.
> > 
> > That's where you have things wrong my friend. Beyond the MARC stuff, which
> > I know is not your responsibility or interest, whatever library advice you
> > are getting is WRONG.
> > 
> > *** Three different items do require three different records. ***
> > 
> Ahh, see this is where I think people confuse internal storage with external
> representations.
> 
> > You have three different physical manifestations of a work, which, if we
> > are still using AACR2R rules -- which are the standard for the anglophone
> > library world ascribed to and endorsed by your National Library as well as
> > those of the Australia, Canada, the United Kingdom and the United State --
> > the RULES require three different records.
> > 
> > The biblio level that you all wisely created acts like an authority record,
> > pulling together different manifestations of a work, because, God only
> > knows what the patron might actually want. But you have to remember that
> > that's all it should do then.
> > 
> > As a pure matter of what is correct, 3 different types of item (book, DVD,
> > large print book) require 3 different records, which would have slightly
> > different data and different MARC coding. If you want to keep the biblio
> > level, then work should begin on making that into the core of the
> > AUTHORITIES for the system (used forms, cross-references, see also's etc.).
> 
> If I can export records in a format like that, and display them to the
> librarian in a format like that. And input them from a format like that.
> 
> What does it matter how they are internally stored??
> 
> What I was talking about is how Koha stores the data .. I think if its
> possible to create valid catalog records that correspond with standards,
> then how we store the data internally doesnt matter.
> Apart from the obvious storing it in a way that provides for fast access.
> And minimal redundancy.
> 
> Perhaps I didnt make that clear enough in my message :) I was talking about
> the internal structure.  
> 
> Chris
> 
> -- 
> Chris Cormack                                                     Programmer
> 027 4500 789                                       Katipo Communications Ltd
> chris at katipo.co.nz                                          www.katipo.co.nz
> _______________________________________________
> Koha mailing list
> Koha at lists.katipo.co.nz
> http://lists.katipo.co.nz/mailman/listinfo/koha



More information about the Koha mailing list