My final panic!!!!

It is the day of submission for this assignment, so I decide to check my staff and OPAC interface one more time.

The staff interface does not work. The error message says it is taking too long to load. I instantly panic, misremembering having tested this on work computer (I had only tested the OPAC, not the staff interface, for some reason).

I decide to ask my husband to check AWS, as this is also not running correctly on my work computer. He says that both the OPAC and staff interface still work as normal. I don't understand, but am less panicked. He suggested that, since the staff interface is on a non-default port (8080, instead of HTTP's usual 80), that it could just be my work's proxy server refusing connections to ports that are not 80. I therefore try check an unrelated site running on a non-default port, and it too does not work. This seems to confirm the problem is at my end.

I try to access through webproxy.net, but this site is blocked by my work. If this were to be implemented through my work, we would need to consider whether this would be an issue on the internal servers, or, if we decided to run on external servers, whether we could perhaps have our 8080 site allowed. Alternatively, after briefly researching the Koha Community wiki (and looking at the Koha pre-web configuration), it looks like we could run the both the staff interface and the OPAC on port 80 on the same server.

The Future....

I am definitely not done with Koha. In fact, I think I still have a lot to learn. The intial things I would like to try are

• More testing to find the many other issues which are sure to exist
• Install Koha on my own server (not on Amazon Web Services). This is just for my own knowledge - I would like to see how the process differs, and then when it comes to implementing for the library I work at, we can make a more appropriate decision.
• Perform more complex customisation, especially for the OPAC. I would like to create a nicer CSS.
• I am very interested in the idea users being able to use tags and subject headings to create RSS feeds that alert them to new content. I would like to see if I could learn enough programming to accomplish this.
• Would like to look at how Koha can be used as a CMS, but also how I would use Koha with another CMS like Drupal.
• As the catalogue records at the library I work at can only be exported a CSV, I would like to attempt to upload a batch of CSV records to Koha, to see how it is done, and to spot potential issues with implementing Koha at work in the future.

Putting Koha through its paces

I now wanted to put my Koha through its paces, and see how it performs.

Basic checks

• I first tested the most important thing: Does it work outside of my computer? Thankfully it did. I tested it on both my husband's and a public computer at the National Library. Making sure I could get to both the staff and OPAC interfaces.
• I also checked it worked on my mobile phone, and it did (however I think it could be customised more for mobile devices).
• I wanted to make sure it would work on different browsers, so tested compatibility with Chrome, Internet Explorer, Firefox, Opera, and Lynx.

Cataloging checks.

• I now wanted to attempt to add records through Z39.50, the copy cataloguing tool, and lo and behold it didn't work. I kept getting the message "No targets selected." I eventually figured out by Googling this error that I needed to add some Z39.50 target for it to search, and found this great video, which showed me how to add some Z39.50 targets from IRSpy.

Z39.50 Servers added

Now I was able to easily find books through this. I then encountered another problem, as I had not created any item types. Since I remembered seeing this earlier, I popped back into this setting to create a "Book" item. I was then able to create the following five records.

• The organization of information /
• Alison Holst's meals without meat : vegetarian recipes /
• Homo mysterious : evolutionary puzzles of human nature /
• 27 cats next door / by Feagles, Anita MacRae
• All about cats / by Burger, Carl 

Now, I searched the catalogue to make sure these all existed, and they did. The search functionality also worked well.

Adding users

It was very simple to create two users (a staff member and a patron).

However, I could not place a hold as a patron. I just kept getting the error message "Sorry no items can be placed on hold, no items available."

I tried to go through all the patron settings, and catalogue settings, but couldn't make it work. I then tried Googling this error, but got nothing useful. Only a couple of links saying that it may be a bug with the zebra indexer. I tried adding barcodes. I even used my staff login to check in out (which worked), but once checked back in, he still could not place a hold. Staff could also not place holds for clients. Now was the time to trawl through all the settings to do with holds (the system preferences are thankfully searchable), and found the holds policy, which did not allow for holds to be place on items that were currently on the shelf. I changed this to allow, and the problem was solved.

I was then able to request this book as Robert Jones, and then locate it in the holds to pull, and check it out, as librarian Karla Martin.

What I learnt - With perseverance and some serious trawling, you can fix even what I believed unfixable. My Koha installation works, but it still has some issues, which I can only discover through testing. I still need to do more testing over the coming weeks to see if all aspects are working, but I also need to change some additional settings first. In this case, none of my problem solving methods worked except for a manual line-by-line search through the settings. This means you cannot always rely on Google. I couldn't find the answer on Google, nor the Community Discussion Lists. I also learnt that testing each facet of the software is very important before launching, so that each problem can be found and a solution hopefully discovered.