[open-bibliography] FRBR examples
Christopher Gutteridge
cjg at ecs.soton.ac.uk
Thu May 27 12:07:12 UTC 2010
I think it makes more sense to pick some things that people will want to
do with the data, and make a good spread of those possible. As far as I
can see, the rationale for work/exp/man is the different ways people
would want to query/reference/retrieve a thingy.
Roughly speaking;
* Work = Do you have a copy of Shakespeare's Hamlet?
* Expression = Do you have a copy of the unabridged Battlefield
Earth? (hopefully not) -- references about paragraphs are to an
expression.
* Manifestation = Do you have a copy of the 1st edition of Alice in
Wonderland --references about page numbers are to a manifestation
(Item is obvious for books, but probably represents also having a copy
available for download.)
Most bibligraphic systems will keep data about work/exp/man against a
single identifier. Sometimes this will be easy to unpack (ISBN belongs
to the manifestation), sometimes not.
I think when looking at what to use for open bibliographic formats we
should start with some educated guesses as to some things people might
do with open bibliographic data; Off the top of my head...
* use 3rd party tools to browse a library catalogue,
* create a distributed ABE books,
* build a reading list,
* cite things in a semanticly enabled document format,
* keep track of their personal book/dvd/cd collection,
* an amazon wishlist style file for your foaf profile,
* library research (as in studying libraries),
* finding next-best versions of unavailable items (eg. finding the
pre-print for a cited journal article).
On 27/05/10 12:26, Weinheimer Jim wrote:
> Christopher Gutteridge wrote:
> <snip>
> Thanks, Karen. This pretty much rubs in that there is no "quick start"
> for this model, and the person creating records is expected to
> understand the details of the data model. This may work well with fully
> trained library staff, but in the author-deposits world I work in,
> that's impractical.
>
> Part of the goal of open bibliographic data is that it should be
> reasonably easy for people to create and consume (and discover, but
> that's a separate discussion).
>
> This model seems to describe the 'truth' better than some, but does it
> facilitate or hinder creation and consumption?
> </snip>
>
> I will point out again, that even if we make the effort to somehow create a coherent FRBR datamodel and manage to get most of our records into it, I still have not seen any advantage it will have over what we have now. I still do not see how it will add a single access point that we do not have presently, how it will help metadata creators (professional or amateur), how it will increase productivity, or anything at all. Karen's examples show the enormous difficulties we face to even retain the capabilities we currently have, even in the extremely simple examples she uses. I fear matters could become far, far more complex when applied in a comprehensive way to the real world.
>
> Putting records into a more accessible XML format or RDF format would be a good first step, but it seems increasingly clear that FRBR is strictly an idealistic intellectual model that falls apart in the practice of the real world, while practical implementation appears more and more unwise.
>
> Perhaps one way of beginning to approach the problem would be to clear the mind of all FRBR, RDA, AACR2, MARC and everything else, and ask: if there were no other formats or records of any sort, what would you do? This would be to approach the problem strictly as a user, which is I think the most important task, and focus on the needs of users. Only then can you begin to build tools that attempt to fulfill these needs, and then decide how best to incorporate the past records with the future records, and so on.
>
> Jim Weinheimer
>
> _______________________________________________
> open-bibliography mailing list
> open-bibliography at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/open-bibliography
>
--
Christopher Gutteridge -- http://id.ecs.soton.ac.uk/person/1248
/ Lead Developer, EPrints Project, http://eprints.org/
/ Web Projects Manager, ECS, University of Southampton, http://www.ecs.soton.ac.uk/
/ Webmaster, Web Science Trust, http://www.webscience.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/open-bibliography/attachments/20100527/62df1328/attachment-0001.html>
More information about the open-bibliography
mailing list