2017-07-13 Resource Access Meeting Notes

Date

13 Jul 2017

Attendees

• Andrea Loigman

• Wendy Wilcox
• Cheryl Malmborg
• William Weare
• Cate Boerema (Deactivated)
• Michael Winkler
• Peter Murray
• Charlotte Whitt
• Mark Canney
• David Bottorff
• David Larsen
• Deb Lamb
• Filip Jakobsen
• Maria Grzeschniok
• Sharon Wiles-Young

Goals

Discussion items

Notes:

RA SIG Meeting Minutes 7/13/17

Andrea loigman

filip jakobsen

Wendy wilcox

Deb lamb

Maria grzeschniok

Michael winkler

David bottoroff

Charlotte whitt

David larsen

Cheryl malmborg

William weare

Peter murray

Sharon wiles-young

Consortial SIG; concern over patrons who belong to multiple instances

Is this a question for user management SIG; looking for feedback

Difficult to address issues that cut across multiple SIGs

How does this system treat patrons correctly in multiple patron groups

Cornell -- corrections script that will overwrite the data outside the system

Not unique to Cornell but a lot of systems do this

Mark Canney

Sept community forum

Planning or presentation team

Monday we have a Vince

Half of next Thursday’s meeting to determine planning committee

Create in JIRA a tag called sig-ra; keep the stories fresh; for next sprint

https://folio-org.atlassian.net/issues/?filter=10418

https://folio-org.atlassian.net/wiki/display/RA/SIG-RA+Stories+and+Issues

Questions about requests

General question: most requests initiated through discovery by patron

Known item request request by staff

Course reserve request for faculty; may be a barcode in reserves management system

Can use barcode but often do not have the barcode; use author, title or call number

Course reserves or on behalf of the patron

Staff unique workflows that have to be taken into account

Request app; you may not be in the middle of a workflow

Getting to an item and then placing a request on an item

Paging workflow and then you need to activate a request from that interface

Things beyond just the placing of requests

General resource search and place a request

item requests for a range of items; look at a title and request multiple volumes; serials with multiple issues

Ability to place Bulk requests

Requesting as a recall

Request app page; one of frustrations being asked to select request type; intuit request type would work; patron isn’t eligible to have items delivered; cant place this request because item isn’t checked out

Smart request type that only offer options that are valid

Give immediate feedback as to why those request options are not valid

Does the request always have a requestor?  Requests that don’t have requestors that don’t have individuals; requestor the person is interested in checking out the book versus staff who have to act on the book

Even a flag or checkbox for a departmental request

Ole; create more and more requests

Are departmental requests always the top of the heap? No...but. How are you going to handle that from a business

Setting priorities

Item status

So we have item status; item status is available or checked out

When a checked out item has been recalled; item status takes on the loan status

Different systems do it differently

Ole does not changed the status to recalled (Boo!) makes it difficult to know the current status of an item

Make recall an item status

Look up item want to see “recal”

Is there a difference between item status and loan status

Or we could have two seperate statuses

Voyager allows item to have multiple statuses

Circulation status and a secondary status

Checked out, in transit, recently returned, recalled, available

Order status; items are created at the point of order

in-process;; cancelled; preservation; missing; lost; on order;

Status and sub-statuses

Damaged would be a separate flag

Created a fast-ad record; status is loaned to a patron;

would not want to conflate processing statuses and circulation statuses

Screen shots of the different status types

Processing statuses

Everyone is aligned that there is not a difference between circulation status that will gets its value from the presence of the loan

Requested but not loaned

Want to see at a glance that there is a queue

Request is like a future pending status

I lean against making a request conflate with item status

Item statuses that can be viewed by the patrons