Home » Posts tagged 'Aleph'

Tag Archives: Aleph

Help!

Problem? Check out the OLS Knowledge Base or open a ticket by emailing support@cuny-ols.libanswers.com.

Serials order record clean up

Libraries are now working on clean-up of Serials order records. An open serials record not attached to a Bibliographic record is not going to have a clear purpose when we eventually migrate. It is also unclear today for staff working in Aleph.

At one library (just before Thanksgiving 2017), we found 262 open serials orders. Of those, 154 orders are not attached to a Bibliographic record. The order creation dates range from 1994 to 2008. Setting those orders aside, this leaves 108 orders (41%) attached to a Bibliographic record where there is a clear journal title.

Now, we know that those ‘unattached’ orders were not all for budget transactions. We do not know which are the ones still being used as a dummy record.

For an order used for ordering / budget transactions purposes having an attached Bib record (with STA=SUPPRESSED) provides better identification. Since it is a suppressed record, never to be displayed to patrons. It would be more direct and maintainable to keep track of how the orders are intended to be used. Anytime staff look at a record to figure something out, people will want to naturally look at the title.

Consider the purely hypothetical record, with

STA	SUPPRESSED
245	Ebsco Melbourne Scholars Package

Without knowing anything else about this example, you already know what the record’s purpose is.

Also, the Bibliographic record should have a brief holdings and item record. The Item record should be set to Item Process Status = NA (not arrived), SU (suppressed), WD (withdrawn), or CA (Order Canceled). These are the Item Process Statuses that will result in the ‘Title’ being suppressed from patron view.

WD might be a good idea if you do not want the record to be migrated, but this would also depend on how you weed Bibliographic records that have these statuses. It will have an implication depending on which software we use to replace Aleph. If you do not weed by IPS, then it frees your hand in choosing an appropriate IPS.

Orders being closed should be marked as Order Status = ‘CLS,’ Invoice Status as ‘Complete,’ and depending on the type of order as ‘Arrived.’ One would also want to look at any related Subscription records. (No reason to show items as still being expected then they are not.)

Please contact OLS for help with specific questions.

Analytics: Circulation Activity Comparison Tool

In January, we introduced you to a CUNY OLS dashboard showing usage of our main library systems. That dashboard continues to be updated each month and we recently improved it, giving it in a new look and providing more school-specific detail.

Now we have a fun new offering: the Circulation Activity Comparison Tool!

Circulation Activity Comparison Tool
Circulation Activity Comparison Tool showing 2 fiscal years and highlighting loans

Features

  • Select Date Type to change the view from monthly to display by weekdays or by hours
  • Click on a single Event Type to view only one type of circulation event: Loans, Returns, or Requests
  • The title of each chart will change automatically to display the current selections for that chart
  • Remove all filter selections by clicking Reset at the left under the charts
  • Remove your last filter selection by clicking Undo in the same location
  • Includes data from Fiscal Years 2014, 2015, and 2016 (through March 2016)
  • Filter by a single SubLibrary or an entire Library (select all relevant SubLibraries in the drop-down selection box)
  • Click on the Loans line (or Returns or Requests) to display that line’s transaction counts (as we did in the above image)
  • Fiscal Year and SubLibrary selections are applied to one chart only
  • Select Date Type and other selections are applied to both charts

Using this tool, you can easily

  • Check your library’s peak hours for loans, returns, and requests
  • View your library’s traffic by day of the week
  • Compare 2 Fiscal Years by selecting different years on the left and right
  • Compare 2 Libraries (select all SubLibraries for one on the left and for another on the right)
  • Compare 2 SubLibraries
  • Mix and match

Acknowledgments

OLS is currently using Tableau Public’s free service to bring you this information. Check the Tableau Public Status page if you can’t access our OLS dashboards.

We owe a huge thank you to Jennifer Murray at SUNY Buffalo for sharing not only their Tableau dashboard but also the logic used to create it. This allowed us to build on the work they did and adapt it to our needs at CUNY.  In that same spirit, the logic we used appears below.

