Re: [libdb-develop] [ANN] LibDB 0.0.1 Released

[Bruce D'A. <bd...@fa...>]

On Feb 6, 2004, at 5:09 PM, Morbus Iff wrote:

> This, I think, is very important for data sharing. Since every
> single thing in LibDB comes with a unique ID, it is imperative that
> the data sharing understands that UniqueIDA on this LibDB installation
> is the same as UniqueIDA on another LibDB installation.

Based on what I've been learning from the MODS community, it seems to 
me you ought to have some way to track with which community a given 
role is associated.  For example, clearly I would want you to include 
the MARC relator role terms, because it allows me to track authors, 
translators, recipients, etc... even directors (which I do keep track 
of).  But it would probably be important to know that role term X is 
associated with that controlled list.  It allows you to then map to 
MODS too, where you have:

<role>
	<roleTerm type="text" authority="marc">writer</roleTerm>
</role>

...or:

<role>
	<roleTerm type="text" authority="libdb-movie">whatever</roleTerm>
</role>

..or some sort of RDF-based uri.

BTW, and only slightly off-topic, one of the useful things I am 
thinking about MODS' handling of this is that one can have more than 
one roleTerm element associated with a name.  E.g.:

<role>
	<roleTerm type="text" authority="dc">creator</roleTerm>
	<roleTerm type="text" authority="marc">writer</roleTerm>
</role>

My thinking here -- and someone confirm that I am right (or not) please 
-- is by having the more generic (but still useful) creator role, it 
can be easily mapped to DC and to any citation formatting output.

Bruce