Feasibility Study of integrating SavaPage with PaperCut to support Copy Shop Scenarios.
Status | under construction |
Date | 2018-09-09 |
A low-threshold customer self-service for print-and-copy. |
Actor | Description |
---|---|
Customer | A person who pays for print-and-copy services. |
Regular Customer | A returning customer. |
Casual Customer | A passer-by customer. |
Object | Description |
---|---|
NFC Card | Identification token for MFP, and optionally SavaPage Print Portal. |
Personal Card | NFC Card issued to a Regular Customer. |
Session Card | NFC Card temporarily issued to a Casual Customer from a fixed pool of rotating cards. |
Scenarios for Regular Customer with a Personal Card.
Actor : Cashier
→ Customer is registered
→ Personal Card is issued
Actors : Customer, Cashier
→ Updated account balance
Actors : Customer, Cashier
→ Updated account balance
Actors : Customer, Cashier
→ Updated account balance
Actor : Cashier
→ Customer is unregistered
→ Personal Card is returned
→ Remaining balance is refunded
Scenarios for a Casual Customer with a Session Card.
Actor : Cashier
→ Session Card is issued
Actor : Cashier
→ Session Card is handed in
→ Customer paid for print and copy
Scenarios for both Regular and Casual Customers.
Actor : Customer
→ Cost is charged to Personal PaperCut Account
Actor : Customer
→ Cost is charged to Personal PaperCut Account
This scenario is very resource friendly, since the user must swipe at the SavaPage Card Reader first, to transfer his jobs to PaperCut, the spoolfiles need only be held in PaperCut for a very short time (30 minutes or so).
Actor : Customer
→ Cost is charged to Personal PaperCut Account
Platform | Method |
---|---|
MFP | NFC Card |
SavaPage Print Portal | Userid + Password, YubiKey authentication, Google OAuth, NFC Card |
PaperCut MF + Embedded
SavaPage follows PaperCut licensing (Educational or Corporate)
SavaPage Users are leading → they are synchronized by PaperCut |
PaperCut User Accounts are leading → they are read/set by SavaPage |
PaperCut Print Job status is leading → they are monitored by SavaPage |
Any MFP with GNU/Linux PPD driver support.
Debian + PaperCut Primary Server + SavaPage Open Print Portal
See Print (2) scenario on how to reduce resource load. |
How to anonymize SavaPage document history for Casual Customers? |
How to cancel pending print jobs from previous session of Casual Customer? |
How to make a newly registered SavaPage user immediately known in PaperCut? |
Enable “On Demand User Creation” in PaperCut → When the user does not exist: create the user on demand (default).
How to make copy jobs visible in SavaPage? |
As PaperCut financial transactions are leading, and made visible in SavaPage by SQL query in PaperCut database, copy jobs will show up as transaction.