These diagnostics may be included In TaskPackageRecordStructure of the Update Extended Service (see Revision 1), as surrogateDiagnostics within recordOrSurDiag, or supplementalDiagnostics. The target may return a diagnostic message alone, multiple diagnostic messages, or it may return a record accompanied by one or more diagnostic messages (in which case the diagnostic message are sypplied in supplementalDiagnostics).
A single message is used when the update has been accepted with nothing else to report (e.g. message 950). When a target returns a record, it is because the current database record is different from that supplied. Within the diagnostic message, addInfo is used by the target to indicate to the origin which parts of the record have changed, so that the origin can use this information, for example to highlight changed data.
The column "Include dbase record" indicates whether the database record should be included: 'n' means "no, don't include the record"; 'm' means "it is mandatory to incluce the record", and 'o' means "including the record is optional".
Code |
Description |
Include dbase record |
AddInfo |
900 |
Bulk edit / replace request accepted |
n |
record ID + version |
901 |
Bulk edit / replace request rejected - not authorised |
n |
|
902 |
Bulk edit / replace request rejected - result set not found |
n |
|
903 |
Bulk edit / replace request rejected - number of records different from result set |
n |
number in results set |
904 |
Bulk edit / replace request rejected - number of records exceeds target threshold |
n |
target threshold |
905 |
Bulk edit / replace rejected - instructions conflict with update type |
n |
|
906 |
Bulk edit / replace rejected - target cannot support case independent matching |
||
907 |
Interactive special update not possible - request has been batched |
n |
package name |
908 |
Update not performed - version conflict |
m |
record ID + version identifier |
909 |
Update not performed - string not found |
m |
Code |
Description |
Include dbase record |
AddInfo |
910 |
Invalid holdings code - holding addition rejected |
n |
record ID of bib record, code |
911 |
Holding not on file - holding change rejected |
n |
record ID of holding |
912 |
Holding not on file - holding deletion rejected |
n |
record ID of holding |
913 |
Cannot find matching bibliographic record - holding addition rejected |
n |
record ID of holding |
914 |
Holding insert rejected - holding record already exists for holding code |
n |
record ID of holding on file |
915 |
Holding replacement or deletion rejected - cannot uniquely identify record |
n |
record Ids of holdings records on file |
916 |
Cannot find holdings record; replacement request processed as an insert |
n |
RecordID of holding |
For the following (920-945) the additional information gives the address within a record enabling the origin to pinpoint the data that is invalid. The address for a MARC record consists of tag / tag sequence / subfield / subfield sequence. Tag sequence refers to the occurrence number of a particular field within a record and not to the sequence of the field in the record as a whole. For example, 700 / 002 refers to the second occurrence of 700 and not to the the second field in the record. Subfield sequence, on the other hand, refers to the actual position of the subfield within the field.
Code |
Description |
Include dbase record |
AddInfo (MARC structure) |
Example (MARC structure) |
920 |
Invalid tag - field rejected |
o |
tag / seq |
983 / 001 |
921 |
Invalid subfield code - subfield rejected |
o |
tag / seq / sf / seq |
700 / 001 / m / 001 |
922 |
Invalid subfield code - field rejected |
o |
tag / seq / sf / seq |
650 / 001 / m / 001 |
923 |
Invalid indicators - field rejected |
o |
tag / seq |
300 / 001 |
924 |
Invalid indicators - warning |
o |
tag / seq |
300 / 001 |
925 |
Missing or invalid fixed code element - default applied |
o |
tag / seq / position |
008 / 001 / 35 |
926 |
Missing or invalid fixed code element - field rejected |
o |
tag / seq / position |
008 / 001 / 6 |
927 |
Missing or invalid fixed code element - element or subfield rejected |
o |
tag / seq / position |
|
928 |
Invalid numeric - field rejected |
o |
tag / seq |
|
929 |
Invalid numeric - element or subfield rejected |
o |
tag / seq / sf / seq |
|
930 |
Invalid repetition of field - field rejected |
o |
tag / seq |
245 / 002 |
931 |
Invalid repetition of element or subfield - element or subfield rejected |
o |
tag / seq / sf / seq |
650 / 001 / a / 002 |
932 |
Invalid repetition of element or subfield - field rejected |
o |
tag / seq / sf / seq |
650 / 001 / a / 002 |
933 |
Missing or invalid mandatory field - record rejected |
o |
tag |
245 |
934 |
Missing or invalid mandatory field - default applied |
o |
tag / data |
008 |
935 |
Missing or invalid mandatory element or subfield - record rejected |
o |
tag / seq / sf |
|
936 |
Missing or invalid mandatory element or subfield - field rejected |
o |
tag / seq / sf |
|
937 |
Missing or invalid mandatory element or subfield - default applied |
o |
tag / seq / sf / data |
|
938 |
Invalid structure of non sort element - record rejected |
o |
tag / seq / sf / seq |
200 / 001 / a / 001 |
939 |
Invalid structure of non sort element - field rejected |
o |
tag / seq / sf / seq |
200 / 001 / a / 001 |
940 |
Invalid structure of non sort element - element or subfield rejected |
o |
tag / seq / sf / seq |
|
941 |
Invalid structure of non sort element - warning |
o |
tag / seq /sf /seq |
|
942 |
Invalid length of fixed field - field rejected |
o |
tag / seq |
008 / 001 |
943 |
Invalid record identifier |
n |
record ID |
|
944 |
Error in unpacking ISO 2709 record supplied |
n |
record |
|
945 |
Unable to read record supplied |
n |
record |
Code |
Description |
Include dbase record |
AddInfo |
950 |
Record insert reviewed and accepted |
n |
recordID + version identifier + reviewers text optional |
951 |
Record insert reviewed and modified |
m |
in additional messages; + reviewers text optional |
952 |
Record reviewed and failed |
o |
recordID + reviewers text optional |
953 |
Record replace or element update reviewed and accepted |
n |
record ID + version identifier + reviewers text optional |
954 |
Record replace or element update reviewed and modified |
o |
in additional messages + reviewers text |
955 |
Record replace, element update or record delete rejected - record or element not found or not uniquely identified |
n |
record ID |
956 |
Record replace, element update or record delete rejected - record protected or locked by another user |
n |
record ID + version identifier + lock expiry (optional) |
957 |
Record replace, element update or record delete rejected - record not locked by requesting user |
o |
record ID + version identifier |
958 |
Record delete request reviewed and accepted - record deleted |
n |
record ID |
959 |
Record delete rejected - record not on file |
n |
record ID |
960 |
Record delete request reviewed and failed - record not deleted |
n |
record ID + reviewers text optional |
961 |
Record delete rejected - database error in accessing or deleting record |
n |
record ID |
962 |
Record delete rejected - cannot delete target record - linked holdings exist |
n |
number of holdings; list of holdings record IDs or codes optional |
963 |
Record delete rejected - cannot delete target record - linked orders, suggestions or reservations exist |
n |
number of orders, suggestions, reservations |
964 |
Cannot process update - version conflict |
m |
|
965 |
Cannot process update - missing or unrecognised date / time stamp |
m |
time stamp (0 if missing) |
966 |
Cannot process update - not authorised |
o |
|
967 |
Cannot process update interactively - record replace or element update rejected |
o |
|
968 |
Record insert, record replace or element update rejected - database error |
n |
record ID |
969 |
Cannot find bibliographic record; replacement request processed as an insert |
n |
record ID |
Code |
Description |
Include dbase record |
AddInfo |
970 |
Record insert rejected - suspect duplicate |
m |
|
971 |
Record insert accepted - warning suspect duplicate |
m |
record ID + version of new record |
972 |
Record insert processed as a merge |
m |
record ID + version of database record |
Code |
Description |
Include dbase record |
AddInfo |
980 |
Heading matches with existing established heading - merged |
o |
tag / seq / data |
981 |
New established heading created |
o |
tag / seq / data |
982 |
Non preferred heading replaced with established heading |
o |
tag / seq / data |
983 |
Authority record rejected - established heading already on file |
m |
|
984 |
Authority record merged - established heading already on file |
m |
|
985 |
Authority record rejected - heading matches an established non preferred heading |
m |
Code |
Description |
Include dbase record |
AddInfo |
990 |
Merge accepted |
n |
record ID + version identifier of target record |
991 |
Merge rejected - target record missing |
n |
|
992 |
Merge rejected - cannot delete origin record - record protected or locked by another user |
o |
record ID of origin record |
993 |
Merge rejected - cannot merge target record - record not locked by requesting user |
o |
record ID + version identifier |
994 |
Merge rejected - cannot delete origin record - linked holdings exist |
o |
record ID of origin record |
995 |
Merge rejected - cannot delete origin record - linked orders or suggestions exist |
o |
record ID of origin record |
996 |
Merge rejected - not authorised |
o |
|
997 |
Merge rejected - version conflict target record |
m |
record ID + version identifier of target record |
998 |
Merge rejected - version conflict origin record |
m |
record ID + version identifier of origin record |