Thomas Feehan said:

>... consider non-cataloguing library data like repositories, j=
>ournal indexes, archives, reading lists, or even non-library data) as the m=
>odel itself.

When catalogue automation first came to Canada as microfiche
catalogues produced from MARC records, formerly divided card files
(e.g., current LCC collection, old DDC collection, vertical file, AV)
became one microfiche catalogue; use of materials in those collections
not formerly in the main catalogue shot up.

Anything which makes these other genre findable in the initial search
will increase their use remarkably.

I've no idea  whether Bibframe will help bring this about or not.  
Perhaps with its word based labels, it will have the appeal to non
cataloguers which now Dublin Core enjoys?

On the other hand, we have one client who has abandoned its catalogue
and gone to spreadsheets when faced with RDA.  Bibframe might cause
other small libraries with no technical service librarians to do the
same?  Non librarian IT folk are more comfortable with tools such as
spreadsheets than OPACs.

We've been approached by a possible new client who has separate Dublin
Core based finding tools for *each* of their nonbook genre.  There is
no standardization across genre of subject headings, and no indication
in the Dublin Core records of which headings are LCSH and which are
local.  There is no standardization of form, e.g., both "State--City"
and "City (State)" exist as subject heading forms.   They want to
create a single list composed of LCSH and local headings for use
across genre lines.  I would like to talk them into a Dublin Core to
MARC crosswalk, so the records can be included in their OPAC.

I am no fan of the segregation which has resulted from Dublin Core.

Whether a MARC/Bibframe crosswalk plus a Dublin Core/Bibframe
crosswalk would help create the combination of these finding tools,
I've no idea.  That combination is a much needed outcome.

   __       __   J. McRee (Mac) Elrod ([log in to unmask])
  {__  |   /     Special Libraries Cataloguing   HTTP://
  ___} |__ \__________________________________________________________