**Note**
If you have the :ref:`HoldsSplitQueue` system preference
- set you will see the holds list split across different tables by either
+ set you will see the holds list split across different tables by either
pickup library, itemtype or both.
**Note**
It's behavior is controlled by the system preferences
:ref:`StaticHoldsQueueWeight <staticholdsqueueweight,-holdsqueueskipclosed-&-randomizeholdsqueueweight-label>`,
:ref:`RandomizeHoldsQueueWeight <staticholdsqueueweight,-holdsqueueskipclosed-&-randomizeholdsqueueweight-label>` and
-:ref:`UseTransportCostMatrix <usetransportcostmatrix-label>.
+:ref:`UseTransportCostMatrix <usetransportcostmatrix-label>`.
If you do not want all of your libraries to participate in the on-shelf
holds fulfillment process, you should list the libraries that \*do\*
will be requested to fulfill an on-shelf hold will be randomized each
time the list is regenerated.
-An alternative to static and randomized is using the
+An alternative to static and randomized is using the
:ref:`Tansport cost matrix <transport-cost-matrix-label>`.
-It takes precedence in controlling where holds are filled from and allows you
+It takes precedence in controlling where holds are filled from and allows you
to define the 'cost' of transport between any two libraries.
To use the Transport cost matrix simply set your UseTransportCostMatrix preference to 'Use'.
entered in the
:ref:`TransfersMaxDaysWarning` system
preference.
-
+
.. _article-requests-label:
Article requests
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Article requests are somewhat similar to holds, but are not requests
-for an item to check out. Instead, article requests are requests for a
-photocopy of a particular section of a book or an article from a serial
-issue. This is very common in academic libraries where researchers may
+Article requests are somewhat similar to holds, but are not requests
+for an item to check out. Instead, article requests are requests for a
+photocopy of a particular section of a book or an article from a serial
+issue. This is very common in academic libraries where researchers may
request a copy of a single article found in a journal.
.. _setting-up-article-requests-label:
Setting up article requests
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-First, enable your system preference for :ref:`ArticleRequests`.
+First, enable your system preference for :ref:`ArticleRequests`.
Set to 'Enable' patrons to place article requests.
-Next you will need to decide how your patrons will make requests,
+Next you will need to decide how your patrons will make requests,
either record only, item only, or both record and item level.
-You can set 3 different system preferences for mandatory fields to be filled
+You can set 3 different system preferences for mandatory fields to be filled
in depending on how your records are requested.
- :ref:`ArticleRequestsMandatoryFields`: make the following fields
following fields mandatory for records that are only record level
requestable
-Next you will want to go into your :ref:`circulation and fine rules
-matrix<circulation-and-fine-rules-label>` and select each rule for which
+Next you will want to go into your :ref:`circulation and fine rules
+matrix<circulation-and-fine-rules-label>` and select each rule for which
you want to allow requests.
-You can allow requests to be made at the record level, item level,
-yes (which means both) and no (which means no article requests may
+You can allow requests to be made at the record level, item level,
+yes (which means both) and no (which means no article requests may
be placed).
.. _placing-article-requests-label:
Now you can place requests on both the staff client and OPAC.
-In the staff client, on the record details page, you will see a
-'Request article' button at the top and an 'Article requests' tab
+In the staff client, on the record details page, you will see a
+'Request article' button at the top and an 'Article requests' tab
to the left. The two options lead to the same page.
|image1394|
-Just like a hold, you will be prompted to enter the patron's card
+Just like a hold, you will be prompted to enter the patron's card
number or name.
|image1395|
**Note**
- Remember, the mandatory fields are set through the three system
- preferences :ref:`ArticleRequestsMandatoryFields`,
- :ref:`ArticleRequestsMandatoryFieldsItemOnly`, and
+ Remember, the mandatory fields are set through the three system
+ preferences :ref:`ArticleRequestsMandatoryFields`,
+ :ref:`ArticleRequestsMandatoryFieldsItemOnly`, and
:ref:`ArticleRequestsMandatoryFieldsRecordOnly`.
If allowed, choose the specific item to request.
Then, click on 'Place request'.
-From the OPAC, patrons can place requests themselves either from the
-results list
+From the OPAC, patrons can place requests themselves either from the
+results list
|image1397|
|image1398|
-As with a hold, if the patron is not logged in, they will be
+As with a hold, if the patron is not logged in, they will be
asked to do so.
The form is the same as the one in the staff interface.
If allowed, the patron chan choose the specific item to request.
-From their acocunt, the patron will be able to follow the progress
+From their acocunt, the patron will be able to follow the progress
of their request from 'pending'
|image1400|
|image1401|
-The patron will also receive an email notification when the status of
+The patron will also receive an email notification when the status of
the request changes.
-Once the request is completed the patron will receive an email notification
+Once the request is completed the patron will receive an email notification
and the article request will no longer appear in their account.
Managing article requests
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Once the article request has been placed, staff will see new requests at
-the bottom of the home page on the staff client. (In the same location
+Once the article request has been placed, staff will see new requests at
+the bottom of the home page on the staff client. (In the same location
as tags, comments and modifications).
|image1402|
|image1403|
-The first step would be for a staff member to process the request, that moves
-the request to the processing tab and alerts other staff members that the
-request is in process. In the actions column, click on the dropdown menu and
+The first step would be for a staff member to process the request, that moves
+the request to the processing tab and alerts other staff members that the
+request is in process. In the actions column, click on the dropdown menu and
select 'Process request'. This will move the request to the processing tab.
|image1404|
Next staff will go to the shelf and make a copy of the requested article.
-Once that is complete, staff can print the article request slip (this can be
-customized in :ref:`notices and slips<notices-&-slips-label>` under AR\_SLIP)
-and staple or paper clip it to the article. In the actions column, you can
+Once that is complete, staff can print the article request slip (this can be
+customized in :ref:`notices and slips<notices-&-slips-label>` under AR\_SLIP)
+and staple or paper clip it to the article. In the actions column, you can
select the dropdown and select print slip.
-Finally, staff will select the complete article request from the actions
-dropdown menu which will send a notice to the patron who made the request
+Finally, staff will select the complete article request from the actions
+dropdown menu which will send a notice to the patron who made the request
letting them know the request is ready for pickup.
This removes the article request from the processing tab.
**Note**
- Actions can also be made in bulk by checking the boxes next to the
- requests to process or by clicking 'Select all', and choosing the new
+ Actions can also be made in bulk by checking the boxes next to the
+ requests to process or by clicking 'Select all', and choosing the new
status from the actions menu on top of the table.
|image1405|
Koha comes with a very basic self checkout module. To enable this module
you need to set the :ref:`WebBasedSelfCheck <webbasedselfcheck-label>` system
preference to 'Enable.' To use this module you have to log in as a
-:ref:`staff member <add-a-staff-patron-label>` with :ref:`self\_check
+:ref:`staff member <add-a-staff-patron-label>` with :ref:`self\_check
permissions <patron-permissions-label>`.
**Note**
::
- $(document).ready(function(){
+ $(document).ready(function(){
$("#login .btn").parent().after("<p><a href=\"http://YOUR_KOHA_OPAC_URL/cgi-bin/koha/sco/sco-main.pl\" target=\"_blank\">Self-Checkout</a></p>");
});
http://YOUR\_KOHA\_OPAC\_URL/cgi-bin/koha/sco/sco-main.pl
When on the self checkout page depending on your value in the
-:ref:`SelfCheckoutByLogin <selfcheckoutbylogin-label>` system preference
+:ref:`SelfCheckoutByLogin <selfcheckoutbylogin-label>` system preference
you will be asked to enter you cardnumber
|image592|
`SelfCheckInModule <selfscheckinmodule-label>` system preference to
'Enable'.
-Then, you will have to :ref:`create a patron <add-a-staff-patron-label>`
+Then, you will have to :ref:`create a patron <add-a-staff-patron-label>`
with the :ref:`self\_checkin\_module permission
<granular-self-check-permissions-label>`.
Create a :ref:`staff patron <add-a-staff-patron-label>` specifically for this
action so that you don't leave a real staff client logged into a
- computer all day. You can give this patron only the aforementionned
+ computer all day. You can give this patron only the aforementionned
permission so it cannot be used for anything else.
Once this is done, you can head over to the self check-in page:
|image1331|
-The patron will either scan the item's barcode, if the computer is
+The patron will either scan the item's barcode, if the computer is
attached to a barcode scanner, or type in their item's barcode in the box
and click 'Add' or press enter.
Most barcode scanners will automatically hit return after scanning.
-Once they have scanned or entered all their items' barcodes, they can
+Once they have scanned or entered all their items' barcodes, they can
click on the 'Check-in' button to return all the items at once.
**Important**
**Important**
- The self check-in module will not warn user if the item is late, if
- they have fines, if the item is on hold for someone else, or if they
+ The self check-in module will not warn user if the item is late, if
+ they have fines, if the item is on hold for someone else, or if they
have messages in their account.
|image1332|
**Note**
- Even if the patron doesn't click 'Finish' the item will still be checked
+ Even if the patron doesn't click 'Finish' the item will still be checked
in from their account.
-You can cutomize the look of your self check-in screens by using the
+You can cutomize the look of your self check-in screens by using the
:ref:`SelfCheckInUserCSS <selfcheckinusercss-label>` system preference or
the :ref:`SelfCheckInUserJS <selfcheckinuserjs-label>` system preference.
projects / kohadocs.git / commitdiff