Preliminary data record - Revision history

Ccsrfischer at 16:53, 23 July 2025

2025-07-23T16:53:23Z

← Older revision		Revision as of 16:53, 23 July 2025
Line 41:		Line 41:
	245 00 LILO & STITCH 2-MOVIE COLLECTION (4K Combo)		245 00 LILO & STITCH 2-MOVIE COLLECTION (4K Combo)
	}}		}}
			==Encoding Level 3 Records as PDRs==
			If a Level 3 record is used as a Preliminary Data Record, all appropriate fields '''must''' be corrected to CCS standards for these records. Most important is changing the 720 to 100, 110, 700 or 710 as appropriate, and checking it in the Authority File. The 260 or 264 field should also include the requisite &Dagger;b and &Dagger;c information, as this affects the display the online catalog.
	==See also==		==See also==
	[[Working with preliminary data records]]		*[[Working with preliminary data records]]
			*[https://www.ccslib.org/Catalogers/images/2/29/Level3.txt Connexion macro to upgrade level 3 records]

	==References==		==References==
	<references />		<references />

Ccsrfischer at 14:53, 26 March 2025

2025-03-26T14:53:22Z

← Older revision		Revision as of 14:53, 26 March 2025
Line 25:		Line 25:

	;Videogames		;Videogames
	: For on-order records or PDRs only, add the videogame platform as it appears in the 753 field after the title in parentheses. This will ensure that acquisitions staff receive and invoice the correct line item. This will be removed from the final record. <ref name="acqin202309">Acquisitions Technical Group Meeting Minutes, September 2023</ref>		For on-order records or PDRs only, add the videogame platform as it appears in the 753 field after the title in parentheses. This will ensure that acquisitions staff receive and invoice the correct line item. This will be removed from the final record. <ref name="acqin202309">Acquisitions Technical Group Meeting Minutes, September 2023</ref>

	: '''Examples:'''		: '''Examples:'''
Line 34:		Line 34:

	;4K Blu-rays		;4K Blu-rays
	: For on-order records or PDRs only, add 4K or 4K combo after the title in parentheses. This will ensure that acquisitions staff receive and invoice the correct line item. This will be removed from the final record. <ref name="acqin202503">Acquisitions Technical Group Meeting Minutes, March 2025</ref>		For on-order records or PDRs only, add 4K or 4K combo after the title in parentheses. This will ensure that acquisitions staff receive and invoice the correct line item. This will be removed from the final record. <ref name="acqin202503">Acquisitions Technical Group Meeting Minutes, March 2025</ref>

	: '''Examples:'''		: '''Examples:'''

Ccsrfischer at 14:47, 26 March 2025

2025-03-26T14:47:11Z

@@ Line 1: / Line 1: @@
-[[Category:Local practices]]
+[https://www.ccslib.org/sites/default/files/2024-05/CCS%20ACQ%20Minutes%209_20_2023.pdf ACQ Meeting minutes, September 2023][[Category:Local practices]]
 [[Category:Preliminary data records]]
 [[Category:Polaris specific topics‏‎]]
@@ Line 22: / Line 22: @@
 * The item is checked out to an in-house user (e.g. Technical Services Supervisor)
 ==See also==
 [[Working with preliminary data records]]

Ccsrfischer at 18:20, 1 November 2022

2022-11-01T18:20:47Z

← Older revision		Revision as of 18:20, 1 November 2022
Line 2:		Line 2:
	[[Category:Preliminary data records]]		[[Category:Preliminary data records]]
	[[Category:Polaris specific topics‏‎]]		[[Category:Polaris specific topics‏‎]]
	'''Preliminary Data records''' (~~PDRs~~), are MARC bibliographic records that have not been fully cataloged by a CCS cataloger. They often contain incomplete bibliographic data, that may later be found to be incorrect. Even if the data is completely accurate, a record is considered preliminary in the local database until a CCS cataloger has reviewed and verified the record with the item in hand, overlaying with an OCLC record if necessary.		'''Preliminary Data records''' (PDR), are MARC bibliographic records that have not been fully cataloged by a CCS cataloger. They often contain incomplete bibliographic data, that may later be found to be incorrect. Even if the data is completely accurate, a record is considered preliminary in the local database until a CCS cataloger has reviewed and verified the record with the item in hand, overlaying with an OCLC record if necessary.

	PDRs may be entered into the CCS database in one of the following ways:		PDRs may be entered into the CCS database in one of the following ways:

Scrap at 17:23, 15 November 2018

2018-11-15T17:23:02Z

← Older revision		Revision as of 17:23, 15 November 2018
Line 12:		Line 12:
	Libraries are encouraged to include OCLC numbers in PDRs whenever possible.<ref name="scrapmin201105">[http://ccslib.org/attachments/File/SCRAP/SCRAP_May_18_2011.pdf SCRAP Meeting minutes, May 2011]</ref>		Libraries are encouraged to include OCLC numbers in PDRs whenever possible.<ref name="scrapmin201105">[http://ccslib.org/attachments/File/SCRAP/SCRAP_May_18_2011.pdf SCRAP Meeting minutes, May 2011]</ref>

	~~These fields indicate~~ a record is preliminary:		The 099 field indicates a record is preliminary and still needs cataloging:
	{{example\|text=		{{example\|text=
	~~049 JEDA~~
	099 PRELIMINARY DATA}}		099 PRELIMINARY DATA}}

	~~The 049 field may have a specific library code instead; some older fully cataloged records may still have JEDA (CCS's OCLC symbol) or have no 049 field at all.~~		The 099 field may have <code>VENDOR PRELIMINARY DATA RECORD</code> instead if the record was obtained from a vendor such as Baker & Taylor rather than being hand-keyed or imported from OCLC, but the term "PRELIMINARY DATA" must be included.

	The 099 field may have <code>VENDOR PRELIMINARY DATA RECORD</code> instead if the record was obtained from a vendor such as Baker & Taylor rather than being hand-keyed or imported from OCLC, but the ~~phrase~~ "PRELIMINARY DATA" must be included.

	Items attached to PDRs can circulate only under the following circumstances:		Items attached to PDRs can circulate only under the following circumstances:

Scrap at 16:03, 6 September 2018

2018-09-06T16:03:40Z

← Older revision		Revision as of 16:03, 6 September 2018
Line 1:		Line 1:
	'''Preliminary ~~data~~ records''' (PDRs), are ~~either hand-keyed brief~~ MARC ~~records or imported OCLC~~ records that have not been ~~locally edited~~ by a CCS cataloger. ~~These records~~ often contain incomplete bibliographic data ~~(ISBN~~, ~~Publisher’s number, title, author, edition, publisher, date, etc.)~~ that may be ~~later~~ found to be incorrect. Even if the data is completely accurate, a record is considered preliminary in the local database until a CCS cataloger has reviewed and verified the record ~~and compared its access points~~ with the item in hand.		[[Category:Local practices]]
			[[Category:Preliminary data records]]
			[[Category:Polaris specific topics‏‎]]
			'''Preliminary Data records''' (PDRs), are MARC bibliographic records that have not been fully cataloged by a CCS cataloger. They often contain incomplete bibliographic data, that may later be found to be incorrect. Even if the data is completely accurate, a record is considered preliminary in the local database until a CCS cataloger has reviewed and verified the record with the item in hand, overlaying with an OCLC record if necessary.

	~~Preliminary data records are~~ entered into the CCS database in one of the following ways:		PDRs may be entered into the CCS database in one of the following ways:
	# Records are [[Input hand-keyed preliminary data records\|hand-keyed]] ~~directly into~~ the ~~database~~.		# Records are [[Input hand-keyed preliminary data records\|hand-keyed]].
	# Records are [[Import preliminary data records from Connexion\|imported ~~electronically~~ from OCLC using Connexion]].		# Records are imported one at a time from OCLC using the Bibliographic Records Find Tool in Polaris.
	# Records are [[~~Import~~ preliminary data records ~~with SmartPort~~\|imported ~~electronically~~ from ~~OCLC using SmartPort~~]].		# Records are [[Import preliminary data records from Connexion\|imported from OCLC using Connexion]].
			# Records are [[Importing vendor preliminary data records\|imported from a vendor]].

	Libraries are encouraged to ~~use~~ OCLC numbers in ~~preliminary data records~~ whenever possible.<ref name="scrapmin201105">[http://ccslib.org/attachments/File/SCRAP/SCRAP_May_18_2011.pdf SCRAP Meeting minutes, May 2011]</ref>		Libraries are encouraged to include OCLC numbers in PDRs whenever possible.<ref name="scrapmin201105">[http://ccslib.org/attachments/File/SCRAP/SCRAP_May_18_2011.pdf SCRAP Meeting minutes, May 2011]</ref>

	~~Three~~ fields indicate a record is ~~still~~ preliminary:		These fields indicate a record is preliminary:
	{{example\|text=		{{example\|text=
	~~Date cataloged=NEVER~~
	049 JEDA		049 JEDA
	099 PRELIMINARY DATA}}		099 PRELIMINARY DATA}}

	The 049 field may ~~contain~~ a specific library code, some older fully cataloged records still ~~say~~ JEDA or have no 049 field at all.		The 049 field may have a specific library code instead; some older fully cataloged records may still have JEDA (CCS's OCLC symbol) or have no 049 field at all.

	The 099 may ~~be replaced with~~ <code>~~099~~ VENDOR PRELIMINARY DATA RECORD</code> ~~when~~ the ~~preliminary~~ record was obtained from a vendor such as Baker & Taylor rather than being hand-keyed or imported from OCLC~~. (Vendor preliminary data records~~ must ~~always~~ be ~~overlaid with a new record from OCLC when the item is cataloged~~.)		The 099 field may have <code>VENDOR PRELIMINARY DATA RECORD</code> instead if the record was obtained from a vendor such as Baker & Taylor rather than being hand-keyed or imported from OCLC, but the phrase "PRELIMINARY DATA" must be included.

	Items attached to ~~these records~~ can circulate only under ~~either of~~ the following circumstances:		Items attached to PDRs can circulate only under the following circumstances:
	# The record ~~contains <code>~~099~~</code> with~~ an ~~indication of~~ intent to ~~upgrade to full MARC~~ (e.g., <code>~~xxxmarc 20080430~~</code>)		* The record's 099 field indicates an intent to fully catalog at a later date (e.g. <code>nikmarc 20180417</code>)
	# The item is ~~to be~~ checked out to an in-house user (e.g., Technical Services~~, Cataloging~~)		* The item is checked out to an in-house user (e.g. Technical Services Supervisor)

	Preliminary data records also help CCS libraries maximize the benefits of cooperative cataloging within the consortium. A library's symbol in the 099 field of a preliminary data record identifies the library that will take responsibility for providing a final bibliographic record that meets CCS standards.

	==See also==		==See also==
	[[~~Identifying~~ preliminary data records]]		[[Working with preliminary data records]]

	==References==		==References==
	<references />		<references />
	~~[[Category:Local practices]]~~
	~~[[Category:Preliminary data records]]~~
	~~[[Category:SirsiDynix-specific topics‏‎]]~~
	~~[[Category:Using WorkFlows‏‎]]~~

Wikiupdatetf at 16:32, 30 August 2017

2017-08-30T16:32:03Z

@@ Line 1: / Line 1: @@
 '''Preliminary data records''' (PDRs), are either hand-keyed brief MARC records or imported OCLC records that have not been locally edited by a CCS cataloger. These records often contain incomplete bibliographic data (ISBN, Publisher’s number, title, author, edition, publisher, date, etc.) that may be later found to be incorrect.  Even if the data is completely accurate, a record is considered preliminary in the local database until a CCS cataloger has reviewed and verified the record and compared its access points with the item in hand.
@@ Line 34: / Line 29: @@
 ==References==
 <references />

Wikiupdatetf at 21:47, 6 February 2017

2017-02-06T21:47:45Z

← Older revision		Revision as of 21:47, 6 February 2017
Line 1:		Line 1:
	[[Category:~~Glossary~~]]		[[Category:Local practices]]
	[[Category:Preliminary data records]]		[[Category:Preliminary data records]]
			[[Category:SirsiDynix-specific topics‏‎]]
			[[Category:Using WorkFlows‏‎]]

	'''Preliminary data records''' (PDRs), are either hand-keyed brief MARC records or imported OCLC records that have not been locally edited by a CCS cataloger. These records often contain incomplete bibliographic data (ISBN, Publisher’s number, title, author, edition, publisher, date, etc.) that may be later found to be incorrect. Even if the data is completely accurate, a record is considered preliminary in the local database until a CCS cataloger has reviewed and verified the record and compared its access points with the item in hand.		'''Preliminary data records''' (PDRs), are either hand-keyed brief MARC records or imported OCLC records that have not been locally edited by a CCS cataloger. These records often contain incomplete bibliographic data (ISBN, Publisher’s number, title, author, edition, publisher, date, etc.) that may be later found to be incorrect. Even if the data is completely accurate, a record is considered preliminary in the local database until a CCS cataloger has reviewed and verified the record and compared its access points with the item in hand.

Kschmdt at 21:37, 10 February 2016

2016-02-10T21:37:50Z

← Older revision		Revision as of 21:37, 10 February 2016
Line 15:		Line 15:
	Date cataloged=NEVER		Date cataloged=NEVER
	049 JEDA		049 JEDA
	~~999~~ PRELIMINARY DATA}}		099 PRELIMINARY DATA}}

	The 049 field may contain a specific library code, some older fully cataloged records still say JEDA or have no 049 field at all.		The 049 field may contain a specific library code, some older fully cataloged records still say JEDA or have no 049 field at all.

	The ~~999~~ may be replaced with <code>099 VENDOR PRELIMINARY DATA RECORD</code> when the preliminary record was obtained from a vendor such as Baker & Taylor rather than being hand-keyed or imported from OCLC. (Vendor preliminary data records must always be overlaid with a new record from OCLC when the item is cataloged.)		The 099 may be replaced with <code>099 VENDOR PRELIMINARY DATA RECORD</code> when the preliminary record was obtained from a vendor such as Baker & Taylor rather than being hand-keyed or imported from OCLC. (Vendor preliminary data records must always be overlaid with a new record from OCLC when the item is cataloged.)

	Items attached to these records can circulate only under either of the following circumstances:		Items attached to these records can circulate only under either of the following circumstances:
	# The record contains <code>~~999~~</code> with an indication of intent to upgrade to full MARC (e.g., <code>xxxmarc 20080430</code>)		# The record contains <code>099</code> with an indication of intent to upgrade to full MARC (e.g., <code>xxxmarc 20080430</code>)
	# The item is to be checked out to an in-house user (e.g., Technical Services, Cataloging)		# The item is to be checked out to an in-house user (e.g., Technical Services, Cataloging)

	Preliminary data records also help CCS libraries maximize the benefits of cooperative cataloging within the consortium. A library's symbol in the ~~999~~ field of a preliminary data record identifies the library that will take responsibility for providing a final bibliographic record that meets CCS standards.		Preliminary data records also help CCS libraries maximize the benefits of cooperative cataloging within the consortium. A library's symbol in the 099 field of a preliminary data record identifies the library that will take responsibility for providing a final bibliographic record that meets CCS standards.

	==See also==		==See also==

Kschmdt at 21:54, 16 April 2013

2013-04-16T21:54:24Z

← Older revision		Revision as of 21:54, 16 April 2013
Line 17:		Line 17:
	999 PRELIMINARY DATA}}		999 PRELIMINARY DATA}}

	~~Though the~~ 049 field may contain a specific library code, some older fully cataloged records still say JEDA or have no 049 field at all.		The 049 field may contain a specific library code, some older fully cataloged records still say JEDA or have no 049 field at all.

			The 999 may be replaced with <code>099 VENDOR PRELIMINARY DATA RECORD</code> when the preliminary record was obtained from a vendor such as Baker & Taylor rather than being hand-keyed or imported from OCLC. (Vendor preliminary data records must always be overlaid with a new record from OCLC when the item is cataloged.)

	Items attached to these records can circulate only under either of the following circumstances:		Items attached to these records can circulate only under either of the following circumstances:
	# The record contains <code>999</code> "intent to upgrade to full MARC" (e.g., <code>xxxmarc 20080430</code>)		# The record contains <code>999</code> with an indication of intent to upgrade to full MARC (e.g., <code>xxxmarc 20080430</code>)
	# The item is to be checked out to an in-house user (e.g., Technical Services, Cataloging)		# The item is to be checked out to an in-house user (e.g., Technical Services, Cataloging)