Versions Compared

Key

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

...

Info

Bellow I add the question and some not so technical and ranked lines from our brainstorm pages. Maybe we can use the questions (should be simplified a bit) and some selected points for the summary.

What's needed to empower a patron to perform his allowed actions and to maintain his account in a discovery system (see https://wiki.folio.org/display/SYSOPS/Brainstorm+page+for+the+patron+interface )

When placing a request or an hold the

R1, L1 etc are reference numbers for the groups internal discussion only/Marie


Before placing a request (BR)

  • BR1 Assuming using Title level requests:
    The patron should see the number of open requests on an instance. (This could help the patron determine if (s)he should bother placing the request or not.)
  • BR2 Assumimg using Item level requests:
    The patron should see the number of open requests each item. (This could help the patron determine if (s)he should bother placing the request or not.)

Placing requests (PR)

  • PR1 The patron should be able to select a preferred location to pickup the item.Patrons
  • PR2 The patron should be able to view information about existing item- and title-level requests, including status and to choose a preferred pickup location that is shown by default.
  • PR3 Assuming Title level requests enabled in FOLIO:
    Although the patron normally is offered "first available copy", for journals/multi-volume-instances where this makes sense, (s)he should instead be offered to choose a specific item
  • PR4 For journals/multi-volume-instances where this makes sense, the patron should be able to request multiple items from the same FOLIO instance


Managing requests (MR) at the patron account in the catalog/discovery layer

  • MR1 The patron should be able to view chosen pick up location for their unfilled request
  • MR2 The patron should be able to see their place in line (queue number)
  • Patrons should be able to view information about items they have checked out (due date, title, author, etc.).
  • Patrons for an unfilled request
  • MR3 The patron should get an estimate of the waiting time for an unfilled request
  • MR4 When the request is awaiting pick up for the patron, this information should be possible to see at the patron account
  • MR5 The patron should be able to see the pickup location for their request that is awaiting pickup
  • MR6 The patron should be able to see the last day to pick up their request that is awaiting pickup
  • MR7 The patron should be able to cancel their request


Managing delivery requests (DR)

  • DR1 The patron should be provided a way of determining which delivery methods are available for a given item/patron combination
  • DR2 The patron should be given an estimated delivery time/day
  • DR3 The patron should be able to cancel pending delivery requests.Patrons a delivery request


Managing loans (L)

  • L1 The patron should be able to see their due date
  • L2 The patrons should be able to see an indication of the the number of renewals left for an itema loan
  • L3 If an item in a patron's loan can't be renewed, it would be helpful to indicate that fact and the reason why this should be indicated before trying to renew (e.g., too many renewals, another patron has recalled it).
  • Patrons should be able to request specific FOLIO items (ie. a specific vol./issue) as well as the "first available" (ie. if you hold multiple copies of the same titles)
  • Patrons L4 The patron should understand why it was not possible to renew (e.g., too many renewals, another patron has recalled it). (Assuming it's not possible to see the information before trying.)
  • L5 The patron should be able to renew multiple loans in a one single actionPatron


Managing fees and fines (F)

  • A patron should be able to see pickup location for their request that is awaiting pickup. Patron their outstanding fees and fines
  • A patron should be able to see hold shelf expiration date for their request that is awating pickup. 
  • Patron should understand what went wrong.
  • Show patron contact information and other info so their history of fees and fines


Manage personal information (P)

  • A patron should be able to see if (s)he is blocked by the library and the reason for this
  • A patron should be able to see what contact information the library has for him/her (so the patron can see if we hold out-of-date info about them.
  • Patron should be able to see if they have a patron block. (The field "Message to patron" could be shown.)
  • Patron )
  • A patron should be able to edit selected information, e.g. email address.


See and understand information about items (I)

  • Relevant data from Enumeration, Chronology, and Volume fields should be clearly and uniformly displayed to patrons.


Other (O)

  • Patron should understand what went wrong when ...


    Most questions above are collected from the pages below.

What's needed to empower a patron to perform his allowed actions and to maintain his account in a discovery system (see Brainstorm page for the patron interface )

What's needed to display proper actions(buttons) and information to an item in a discovery system. (see https://wiki.folio.org/display/SYSOPS/Brainstorm+page+for+the+availability+interface )

  • Patron should be provided a simple way of determining which delivery methods are available for a given item/patron combination
  • Patron should be given an estimated delivery time/day
  • Relevant data from Enumeration, Chronology, and Volume fields should be clearly and uniformly displayed to patrons.
  • Allow title level/item level request depending on instance type.
  • The patron should see the number of unfilled title level requests on an instance, before placing the request
  • See number of already existing holds for checked-out items

    *Are these questions only available to currently highly engaged FOLIO org. survey takers so they understand the context of these questions?

    ...