Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

IMS's PWD and PWI API's are used during deaccessioning an item.

When an item to be deaccessioned is available in SCSB database then PWD api is called otherwise PWI api is called to perform deaccession.                                                     

PERMANENT WITHDRAWAL - DIRECT

IMS will accept JSON-encoded REST calls to permanently retrieve items from the storage facility.  The required fields are the owner code (CustomerCode), the item barcode (itemBarcode) and the stop code (destination).

Request format for permanent retrieval item - direct
{ "dsitem":
   { "ttitem": [
     {
       // required fields
       "CustomerCode": "string"
       "itemBarcode": "string"
       "destination": "string"

       "requestorName": "string"
       // or at least one of
       "requestorFirstName": "string"
       "requestorMiddleName": "string"
       "requestorLastName": "string"
     }
     , { "CustomerCode": "string" ... } ...
   ] } // end of ttitem array   
}
Response format for permanent retrieval item - direct
{ "dsitem":
  { "ttitem": [
    {
      // required fields
      "CustomerCode": "string"
      "itemBarcode": "string"
      "destination": "string"

      "requestorName": "string"
      // or at least one of
      "requestorFirstName": "string"
      "requestorMiddleName": "string"
      "requestorLastName": "string"
      “errorCode”: “string”
      “errorNote”: “string”
    }
     , { "CustomerCode": "string" ... } ...
  ] } // end}
  • The CustomerCode and destination fields must either match the owner and stop codes in the LAS system.
  • The owner code is used only for verification purposes.  It is compared to the code stored in the LAS system, and an error is returned if it does not match
  • LAS does not separately store the first, middle, and last names of the requestor.  If the requestor is blank or missing, it will be constructed from the requestorFirstName, requestorMiddleName, and requestorLastName.  If the requestor field contains data, the other three fields are ignored.

Error codes for permanentlyRetrieveItem

errorCode

errorNote

Description

itemNotOnFile


Item barcode not found in LAS

wrongCustCode

CustomerCode: XX

The supplied customer code does not match the one stored in LAS.  The correct code is returned in the errorNote.

itemWithdrawn

item status, if available.  Otherwise, the message "Status unknown - possible reaccession" is returned.

The item has been permanently withdrawn from LAS.

missingReqData

Comma-delimited list of required fields that were not supplied.  If requestor data is missing, the field “requestor” is reported.

One or more required fields were empty

InternalErr

The nature of the error that occurred.

LAS consistency error.  These should never occur – but best practice requires they be tested for

Sample permanent retrieval - direct call
curl -i -X POST -H "Content-Type:application/json" \
  http://$HOST/lasapi/rest/lasapiSvc/permanentlyRetrieveItem \
  $HOST/permanentlyRetrieveItem -d \
  '{ "dsitem":{ "ttitem": [ 
     { "CustomerCode":"AR", "itemBarcode":"AR00000612", "destination":"AR",
       "requestor":"requestorName" },
] }'

Field Descriptions for permanentlyRetrieveItem

JSON field

Description / Typical usage

Data Type

Field width

CustomerCode

Owner code

alphanum

3

itemBarcode

Item barcode

alphanum

20

destination

Delivery stop

alphanum

8

requestor

Item requestor

string

70

requestorFirstName

First name of requestor

string

28

requestorLastName

Last name of requestor

string

28

requestorMiddleName

Middle name of requestor

string

16

errorCode

Error code (output only)

alphanum

16

errorNote

Additional detail (output only)

string

60

  • No labels