MODINREACH-79 - Getting issue details... STATUS

D2IR Record contribution API data endpoints

Contribution

Contribute Batch Items

Add and modify item records.

URL parameters

Request parameters

ItemInfo

Contribute Bib

Adds and modifies bib records. The bibId can be used as the local system's unique bib identifier. Local sites
that have nonconforming record identifiers will need to have those identifiers converted to match the D2IR
bibId restrictions described in the table below. The submitted bib ID will become the unique INN-Reach cata-
log bib identifier.

URL parameters

Request parameters

Verification

Look Up Bib by bibId

This method allows a client to look up a bibliographic record by its ID.
The central returns the following status codes:

• 200 - The record was found, and the corresponding central record has been loaded.
• 404 - The record was not found in the "z" section of the i-file index.
• 500 - An error exists in the milproto format, or a system error occurred.

URL parameters

Response content

Sample Success Response:

{
"status":"ok",
"reason":"success",
"errors":[],
}

Sample Failure Response:

{
"status":"failed",
"reason":"Record not found",
"errors":[],
}

Look Up Bib by bibId and itemId

This method allows a client to look up a bibliographic record by its bibID and itemId.
The central returns the following status codes:

• 200 - The item was found, and the corresponding central record has been loaded.
• 404 - The item was not found by either the bibId or itemId.
• 500 - The item was found but belongs to a different bibliographic record than the one specified by the bibId.
• 500 - An error exists in the milproto format, or a system error occurred.

URL parameters

Response content

Sample Success Response:

{
"status":"ok",
"reason":"success",
"errors":[],
}

Sample Failure Response:

{
"status":"failed",
"reason":"Record not found",
"errors":[],
}

Sample Failure Response:

{
"status":"failed",
"reason":"Server internal error",
"errors": {
	"type": "error",
	"name": "Internal error",
	"reason": "Failed to load central record"
  }
}