Interview Questions.

Question 1. When Did You First Consider Using Koha?

Answer :

We started out lurking at the Koha list about a year ago, although now I don’t remember how Koha first got here to our attention. In January of this year, I’d visible enough to drag collectively a “tech group” along with me, the assistant director, our webmaster, our systems administrator, and our flow software program supervisor. We determined to embark on an experiment: Could we switch all of our automation software, from operating structures to net equipment, to Open Source by using the cease of this yr? We determined that there was no “fulfillment” or “failure” involved, only a easy research question with a “sure” or “no” solution. No matter the outcome, we might have gathered a number of facts, and we made plans from the very beginning to proportion this facts with the library network.

Question 2. What Was The Initial Draw Of Koha?

Answer :

Freedom. We need to apply the Internet to offer some cutting edge information offerings to our library purchasers, however we realized that this will require us to have control of our automation and database software program. We needed the liberty to exchange things, to trade the code if important, due to the fact the sorts of matters we need to do aren't going to seem in industrial library software for years. (Commercial library software carriers are extra interested by the lowest line than the cutting facet.)

Perl Scripting Interview Questions
Question three. What Drawbacks Did You See With Koha?

Answer :

The same drawbacks that plague a few of the smaller Open Source projects, I suspect. First is the abnormal tempo of improvement. Since Koha code improvement is a “spare time” activity for maximum of the programmers, the tempo of Koha’s boom is tough to are expecting. We discovered ourselves waiting for vital modules to be developed, now and again wondering if they ever might be developed, often suspecting that the answer to our unique studies query would be “no” – we couldn’t switch to a totally Open Source device.

The second is the hassle of “splintering.” If we took the developing Koha code and completed it to healthy our wishes, tough-coding the features we wished and leaving out things we didn’t need, we would have in effect created a new version of Koha that had departed from the primary improvement tree. That might suggest that we couldn't take advantage of destiny enhancements to the main tree.

Question four. You’ve Made A Decision To Contribute To The Development Of Koha. When Hlt First Commissioned Koha, They Decided To Make It Open Source Hoping That Other Libraries Would Step In And Support Development Of New Features As Well. What Are Your Thoughts On This Model?

Answer :

We’ve come to recognise that this can be the only feasible version, and possibly the solution to the question I just posed. It’s crucial that libraries do not look on Open Source as loose software program that they simply down load, press a button, and all their troubles will magically be solved. Open Source requires simply as a great deal dedication as industrial software program – you continue to handiest get what you pay for. Libraries must technique Open Source with the notion that they will devote a number of workforce time to know-how the code and how the software program does its activity. They should additionally be geared up to commit economic sources as properly, just as though they have been still paying annual license charges for industrial software program.

The difference is, with industrial software program a huge part of the license price goes to analyze and development over which the library has no manipulate, at the same time as with Open Source that equal cash can fund the development of the software program modules that the library honestly wishes. HLT has paid their money and received a product that works great for their desires. Now other libraries can pay a touch extra cash and obtain enhancements to that product to be able to make it suit their needs – without having to pay for the development of an entire software bundle. HLT got what it wanted, we plan to get what we want, different libraries will pay and get what they need. The libraries are paying a one-time expense that’s possibly much less than their annual license expenses, so they win. The programmers get a completely clear concept of what libraries want (cash talks!), so that they win. It’s a exquisite model for achievement.

Perl Scripting Tutorial
Question five. What Kind Of External Support Are You Using, Or Do You Foresee Using As You Convert Into Koha?

Answer :

Very little. We originally thought we would use a database consultant to assist in transferring our facts from our contemporary device to Koha. (This is a venture that’s commonly dealt with by way of the “new” software program vendor when libraries switch from one commercial product to any other.) We’ve lately realized, but, that the mechanics of the records switch aren't as difficult as identifying which information we want to keep and that is superfluous. For that reason, we’ll probable do the information transfer ourselves.

Otherwise, the tech crew is running to study the tools we will want to keep the software program: perl, linux, Mysql, Hypertext Preprocessor, etc. We regard this mastering system as part of our investment in Koha. And do not forget, our authentic motivation in searching at Koha changed into the ability to provide some reducing area offerings, so we’ll need to have a radical understanding of the software program for more than simply preservation purposes.

Linux Embedded systems Interview Questions
Question 6. What Are The Major Milestones In The Conversion Process?

Answer :

A massive one become the release of Koha 1.2.0 in July. For the first time, we saw a product that looked like a possible alternative to our current software. In late August, we held a day-lengthy assembly of the tech crew to review the whole thing that we had seen and found out so far in our research project, and we decided that Koha lacked most effective 3 actually crucial things for our needs: full MARC support, a Z39.50 server module, and a SIP2 or NCIP module. To fill the ones desires, we determined to dedicate a few economic assets to Koha development.

Our destiny plan is to move a number of our statistics into the present day model of Koha to see what adjustments we can want to make within the Koha tables. (And we would then recommend to the Koha builders that those forms of modifications need to be built into some sort of configuration application or template, as opposed to being tough-coded.) Once we've got a touch of our information transferred and running, we can transfer the relaxation and plan to run Koha in tandem with our vintage movement device. This will no longer only allow workforce to get acquainted with the new system (Koha), it's going to also give them an opportunity to request adjustments to displays, customized capabilities, and so on. Once we find that Koha has emerge as the system of choice for the workforce, we will shut down the antique automation system.

Question 7. When Will Your Patrons Be Able To See Koha In Action?

Answer :

We anticipate that Koha will take over from the vintage gadget sometime for the duration of the summer season of 2003.

Linux Embedded systems Tutorial Application Software Interview Questions
Question 8. How Do I Merge Records?

Answer :

Go to the cataloging seek and search for the data you want to merge. Select the records you want to merge. Select which report you need to be the principle document after which select the fields you want to merge.

Question 9. Why Isn’t Koha Detecting Duplicate Patrons?

Answer :

Koha detects duplicate patrons the use of FirstName, Surname and Date of Birth. Unless all three are an actual suit, the client isn’t taken into consideration a dup.

Git (software program) Interview Questions
Question 10. The Availability Numbers Don’t Look Right On The Search Results Screen, Why Not?

Answer :

There is a restriction to how many items Koha will check in seek consequences — examine the system desire Mac Search Results Items Per Record Status Check.

Git (software program) Tutorial
Question eleven. Why Some Do Items Show As Available And Checked Out In Search Results At The Same Time?

Answer :

Who an object turned into looked at to is stored inside the ‘issues’ table in Koha. The due date is likewise stored in gadgets.On mortgage, which on occasion receives set to null.

Docker (software) Interview Questions
Question 12. How Can I Delete Ebook Records In Batch?

Answer :

If you have got a file of urls or ‘bookids’ from your vendor, we can be capable of run a script to delete those bibs for you. Send us the report you obtained from the seller.

Perl Scripting Interview Questions
Question 13. When Checking Out An Item, Why Is The Due Date Is Prior To The Checkout Date?

Answer :

In the move and first-class rule table, test to look if this item kind and client category have a difficult due date set – and if this date is within the past.

Docker (software program) Tutorial