I agree that it's extremely important to base the model on use cases and
the corresponding natural language that domain experts actually use. If
the domain experts are good, the jargon will be based on common-sense
vocabulary as much as possible and only split hairs that the use cases
justify. Modeling is ultimately a compromise as participants and use
cases some and go.
If I've learned one thing, it's that a thesaurus is modeling expert's
best friend.
Jeff
> -----Original Message-----
> From: Bibliographic Framework Transition Initiative Forum
> [mailto:[log in to unmask]] On Behalf Of Kevin M Randall
> Sent: Thursday, January 17, 2013 8:58 PM
> To: [log in to unmask]
> Subject: Re: [BIBFRAME] Input screens
>
> > Moreover,
> > there is a big difference between 1) *requiring* the use of the MARC
> > format for everyone doing cataloging, and 2) prohibiting everyone
> from
> > learning more about the underlying metadata structures. I hope my
> > previous posts on this topic didn't give the impression that I was
> > espousing the latter; nothing could be further from the truth!
>
> Oops, what I meant was:
>
> There is a big difference between 1) allowing the use of natural-
> language, non-MARC input forms for anyone doing cataloging, and 2)
> prohibiting everyone from learning more about the underlying metadata
> structures.
>
> That is, I am *for* helping things out by making easier input tools,
> but I am *not* in favor of allowing *only* those tools.
>
> Kevin M. Randall
> Principal Serials Cataloger
> Northwestern University Library
> [log in to unmask]
> (847) 491-2939
>
> Proudly wearing the sensible shoes since 1978!
|