[libdb-develop] locations

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

On Feb 20, 2004, at 10:54 AM, Morbus Iff wrote:

> >> From an "FRBR model" standpoint, it really doesn't. FRBR mentions 
> that
> >> an item is located somewhere, but it doesn't set out to 
> conceptualize
> >> "location" as anything but a relationship/attribute.
> >
> >Which is a problem in the real world.  Clearly the FRBR is a
> >meta-model; it solely defines broad structures.  But implementations
> >need to sort out these details.  I'm not exactly sure how to deal with
> >this, but I get the feeling there's an elegant way to do just that.
>
> Welp, what are your requirements for a "location"?

At minimum, the ability to distinguish physical locations (.e.g 
archival holding locations) from electronic.  For electronic, citations 
require date accessed info.

Beyond that, I've noted this awkwardness on the MODS list.  In this 
example (only quasi-hypothetical):

	Collection X, ABC Archive, Box 23, Folder 324

...the collection info is actually a title associated with the isPartOf 
(or mods relatedItem "host") structure, so that's no big deal.  Beyond 
that, I actually have three further chunks of information.  But then 
... is the archive really a location, or should it be handled by some 
other structure?   Box and folder are two separate location 
designations, but then this starts to become blurred with another 
structure: "parts" in MODS, which represent things like page, volume 
and issue numbers.  Where's the conceptual line between a folder and an 
issue, after all?  Maybe a distinction between an, um, manifestation 
and an item??

Ugh, am rambling...

Bruce