FAQs

Yes! 

• Search for the record you'd like to copy
• Choose the record by clicking on the title
• Click on 'Edit'
• Choose to 'Edit as New (Duplicate)'
  
  
• After editing your record, click 'Save'
• You will be warned that this record was a duplicate
  
  
  
• Choose 'No' to save this as a new record

Koha currently lets you download bib records converted to various XML-based metadata formats, including MODS, one at a time.  It would not be difficult to make a batch MODS exporter, and if you're OK with the default MODS to MARC21 stylesheet, a MODS import wouldn't be hard to do either.

Although there is a desire to enhance Koha so that it can natively store bibliographic metadata in formats other than MARC, that will be further down the road.

The "staging area" and "reservoir" are the same thing. Staging a record (via the Tools job) does *not* automatically add the record to the main catalog, it puts it in the reservoir. You have to commit it via the manage import batches job

Go through System Administration interface. You will find Authorized Values link. There you can see and add codes for almost all values showing up in drop down boxes used in editor of bibliographic and item data. For your particular case you need LOC.

Exploring more into your frameworks will give you the ability to control the behavior of editor for bib end item data. You can see and set up authorized values for every MARC field.

Search for the partial record in your catalog and then go to Edit > Edit Record and from there you can do a Z39.50 search to pull in a more full record or you can do your full cataloging there.

Not currently.  This feature is likely to be developed soon.

You just have change the itemcallnumber system preference, by default this preference is set to Dewey.

• Get there: More > Administration > Global system preferences > Cataloging > itemcallnumber

• Some of these will automatically enter the data just by clicking in the text field, others require that you click on the '...'

1. bulkmarcimport (BMI) is done through command-line whereas stage MARC records for import (SMRI) uses the web interface.
2. With BMI the records get cataloged directly so the reservoir step is skipped, contrary to what happens with SMRI.
   

So, given that, what's the intended use of the two functionality ? Being new to the library science field, I suspect that there is perhaps something more to the story than what I know.

BMI is usually used when migrating. So it's only once, before you go live. SMRI is used on a daily basis by librarians. For example after getting your order list from your book vendor you can easily import that list into the catalog without having to re-enter all of that information.

There are several recommendations:

1. I have found that AMICUS from Canada is quite good, with MARC-21 records from LoC and the British Library system. It does you require that you register (free) every 6 months http://www.collectionscanada.gc.ca/amicus/006002-400-e.html
• Do you find that there's extensive French language content in the AMICUS records? We prefer to keep our records relatively "clean", so lots of French subject headings, etc. would be an issue for us.
• No, they have the same records as everyone else. Very English. One good thing about AMICUS is that they have taken the British Library's records which are NOT marc and converted them to marc21 and made them available via a z39.50 server.
2. The ‡biblios.net open cataloging service's bibliographic records can be accessed via Z39.50.  Connection settings are at https://bws.biblios.net/doku.php/searching_for_bibliographic_and_authority_records#advanced_searching_with_z39.50
• The sources include the Open Library, LC, the Talis Union Catalogue, contributions by several specialized libraries, and ‡biblios.net users.
3. I always find that the big US publics (Boston, New York, etc) have great records.
   

Koha supports both MARC21 and UNIMARC standards for Authority Control.

One feature of UNIMARC that is especially attractive is the storage of a link ID at the bibliographic tag level in $6 that maintains it easy to point to the appropriate

001 tag of the appropriate Authority record -- this makes it very simple to reference and update bibliographic data when authority data is changed. The MARC21 standards committee will be adding this feature into the MARC21 standard for authorities shortly as a $0, but you can begin using Koha authority records with identifiers linking bibliographic and authority data immediately using the local-use $9 (set up by default in new Koha installations).

Koha in MARC21 setup uses the  999 to register the unique identifier of each bibliographic record.

IMPORTANT: Koha uses two unique identifiers of each bibliographic record.

• The 999$c field stores the Koha biblionumber  [used in the MySQL table 'biblio']
• The 999$d field stores the Koha biblioitemnumber  [used in the MySQL table 'biblioitems']
  

The reason for this is that the 001 field field 001 is a special field that you cannot map data to in Koha

One can not delete the "Default" Framework, yet can delete the other frameworks that have been created.  This error message does not refer to records in your database but to the MARC21 tags and subfield setup in that framework.

You can delete the unwanted framework/s from .....cgi-bin/koha/admin/biblio_framework.pl. Click on delete and confirm.

It sounds like you have to turn the BiblioAddsAuthorities system preference ON. When this preference is OFF it locks the 100 field so that you cannot type in it, just search for an authority to add.

This is because you created the new shelving location with a code value of 0 (zero)

