3 Lessons that I learned from Summon Implementation (Web discovery layer)

web-design

It’s almost been a year since we roll-out our library’s web discovery layer known as KORAL: KAUST Online Resources Access Layer (powered by Proquest Summon).  [Check out my earlier post on our journey to implement Summon. ]

What are the 3 main lessons that I learned?

brainstorm

(1) Management buy-in: It’s imperative to obtain management buy-in and support; without which,  things may go bumpy.  With management support, resources may be spared to aid your cause; tasks delegation made easier and fund(s) may be released to boost your project success chances.

(2) Testing(s) and Engaging the User community: I have always believed in engaging our user when implementing any public-facing interface projects.  At the end of the day, our users are the ones who will ultimately use the interface/system.  They are not at all dumb as some of us would think.  By getting their feedback, we are made to see things in a different light; some of which are those that we least expected.  Examples of some of  these user engagement activities are:

  • UX: Usability testing(s)
  • Focus Group interviews
  • One to One interviews
  • Card sorting exercises
  • Online surveys
  • Informal chats

(3) Communication: Whether you are communicating to team members, communicating upwards to library management or communicating to the users, there has to be openness and transparency.   We have to be receptive to the feedback; some may be stinging to the ears BUT if it is for the common good, then we have to put our egos aside.  At the same time, if it’s necessary to deliver some negative news, then we have to inform that as well.  However,  when dealing with negative news, there has to be tactfulness and sensitivity involved.  Not many could react well to negative information.   Most importantly, communication is always a 2-way ‘street’.  Be prepared to take as much as you are ready to give.

These are the main ones among the others that I have learned during the project implementation.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s
https://rindraramli.me/2017/04/30/3-lessons-that-i-learned-from-summon-implementation-web-discovery-layer/
rindraramli.me
crawl=CC-MAIN-2018-17
85341
application/http; msgtype=response
sha1:APPYZYOJWVSG3CI7BQS5VSS6JLM3RRRM
<urn:uuid:f4df0940-1213-48c8-932e-e5365c82b48b>
2018-04-25T21:59:58Z
192.0.78.25
text/html
sha1:6P2OJLHMSGGVYOIW2QHYOBD7W5T4JDXU
<urn:uuid:9dbf18ca-56e8-4c74-a108-499a25d5078e>
https://rindraramli.me/2017/04/30/3-lessons-that-i-learned-from-summon-implementation-web-discovery-layer/
length
response
<urn:uuid:8a537468-33db-4f06-9216-8d3814e2dbf2>
robots: classic
hostname: ip-10-140-228-121.ec2.internal
software: Nutch 1.6 (CC)
isPartOf: CC-MAIN-2018-17
operator: Common Crawl Admin
description: Wide crawl of the web for April 2018
publisher: Common Crawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf