It seems to me that what is needed can be accomplished simultaneously
with the right tools. Guidelines on what to record should be less of a
concern for this new encoding structure, and would be covered in rules
for description such as RDA and other standards.
In my ideal cataloging utility, you could type the name of the
publisher (or other entity), and it would pull up a list of controlled
names which are established.* Choose one or create a new one**. If the
form is different, it would ask you whether you want to add your form
as a variant form (if yes, then it would add it in the form you
typed). The program would ask you if you would like to display the
transcribed name or the control name (or another name which is a
variant/parallel form) in your local catalog. In turn, these would
mark up the data with pointers to these registered entities, continue
to give transcribed forms as they appear, provide URI to established
entities, and gather instances (meaning that word generically, and not
in reference to anyone else's definition) in local and union catalogs.
This may be naive thinking, but why does it have to be harder than this?
* At this point, you would check the existing established identities
(or search for other forms).
** And provide an automated method for reporting dupes locally or to OCLC or LC.
Recorded Sound Cataloger
Library of Congress
(just my random Saturday morning musings and not officially speaking
for my employer)
On Fri, Nov 30, 2012 at 9:03 PM, Roy Tennant <[log in to unmask]> wrote:
> On 11/30/12 11/30/12 € 4:43 PM, "J. McRee Elrod" <[log in to unmask]> wrote:
>> I remember Lubetsky's objection to redundancy. I would not want to
>> clutter the display with two different forms of the publisher's name,
>> or even worse, the same form given twice.
> Clutter the display? We're talking about (or should be) capturing and
> encoding the data. Software of a wide variety will be written to parse the
> data, decide what gets displayed, and add appropriate punctuation for the
> purpose. Making any assumptions about what will be displayed is, in fact,
> impossible, since that would assume we know about all the environments in
> which this data would be used. All we need to figure out now is what data is
> important to capture and how to encode it. And the "how" will be, at times,
> linking to an authoritative source.