To a lesser extent, the same can be said of holdings locations - which can be nested pretty deep: institution - sub-unit - building - alcove.... Each could use links to maps.


On 6/24/15 9:56 AM, Vitus Tang wrote:
[log in to unmask]" type="cite">

If I understand it correctly, a bibframe Item could be as broad as an entire run of a serial publication, or a whole archival collection. These compound items could have large number of component items, each representing a part of a large and complicated Instance. In such scenarios, it would seem the bf:enumerationAndChronology property would be key to expressing how each component item fits into the compound item, and how all these Items relate to each other. I am concerned that the expected value of this property is “literal”, as specified in the proposal.


Enumeration and chronology information is often hierarchical (e.g. the MARC holdings format provides for six levels of enumeration and four levels of chronology), and consists of parts that would best be separately identified (e.g. separate the caption from the numbering) if the data is to be machine-processable. And I think most libraries would want this kind of data machine-processable, in order to support features such as finding a specific volume/number/part of a serial, a specific box or folder of an archival collection, or displaying a set of items in their intended order. Is there any way that bf:enumerationAndChronology can be extended to support this type of information?




-- Vitus


Vitus Tang
Metadata Department
Stanford University Libraries

From: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] On Behalf Of Denenberg, Ray
Sent: Friday, June 19, 2015 8:42 AM
To: [log in to unmask]
Subject: [BIBFRAME] BIBFRAME Item Proposal



Attached, the second of several proposals:  BIBFRAME Item Proposal.




Ray Denenberg

Library of Congress


Karen Coyle
[log in to unmask]
m: +1-510-435-8234
skype: kcoylenet/+1-510-984-3600