 |
 |
Wayne, Anna: Some of the difficulty of mapping local call numbers arises from the fact that they are really used in two ways in libraries. On a purely practical level, they are indeed "call numbers," e.g. identifying the precise spot on the shelf where an item can be found. Given this, and the dearth of other kinds of unambiguous identifiers for physical materials, putting a call number into Identifier for a physical resource might be a reasonable decision. On the other hand, the reason call numbers create browsable shelves and accession numbers don't is that that they are, at bottom, classification numbers, with the addition of "book numbers" or "Cutter numbers" that enhance their use in identification. This classification function is why some libraries put "call numbers" on digital materials--not to place them on some virtual shelf somewhere, nor to identify them (they normally carry other means of unambiguous identification), but to relate them to other materials on the same topic. Classification is defined by Dublin Core as part of the Subject element, as you have noted, and local call numbers are really classification PLUS identification, in a sense. Therefore, you might want to include call numbers as Identifier AND Subject, if indeed those are the dual purposes supported by those 'local call numbers.' Source is probably not a good idea, unless you are using the call number as an identifier of a related work. The call number/identifier should not refer to the resource being described in the rest of the DC description, since Source is explicitly defined as "A reference to a resource from which the present resource is derived," in other words, a specific "derived from" relationship. Regards, Diane I. Hillmann Editor, "Using Dublin Core" >I think you've got at least 2 choices -- Identifier or Source. > >Neither one of those is specific to 'local'. > >We tend to use Identifier for a number that actually gets the user to the >resource being cataloged. If it's electronic, it might resolve to a URL. > >We use Source for non-electronic identifiers, like call numbers. Further, >we use Qualified Dublin Core and so can distinguish 'local' call numbers >from other 'standard' identifiers or sources. > >Wayne > >> -----Original Message----- >> From: General DCMI discussion list >> [mailto:[log in to unmask]] On Behalf Of Anna Schein >> Sent: Monday, October 09, 2006 12:41 PM > > To: [log in to unmask] >> Subject: DC Element for Local Call Number >> >> Hello All, >> >> Could someone please tell me which DC element I should use for a >> locally devised accession number call number? I am finding Dublin >> Core >> elements for Library of Congress, Dewey Decimal, and Universal Decimal >> call numbers, but can't find the DC element for a local call number >> scheme. >> >> In MARC, the field tag would be 099. What element is comparable in >> Dublin Core? >> >> Thanks in advance for your help, >> >> Anna >> >> >> >> Anna M. Schein, University Librarian >> Curator, Printed Ephemera Collection, WV & Regional History Collection >> Biblographer, Native American & Hispanic American Studies, TESOL, >> Linguistics >> >> 2510 Wise Library >> PO Box 6069 >> West Virginia University Libraries >> Morgantown, WV 26506-6069 >> [log in to unmask] >> Tele: (304) 293-4040 ext. 4065 >> Fax: (304) 293-3981 >> -- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Diane I. Hillmann Research Librarian Cornell University Library Email: [log in to unmask] Voice: (607) 387-9207 *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*