Thomas said:
And a further point, as is brought up in some entity-relationship modeling
discussions...
Attributes can become entities.
Normally, an attribute is some value by itself. However, that value could also
be pulled in from a table where that value has associated other values or
Karen,
Heidrun, looking at these examples (which naturally do not tell the
whole story) it seems to me that the authority records in your
catalogs do more than just establish preferred name forms; instead,
they approach what to me seems more like the description of a person
entity. The
On 07/06/2012 20:42, Brenndorfer, Thomas wrote:
snip
You still don't get it.
Everything you're doing is based upon some data element somewhere that a user
must act upon. It doesn't have to be traditional bibliographic data for the
FRBR user task to apply. You're still looking for things,
Karen,
I don't know what your authority records look like nor how they are
exchanged and updated. Perhaps that's another difference, and
something we could learn from German libraries?
O.k, so here is some basic information about cataloguing procedures in
Germany. Beware - this is going to
Heidrun,
Thank you for taking the time and effort to explain your system to us.
It's time cataloguing and ILS expertise became a two way street.
There are three levels to take into account, which interact with each
other and whose data are constantly synchronized: 1. The national
level ... 2.
5 matches
Mail list logo
