Accession Batch is similar to the accession API except that accession batch API accepts multiple item barcodes in a single request call. The accession batch process is a deferred process to reduce performance bottlenecks. The barcodes and customer codes are persisted and is processed as per schedule of the Accession job, usually, nightly. After processing, a report on the barcodes that were processed is prepared and stored at the FTP location.S3 location. Accession Batch does not have any limit on number of items to be added.
| Request - Accession Batch |
|---|
API End Point : /sharedCollection/accessionBatch |
| Code Block |
|---|
| language | js |
|---|
| title | Request - Accession Batch |
|---|
| linenumbers | true |
|---|
|
[{
"customerCodeimsLocationCode":"Storage Location"PA", // Customer code as stored in GFA LAS. This is used to identify the institution in SCSB. RECAP for ReCAP Warehouse, HD for Harvard Depository
"accessionRequests":[
{
"customerCode":"PA",
"itemBarcode": "PULTST54340" //
Item Barcode. Unique and common across SCSB},
GFA LAS and partners' ILS. }, {
"customerCode": "PA",
"itemBarcode": "PULTST54320"PULTST54341"
},
{
"customerCode": "PA",
"itemBarcode": "PULTST54210PULTST54342"
}
]
} |
| Code Block |
|---|
| language | js |
|---|
| title | Response - Accession Batch |
|---|
| linenumbers | true |
|---|
|
The accession request is successfully processed. |
...