Common use of Value Label Notes Iss Rev Clause in Contracts

Value Label Notes Iss Rev. List 1 Notification or update type 0 01 Early notification Use for a complete record issued earlier than approximately six months before publication 0 02 Advance notification (confirmed) Use for a complete record issued to confirm advance information approximately six months before publication; or for a complete record issued after that date and before information has been confirmed from the book-in-hand 0 03 Notification confirmed on publication Use for a complete record issued to confirm advance information at or just before actual publication date, usually from the book-in-hand, or for a complete record issued at any later date 0 11 04 Update (partial) In ONIX 3.0 only, use when sending a ‘block update’ record. A block update implies using the supplied block(s) to update the existing record for the product, replacing only the blocks included in the block update, and leaving other blocks unchanged – for example, replacing old information from Blocks 4 and 6 with the newly-received data while retailing information from Blocks 1–3 and 5 untouched. In previous ONIX releases, and for ONIX 3.0 using other notification types, updating is by replacing the complete record with the newly-received data 0 42 Value Label Notes Iss Rev 05 Delete Use when sending an instruction to delete a record which was previously issued. Note that a Delete instruction should NOT be used when a product is cancelled, put out of print, or otherwise withdrawn from sale: this should be handled as a change of Publishing status, leaving the receiver to decide whether to retain or delete the record. A Delete instruction is used ONLY when there is a particular reason to withdraw arecord completely, eg because it was issued in error 0 08 Notice of sale Notice of sale of a product, from one publisher to another: sent by the publisher disposing of the product 2 09 Notice of acquisition Notice of acquisition of a product, by one publisher from another: sent by the acquiring publisher 2

Appears in 1 contract

Samples: www.editeur.org

AutoNDA by SimpleDocs

Value Label Notes Iss Rev. List 1 Notification or update type code 0 01 Early notification Use for a complete record issued earlier than approximately six months before publication 0 02 Advance notification (confirmed) Use for a complete record issued to confirm advance information approximately six months before publication; or for a complete record issued after that date and before information has been confirmed from the book-in-hand 0 03 Notification confirmed on publication Use for a complete record issued to confirm advance information at or just before actual publication date, usually from the book-in-hand, ; or for a complete record issued at any later date 0 11 04 Update (partial) In ONIX 3.0 only, use when sending a ‘block update’ record. A block update implies using the supplied block(s) to update the existing record for the product, replacing only the blocks included in the block update, and leaving other blocks unchanged – for example, replacing old information from Blocks 4 and 6 with the newly-received data while retailing information from Blocks 1–3 and 5 untouched. In previous ONIX releases, and for ONIX 3.0 using other notification types, updating is has generally been by replacing the complete record with the newly-received data replacement using code 03, and code 04 is not used 0 42 Value Label Notes Iss Rev 11 05 Delete Use when sending an instruction to delete a record which was previously issued. Note that a Delete instruction should NOT be used when a product is cancelled, put out of print, or otherwise withdrawn from sale: this should be handled as a change of Publishing status, leaving the receiver to decide whether to retain or delete the record. A Delete instruction is only used ONLY when there is a particular reason to withdraw arecord a record completely, eg because it was issued in error 0 08 Notice of sale Notice of sale of a product, from one publisher to another: sent by the publisher disposing of the product 2 09 Notice of acquisition Notice of acquisition of a product, by one publisher from another: sent by the acquiring publisher 2

Appears in 1 contract

Samples: www.editeur.org

Value Label Notes Iss Rev. List 1 Notification or update type 0 01 Early notification Use for a complete record issued earlier than approximately six months before publication 0 02 Advance notification (confirmed) Use for a complete record issued to confirm advance information approximately six months before publication; or publication;or for a complete record issued after that date and before information has been confirmed from the book-in-hand 0 03 Notification confirmed on publication Use for a complete record issued to confirm advance information at or just before actual publication date, ,usually from the book-in-hand, or for a complete record issued at any later date 0 11 04 Update (partial) In ONIX 3.0 only, use when sending a ‘block update’ record. A block update implies using the supplied block(s) to update the existing record for the product, replacing only the blocks included in the block update, and leaving other blocks unchanged – for example, replacing old information from Blocks 4 and 6 with the newly-received data while retailing information from Blocks 1–3 and 5 untouched. In previous ONIX releases, and for ONIX 3.0 using 3.0using other notification types, updating is by replacing the complete record with the newly-received data 0 42 Value Label Notes Iss Rev 05 Delete Use when sending an instruction to delete a record which was previously issued. Note that a Delete instruction should NOT be used when a product is cancelled, put out of print, or otherwise withdrawn from sale: this should be handled as a change of Publishing status, leaving the receiver to decide whether to retain or delete the record. A Delete instruction is used ONLY when there is a particular aparticular reason to withdraw arecord a record completely, eg because it was issued in error 0 08 Notice of sale Notice of sale of a product, from one publisher to another: sent by the publisher disposing of the product 2 09 Notice of acquisition Notice of acquisition of a product, by one publisher from another: sent by the acquiring publisher 2

