Release Notes SCSB v0.9.25

Commit Id, date and version

1) Tag:

             scsb-solr-client : 0.9.25

             scsb-etl : 0.9.25

             scsb-circ : 0.9.25

             scsb : 0.9.25

             scsb-shiro : 0.9.25

             scsb-ui : 0.9.25

2)  Date:

             6th June 2017

3) DB Changes:

             1) RECAP-761 - Removed tables ITEM_TRACKING_INFO_T, PATRON_T, REQUEST_INST_BIB_T which are unused.

                                        Removed Loaned, InTransit, ShippedToILS, ShippedToReCAP status from ITEM_STATUS_T table.

             2) RECAP-730 - Removed 'superadmin' user from the application.

4) Solr Changes:

             NIL

Deliverables

S No

Components

JIRA

Summary

Priority

Issue Type

Labels

Comments

1Submit Collection

RECAP-722

Submit Collection:: MARC XML format record is not working if file contains special charactersHighestBug

2User Management

RECAP-730

Delete 'superadmin' username in TST and UATMediumTask

3Request

RECAP-737

Request: Reduce 2000 to 1000 characters for request notes to avoid request EDD and Exception issues.HighestBug

4Submit Collection

RECAP-745

Rejection Report - Submit Collection APIMediumTask

5Request

RECAP-751

Recalls - cross partnerMediumTask

6Ongoing Accession

RECAP-754

Ongoing Accession Report generated with blank fields. (Without data) and file name also incorrect.HighestBug

7Export Data Dump

RECAP-756

Fix description for date in Swagger - exportDataDumpMediumTask

8Submit Collection

RECAP-758

Items disappears during submit collectionMediumBug

9Bulk Accession

RECAP-759

Process Bulk accession based on status instead of date.MediumTask

10

RECAP-761

Remove table item_tracking_info_t , patron_t, request_inst_bib_t and obsolete Item Statuses from item_status_t tableMediumTask

11Ongoing Accession

RECAP-770

Accession - Add OwningInst BibId, OwningInst HoldingId and OwningInst ItemId of existing Item in the Item already accesioned error messageMediumTask

12Ongoing Accession

RECAP-771

Accession:: When accessing the barcode, Summary Holding and Chronology & Enumeration, Call number are not stored in the DB.HighestBug

13Ongoing Accession

RECAP-772

Accession - Add error message while accessioning a barcode, but the owning inst itemid of the barcode is already linked with another barcodeMediumTask

14Ongoing Accession

RECAP-775

Accession:: Exception report is not generated and app has displayed incorrect error message when accessioning the barcodeHighestBug