2020-10-22 Resource Access Meeting Notes

Date

Oct 22, 2020

Attendees

@Andrea Loigman

@Joanne Leary

@Michelle Suranofsky

@Monica Arnold

@Mark Canney

@Joshua Lambert

@Laurence Mini

@Emma Boettcher

@Kimie Kester

@Rameka Barnes

@Cheryl Malmborg

@Darcy Branchini

@David Bottorff

@tpaige@umass.edu

@Jana Freytag

Discussion Items

Time	Item	Who	Description	Goals/Info

Time	Item	Who	Description	Goals/Info
2min	Administrivia	@Jana Freytag	Holiday (Jana) next week Daylight saving time in Europe this Saturday	Notetaker - @Jana Freytag
20Min	item states - Lost item application and the using of statistical codes	@Michelle Suranofsky	Talk about the Lost Item application and the possibility using of statistical categories
20Min	Claimed returned report	@Emma Boettcher	approval of wireframe for claimed returned search

Meeting Outcomes

Functional Area	Product Owner	Planned Release (if known)	Decision Reached	Reasoning	Link to supporting materials	Comments

Functional Area	Product Owner	Planned Release (if known)	Decision Reached	Reasoning	Link to supporting materials
e.g. loans, fees/fines	Name	e.g. Q4 2018, Q1 2019	Clearly stated decision	Because... Because...	e.g. mock-up, JIRA issue
Loans	@Emma Boettcher		Show effective location on CR report; allow users to filter by effective location & primary service point for that location Add more information about locations in export, but revisit that in the group Limit # of searches by the primary service point for the effective location

Notes

Administrativa:
1. we switch our Thursdays meeting time to the full hour again (10:00/11:00/17:00)
2. Jana will send out new invitations with the correct time table for next week (daylight saving time in Europe)
3. Next weeks Thursday meeting will be cancelled
Lost item Application
1. Lehigh was given a grand by EBSCO for developing this application
2. more item statuses were needed and Emma suggested statistical categories
3. feedback about statistical codes:
  1. David B.: likes this approach (lost item> newly purchased item > lost item stays in the original status)
  2. Andrea: would duplicating a status
  3. Michelle: there will be a status code that defines the item as beeing a lost item
  4. button: purchase/request>
  5. Process status could be fitting (process status will be costume statuses)
  6. difference between statistical codes (repeatable) and process status (automatically changed by a certain process)
Claimed returned report
1. we looked at the mock ups and csv report
2. In the Report (UI)
  1. Options: Add search, Declared lost, mark as missing, User details, fee/fine details, item details, loan details
3. We wanted to be able to filter by location, what location do we want?:
  1. Group: effective location would be prefferable on the UI
  2. Which part should be exported?
    1. Joanne: permanent location, temporary location, effective location
  3. Marc C.: Print a pick slip would be a helpful feature vs. the csv export (similar to the request app)
4. Service Points
  1. limit the number of searches based on location, service point
  2. by which attribut is the limit of searches set
    1. Location, Service Point, Effective Location
    2. setting it by Tenant is to general