Appears in 1 contract

Samples: www.editeur.org

Value Label Notes Iss Rev. List 1 Notification or update type 0 01 Early notification Use for a complete record issued earlier than approximately six months before publication 0 02 Advance notification (confirmed) Use for a complete record issued to confirm advance information approximately six months before publication; or for a complete record issued after that date and before information has been confirmed from the book-in-hand 0 03 Notification confirmed on publication Use for a complete record issued to confirm advance information at or just before actual publication date, usually from the book-in-hand, or for a complete record issued at any later date 0 11 04 Update (partial) In ONIX 3.0 only, use when sending a ‘block update’ record. A block update implies using the supplied block(s) to update the existing record for the product, replacing only the blocks included in the block update, and leaving other blocks unchanged – for example, replacing old information from Blocks 4 and 6 with the newly-received data while retailing information from Blocks 1–3 and 5 untouched. In previous ONIX releases, and for ONIX 3.0 using other notification types, updating is has generally been by replacing the complete record with the newly-received data replacement using code 03, and code 04 is not used 0 42 Value Label Notes Iss Rev 11 05 Delete Use when sending an instruction to delete a record which was previously issued. Note that a Delete instruction should NOT be used when a product is cancelled, put out of print, or otherwise withdrawn from sale: this should be handled as a change of Publishing status, leaving the receiver to decide whether to retain or delete the record. A Delete instruction is used ONLY when there is a particular aparticular reason to withdraw arecord a record completely, eg because it was issued in error 0 08 Notice of sale Notice of sale of a product, from one publisher to another: sent by the publisher disposing of the product 2 09 Notice of acquisition Notice of acquisition of a product, by one publisher from another: sent by the acquiring publisher 2

Appears in 1 contract

Samples: www.editeur.org

Value Label Notes Iss Rev. List 1 Notification or update type 0 01 Early notification Use for a complete record issued earlier than approximately six months before publication 0 02 Advance notification (confirmed) Use for a complete record issued to confirm advance information approximately six months before publication; or for a complete record issued after that date and before information has been confirmed from the book-in-hand 0 03 Notification confirmed on publication Use for a complete record issued to confirm advance information at or just before actual publication date, usually from the book-in-hand, or for a complete record issued at any later date 0 11 04 Update (partial) In ONIX 3.0 only, use when sending a ‘block update’ record. A block update implies using the supplied block(s) to update the existing record for the product, replacing only the blocks included in the block update, and leaving other blocks unchanged – for example, replacing old information from Blocks 4 and 6 with the newly-received data while retailing information from Blocks 1–3 and 5 untouched. In previous ONIX releases, and for ONIX 3.0 using other notification types, updating is by replacing the complete thecomplete record with the newly-received data 0 42 Value Label Notes Iss Rev 05 Delete Use when sending an instruction to delete a record which was previously issued. Note that a Delete instruction should NOT be used when a product is cancelled, put out of print, or otherwise withdrawn from sale: this should be handled as a change of Publishing status, leaving the receiver to decide whether to retain or delete the record. A Delete instruction is used ONLY when there is a particular reason to withdraw arecord a record completely, eg because it was issued in error 0 08 Notice of sale Notice of sale of a product, from one publisher to another: sent by the publisher disposing of the product 2 09 Notice of acquisition Notice of acquisition of a product, by one publisher from another: sent by the acquiring publisher 22 Value Label Notes Iss Rev 88 Test update (Partial) ONIX 3.0 only. Record may be processed for test purposes, but data should be discarded when testing iscomplete. Sender must ensure the <RecordReference> matches a previously-sent Test record 26 89 Test record Record may be processed for test purposes, but data should be discarded when testing is complete. Sendermust ensure the <RecordReference> does not match any previously-sent live product record 26 List 2 Product composition 9 00 Single-component retail product 9 39

Appears in 1 contract

Samples: www.editeur.org

