search

RCPL / v3

RichlandLibrary.com v3 — presently a prototype built with Jekyll
https://rcpl.github.io/v3/
0 stars 1 forks source link

Job Story: Requests and Approvals #127

Open Jordanwmorris opened 7 years ago

Jordanwmorris commented 7 years ago

I want to reserve a room.

img_0783

  1. Starting point: Pick locations and times for rooms needed
  2. Select one or more rooms (staff has ability to reserve more than one)
  3. Submit reservation
  4. Sign in to account for personal information to be pulled
  5. read terms and conditions if necessary (if already read then this wont show up)
  6. then you're taken to a page that shows that reservation as well as the past reservations allowing you to edit and cancel reservations
attheshow commented 7 years ago

@Jordanwmorris The photo appears to be cut off at the top. Are you able to re-upload it or take a replacement photo?

attheshow commented 7 years ago

Also, I'm wondering if the "Requests & Approvals" heading was related to another discussion. I can't remember how that tied into room reservation.

m011yw01fe commented 7 years ago

@attheshow I think Wray suggested as the title of this job story, but I don't know if that's because 'Requests' is just too vague or if it's because of all the other user stories that could fall under this job story, like requests for purchases of titles to add to RCPL collection, requesting titles to be held for pick up at preferred branch, requesting to be registered for a program, etc.

Hopefully many approvals (or denials) could be automated, like if a child tried to register for an adult class, but I do think all requests need to be approved in one way or another. And the idea is that a patron could look at their account online and verify that they placed a request accurately, and then see when its status changed from 'pending' to either 'approved' or 'denied'.

Rest of group: am I right? Definitely chime in if there's another idea about this. Also, any suggestions for another type of job story to work on?

wraybowling commented 6 years ago

Let's find a way to rewrite the description of this issue to better reflect all the ideas that came out of the session:

A user could make any kind of request

  1. a purchase
  2. an obituary
  3. an answer to a question
  4. a recommendation for an item or a list
  5. a room reservation
  6. scheduling time with a staff member
  7. scheduling time in a space that has its own operating hours
  8. etc...

It's a more broad concept. As Peter described it today, it's the concept of a "ticketing system"