I keep thinking about the fact that RDA treats the data elements as
strings, but we might want the possibility of more precision for the
future. I have mapped out one field, publication statement, as three
logical levels (which might be expressible in a single data description
-- this is conceptual).
Publication statement (level 1)
type = literal
rules = no
equivalent = dc:publisher
Publication statement (level 2)
rules = RDA
equivalent = MARC 260 field
components:
place
type = literal
publisher
type = literal
date of publication
type = literal
Publication statement (level 3)
rules = RDA+
equivalent = none yet
components:
place
transcribed place
rules = RDA
type = literal
country code
type = list
list = (ISO ??)
city code
type = list
list = ??
publisher
transcribed publisher
rules = RDA
type = literal
publisher identifier
type = URI or link [to record with
name, address, etc.]
date of publication
transcribed date
rules = RDA
type = literal
date
type = [need a date definition with
a code for degree of accuracy (exact, approx.,
range, etc.) what date represents (pub date,
(copyright date) and format as typed literal]
Now I want to try it out with some other fields, so I may start putting
them on the wiki if people find this kind of analysis at all useful.
kc
--
-----------------------------------
Karen Coyle / Digital Library Consultant
[log in to unmask] http://www.kcoyle.net
ph.: 510-540-7596 skype: kcoylenet
fx.: 510-848-3913
mo.: 510-435-8234
------------------------------------
|