Joan Schuitema had a problem sending this message to the list
-- I'm reposting while the Webmaster tries to sort out it out.

it outi Message-Id: <[log in to unmask]>
X-Mailer: Novell GroupWise 4.1
Date: Tue, 12 May 1998 16:01:16 -0500
From: Joan Schuitema <[log in to unmask]>
To: [log in to unmask]
Subject: Local core level modifications -Reply
Mime-Version: 1.0
Content-Type: text/plain
Content-Disposition: inline

The core standard prescribes a floor of description and
access which can be further added to all the way to full.
Therefore, the core record is often described as being
dynamic and upwardly compatible.    This means that once a
core record has been created, other institutions may
continue to add fields to the record up to full level and
still code it as core.  So, should you wish to add the 041,
043 and 504 to an existing core record, you can lock and
replace the master record in OCLC.  It would still be coded
as core.

I hope this helps.  Let me know if you have further
  --Joan Schuitema, Chair Standing Committee on Standards

>>> Jacqueline Jo Byrd <[log in to unmask]> 05/12/98
01:48pm >>>
I have a question about how libraries are handling local
modifications to
PCC core level standards on PCC core level records input by
another institution.  For example, if you have decided to
make 043's,
041's, and
504's as part of your required (if applicable) local core
level standard, do you add these fields to the permanent
record in OCLC, or do you add them only to the record in
the local system?

Thanks for any comments!
Jackie Byrd,
Indiana University Libraries