RforP

When the people would like the library to add an item to the collection, they complete a webform[1]. Through an auto-generated email sent to req-purchase@mfrl.org, a ticket is created in a task ticket system. The ticket system will manage the request for the remainder of the process.

Format

Nobody really "sees" the email - it just defines the characteristics of the ticket.

Subject line shall be:

• [RP] plus
• first 15 characters of title (excluding The / A / An) plus pipe plus
• format [Book| DVD | Game | eBook | Audio | Book-CD | Music CD]

Example: [RP] dogs can run | eBook

If the contact choice is Phone, the first line should include [No Email Address]

If the contact choice is No Contact, the first line should include [No Contact]

Who gets the ticket?

• If Format = eBook or Audiobook, the first line of the email should be #electronic (will get routed to KK)
• If Format = Game, the first line of the email should be #physicalyouth (will get routed to SP)
• If not #electronic and Audience = Teens or Kids, then first line of the email should be #physicalyouth (will get routed to SP)
• Otherwise, notice will go to RS/LS (Techstaff) as a "Team".

When a ticket is created:

• Ticket Assignee gets Ticket Assigned to you email
• Patron gets Purchase Request Case Opened [#RP123456] email. Terminology: Ticket system calls patron the "ticket owner".

VR will have access to the system as a backup for Techstaff team.

Branch managers won't have access to ticket system, but may be referenced as "contributor". This will allow them to get emails when patrons need to be contacted by phone.

Tasks?

Do we want to have tasks? I don't think so.