Versions Compared

Old Version 2

changes.mady.by.user Andrea Loigman

Saved on

compared with

New Version 3

changes.mady.by.user Cate Boerema (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

...

TimeItemWhoDescriptionGoals
5minHousekeeping
Andrea Loigman
  • Notetaker -

15minNotice logic - follow-upDarcy Branchini
Approval: to move forward with logic in notice policies
15minRequests: Check in modalsCate Boerema (Deactivated)* https://issues.folio.org/browse/UICHKIN-50
* https://issues.folio.org/browse/UICHKIN-49		Review of mockups and stories related to check-in modals for in transit and awaiting pickup requests:
25minRequests: Paging requestsCate Boerema (Deactivated)Item State Use Cases- reviewApproval of paging use cases

Meeting Outcomes

Functional Area

Product Owner

Decision Reached

Reasoning

Link to Supporting Materials

Comments

e.g. loans, fees/finesNameClearly stated decision
  • Because...
  • Because...
e.g. mock-up, JIRA issue
RequestsCate Boerema (Deactivated)

The information in the Awaiting pickup modal attached to

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUICHKIN-50
is correct


Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUICHKIN-50

  • Next step on modal is to get a good UX mockup so we are sure we are using the right patterns etc
  • It was suggested that hold slips should have the option to display pickup service point (in case the item is discovered somewhere random, you would like to know where it should be sitting) - Darcy Branchini will create story for adding a token for pickup service point to the hold slip
  • It was requested that you be able to specify for each service point whether hold slips will print by default and whether transit slips will print by default - Cate Boerema (Deactivated) will have this mocked up and bring to SIG
RequestsCate Boerema (Deactivated)

The information in the In transit modal attached to

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUICHKIN-49
is correct


Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUICHKIN-49

  • Next step on modal is to get a good UX mockup so we are sure we are using the right patterns etc
Requests

Cate Boerema (Deactivated)

Need to be able to configure which request types are allowed for which item states (availability)
  • For example, some institutions may allow hold requests on On Order items while others don't
  • When there are custom availability states, you will definitely need this
  • Most systems today allow this

Requests

Cate Boerema (Deactivated)

We can assume that Recall requests are only allowed when Availability = Checked out


Notes