Just FYI the system interprets authorized values of 0 as equaling a null so when you edit a record in cataloging where the authorized value in a field was assigned  where the code was 0, the value displays as null in the item editor (or MARC editor) instead of the value the library  meant it to be.

There are several CSS preferences that can be changed to alter the display of your OPAC. 

The external stylesheet (opacstylesheet) overwrites the one that lives on the koha server (opaclayoutstylesheet).

• Get there: Administration > Global System Preferences > OPAC

Yes.  Just enter an item type for new items and assign different circulation rules for this item type.

Yes, you can use HTML in your news posts, in fact, using HTML in the posts on your OPAC will make the look and feel more friendly to your patrons.

To change Koha's Zebra configuration from UNIMARC to MARC21, change the following Zebra configuration files, which will be located in /etc/koha/zebradb if you used a "standard" installation.

zebra-authorities.cfg - edit profilePath to replace 'unimarc' with 'marc21'
zebra-authorities-dom.cfg - make same change to profilePath
zebra-biblios.cfg - make same change to profilePath

Next, change the 'marcflavour' system preference (via the Administration page on the Koha staff interface) to 'MARC21'.

Next, stop and restart the zebrasrv daemon on your server.

Finally, if you have MARC records already loaded in your database, reindex them by running misc/migration_tools/rebuild_zebra -a -b -r

All of the information about your Koha install can be found on the 'About Koha' page.

• Get there: More > About Koha

In administration, go to Links Koha - MARC DB, go to biblio, and change author to 110a. Then, run the script intranet/scripts/misc/rebuildnonmarc.pl

In 3.0, it should display by default when you have the XSLTDetailsDisplay system preference turned ON.

• Get there: More > Administration > Global preferences > OPAC > XSLTDetailsDisplay

"My Library" logs you into the branch that is specified in your account (borrowers table).  This provides a default that is almost always correct for all staff in all branches (exceptions: librarians at multiple branches, central staff, the superuser who has NO branch, etc.). 

If all your staff users have their home branch set correctly, then there is no difference between the two choices for them.  Both are correct.  You could eliminate "My Library" from your local list, but there's not much point.

Turn OFF the autobarcode system preference and the plugin will be automatically disabled.

We have a framework now for javascript-based keyboard shortcuts. If you suggest a good one that won't conflict with standard browser shortcuts the developers can add it.

These shortcuts already exist and have been tested in Windows, Firefox and Internet Explorer:

• Alt-u to move focus to Check Out form
• Alt-r to move focus to Check in Form (or to Check In link on main page)
• Alt-q to move focus to Search form

The globalDueDate is a fixed due date - all loans get that due date. The ceilingDueDate establishes an upper bound, and if a loan's due date per the circ policy falls before the ceiling, nothing happens. But if the due date would ordinarily fall after the ceiling (say, for a four week loan made one week before the ceiling), the ceiling is used instead.

Is your operating system Windows?

• Open  a command prompt and type: cd \mysql\bin
• Type: mysqladmin -u koha -p password YourNewPasswordHere
• You will be prompted for the current password which is "koha"
  

The above action will reset the mysql password.

Open the C:\etc\koha.conf and set the new password in the pass=koha line.

Restart apache to implement the change

Go through System Administration interface. You will find Authorized Values link. There you can see and add codes for almost all values showing up in drop down boxes used in editor of bibliographic and item data. For your particular case you need LOC.

Exploring more into your frameworks will give you the ability to control the behavior of editor for bib end item data. You can see and set up authorized values for every MARC field.

You can turn 'on' the Cart feature in 'Global System Preferences'

• Get there: More > Administration > Global System Preferences > OPAC > opacbookbag

Not currently.  This feature is likely to be developed soon.

A template is linked to a script via the call to get_template_and_user - see any of the existing scripts for an example.

