Ongoing Accession Process
The following process describes the ongoing accession of items into SCSB.
Step 1: IMS Site will do a barcode scan to accession and make an API call (Accession) to SCSB to send barcode, customer code and IMS location Code
Step 2: SCSB will make a Bib-data API call to the institution on the provided end point
Step 3: ILS sends the bib-records in MARCXML or SCSBXML format
SCSB Ongoing Accession / Submit Collection (through API)
Step 4: SCSB will create a bib record tree in the SCSB Database
Submit Collection Process:
Submit Collection process is used to update metadata of already existing bibliographic records in SCSB. SCSB Provides two different methods to update the existing collection.
Method 1: Institutions prepare MARCXML or SCSBXML of bibliographic records and place them on appropriate AWS S3 drive allocated to them. SCSB nightly job process them and update the records as provided. Institutions will find 2 different folders a) protection b) no_protection . Institutions requested to place xml files/.gz files with bibliographic records in “protection“ folder if they don’t want to modify CGD of the records and place files in “no_protection“ folders if they want to update CGD as given in the files. Files should not contain more than 4000 bib records per file if they are placing files in the “no_protection“ folder.
This is the most preferred method for updating the SCSB bibliographic records on a daily basis.
Following is the sequence diagram for the this method.
Method 2: Institutions can update the bibliographic records of SCSB by calling “SubmitCollection“ API. Details are given at Submit Collection API. This method is primarily used to update the records immediately under rare situations.