2024-04-24 RS OST meeting notes

make sure Jason records meeting / any announcements?

1

Jason

Analytics AFN digital requests reports discussion

30-40

Steve Burke

when requests are finished/completed, many data points are gone/vanished.

question: how does anonymization impact this data loss? ans: ‘little impact’, has more to do with completion of request

“requestor data” is a big piece of data loss that impacts the loss of our reports. “creator field” not working correctly - bug filed with development (ques: retroactive? ans: will follow up) - lender created requests will never have this creator field.

question: is this afn specific? what impact would p2p have? ans: for p2p, then lending requests are separated out & borrower/lender link is maintained; would still need multiple tables

question: frequency of exporting data? export prior to completion of requests… ans: anonymization could impact data available, but potentially exporting before completion may include data that get lost [SB will follow up]

question: would it be possible to get gross digital lending numbers (not separated by campus)? ans: will follow up on case

question: could we use statistical user categories? ans: problem cannot do this as an automatic process; would not be able to determine source uni for linked account; would have to be manually assigned (in batches & sets)

Capture important topics for future discussion

items being kicked out to WorldshareILL at end of ROTA even though we have those items in our catalog (Demitra)

[RS OST SC notes 5/1/23: hold for consideration post Tipasa implementation]: ‘pick up anywhere exceptions’: review shared messages, what would be next steps
metrics on how often ‘pick up anywhere’ requests have to be changed to home campus (Jason) → may lead to: editing pu loc for this requests → may lead to: harmonizing bookbands

x/x