Nifty study.
Karen Coyle said:
> think about having a publisher "entity" and not just a string
> in our data.
When you say "not just a string" do you mean "instead of a string" or "as
well as a string"?
Wouldn't we want both the transcribed string *and* the "publisher entity",
at least for those things that are not in a digital form and immediately
available for checking, for:
- historical purposes (what was on the thing at the time it was published?)
- record matching purposes (am I really looking at the same thing you
describe? without having to go to the link to see whether the name on my
thing is a variant name in the 'authority record' each time )
- verification that the correct "publisher entity" was chosen (whoops, this
should be http://blahblah/0-05 not http://blahblah/0-06)
Could you give us an example of how this data *might* be entered as an
element in a template, e.g.:
Publisher: HarperPerennial (http://blahblah/0-06)
or
Publisher: HarperPerennial
Publisher ID: http://blahblah/0-06
or
Publisher: http://blahblah/0-06
or
Publisher: HarperPerennial [with an underlying link to http://blahblah/0-06]
Deborah
------
Deborah Fritz
MARC Database Consultant
The MARC of Quality
www.marcofquality.com
Voice/Fax: (321) 676-1904
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4262 (20090720) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Received on Tue Jul 21 2009 - 10:25:11 EDT