Home » Posts tagged 'Aleph' (Page 4)

Tag Archives: Aleph

Help!

Problem? Check out the OLS Knowledge Base or open a ticket by emailing [email protected].

Why Does OneSearch Say We Have the Electronic Book?

We’re finding that the Merck Manual is in our results as an e-resource but we only have it in print. Why does this happen?

OneSearch interprets cataloging quite literally.

In this case, the MARC record contains this 856 field (full record):

85641 $uhttp://www.merck.com/pubs/mmanual%5Fhome2/

The second indicator has a mission-critical role (MARC 856 field @ LOC)

  • # – No information provided
  • 0 – Resource
  • 1 – Version of resource
  • 2 – Related resource
  • 8 – No display constant generated

OneSearch interprets all 2nd indicator values EXCEPT 2 as a version of the e-resource.   Since, in the case above, the 2nd indicator = 1, OneSearch reports that the e-resource is available.

If a link is NOT to an actual e-resource, but links to related content, the 2nd indicator should be a 2.

There is one exception.  Sometimes tables of contents and other materials are classified with 2nd indicator = 1, that is, a version of the resource.  In that case, in order to avoid OneSearch reporting that the e-resource is owned, both of the following must be true:

  • at least one of these note subfields must appear:  $3, $y, or $z
  • one of these note subfields must contain one of the following texts:
    • Table of contents (or Inhaltsverzeichnis or Table des matières or Indholdsfortegnelse)
    • Sample text
    • Publisher description (or Klappentext)
    • Book review
    • Contributor biographical information

The most common cataloging for these at CUNY

  • 85641$3 for “Table of contents” and “Sample text” notes
  • 85642$3 for “Publisher description” and “Book review” notes

Before reporting this type of issue to OLS, please check the record metadata with your cataloger.

If the reason for the problem is not obvious from the cataloging and a work order is opened, please copy the 856 field into the work order.

This post was originally published on 29 April 2015. We updated it on 18 August 2015 to reflect the latest information regarding the texts which do not indicate an e-book (for example, klappentext).

Automatic barcode loading and activation in Aleph

The beginning of the semester brings to the library thousands of new students who need to activate their barcodes in order to use library services. What if we told you the loading of active barcodes could be automated?

To begin, you need to first sit down and consider the details:

How frequently will barcodes be loaded into Aleph?

The answer to this question varies campus to campus. For example, the School of Professional Studies (SPS) tends to have a more frequent student turnover population, so an ongoing load of barcodes (such as weekly or monthly) has more advantage. A campus with a more traditional semester structure may be satisfied with loads at the start of the semester. However, even this merits discussion: Should the patron load include barcodes only once at the start of the semester or also include a second load two weeks later (for students registering late)? Should it be just the Spring and Fall, or also include the Summer?

Keep in mind that it would not be techncally possible for daily loads (due to the sheer size of our university). However, we already have weekly loads. Patron loading is scheduled in the off hours as as not to interfere with other batch processing, such as loading/updating bibliographic records, and various patron notices.

Who will be included in these loads?

The scope of the patron load should consider whether to have students loaded just at the start of their academic career at your institution, or loaded every year. Repeatedly loading students every semester will overwrite any changes manually made by staff over time. If someone gets a new ID card, their barcode will be corrected. The update of the barcodes cannot be blocked, so a patron’s barcode will revert to whatever is on record by the ID office.

Would freshmen be loaded both semesters or just when they are new? Would it include summer semester students, who may be taking only a single class? Should the load instead only include people who have been issued a new ID card within the past seven months (for incoming students as well as those being re-issued ID cards)?

What role do barcodes play in authentication on your campus?

The way barcodes are used for authentication varies campus to campus. Some libraries use it for access to electronic resources. Some security staff screen patrons for access based on the ID card.

Does the campus provide an ID with a unique barcode already printed on the card?

The barcode to be loaded should appear on the ID card. (How else will students or barcode readers know what their barcode is?) What if a person has multiple campus relationships (potentially two or more barcodes) and prefers a certain barcode to be their main, active barcode? How would a library manage a situation where someone has their campus’s barcode overwritten each semester (while the individual would rather retain a barcode from a different campus)? Staff will then have to create two accounts for a patron, and does your library wanting to take on manually maintaining the second account?


These considerations vary greatly across the CUNY libraries so please discuss them internally before beginning any work. When you’re ready to proceed, designate someone from library as the point person on this project. The next step will be for this person to open a work order with these specifications. This will be followed by contacting the various other groups involved, and continue to manage follow-up for this project. This includes dialog with the campus staff that manage barcode IDs and IT/CIS.

What is recommended?

The Office of Library Services recommends loading only incoming students (new freshmen and transfer students) OR people who have been issued new IDs within the past seven months. (Seven months is based on understanding the patron loading cycle details.) This will eliminate lines at service desks for 99% of new students. Over time, the majority of students will be covered. This would be a large increase over the current estimated 50% of a campus’s students having a barcode entered. Any subsequent changes would be a more rare exception, and, once corrected by staff, these changes/corrections would be preserved.

OLS has a separate request for changes pending to improve the way that patrons are imported from CUNYfirst. This includes loading patrons 7 to 10 days before the start of a semester, and improving the identification of a primary campus relationship (Home Library). Until this is in place, we do not have a way to only load barcodes when it is a patron’s home campus.

Why you should not remove a lost item record in Aleph

If you’re considering deleting a “lost” item from the catalog, consider this: removing a “lost” item record also removes its circulation history! This affects library circulation statistics and item counts. Item records also contain a “date last returned” field that can be used to identify items that no longer have relevant circulation history. This information is included in reports listing items with a specific Item Process Status (IPS).

When working with a lost item, you should instead mark it with an appropriate IPS. Lost items can be flagged as missing in transit, lost/paid, lost, withdrawn (“weeded”), or suppressed. Local technical services staff should determine which IPS is most appropriate to classify a particular item in the catalog.

To ensure that a lost item record is not removed by mistake, a new automated process was introduced with Aleph v21 so that when all lost charges are resolved/removed, any remaining loan record will eventually be removed. This also ensures that a lost item would not be listed “on loan” in the OPAC when it is actually lost or missing.

Find information about item process statuses, lost items, and more on the OLS Support Site.

Easily move permanent items into temporary Course Reserves

With our updated version of Aleph, adding items to Course Reserves is easier than ever. (Removing them is a breeze now, too.) Items that are cataloged as being in the “Stacks” or any other permanent collection (including permanent “Reserves”) can be quickly added to the Course Reserves module. This process eliminates the need to edit records in the Cataloging module, allowing a trained College Assistant or student worker to place previously-cataloged items into the temporary Course Reserves, automatically changing their location to “Course Reserves.”

Removing the items added through this process is automated and does not require any manual updates. On the 4th of each month, simply look in the Task Manager for a report named ‘course_resv_inactive_XX’ (where ‘XX’ is your 2-letter institution code). Items in this report will no longer be listed for this course in the OPAC or in OneSearch. When no longer needed, simply delete each item from its corresponding course(s), and the data clean-up is completely finished. A deleted item’s bibliographic record is automatically suppressed.

More details on Aleph Course Reserves can be found on the OLS Support Site.

Archive

April 2025
M T W T F S S
 123456
78910111213
14151617181920
21222324252627
282930