Page Comparison

1 . SCSB API's consumed by LAS

Note: All are RESTful services

1. Cancel Request
2. Refile Item
3. Accession
4. Accession Batch
5. Bulk Request

2. LAS API’s consumed by SCSB  

1. Hearbeat API
2. Request API
3. Item status check
4. Permanent Withdrawal - Direct
5. Permanent Withdrawal - Indirect

1 . ITEM STATUS CHECK

Scsb uses LAS item status check api to check the status of item in LAS and process accordingly for any requests such as Retrieval, Recall or EDD. The api is also used in Refile process and status reconciliation process. Whenever there is a need to check the status of an item in LAS this api is called.

LAS will accept JSON-encoded REST GET calls to retrieve the status of an item.  Given a barcode, the itemStatus API will return the item’s owner and a string describing the item’s status in the LAS system.

{ "itemStatus":
 [ 
   { "itemBarCode": "string" } 
   , { "itemBarCode": "string" }  ...
  ] 
}

{ "dsitem":
 { "prods:hasChanges": boolean,      # IGNORE
   "prods:before":{ JSON data }      # IGNORE
   "ttitem": [
     { "itemBarcode":"string",
        "itemStatus":"string",
        "CustomerCode":"string"
     }  
     , { "itemBarcode":"string",
          "itemStatus":"string",
          "CustomerCode":"string"
      }  ...
   ],
 }
}

curl -G -g -o - http://$HOST/lasapi/rest/lasapiSvc/itemStatus --data-urlencode \
'filter={ "itemStatus": [ 
  { "itemBarCode": "AR00035602" }
 ] }'

Field Descriptions for itemStatus api call

...

JSON field

...

Description / Typical usage

...

Data Type

...

Field width

...

itemBarcode

...

Item barcode

...

alphanum

...

20

...

CustomerCode

...

LAS Owner code

...

alphanum

...

3

...

itemStatus

...

Item Status

...

String

...

40

GFA’s PWD and PWI api’s 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.                                                     

2 . PERMANENT WITHDRAWAL - DIRECT

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

...

• The CustomerCode and destination fields must either match the owner and stop codes in the LAS Storage Location IMS system.
• The owner code is used only for verification purposes.  It is compared to the code stored in the LAS the Storage Location IMS system, and an error is returned if it does not match
• LAS does Storage Location IMS 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.

...

...

3 . PERMANENT WITHDRAWAL - INDIRECT

LAS will accept JSON-encoded REST calls to mark retrieve items as permanently withdrawn from ReCAP.  The required fields are the owner code (CustomerCode) and the item barcode (itemBarcode).

{ "dsitem":
  { "ttitem": [
    {
      // required fields
      "CustomerCode": "string"
      "itemBarcode": "string"
    }
    , { "CustomerCode": "string" ... } ...
  ] } // end of ttitem array   
}

{ "dsitem":
  { "ttitem": [
    {
      // required fields
      "CustomerCode": "string"
      "itemBarcode": "string"
      “errorCode”: “string”
      “errorNote”: “string”
    }
    , { "CustomerCode": "string" ... } ...
  ] } // end of ttitem array   
}

• The CustomerCode field must either match the owner code in the LAS system, or must be mappable to it.  The current documentation assumes that the actual LAS codes will be used.
• The owner code is uttsed only for verification purposes.  It is compared to the code stored in the LAS system.

Error codes for permanentlyRetrieveItemIndirect

...

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.  (This should never happen).

...

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

...

itemNotOut

...

Item status

...

Item is not “OUT” according to LAS, and therefore cannot be indirectly withdrawn.

...

InternalErr

...

The nature of the error that occurred.

...

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

curl -i -X POST -H "Content-Type:application/json" \
  http://$HOST/lasapi/rest/lasapiSvc/permanentlyRetrieveItemIndirect \
  $HOST/permanentlyRetrieveItem -d \
  '{ "dsitem":{ "ttitem": [ 
     { "CustomerCode":"AR", "itemBarcode":"AR00051608" }
] }'

Field Descriptions for permanentlyRetrieveItemIndirect

NOTES:  Use of Color

In field description tables, three colors are used:

...