[openbiblio-dev] BibJson and non written material

[Mark MacGillivray]

Hi Sylvain,

BibJSON so far has been used mainly for metadata about books or articles.
In essence the same technology could be used for CD or DVD and so on, as
really it is all just metadata about some piece of information.

There are no specific examples of representing a CD in bibjson, you could
come up with some if you wanted to do so that followed similar convention -
e.g. there is a "type" field commonly used, so you could just call it "cd"
or "dvd". The various sorts of person involved would probably be different,
e.g. rather than author and editor you may have performer and composer
lists.

Whilst this would be simple to store, the question would be how you want to
display it; a list of books or articles are known to have authors, so by
default the bibserver facetview options include an "author" facet. However
if you expect to have a lot of records containing "composer" objects, for
example, you could add a "composer" facet to your facetview options.

Mark



On Sat, Feb 16, 2013 at 12:39 PM, Sylvain Hellegouarch <
sylvain.hellegouarch at gmail.com> wrote:

> Hi,
>
> I'm new to the OpenBiblio world but I've liked what I've seen.
>
> I was working on a dataset of a French local library which contains books,
> articles but also CD, DVD, etc.
> This made me wondering whether or not BibJSON was the appropriate tool to
> store information about the whole dataset? Or does it only target written
> materials such as books or articles?
>
>  Thanks for any input you could provide,
> --
> - Sylvain
> http://twitter.com/lawouach
> http://www.defuze.org
>
> _______________________________________________
> openbiblio-dev mailing list
> openbiblio-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/openbiblio-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/openbiblio-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/openbiblio-dev/attachments/20130216/9d5cf83b/attachment.html>