1.1. What is the Unnamed search that appears in My Selection Lists?

Confirmed Version: Evergreen 2.1

In the Acquisitions module of Evergreen, when performing a General Search that involves the specific type "line items & catalog records" the staff user working with the module will notice upon switching to the My Selection Lists page an additional pre-filled search titled "Unnamed" that appears to be filled with random items.

This "canned" search is created within /openils/var/web/js/ui/default/acq/search/unified.js by virtue of the function URIManager. In this portion of code, there are several different canned searches, however the one pertinent to this issue is pl, which refers to picklist.

When the staff member executes a search in General Search and specifically chooses line items & catalog records, a canned search is simultaneously created from the general results that is output to My Selection Lists as Unnamed. This canned search utilises the union of all items contained in the search results that were also created by the staff member running the general search.

Members with admin permissions may or may not notice items created by other staff connected to the Admin account.

This Unnamed search may serve as a starting point for a staff member creating a new pick list, and may be ignored or deleted at will.

Any future General Searches with the above parameter update and change the Unnamed search results. If Unnamed is deleted, a new search will re-create it.

This is a normal function of the Evergreen system.

2.1. How to add a merge profile

To add a merge profile, go to Cataloging MARC Batch Import/Export. You should see this:

You will notice at the top the "Edit Merge Overlay Profiles". Click on that. It will lead you to this:

As you can see, the org unit is selectable, but there are no profiles for my org unit yet. So click "New Merge Profile". A screen will pop up like this:

I will then enter "Blank" and select my org unit. Nothing else need be added. Click "Save". You will be returned to the previous screen. There you will observe the new profile:

We now return to the original screen by clicking "Import Records". Remember, once you return, you MUST click "Reload" to get a fresh copy of the contents of this screen. Then you will be able to select your new profile.

3.1. Support Procedures

To Submit a support issue via email: support@esilibrary.com -- When submitting an email ticket please remember to supply as much information as possible. This includes the steps taken to create the issue, what you were originally trying to do, and what actually happened after you took those steps. Usually the support staff try and recreate the issue so that they may fully understand the issue and resolve it quickly. If provided with enough information to recreate the problem, we can formulate a solution for you quickly and efficiently.

To submit or check on a request via the web portal: http://support.esilibrary.com -- When logging in for the first time, first select "Check on a Request." Enter your email address as shown above and click 'Retrieve password' to have a password generated and emailed to you. This password will allow you to check on all tickets submitted. To check on one specific request, enter the access key that can be found in the confirmation of submission email that you receive after a ticket is created. There is also a link in the confirmation email that will take you directly to the ticket to update or retrieve more information.

To Call in Urgent Support Issues: 1-877-OPEN-ILS Option 2. Our phone number can also be found on the support web portal should you need to find it quickly. Urgent issues include, but are not necessarily limited to: system down scenarios, complete loss of searching or circulation, or other complete loss of functionality scenarios.

3.2. Master Permissions List

4.1. Installation of the Evergreen Staff Client in Mac Environments

1. Fetch & install latest Xulrunner from here:

http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/1.9.2.10/runtimes/

2. Fetch the staff client build directory you want to run.  For example:

http://catalog.example.org/current-client-build.zip

3. Unpack the build directory somewhere, e.g. Desktop.

4. Open Terminal app and navigate to the directory where the "build" directory is sitting, then follow these steps (don't type the $'s):

$ cd ~/Desktop/
$ APPNAME=StaffClientKCLSProd
$  sudo rm -rf "/Applications/$APPNAME.app";
$ /Library/Frameworks/XUL.framework/xulrunner-bin --install-app build /Applications "$APPNAME.app";

You now have an application in your Applications folder called "StaffClientKCLSProd".  You can run it directly from there w/ the usual double-click. 

If you want to run the application with the console for debugging, continue like this:

$ cd "/Applications/$APPNAME.app/Contents/";
$ MacOS/xulrunner Resources/application.ini -console

To update, repeat steps 2-4, changing the APPNAME variable depending on which Evergreen server you want to talk to.  

4.2. Changing Workstation Name

In Linux, a hidden directory is provided of ~home/.openils/open_ils_staff_client/[random].default/chrome/.

The file you are looking for is ws_info. Delete this file, as it will be re-created when the next login occurs.

This login will force a new registration.

In Wine, change directory into the place your Evergreen Staff Client is located. This is usually ~home/.wine/drive_c/windows/profiles/[username]/Application\ Data/OpenILS/open_ils_staff_client/Profiles/[random].default/chrome/.

The file you are looking for is ws_info. Delete this file, as it will be re-created when the next login occurs.

This login will force a new registration.

On your computer, go into your "Documents and Settings" folder.

Go into the Application Data folder. If you don't see it, you'll need to go into Tools >> Folder Options >> View tab and turn on "Show hidden files and folders."

Go into the open_ils_staff_client folder.

Go into the Profiles folder.

At this point you will see another folder name. It will be a bunch of characters and letters followed by .default. Go into that folder.

Go into the chrome folder.

Now delete the file ws_info.