The FOSS PBX system Asterisk (http://www.asterisk.org/) could do what you propose, but would need additional programming for the Asterisk<->Koha interface.

This code is planned to be written in the summer of 2009.

This can be done with CSS very easily. The quickest way is edit the System Preference 'OPACUserCSS', and add the line:

The 'OPACUserCSS' is applied to the page last, so it will override any other CSS.   Alternately, you can directly edit the CSS file(s) specified by the system preferences 'opaclayoutstylesheet' and 'opaccolorstylesheet', which can be found in the css directory under the OPAC templates directory in your installation.

• Get there: More > Administration > Global preferences > OPAC > OPACUserCSS
• Get there: More > Administration > Global preferences > OPAC > opaclayoutstylesheet
• Get there: More > Administration > Global preferences > OPAC > opaccolorstylesheet

You just have change the itemcallnumber system preference, by default this preference is set to Dewey.

• Get there: More > Administration > Global system preferences > Cataloging > itemcallnumber

There is a syspref for 'globalDueDate' that will override any dates set in the circulation matrix. 

• Get there: More > Administration > Global preferences > Circulation > globalDueDate

As for holidays, there is a calendar module in Koha that will let you assign the days that your library isn't in session.

• Get there: More > Tools > Calendar

You will be brought to a confirmation page to make sure that you really want to delete that category:

If the category is used for any patrons, you will be unable to delete the category:

No.  This field is looking for the borrowernumber assigned to the patron by Koha.

When an item becomes overdue (ie, duration of checkout) is defined in Koha's 'Administration' module:

• Get there: More > Administration > Patrons and Circulation > Circulation Rules
  

Koha in MARC21 setup uses the  999 to register the unique identifier of each bibliographic record.

IMPORTANT: Koha uses two unique identifiers of each bibliographic record.

• The 999$c field stores the Koha biblionumber  [used in the MySQL table 'biblio']
• The 999$d field stores the Koha biblioitemnumber  [used in the MySQL table 'biblioitems']
  

The reason for this is that the 001 field field 001 is a special field that you cannot map data to in Koha

If you create a patron category that has "overdue notice required" set to "Yes," that means the category will appear in the "Overdue 'Notice/Status Triggers'" matrix.  If your patron category has "overdue notice required" set to "No," that patron category will not appear in the triggers matrix.

You may not have the 'Logs' system preference turned on

• Get there: More > Administration > Global System Preferences > Logs

After 2009-08-15, Amazon Web Services will expect that all requests to the Product Advertising API, which is what Koha uses for retrieving reviews and other enhanced content from Amazon, include signatures.  This patch and subsequenct patches implement this functionality.

What this means in practice (assuming the user has elected to use any enhanced content from Amazon) is that

1. The user must get a Amazon Secret Access Key.  This can be done by logging in to the user's AWS account at (e.g.) http://aws.amazon.com/, going to the 'Access Identifiers' page, and from there retrieving and/or creating a new Secret Access Key.
2. The contents of the Secret Access Key should then be entered into the new AWSPrivateKey system preference.

Once that is done, grabbing reviews and table of contents from Amazon should work as normal.  If the user doesn't do this before 2009-08-15, reviews and TOCs will no longer be supplied from Amazon, although there should be no crashes - the content will simply not show up.

Note that the requirement to sign requests does *NOT* appear to apply to simply displaying book covers from Amazon.

Each news item has an "Appear in position" number assigned to it.  If two items have the same number (for example 1) then either item may appear first.  To ensure that your news appears in the order you want, always edit existing news items so that their "Appear in position" number is as you'd expect it to be.

Changing the 'marcflavour' syspref won't help.

This is because you created the new shelving location with a code value of 0 (zero)

Just FYI the system interprets authorized values of 0 as equaling a null so when you edit a record in cataloging where the authorized value in a field was assigned  where the code was 0, the value displays as null in the item editor (or MARC editor) instead of the value the library  meant it to be.

Search for the partial record in your catalog and then go to Edit > Edit Record and from there you can do a Z39.50 search to pull in a more full record or you can do your full cataloging there.

Although it's not possible to change the order of the fields in the patron record so that all required fields are at the top, it is possible to hide fields that the library never intends to use. You can do this by entering javascript in the staff client system preference "intranetuserjs".

For example, if you wish to hide the Salutation, Initials, Other name and Street number and Street type fields, you need to enter the following:

$(document).ready(function(){
       $("#entryform #btitle").parent().remove();
       $("#entryform #initials").parent().remove();
       $("#entryform #othernames").parent().remove();
       $("#entryform #streetnumber").parent().remove();
       $("#entryform #streettype").parent().remove();
});

You need a line for each field that you wish to hide. The field names come from the HTML source code and are generally the same as the table column names, but not in all cases.

Below are the fields i the patron record:

TIP: If you hide the "Street number" field", the "Street type" field will appear even though you haven't defined any street types.

When viewing the patron's record there will be a note above the patron's name:

You can also see this information when editing a patron under the 'Patron Account Flags':

When an imported patron matches an existing one, keep data in the original record unless our import file includes that column.

The email will show you what changes the patron has made to their info.  You then need to make those changes via the patron interface on the staff client.

When you receive this email it will look something like this:

Subject: User Request for update of Record.

Borrower 1

has requested to change her/his personal details.

Please check these new details and make the changes:

surname : Smyth  -->  Smith

firstname : Rachel  -->  Rachel

phone :   --> 

fax : 555-555-5555  -->  555-555-5444

address : 111 Main Street  -->  123 Main Street

address2 :

city : Athens, OH  -->  West Newbury, MA

45701

phone :   --> 

mobile :   --> 

fax :

phonepro :

emailaddress :   -->

B_streetaddress :   -->  

B_city :   --> 

B_zipcode :   --> 

dateofbirth :   --> 

sex : F  -->  F

Not at this time.

You will be brought to a confirmation page to make sure that you really want to delete that category:

If the category is used for any patrons, you will be unable to delete the category:

There is a limit of 100K on the size of the picture uploaded and it is recommended that the image be 120x200 pixels, but smaller images will work as well.

There is a ReturnBeforeExpiry system preference that determines if the book is due at the regular due date or on the patron expiration day.  If ReturnBeforeExpiry is on, then the due date can't be after the borrower expires.

• Get there: More > Administration > Global system preferences > Circulation > ReturnBeforeExpiry

When an item becomes overdue (ie, duration of checkout) is defined in Koha's 'Administration' module:

• Get there: More > Administration > Patrons and Circulation > Circulation Rules
  

First you will need a patronimages/ directory.  If you do not have this directory you will see the following error.

• Contact your system administrator to create this directory and you'll be set to go.

Next you will need to turn the 'patronimages' system preference is set to 'ON' to use this feature.

• Get there: More > Administration > Global System Preferences > Patrons > patronimages

No, this report will only remove connections between patrons and items they have checked out in the past but have returned to the library.

Yes, just go to Tools > Notices and edit the Check In and Check Out notices.

• Get there: More > Administration > Global system preferences > Patrons > EnhancedMessagingPreferences

Yes, just make sure you have the OpacRenewalAllowed system preference turned to on.

• Get there: More > Administration > Global System Preferences > OPAC > OpacRenewalAllowed

If you want to prevent patrons from renewing items (in Koha 3.2) when they owe over a certain amount you can set that by setting the OPACFineNoRenewals system preference with the max a patron can owe and still be able to renew items.

• Get there: More > Administration > Global System Preferences > Circulation > OPACFineNoRenewals
  

You can make use of the Holidays Calendar by turning on the proper system preferences

• Get there: More > Administration > Global System Preferences > Circulation > useDaysMode
• Choose the method for calculating due date: select Calendar to use the holidays module, and Days to ignore the holidays module
• Get there: More > Administration > Global System Preferences > Circulation > finescalendar
• This will use the check the holiday calendar before charging fines
  

When viewing the patron's record there will be a note above the patron's name:

You can also see this information when editing a patron under the 'Patron Account Flags':

To schedule overdue notices, you must use Koha's 'Notice/Status Trigger' tool.

• Get there: More > Tools > Overdue notice/status triggers
  

The globalDueDate is a fixed due date - all loans get that due date. The ceilingDueDate establishes an upper bound, and if a loan's due date per the circ policy falls before the ceiling, nothing happens. But if the due date would ordinarily fall after the ceiling (say, for a four week loan made one week before the ceiling), the ceiling is used instead.

This info is available by default (unless you purge it periodically) from the moredetail.pl screen (click on an item's barcode).

This occurs at checkout after scanning the patron's barcode, at circulation.pl.

See the section in red on the right of this screenshot:

The patron is allowed to continue borrowing until their fines have reached a certain configurable threshold, by default $5.00.

The FOSS PBX system Asterisk (http://www.asterisk.org/) could do what you propose, but would need additional programming for the Asterisk<->Koha interface.

This code is planned to be written in the summer of 2009.

There is a syspref for 'globalDueDate' that will override any dates set in the circulation matrix. 

• Get there: More > Administration > Global preferences > Circulation > globalDueDate

As for holidays, there is a calendar module in Koha that will let you assign the days that your library isn't in session.

• Get there: More > Tools > Calendar

If you want Koha to trigger an action (send a letter or debar member), a delay value is required. No delays means no actions will be performed.

It's the latter - on the 5th day it's $.10.

When you check it in you will get a message telling you that the book has been marked as found. 

This means that the Lost status is changed on the item back to available.

The system will try to fill the hold locally first, then randomize (choose first available from other branches) if it can't fill it locally.

Koha handles overdue notices in one of two automated ways: by email or by printed labels.

If a borrower has an email defined in their patron account, overdue notices automatically get sent to the patron's email account according to the schedule defined in the 'Notice/Status Triggers' Tool.

TIP: Patrons can alter their notification setting using the Messaging tool on their account.

Borrowers that have no email defined will have their notices sent via email to the library for printing.  The email is sent to the branch admin email, or failing that to the address set in the system preference as the 'KohaAdminEmailAddress'. This email is generated by the misc/cronjobs/overdue_notices.pl cron job.  Contact your system administrator for help with this setting.

IMPORTANT: The email notice report that is compiled and sent to the admin (for borrowers with no email in Koha) rely on the 'delays' to determine when/how often that email gets sent as well.

There is a ReturnBeforeExpiry system preference that determines if the book is due at the regular due date or on the patron expiration day.  If ReturnBeforeExpiry is on, then the due date can't be after the borrower expires.

• Get there: More > Administration > Global system preferences > Circulation > ReturnBeforeExpiry

When an item becomes overdue (ie, duration of checkout) is defined in Koha's 'Administration' module:

• Get there: More > Administration > Patrons and Circulation > Circulation Rules
  

This tool takes all branches in the overdue rules and sent notifications to them. So, if you have a default rule & a branch rule, the notification will be generated twice.

A quick fix is to discard "default rule" for instance.

If you create a patron category that has "overdue notice required" set to "Yes," that means the category will appear in the "Overdue 'Notice/Status Triggers'" matrix.  If your patron category has "overdue notice required" set to "No," that patron category will not appear in the triggers matrix.

After holidays are entered on the calendar, circulation rules are then recalculated to taken in to account that library is closed and there will be no one present to return items.

No, this report will only remove connections between patrons and items they have checked out in the past but have returned to the library.

You can choose Numbering formula: Volume {X}, Number {Y}, {Z} (Z if you want the year for instance)

Then you edit advanced pattern :

For X :
    Add  : 1
    once every : 4 (every 4 issues for a quarterly, as volume changes every year)
    When more than  9999999
    inner counter
    Set back to     0
    Begins with 104

inner counter : if you begin with first issue of the year write nothing or 0; if you begin with the second issue (april-june for instance), inner counter = 1 (you say to koha to take into account already one "received" issue, to calculate when the volume changes) ; ...

For Y :
    Add  : 1
    once every : 1 (for each received issue)
    When more than  9999999
    inner counter     :     same as for X
    Set back to     0
    Begins with 486

For Z :
    Add  : 1
    once every : 4
    When more than  9999999
    inner counter     :     same as for X
    Set back to     0
    Begins with 2009

You let "When more than 9999999" , "Set back to 0", as volume, number and year increase continuously

In the end your pattern should look like this:

A routing list is a list of people who should receive a serial when it arrives in the library. This is an easy way to pass a popular library related journal from staff member to staff member without writing a list of names and stapling it to the journal (a common method used in many libraries).

It sounds like you have to turn the BiblioAddsAuthorities system preference ON. When this preference is OFF it locks the 100 field so that you cannot type in it, just search for an authority to add.

Anyone with superlibrarian permission to edit/delete public patron lists.  Editing is limited to editing the title or sorting order.

Login to your account and visit your account page.  Click the My Lists tab on the left to see just your lists.

After adding items to a list, you have to manually click 'Clear All' at the top of the results page in order to remove checks from the boxes of the items you've selected.

See example below

Even if lists are 'disabled' for the OPAC, staff users still have access to them from the staff side. The 'virtualshelves' preference only affects whether or not the feature is available from the OPAC.

Yes, you can use the Task Scheduler tool.

• Get there: More > Tools > Task Scheduler
  

At this time the only way to search for tags is from the 'my tags' tab on Your Account.

• Get there: OPAC > your name > my tags
  

Yes, you can use HTML in your news posts, in fact, using HTML in the posts on your OPAC will make the look and feel more friendly to your patrons.

You can make use of the Holidays Calendar by turning on the proper system preferences

• Get there: More > Administration > Global System Preferences > Circulation > useDaysMode
• Choose the method for calculating due date: select Calendar to use the holidays module, and Days to ignore the holidays module
• Get there: More > Administration > Global System Preferences > Circulation > finescalendar
• This will use the check the holiday calendar before charging fines
  

To schedule overdue notices, you must use Koha's 'Notice/Status Trigger' tool.

• Get there: More > Tools > Overdue notice/status triggers
  

The "staging area" and "reservoir" are the same thing. Staging a record (via the Tools job) does *not* automatically add the record to the main catalog, it puts it in the reservoir. You have to commit it via the manage import batches job

There are two system preferences you can set for this.

• TagsShowOnDetail defaults to 10 and defines what displays on the book detail page
• Get there: More > Administration > Global system preferences > Enhanced Content > TagsShowOnDetail
• TagsShowOnList defaults to 6 and is defined what displays on the search results page
• Get there: More > Administration > Global system preferences > Enhanced Content > TagsShowOnList

Set either of these to zero to have no tags display.

When an imported patron matches an existing one, keep data in the original record unless our import file includes that column.

Not at this time.

There is a syspref for 'globalDueDate' that will override any dates set in the circulation matrix. 

• Get there: More > Administration > Global preferences > Circulation > globalDueDate

As for holidays, there is a calendar module in Koha that will let you assign the days that your library isn't in session.

• Get there: More > Tools > Calendar

1. bulkmarcimport (BMI) is done through command-line whereas stage MARC records for import (SMRI) uses the web interface.
2. With BMI the records get cataloged directly so the reservoir step is skipped, contrary to what happens with SMRI.
   

So, given that, what's the intended use of the two functionality ? Being new to the library science field, I suspect that there is perhaps something more to the story than what I know.

BMI is usually used when migrating. So it's only once, before you go live. SMRI is used on a daily basis by librarians. For example after getting your order list from your book vendor you can easily import that list into the catalog without having to re-enter all of that information.

There is a limit of 100K on the size of the picture uploaded and it is recommended that the image be 120x200 pixels, but smaller images will work as well.

No.  This field is looking for the borrowernumber assigned to the patron by Koha.

This tool takes all branches in the overdue rules and sent notifications to them. So, if you have a default rule & a branch rule, the notification will be generated twice.

A quick fix is to discard "default rule" for instance.

You may not have the 'Logs' system preference turned on

• Get there: More > Administration > Global System Preferences > Logs

One can not delete the "Default" Framework, yet can delete the other frameworks that have been created.  This error message does not refer to records in your database but to the MARC21 tags and subfield setup in that framework.

You can delete the unwanted framework/s from .....cgi-bin/koha/admin/biblio_framework.pl. Click on delete and confirm.

First you will need a patronimages/ directory.  If you do not have this directory you will see the following error.

• Contact your system administrator to create this directory and you'll be set to go.

Next you will need to turn the 'patronimages' system preference is set to 'ON' to use this feature.

• Get there: More > Administration > Global System Preferences > Patrons > patronimages

After holidays are entered on the calendar, circulation rules are then recalculated to taken in to account that library is closed and there will be no one present to return items.

Each news item has an "Appear in position" number assigned to it.  If two items have the same number (for example 1) then either item may appear first.  To ensure that your news appears in the order you want, always edit existing news items so that their "Appear in position" number is as you'd expect it to be.

No, this report will only remove connections between patrons and items they have checked out in the past but have returned to the library.

Yes, you can use the Task Scheduler tool.

• Get there: More > Tools > Task Scheduler
  

The statistic reports are somewhat inclusive.  To get reports for the month of November you would search between November 1 and December 1.

There is a page on the Koha Wiki: http://wiki.koha.org/doku.php?id=sql_library with reports written by Koha libraries around the world.

NEKLS also has a great page (http://www.nexpresslibrary.org/training/reports-training/ ) with a list of reports they have written.

Fine/Fee types:

• C = credit
• FOR =forgiven
• W = writeoff
• F = overdue fine
• FU = overdue, still acccruing
• PAY = payment
• A = acc't management fee
• M = Sundry
• L = Lost Item
• N = New Card

The fines table is the accountlines table and the field is accounttype

Anyone with superlibrarian permission to edit/delete public patron lists.  Editing is limited to editing the title or sorting order.

There are several CSS preferences that can be changed to alter the display of your OPAC. 

The external stylesheet (opacstylesheet) overwrites the one that lives on the koha server (opaclayoutstylesheet).

• Get there: Administration > Global System Preferences > OPAC

Yes.  Simply check the items in your cart that you want to place on hold and click 'Place Hold'

To receive updates via email you can paste the RSS feed address into an RSS to email service such those listed in this guide from RSS Compendium (http://allrss.com/rssreadersemail.html).

Yes, just make sure you have the OpacRenewalAllowed system preference turned to on.

• Get there: More > Administration > Global System Preferences > OPAC > OpacRenewalAllowed

If you want to prevent patrons from renewing items (in Koha 3.2) when they owe over a certain amount you can set that by setting the OPACFineNoRenewals system preference with the max a patron can owe and still be able to renew items.

• Get there: More > Administration > Global System Preferences > Circulation > OPACFineNoRenewals
  

At this time the only way to search for tags is from the 'my tags' tab on Your Account.

• Get there: OPAC > your name > my tags
  

At this time, this is not a feature of Koha.  All comments go through moderation.

Yes, you can use HTML in your news posts, in fact, using HTML in the posts on your OPAC will make the look and feel more friendly to your patrons.

In administration, go to Links Koha - MARC DB, go to biblio, and change author to 110a. Then, run the script intranet/scripts/misc/rebuildnonmarc.pl

In 3.0, it should display by default when you have the XSLTDetailsDisplay system preference turned ON.

• Get there: More > Administration > Global preferences > OPAC > XSLTDetailsDisplay

It takes adding just a bit of HTML to your front page, along the lines of

<form name="searchform" method="get" action="http://YOUR_OPAC_HOST/cgi-bin/koha/opac-search.pl">
 <input type="text" name="q" />
 <input type="submit" value="Search Catalog" />
</form>

You can alter this feature by changing the reviewson system preference.

• Get there: More > Administration > Global system preferences > OPAC > reviewson

Login to your account and visit your account page.  Click the My Lists tab on the left to see just your lists.

This is currently hard-coded into the template, so it requires template customization of opac-advsearch.tmpl.

What you can do is use http://plugins.jquery.com/project/cookie

Then you can do something like

var cookie = $.cookie("CGISESSID");
 if (!cookie){
  hide the search
}

There are two system preferences you can set for this.

• TagsShowOnDetail defaults to 10 and defines what displays on the book detail page
• Get there: More > Administration > Global system preferences > Enhanced Content > TagsShowOnDetail
• TagsShowOnList defaults to 6 and is defined what displays on the search results page
• Get there: More > Administration > Global system preferences > Enhanced Content > TagsShowOnList

Set either of these to zero to have no tags display.

After adding items to a list, you have to manually click 'Clear All' at the top of the results page in order to remove checks from the boxes of the items you've selected.

See example below

You can turn 'on' the Cart feature in 'Global System Preferences'

• Get there: More > Administration > Global System Preferences > OPAC > opacbookbag

Even if lists are 'disabled' for the OPAC, staff users still have access to them from the staff side. The 'virtualshelves' preference only affects whether or not the feature is available from the OPAC.

This can be done with CSS very easily. The quickest way is edit the System Preference 'OPACUserCSS', and add the line:

The 'OPACUserCSS' is applied to the page last, so it will override any other CSS.   Alternately, you can directly edit the CSS file(s) specified by the system preferences 'opaclayoutstylesheet' and 'opaccolorstylesheet', which can be found in the css directory under the OPAC templates directory in your installation.

• Get there: More > Administration > Global preferences > OPAC > OPACUserCSS
• Get there: More > Administration > Global preferences > OPAC > opaclayoutstylesheet
• Get there: More > Administration > Global preferences > OPAC > opaccolorstylesheet

After 2009-08-15, Amazon Web Services will expect that all requests to the Product Advertising API, which is what Koha uses for retrieving reviews and other enhanced content from Amazon, include signatures.  This patch and subsequenct patches implement this functionality.

What this means in practice (assuming the user has elected to use any enhanced content from Amazon) is that

1. The user must get a Amazon Secret Access Key.  This can be done by logging in to the user's AWS account at (e.g.) http://aws.amazon.com/, going to the 'Access Identifiers' page, and from there retrieving and/or creating a new Secret Access Key.
2. The contents of the Secret Access Key should then be entered into the new AWSPrivateKey system preference.

Once that is done, grabbing reviews and table of contents from Amazon should work as normal.  If the user doesn't do this before 2009-08-15, reviews and TOCs will no longer be supplied from Amazon, although there should be no crashes - the content will simply not show up.

Note that the requirement to sign requests does *NOT* appear to apply to simply displaying book covers from Amazon.

The Amazon that can be pulled via the Amazon Web Services are different from those found on Amazon web site. On Amazon, you get publisher reviews with Amazon reviews. But for copyright reasons, publisher reviews are not accessible by AWS.

Each news item has an "Appear in position" number assigned to it.  If two items have the same number (for example 1) then either item may appear first.  To ensure that your news appears in the order you want, always edit existing news items so that their "Appear in position" number is as you'd expect it to be.

This feature is yet to be developed, but is in the works.

Anyone with superlibrarian permission to edit/delete public patron lists.  Editing is limited to editing the title or sorting order.

Yes, you can use HTML in your news posts, in fact, using HTML in the posts on your OPAC will make the look and feel more friendly to your patrons.

Even if lists are 'disabled' for the OPAC, staff users still have access to them from the staff side. The 'virtualshelves' preference only affects whether or not the feature is available from the OPAC.

The Amazon that can be pulled via the Amazon Web Services are different from those found on Amazon web site. On Amazon, you get publisher reviews with Amazon reviews. But for copyright reasons, publisher reviews are not accessible by AWS.

Each news item has an "Appear in position" number assigned to it.  If two items have the same number (for example 1) then either item may appear first.  To ensure that your news appears in the order you want, always edit existing news items so that their "Appear in position" number is as you'd expect it to be.

Yes, just go to Tools > Notices and edit the Check In and Check Out notices.

• Get there: More > Administration > Global system preferences > Patrons > EnhancedMessagingPreferences

To schedule overdue notices, you must use Koha's 'Notice/Status Trigger' tool.

• Get there: More > Tools > Overdue notice/status triggers
  

If you want Koha to trigger an action (send a letter or debar member), a delay value is required. No delays means no actions will be performed.

A routing list is a list of people who should receive a serial when it arrives in the library. This is an easy way to pass a popular library related journal from staff member to staff member without writing a list of names and stapling it to the journal (a common method used in many libraries).

Koha handles overdue notices in one of two automated ways: by email or by printed labels.

If a borrower has an email defined in their patron account, overdue notices automatically get sent to the patron's email account according to the schedule defined in the 'Notice/Status Triggers' Tool.

TIP: Patrons can alter their notification setting using the Messaging tool on their account.

Borrowers that have no email defined will have their notices sent via email to the library for printing.  The email is sent to the branch admin email, or failing that to the address set in the system preference as the 'KohaAdminEmailAddress'. This email is generated by the misc/cronjobs/overdue_notices.pl cron job.  Contact your system administrator for help with this setting.

IMPORTANT: The email notice report that is compiled and sent to the admin (for borrowers with no email in Koha) rely on the 'delays' to determine when/how often that email gets sent as well.

When an item becomes overdue (ie, duration of checkout) is defined in Koha's 'Administration' module:

• Get there: More > Administration > Patrons and Circulation > Circulation Rules
  

This tool takes all branches in the overdue rules and sent notifications to them. So, if you have a default rule & a branch rule, the notification will be generated twice.

A quick fix is to discard "default rule" for instance.

If you create a patron category that has "overdue notice required" set to "Yes," that means the category will appear in the "Overdue 'Notice/Status Triggers'" matrix.  If your patron category has "overdue notice required" set to "No," that patron category will not appear in the triggers matrix.

Just enter a wildcard (*) in front number you want to find in the barcode.

To change Koha's Zebra configuration from UNIMARC to MARC21, change the following Zebra configuration files, which will be located in /etc/koha/zebradb if you used a "standard" installation.

zebra-authorities.cfg - edit profilePath to replace 'unimarc' with 'marc21'
zebra-authorities-dom.cfg - make same change to profilePath
zebra-biblios.cfg - make same change to profilePath

Next, change the 'marcflavour' system preference (via the Administration page on the Koha staff interface) to 'MARC21'.

Next, stop and restart the zebrasrv daemon on your server.

Finally, if you have MARC records already loaded in your database, reindex them by running misc/migration_tools/rebuild_zebra -a -b -r

This is currently hard-coded into the template, so it requires template customization of opac-advsearch.tmpl.

You have to set your index to rebuild with these settings: misc/migration_tools/rebuild_zebra.pl -b -a -z

See also misc/cronjobs/crontab.example so that you can schedule the index to be rebuilt regularly.

You can put it on whatever port you like. Just look in koha-httpd.conf and make changes accordingly.

Assuming you're using Koha 3 with Zebra and that Zebra is configured to expose a public Z39.50 service, you would need to report the following:

• server name
• Z39.50 port
• database name - by default, that will usually be 'biblios'
  

The default Zebra configuration for MARC21 uses the Bib-1 attribute set.

You will need two different host names, one for OPAC, one for Admin.

Example, using your email domain:

library OPAC domain: library.solanco.k12.pa.us

library admin domain: admin.solanco.k12.pa.us

Ensure these two domains are added to your domain server.

Once you can see the domains on your LAN or on the open Internet, edit the Apache config for the virtual hosts, which is either in /etc/apache2/sites-available/default or (rarely) /etc/apache2/httpd.conf.

In order to do this, you need to uncomment the "publicserver" portion of koha-conf.xml and then add a target in the 2nd koha-conf.xml. 

It will go from: 

<!-- <listen id="publicserver" >tcp:@:9999</listen> -->

to  

<listen id="publicserver" >tcp:@:9999</listen>

Then restart zebasrv and connect on the port specified (9999).

The target setup would be to the koha1 server (name or IP), port 9999, UTF-8 encoding.  The encoding is remarkable because most other MARC21 targets will use MARC-8 encoding.  By default our zebra provides UTF8.

Yes. You add another retrieval section which does that . You can use the 'marc' rule to convert from/to ISO2709. It might look as follows:

<retrievalinfo>
 <retrieval syntax="usmarc">
 <backend syntax="xml" name="dc">
  <xslt stylesheet="tst_record_conv.xsl"/>
  <marc inputcharset="utf-8" outputcharset="marc-8"
          inputformat="xml" outputformat="marc"/>
 </backend>
 </retrieval>
</retrievalinfo>

You should do a backup of your MySQL DB as a whole with 'mysqldump' command. More specifically, framework info are in those tables:

   marc_subfield_structure
   marc_tag_structure
   auth_subfield_structure
   auth_tag_structure