paper: refund to user on a machine

[TonyLianLong]

As mentioned in here, I guess this could be helpful in some case that the username is hard to type.

[raymondnumbergenerator]

I could see paper taking a flag that allows a machine to be specified instead of a username. It doesn't seem too difficult to add and doesn't really add that much feature bloat so yeah.

It doesn't hurt to add this feature to paper but like I mentioned in the other thread, it's probably easier for a user to state their username than for opstaff to figure out which machine a user is logged into.

[cg505]

A more comprehensive solution would be a usable GUI for opstaff that quickly shows logged in users for any desktop on a map, and has tools to refund easily from machine or by user. This is obviously harder and would be a longer-term goal.

[MrMinos]

A more comprehensive solution would be a usable GUI for opstaff that quickly shows logged in users for any desktop on a map, and has tools to refund easily from machine or by user. This is obviously harder and would be a longer-term goal.

Lapmap can be that GUI solution for opstaff, which could incorporate the reference issue above in lapmap.

[raymondnumbergenerator]

I think a separate UI for opstaff to do refunds is a good idea, but I don't know about attaching that to labmap. Labmap was designed to be a page that displays on the tv and isn't flexible enough to tack much more features onto.

I'm thinking that we could have a page ocf.io/refund that's only accessible to opstaff and staff shows a list of all logged in users, their real name from ldap and the machine they're logged into and a button that opens a form allowing you to enter number of pages and a reason for a refund.

If we want this page to be more general than just administering page refunds maybe it could just be ocf.io/users or something and also include other useful information like a user's group and add more features in the future.

[axmmisaka]

What about using https://github.com/ocf/printlist?

[PotatoParser]

Printlist was created to display print jobs. It's not intended to act as a UI for staff to interact on.

[axmmisaka]

I know, but what I'm trying to say is they do share a lot of similar functions that might be beneficial to utilize...

[PotatoParser]

Not quite, printlist only polls data from outgoing print jobs. It does not use any information regarding what computer a print request was sent from. If anything, we would simply have to subscribe to the redis channels and use that data.

[axmmisaka]

By the description the important thing is to fix the problem that some's username is hard to type... So computer isn't that important I guess