Technical Details

The data source is the Aleph Z35 Events table.

The selected fields are: Time Stamp (includes date, hour), Date (formatted), SubLibrary, and Circulation Event Type (groups 1 or more related events together)

Circulation Event Type Criteria

  • Loan: selected loan transactions
  • Return: return transactions
  • Requests: hold request transactions

Other Details

  • Limit to certain transaction types
  • Limit transaction dates to the 2 previous fiscal years plus the current fiscal year (July 2013-current date)
  • The order-by option is not required and merely makes the output easily scannable
  • The output is tab-delimited

SQL

set heading off
set pause off
set pagesize 0
set linesize 2900
set colsep |
select z35_time_stamp || chr(9) || substr( z35_event_date, 5, 2) || '/' || 
substr( z35_event_date, 7, 2) || '/' || substr( z35_event_date, 1, 4)
 || chr(9) || Z35_SUB_LIBRARY || chr(9) ||  ( CASE
WHEN z35_event_type IN ('50','56') THEN 'LOAN'
WHEN z35_event_type in ('61') THEN 'RETURN'
WHEN z35_event_type in ('71','72','73','74') THEN 'REQUEST'
END)
from xxx50.z35  -- where 'xxx' is your library prefix
where z35_event_type in ('50','56','61','71','72','73','74')
and z35_event_date > '20130630'
and z35_event_date < '20160401'
order by z35_time_stamp
;
exit

Changes to centrally-hosted EZproxy authentication

Recently, the Office of Library Services has made improvements to the way the centrally-hosted EZproxy servers handle authentication so that they restrict expired patrons from having access to electronic resources. This issue goes beyond a single group of patrons, such as high school students. This cuts across a variety of patron groups.

Centrally-hosted EZproxy authentication originally only checked whether a barcode was valid (i.e., the five-digit institution prefix). Subsequent improvements gave us the ability to check whether or not a patron had library privileges restricted due to overdue items or fines of $5 or more.

Until a couple of weeks ago, someone who graduated school or left their job at CUNY could have ongoing access to electronic resources for years. By remaining active in the Aleph catalog (e.g., with a minor fine), the patron’s barcode was deemed valid by the authentication process.

The recent changes to the way the centrally-hosted EZproxy servers authenticate users now allow us to also check the patron’s expiration date in his/her Aleph account.

Patrons that are loaded via the automated (CUNY-wide) batch loading process automatically receive global patron accounts. Barcode are needed for remote access to e-resources via the centrally-hosted EZproxy instances. Some libraries add them manually while others add them via a batch process.

Circulation staff are trained in-house about how to manually create local patron accounts. Depending on how staff set up these account, they can be given a variety of different privilege levels, including remote access to electronic resources.

For more details on new patron registration, please speak with your Access Services Librarian. If you have questions about patrons’ remote access to e-resources, please consult with your E-Resources Librarian.

Any remaining questions, please do not hesitate to contact OLS.

Aleph alerts that what once was lost now is found

Did you know? The Aleph GUI can notify Access Services staff when patrons check out an item with an incorrect item processing status (IPS). Let Aleph do more to help patrons have an accurate description of an item’s true status!

When a missing item is labeled as “Missing” or “Lost” (IPS = LO, MI, MT, or SE), it may later be found. The Aleph GUI can display an alert message during check out (or CLICs processing) that the IPS should be corrected. (Aleph will then remove the IPS.)

To enable this on-screen notification, please make a change to the following file on your desktop PC:

C:\Aleph21Prod\Circ\tab\circ.ini

In the “General” section, add the following lines:

[General]
DatesDefaultSubLibrary=[MAIN SUBLIBRARY, e.g., XX001]
UpdateDatesDefaultSubLibrary=Y
NotifyProcessStatus=Y

For more details, please see the OLS Support Site for the Aleph client installation instructions (see step 19-G).

Archive

March 2024
M T W T F S S
 123
45678910
11121314151617
18192021222324
25262728293031