Someone emailed me off-list to ask where Penn landed on Lean Library and it
feels only fair to reply to all. I’m again writing on behalf of our
library’s Discovery Team (I’m the person on the team who happens to follow
code4lib..).

Last winter, after my previous post, Penn had another meeting with a new
Lean Library staff member, Claus Wolf, who was able to answer the team’s
questions on both the technical and policy side. A bug that was sending
browsing data to LL had been fixed and verified, and they made changes to
their documentation that made the functionality and expectations clearer
for both users and us, as the institution recommending and licensing the
product. On the basis of this, we did sign a license.

We’ve only been offering it for less than one full semester, so the uptake
has been moderate, but we’ve gotten good feedback from some users,
including faculty who went out of their way to let us know how much it’s
helping them. We’ll do more of a push at the start of the fall semester.

Emily

On Mon, Oct 15, 2018 at 10:56 AM Johan Tilstra <[log in to unmask]>
wrote:

> Hi Emily,
>
> I'm sorry to hear that you feel we've been evasive and confusing in our
> communications with you. It's painful to read that your concerns actually
> increased. It must be because of our clumsiness, as we really have nothing
> to hide. We fully understand how important it is for librarians and end
> users to have full confidence in us and we want to be completely
> transparent in what we do and - maybe even more important - in what we
> don't do. We feel that's the only way to fulfill Lean Library's sole
> mission: to make the lives of patrons easier.
>
> I'm glad our conversations are ongoing and I look forward to our meetup at
> Charleston in a few weeks.
>
> I invite others with questions or feedback to also get in touch with us.
> We're very much work in progress so all input is highly appreciated.
>
> Johan
> CEO, founder of Lean Library
>
>