LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  January 2017

CODE4LIB January 2017

Subject:

Re: Marketing Ticket System

From:

Michael Schofield <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Wed, 18 Jan 2017 17:27:05 +0000

Content-Type:

multipart/mixed

Parts/Attachments:

Parts/Attachments

text/plain (65 lines) , dashboard.PNG (65 lines)

Hey Nathan,

I think my inner-consultant would suggest to go with a tried-and-true third party just so the technical debt of something homegrown doesn't add to your overhead, but I don't really follow my own advice. You'll probably get some really good feedback, but let me tell you a little bit about what I'm doing and maybe that will spark your imagination.

Check out the attached picture.

I'm building a ticketing system and services dashboard using Bitbucket / Github issues. Basically, every service area has its own repository -- whether there's code in it or not -- so I can leverage all the APIs and integrations built around these issue trackers. Where there *is* code involved (e.g., most of web services) I can update the status of a thing by committing the fix or the new feature. When there's not, the issue tracker is still really useful.

So, if you're a staff-member, you can visit this page and

1. Submit a request or a bug or whatever

2. Based off your selections, the system will a) create an issue in the relevant repository, if necessary; b) email the various cross-departmental people who need to know (e.g., a "gross stuff on the computers" report doesn't need to come to web team); c.) and update the dashboard.

3. Let's say I can respond to the ticket either through this system, github/bitbucket, or through a commit. It resolves itself, and the dashboard reflects the up-to-datedness.

If a user clicks on any of these service areas they will see a list of all issues, so they can see if something's been requested or reported. I'm still building-out the ticketing system's admin area but it's pretty much the same view except you can pull all issues assigned to an individual, sort them by priority or however you determine your to-do list, and stuff like that.

One upshot of using issue-trackers that have an API is that the interface for interacting with it can be all javascript. Even though I went against my inner-consultant's advice, the staff interface is just one page. Also, Github/Bitbucket integrate with eeeverything - trello, slack, automagic emails, you name it. Really useful mashup.

Anyway, food for thought :).

Michael Schofield | @schoeyfield 
www.LibUX.co

-----Original Message-----
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Nathan Wittmaier
Sent: Wednesday, January 18, 2017 12:03 PM
To: [log in to unmask]
Subject: [CODE4LIB] Marketing Ticket System

Our library system serves 31 branches in three counties, and we have historically used an Access database and forms to manage our marketing ticket system, for branch staff to enter requests and to manage print and web jobs for the marketing department. However, this system is showing its age and is becoming more disagreeable with wireless platforms and non-Windows devices. We are exploring other options, but I was curious what other library systems out there use for this type of thing and if there are any software systems available to purchase or open-source that libraries use for ticket systems.

The options we are considering right now are:

-          In-house build of a ticket system web application

-          Using Sharepoint Workflows

-          Best Practical Request Tracker system (based on Drupal)

I would love to find out about any other products or systems that libraries use for ticket systems in general or marketing/printing ticket systems specifically.

Thanks so much!

Nathan Wittmaier
Web Developer
[log in to unmask]
Mid-Continent Public Library
15616 E. 24 Highway
Administrative Headquarters
Phone: (816) 503-4145
http://www.mymcpl.org<http://www.mymcpl.org/>

Exceptional service, one person at a time ... it begins with me.




[http://www.mymcpl.org/sites/all/themes/mcpl/_resources/img/css/logo.gif]<http://www.mymcpl.org/>
________________________________
Unless explicitly attributed, the opinions expressed are personal and not that of Mid-Continent Public Library.
________________________________

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager