...
The intention of this round of testing is to cover the major use cases for resource sharing via DCB. What is reflected “in scope” is approximately 80% of the use cases required to have a complete solution supporting resource sharing. Over the coming months, the remainder of the use cases will be developed, tested and then supported on-going for Sierra, FOLIO, FOLIO ECS and Polaris.
Info |
---|
During the beta testing phase, please be aware that updates to member records and transactions will take between 2-5 minutes to complete. |
In scope
Sierra libraries
Item requesting
Patron affiliation
Patron authentication
Pickup location selection
Full happy path circulation lifecycle
Lending – produce paging slip → checkin (to trigger hold) → put in-transit to pickup location + produce in-transit slip
Borrowing – hold → checkin (received) + produce hold slip + put on-holdshelf + produce pickup notification → checkout to patron + date due slip → checkin from patron + put in-transit + produce in-transit slip
Lending – checkin + remove transaction
Borrowing – remove transaction (transaction complete)
Patron cancellation of a request
Borrowing – Patron account in OPAC or Discovery → cancel request → remove hold
Lending – remove hold (transaction complete)WebPAC
Encore
Vega
Bibliocommons
Not in scope
Polaris, FOLIO, FOLIO ECS platforms
Volume-level requesting
Patron eligibility/blocks
Pickup anywhere
Geographic proximity item selection
Item owning site cancellation
Transfer to another item
Renewals
Holds
...
Group | Institution | Member | Other info (cluster/hostLMS) | Status | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|
1 | Lindenwood | Jake Morrisey | bridges | PROGRESSING II validate config | |||||||
1 | William Woods | Rachel Utrecht | avalon | PROGRESSING II validate config | |||||||
2 | Springfield-Greene County | Stephanie Ruhe | standalone SGCL | PROGRESSING II validate config | |||||||
2 | West Des Moines Library | Heather Hildreth | standalone | PROGRESSING II validate config | |||||||
3 | Washington University | Eric Joslin | standalone | PROGRESSING Write config | |||||||
3 | NW Missouri | tbd | tbd | KC-Towers | PROGRESSING II Validate Config | ||||||
tbd | Southeast Missouri State | Susan Welker | standalone | BLOCKED NO CREDS | tbd | NW Missouri | tbd | tbd | KC-Towers | PROGRESSING II Validate Config |
Test records
Each library will need a patron, a bib and an a linked item to conduct testing. You can use preexisting pre-existing or newly created records but the key is to make sure that your library solely owns the title. This will prevent the system from directing requests to another library. Some guidelines for each record type:
...
We strongly suggest that the records are fully defined as if they are a legitimate part of your catalog or your patron database. This will best exercise the software and allow for the surfacing of issues within Sierra client displays (e.g. check-in and checkout, holdshelf), within notices and slips, and within public patron account features.
Test records spreadsheet (to transfer to Jag’s Test Record Template)
Test record template (use this instead of the spreadsheet)After creating your records, please document them in the test page that has been created for you under this parent page. On the page, look for the directory pane on the left side of the screen. From there, take a look at this screen recording to create a new, child page using a template. The recording shows a bib template (“test-record-bib”) but there are also item and patron. Search for the term “test-record-item” and, separately, “test-record-patron” when creating your other two test record pages.
To archive: Test records spreadsheet
Test guidance
There are 2 test cases – 1 for the lending side and 1 for borrowing side. Every member is assigned testing feedback issues for test cases as a borrower and as a lender.
...