Value Label Notes Iss Rev. List 1 Notification or update type 0 01 Early notification Use for a complete record issued earlier than approximately six months before publication 0 02 Advance notification (confirmed) Use for a complete record issued to confirm advance information approximately six months before publication; or for a complete record issued after that date and before information has been confirmed from the book-in-hand 0 03 Notification confirmed on publication Use for a complete record issued to confirm advance information at or just before actual publication date, usually from the book-in-hand, or for a complete record issued at any later date 0 11 04 Update (partial) In ONIX 3.0 only, use when sending a ‘block update’ record. A block update implies using the supplied block(s) to update the existing record for the product, replacing only the blocks included in the block update, and leaving other blocks unchanged – for example, replacing old information from Blocks 4 and 6 with the newly-received data while retailing information from Blocks 1–3 and 5 untouched. In previous ONIX releases, and for ONIX 3.0 using other notification types, updating is by replacing the complete record with the newly-received data 0 42 Value Label Notes Iss Rev 05 Delete Use when sending an instruction to delete a record which was previously issued. Note that a Delete instruction should NOT be used when a product is cancelled, put out of print, or otherwise withdrawn from sale: this should be handled as a change of Publishing status, leaving the receiver to decide whether to retain or delete the record. A Delete instruction is used ONLY when there is a particular reason to withdraw arecord a record completely, eg because it was issued in error 0 08 Notice of sale Notice of sale of a product, from one publisher to another: sent by the publisher disposing of the product 2 09 Notice of acquisition Notice of acquisition of a product, by one publisher from another: sent by the acquiring publisher 2

Appears in 1 contract

Samples: www.editeur.org

Value Label Notes Iss Rev. List 1 Notification or update type 0 01 Early notification Use for a complete record issued earlier than approximately six months before publication 0 02 Advance notification (confirmed) Use for a complete record issued to confirm advance information approximately six months before publication; or for a complete record issued after that date and before information has been confirmed from the book-in-in- hand 0 03 Notification confirmed on publication Use for a complete record issued to confirm advance information at or just before actual publication date, usually from the book-in-hand, or for a complete record issued at any later date 0 11 04 Update (partial) In ONIX 3.0 only, use when sending a ‘block update’ record. A block update implies using the supplied block(s) to update the existing record for the product, replacing only the blocks included in the block update, and leaving other blocks unchanged – for example, replacing old information from Blocks 4 and 6 with the newly-received data while retailing information from Blocks 1–3 and 5 untouched. In previous ONIX releases, and for ONIX 3.0 using other notification types, updating is by replacing the complete record with the newly-newly- received data 0 42 Value Label Notes Iss Rev 05 Delete Use when sending an instruction to delete a record which was previously issued. Note that a Delete instruction should NOT be used when a product is cancelled, put out of print, or otherwise withdrawn from sale: this should be handled as a change of Publishing status, leaving the receiver to decide whether to retain or delete the record. A Delete instruction is used ONLY when there is a particular reason to withdraw arecord a record completely, eg because it was issued in error 0 08 Notice of sale Notice of sale of a product, from one publisher to another: sent by the publisher disposing of the product 2 09 Notice of acquisition Notice of acquisition of a product, by one publisher from another: sent by the acquiring publisher 22 Value Label Notes Iss Rev 88 Test update (Partial) ONIX 3.0 only. Record may be processed for test purposes, but data should be discarded when testing is complete. Sender must ensure the <RecordReference> matches a previously-sent Test record 26 89 Test record Record may be processed for test purposes, but data should be discarded when testing is complete. Sender must ensure the <RecordReference> does not match any previously-sent live product record 26 List 2 Product composition 9 00 Single-component retail product 9 39 10 Multiple-component retail product Multiple-component product retailed as a whole 9 39 11 Multiple-item collection, retailed as separate parts Used only when an ONIX record is required for a collection-as-a-whole, even though it is not currently retailed as such 9 39 20 Trade-only product Product available to the book trade, but not for retail sale, and not carrying retail items, eg empty dumpbin, empty counterpack, promotional material 9 39 30 Multiple-item trade-only pack Product available to the book trade, but not for general retail sale as a whole. It carries multiple components for retailing as separate items, eg shrink-wrapped trade pack, filled dumpbin, filled counterpack 9 39 31 Multiple-item pack Carrying multiple components, primarily for retailing as separate items. The pack may be split and retailed as separate items OR retailed as a single item. Use instead of Multiple-item trade-only pack (code 30) if the data provider specifically wishes to make explicit that the pack may optionally be retailed as a whole 21 39 List 3 Record source type 0 00 Unspecified 0 01 Publisher 0 02 Publisher’s distributor Use to designate a distributor providing primary warehousing and fulfillment for a publisher or for a publisher’s sales agent, as distinct from a wholesaler 0 46 03 Wholesaler 0 04 Bibliographic agency Bibliographic data aggregator 0 05 Library bookseller Library supplier. Bookseller selling to libraries (including academic libraries) 0 06 Publisher’s sales agent Use for a publisher’s sales agent responsible for marketing the publisher’s products within a territory, as opposed to a publisher’s distributor who fulfills orders but does not market 4

Appears in 1 contract

Samples: editeur.org

AutoNDA by SimpleDocs