When you restart the staff client now, it should once again prompt you for your workstation name.

Uninstalling won't do it, since it hangs onto the config information.

5.1. Item was visible, but now I can't find it. Help!

In the event an item formerly visible in an OPAC seems to magically disappear, a simple question needs to be asked.

• Can the item be located in the staff client via a cataloger permission, or by barcode in the database?

If NO, then consult with your Cataloger on staff.

If YES, then consider the following:

Every item, depending on its point in the Status cycle has an ability to appear or not to appear via config.copy_status in the database.

First, determine your current item's status through asset.copy in the column status. The integer provided corresponds with config.copy_status.id.

The row provided by this id with have four columns. The last, opac_visible, will determine if your item can be viewed in the OPAC or not.

Once this status changes, say from Reservation Shelf to Available, then your item will once again appear in the OPAC.

6.1. Built in Self Check Basics 2.0.0.0

Q.) Is self checkout only accessible via a web browser or is there a client that can be installed?

7.1. Opportunistic and Targeted Holds with Staffing

7.2. Holds Boundaries

7.3. Holds target eligibility

For a copy to be considered for a hold, the library must be opened (IE: no entry in asset.org_unit_closed or closed in actor.hours_of_operation), the copy must be circulate=true, holdable=true, reference=false, deleted=false, the volume must be deleted=false, , the copy location must be holdable=true and circulate=true.

Attached diagram from Grace

7.4. Status of -1 when displaying hold for specific patron

When displaying the hold status for a specific item on the record of a specific patron library staff may observe the status code of -1 for a status code.

This means that the item, and the hold on that item are in an inconsistent state. An example of this is when a hold is placed on an item that is currently checked out by another patron, or otherwise unavailable for the fulfillment of the hold. This status will change once the item is checked in, or otherwise made available for the hold to be fulfilled.

Status of this item can be checked in the database table asset.copy_status by selecting for the captured copy.

This is a normal operation, and not an error.

8.1. Search Relevancy

Version:1.0 StartHTML:0000000167 EndHTML:0000006750 StartFragment:0000000457 EndFragment:0000006734

Search Relevancy Ranking

Summary

The base relevancy score is determined by the cover density of the searched terms. After this base score is determined, items may receive score bumps based on word order, matching on the first word, and exact matches depending on the type of search performed.

Gory Details

The core relevance is based on the average, across the containing metarecord, of the cover density of the stemmed version of the searched terms in all matching record. heh... here's an example:

Metarecord (MR) 1 contains records (REC) 5, 6 and 7, and MR 2 contains REC 8.

Keywords for:

• REC 5: "foo bar baz boo"

• REC 6: "fee bar fie fo baz"

• REC 7: "bar baz fee fo bar"

• REC 8: "harry potter and the cowboy bar rowling j k"

User searches for "bar", which matches all of the above keywords. We score the individual matches:

• REC 5: 0.9

• REC 6: 0.8 (keywords are longer, so cover density is lower)

• REC 7: 1.4 (matched twice, CD is higher)

• REC 8: 0.6

Then, we get the average per MR:

• MR 1 := AVG( 0.9, 0.8, 1.4 ) == 1.03

• MR 2 := AVG( 0.6 ) == 0.6

That provides a base to work with, which we then augment with bonuses in specific cases. Bonuses, or "relevance bumps", are supplied as a multiplier to the base CD relevance on a per-record basis. They cause a small effect when only one of many RECs within a MR gain that bonus, but when most RECs gain that bonus they help to push the "best" MRs to the top of the list.

For subject and author searches, because the indexed strings are so short, and word order basically irrelevant, there are not special bonuses and we use the base CD ranking for relevance ordering.

For keyword searches, word order is important, because people generally type in phrases as they would speak them and the indexed strings are long enough for order to be relevant. With that in mind, we provide a bonus multiplier of 1.2 (20%) to the rank of each matching record where all of the words (unstemmed, but stripped of diacritics and lower cased) in the user's query are in the same order as they are in the searched field.

For series title searching, word order is less important, but the first indexable, non-article word and the possibility of a complete match are important. A first-word match (the first indexable word in both the query and the searched string are the same) provides a bonus of 1.5 (50%). If the entire series title, minus leading articles, matches the entire user query then we provide a very big bonus of 200.

Title searches, which search all titles but series titles, combine the relevance bonuses from keyword (word order) and series (first word and whole string) to provide very good matching, especially on very short titles which would otherwise have little chance of coming to the top, even thought they are the most likely target of a short title query.

10.1. is not running notices

This page is based on the idea that your Evergreen server has an active mail service, and an outgoing SMTP server to connect to. If these are fulfilled, check the following:

• Verify that your definitions in action_trigger.event_definition are marked "true" rather than "false".
• Check /openils/bin for the existence of action_trigger_runner.pl
• Check /openils/conf for action_trigger_filters.json. It is possible that you may find a single file similar to this, but with the extension *.example. Copy this into a new file, minus the "example" suffix.
• Check crontab and verify an entry with action_trigger_runner.pl