Yeah, you definitely provide a lot of search and refinement options, Steven. We don't really have the issue of clustering people by branch library so our directory is pretty simple. We used to have a listing of librarians by expertise but got rid of that in the directory and just rely on contact info in more specific contexts (our collections team librarians are listed on the library purchase request form, for example).
I will say people dig the colors we use for the departments.
Head of Library Systems & Technology (Librarian III)
Miller Nichols Library
University of Missouri--Kansas City
From: Code for Libraries <[log in to unmask]> On Behalf Of Turner, Steven
Sent: Thursday, April 4, 2019 3:59 PM
To: [log in to unmask]
Subject: Re: [CODE4LIB] tools in use for staff directory applications?
Hi Buddy - I am partial to our staff directory.
Steven Turner, MLIS
Manager, Web Technologies and Development, Assistant Professor
The University of Alabama
416 Gorgas Library | Box 870266, Tuscaloosa, AL 35487-0266 office 205-348-1638 [log in to unmask] | http://www.lib.ua.edu/
“To dwell inside a well-functioning machine is to be largely unaware of its functioning. That’s its gift, and we accept it thoughtlessly, ungratefully, unknowingly."
[cid:[log in to unmask]]
On Apr 4, 2019, at 3:22 PM, Pennington, Buddy D. <[log in to unmask]<mailto:[log in to unmask]>> wrote:
Our website is built on .NET and we use Oracle to store staff info.
Head of Library Systems & Technology (Librarian III) Miller Nichols Library University of Missouri--Kansas City
From: Code for Libraries <[log in to unmask]> On Behalf Of Sean Aery
Sent: Thursday, April 4, 2019 3:13 PM
To: [log in to unmask]
Subject: [CODE4LIB] tools in use for staff directory applications?
At Duke University Libraries, we are planning to design/develop a new staff directory application this spring. It seems like this would be a fairly common area of need, but there don't appear to be any widely-adopted solutions out there. So we're interested in learning more about what our peers (y'all) do to power their staff directories.
For some added context, we use Drupal 7 for our website and a growing percentage of the applications we support use Ruby on Rails. We don't have much in-house experience with JS frameworks like Vue or React. Whatever we use to build the directory, it should be able to represent people (with photo, contact info, bio, etc.), display a browsable hierarchy of organizational units, and be widely discoverable and accessible.
Does anyone have a solution they like for their staff directory? What tooling do you use and why? Any words of advice you could share?
Digital Projects Developer
Duke University Libraries
030U Bostock Library Box 90198
Durham, NC 27708
[log in to unmask]