Value Label Notes Iss Rev. List 1 Notification or update type 0 01 Early notification Use for a complete record issued earlier than approximately six months before publication 0 02 Advance notification (confirmed) Use for a complete record issued to confirm advance information approximately six months before publication; or for a complete record issued after that date and before information has been confirmed from the book-in-hand 0 03 Notification confirmed on publication Use for a complete record issued to confirm advance information at or just before actual publication date, usually from the book-in-hand, or for a complete record issued at any later date 0 11 04 Update (partial) In ONIX 3.0 only, use when sending a ‘block update’ record. A block update implies using the supplied block(s) to update the existing record for the product, replacing only the blocks included in the block update, and leaving other blocks unchanged – for example, replacing old information from Blocks 4 and 6 with the newly-received data while retailing information from Blocks 1–3 and 5 untouched. In previous ONIX releases, and for ONIX 3.0 using other notification types, updating is by replacing the complete thecomplete record with the newly-received data 0 42 Value Label Notes Iss Rev 05 Delete Use when sending an instruction to delete a record which was previously issued. Note that a Delete instruction should NOT be used when a product is cancelled, put out of print, or otherwise withdrawn from sale: this should be handled as a change of Publishing status, leaving the receiver to decide whether to retain or delete the record. A Delete instruction is used ONLY when there is a particular aparticular reason to withdraw arecord a record completely, eg because it was issued in error 0 08 Notice of sale Notice of sale of a product, from one publisher to another: sent by the publisher disposing of the product 2 09 Notice of acquisition Notice of acquisition of a product, by one publisher from another: sent by the acquiring publisher 2

Appears in 1 contract

Samples: www.editeur.org

Value Label Notes Iss Rev. List 1 Notification or update type 0 01 Early notification Use for a complete record issued earlier than approximately six months before publication 0 02 Advance notification (confirmed) Use for a complete record issued to confirm advance information approximately six months before publication; or for a complete record issued after that date and before information has been confirmed from the book-in-hand 0 03 Notification confirmed on publication Use for a complete record issued to confirm advance information at or just before actual publication date, usually from the book-in-hand, or for a complete record issued at any later date 0 11 04 Update (partial) In ONIX 3.0 only, use when sending a ‘block update’ record. A block update implies using the supplied block(s) to update the existing record for the product, replacing only the blocks included in the block update, and leaving other blocks unchanged – for example, replacing old information from Blocks 4 and 6 with the newly-received data while retailing information from Blocks 1–3 and 5 untouched. In previous ONIX releases, and for ONIX 3.0 using other notification types, updating is by replacing the complete record with the newly-received data 0 42 Value Label Notes Iss Rev 05 Delete Use when sending an instruction to delete a record which was previously issued. Note that a Delete instruction should NOT be used when a product is cancelled, put out of print, or otherwise withdrawn from sale: this should be handled as a change of Publishing status, leaving the receiver to decide whether to retain or delete the record. A Delete instruction is used ONLY when there is a particular reason to withdraw arecord a record completely, eg because it was issued in error 0 Value Label Notes Iss Rev 08 Notice of sale Notice of sale of a product, from one publisher to another: sent by the publisher disposing of the product 2 09 Notice of acquisition Notice of acquisition of a product, by one publisher from another: sent by the acquiring publisher 2

Appears in 1 contract

Samples: www.editeur.org

Value Label Notes Iss Rev. List 1 Notification or update type 0 01 Early notification Use for a complete record issued earlier than approximately six months before publication 0 02 Advance notification (confirmed) Use for a complete record issued to confirm advance information approximately six months before publication; or for a complete record issued after that date and before information has been confirmed from the book-in-hand 0 03 Notification confirmed on publication Use for a complete record issued to confirm advance information at or just before actual publication date, usually from the book-in-hand, or for a complete record issued at any atany later date 0 11 04 Update (partial) In ONIX 3.0 only, use when sending a ‘block update’ record. A block update implies using the supplied block(s) to update the existing record for the product, replacing only the blocks included in the block update, and leaving other blocks unchanged – for example, replacing old information from Blocks 4 and 6 with the newly-received data while retailing information from Blocks 1–3 and 5 untouched. In previous ONIX releases, and for ONIX 3.0 using other notification types, updating is by replacing the complete record with the newly-received data 0 42 Value Label Notes Iss Rev 05 Delete Use when sending an instruction to delete a record which was previously issued. Note that a Delete instruction should NOT be used when a product is cancelled, put out of print, or otherwise withdrawn from sale: this should be handled as a change of Publishing status, leaving the receiver to decide whether to retain or delete the record. A Delete instruction is used ONLY when there is a particular reason to reasonto withdraw arecord a record completely, eg because it was issued in error 0 08 Notice of sale Notice of sale of a product, from one publisher to another: sent by the publisher disposing of the product 2 09 Notice of acquisition Notice of acquisition of a product, by one publisher from another: sent by the acquiring publisher 2

Appears in 1 contract

Samples: www.editeur.org

Time is Money Join Law Insider Premium to draft better contracts faster.