LAW-VUG Enhancement Recommendations
Created by Melody Lembke, Technical Services Librarian, Los Angeles County Law Library
Additional contributions from the LAW Special Interest Group of VUG
Fuller implementation of the MARC holdings fields, especially:
Component titles
Problem: Unable to link serials check-in components holdings with MFHD holdings for meaningful display in the OPAC. Unable to generate a display label from serials check-in to make the distinction in the OPAC as to what supplement or basic unit or index component belongs with its corresponding unit from the MFHD display. Desire to have better linking between component titles and OPAC display. Libraries can identify components by using $o in the MARC holdings field, but check in information should display associated with the correct component.
Description: The OPAC display from serials check-in for multi-component serials cannot be interpreted. Many serials have multiple components of the basic, supplementary, and/or index level. When these multiple check-in components are displayed in the OPAC, they are lumped together by component type with no linkage to their associated MFHD field (their specific field for records with multiple/duplicate 85x/86x). Additionally there is no ability to generate a display label from serials check-in to make the distinction in the OPAC as to what supplement or basic unit or index belongs with its corresponding unit from the MFHD display.
As currently designed, "component" in checkin is merely a quick retrieval mechanism within Acquisitions. Quick retrieval is desirable, but should not be a substitute for the ability to link to the desired component and a display name. Library's should be able to decide which holdings record (in the case of multiple holdings with different 844's), or to which element of a single holdings record the checked in item is related.
Examples: LACLL
[From L.A. County Law Library database] Labor relations reporter.
Here "Recent issues" refers to three separate parts of the reporter service; "Supplements" to another, yet since there is no correlation between the MFHD and no labels to designate what these parts are, the OPAC display is meaningless.
[From Syracuse University Law Library database].
Do a Title search = New York consolidated laws service in our OPAC. Display of "Current issues" and "Supplements" is meaningless since there are so many. The practice of law requires that the most up-to-date information be available; it is a critical role for law libraries. For patrons to not be able to determine that we have the (2001 May) v. 1-v. 2 of the quarterly update service is a DIS-service to our patrons! Serials check-in needs to accommodate the labeling of components.
Do a Title Search = Mertens Law of Federal Income Taxation in our OPAC. Here, the supplements have had labels attached (manually) in check-in to give some meaning to the OPAC display, to designate which supplemental component corresponds to which MFHD 866. Without adding these labels, the eight supplements from check-in would not be interpretable.
Do a Title Search = USCA in our OPAC. Select record # 1. Here, the supplements display form OPAC is misleading and labels would help.
Me too: LACLL
Implement $8 and 852 $t of MARC holdings
Problem: Libraries cannot use MARC holdings fields (MFHD field delimiter $8 and MFHD field 852 delimiter $t) to determine sequencing of holdings in the OPAC.
Description: When a record has multiple holdings either to reflect multiple locations or multiple copies in a single location, the MARC holdings format has a $8 field in the 852 that can be used to sort the holdings records in the way that the library wants. Currently Voyager sorts multiple locations in alpha order. If there are multiple holdings for a single location they are sorted in holdings record number order. See MARC 21 holdings 852 p.9 for examples.
In the same vein, the 852 field has a $t field that would allow the sequencing of copies for the same location. Or in law we have multiple holdings for same copy and location because of pieces like transfer binders or superseded volumes. All of these could be sequenced correctly if $8 were implemented. Endeavor claims that Voyager has implemented MARC holdings. This is true only in a very limited sense.
Example: [From L.A. County Law Library database] Currently because we cannot sort by the sequencing feature of $8 we label our Main library "AtMain" to get it to display first before our 9 branches. If staff do not watch the holdings record number, they may get copies out of order. Search Witkin California procedure 4th. Note the name of the Main library and the mis-sequenced copies.
Me too: LACLL
Better prediction of regular irregulars
Problem: Serials publication patterns do not have the ability to predict regular irregulars.
Description: I believe this is an enhancement that the serials group is also working on. We should be able to replicate patterns for a year without editing. From as simple as a biennial that is always issued in June and November, not June and December, to a serial that every year has both combined issues and skipped months. These are predictable, but the system does not have a way to predict a year and have it repeated.
Example: {I'll try and remember to give specific examples as I approve PO's for converted titles the next several weeks.}
Me too: LACLL
Complete authorities validation algorithm.
Jurisdiction validation. Any heading with a $z shows as a partial validation. Every $z shows as not authorized.
Problem: Create authority validation of jurisdiction subdivisions against 781 fields in 151 authority records and/or 151 fields. The way the system works now is unacceptable. This validation piece was promised during the Authority Task Force work, but never delivered.
Description: Most subject headings for law have a $z Jurisdiction in them. Subject authority validation does not validate the $z (unless the library were to create a complete string for every use of a heading $a$x$z, which would be ridiculous). While many jurisdictions would validate if the validation algorithm would match a $z against a 151 heading, indirect jurisdictions (i.e. most cities in the United States) would need to match against the 781 field in a 151 record. See MARC21 format for authority data, page 781 for examples. LC has said that they will begin using this field.
Example: Make sure under Options>Preferences>Validation the box for "Bypass authority validation" is NOT checked. Save any LACLL record to the database that has a $z in a subject heading.
Me too:
Complete validation of string
Problem: Authority validation only matches against $a. $a and $x, $y are not validated even when an authority record for that combination has been loaded into the system if a $z intervenes.
Description: An authority record may be in the system for $a $x, however, if the heading correctly in the bibliographic record is $a $z $x
Example: Save LACLL bib record 50925 to the database. Subject heading COUNTY SERVICES–CALIFORNIA–CONTRACTING OUT does not validate even though there is an authority record for County services$xContracting out in the database (55380)
Me too: LACLL
Display controls at the component level
Problem: Libraries have no ability to configure OPAC display of serials check-in for each component. Currently automatic display of serials check-in is set to display all.
Description: Libraries want to be able to determine and set display intervals for each component in serials check-in. Currently display of the serials check-in is set to display all. Libraries want the ability to set a display interval (e.g. display last # of receipts, or do not display any, i.e. display last 0 # of receipts, etc.) for each component in serials check-in. The automatic display interval should also be able to manually override.
Example Each component should be able to have a display interval set (e.g. display last # of receipts, to not display any = display last 0 # of receipts, etc). To display last receipt only = "Display latest 1 receipt." Operators also need to be able to override this on the history screen to accommodate extraneous receipts that are added in the check-in process, yet should not be counted as the "latest" receipt.
[From Wake Forest University Professional Center Library] This would be very helpful, as everyone who has to deal with newspapers and other dailies knows. I would like to add to this the capability of having a default setting for "Do Not display in OPAC." We check in our replacement volumes, reporter volumes, etc. so we have a record and we always have to turn the displays off after we update the MFHD.
[From Syracuse University Law Library] Our policy is to display the latest receipt only of predictable serials (e.g. Akron law review); to display latest 1 receipt of serials that have been by-passed due to the inability to predict their irregularity (e.g. NY Jurisprudence, 2d, CD-ROM); to display 0 of other by-passed (e.g. USCA, replacement volumes; CLS, repl. v.; North Carolina Digest, replacement volumes; NY Practice Series, bound volumes).
Me too: LACLL
Link from problem list to exact component.
Problem statement: Inability to access check-in components directly from the problem list. Problem list now has component name, but no click-able link to the component.
Description: As the system is currently designed, you can access an individual component's problem list directly from check-in (history -> problems history tab). However, if you start at the problems list, you cannot access the specific serials check-in directly from the problems list. You can view the components name in the problem list (there's a column for component), but you cannot open the components or check-in from there.
This is a problem since staff need to be able to access the specific check-in records directly from the problems list. This oversight seems to be a design flaw that prevents seamless integration of acquisitions/serials workflow. If you begin your problem resolution with the problems list, you cannot access the serials check-in directly. There is no click-able link from the component column on the problems list.
Examples: [specific to the Syracuse University Law Library database]. Start at "Order Maintenance" "Problems." Search by Mark Reason = System Claim. Select any Marked Issue. You can "click" to directly access a PO or an Invoice, but not to access the component in serials check-in. Although the component name is listed, there is no link.
Me too: LACLL
Link from purchase order to check-in component:
Problem statement: Inability to access check-in components directly from purchase order. As the system is currently designed, you can access the purchase order directly from the check-in screens ("view order" buttons). However, you cannot access serials check-in directly from the purchase order. You can view the components (from Line Item, Display, Components), but you cannot access the components or their check-in from there.
Description: This is a problem since staff need to be able to access associated check-in records directly from the PO. This oversight seems to be a design flaw that prevents seamless integration of acquisitions/serials workflow. If you begin your problem resolution with the purchase order, you cannot access the serials check-in directly. There is no "view check-in" or "view components" option from the PO.
Examples: [specific to the Syracuse University Law Library database] Retrieve and open purchase order # 2671. This PO has 18 line items on it. Of the 18 line items, no. 1-13 & no. 18 have components attached. In fact, of those 14 line items with components, there are a total of 54 components!!!!! Yes! :( Unfortunately, however, we cannot access the component's check-in information directly from here. In order to get to the check-in information, we need to open up serials check-in, search the components' titles, then proceed with our workflow
Me too: Oklahoma City University Law Library, Cornell Law Library,
Piece level information better integrated into the acquisitions module.
Problem: "Piece" field should be integrated (and indexed) into acquisitions module (invoice tab of purchase orders, payment history tab in serials history) and printed on voucher/check requests.
Description: In 2000 a piece field was added to the invoice to record what you are paying for. However, this field should be better integrated into other parts of the module. In the brief invoice list that displays from the invoice tab on the purchase order, the piece information should display so that the operator can quickly select the invoice in question. When the voucher/check request is printed the piece information should print as well, etc.
Example: In the brief invoice list that displays from the invoice tab on the purchase order, the piece information should display so that the operator can quickly select the invoice in question.
Me too: LACLL
Received status
Problem: Line item status of "Received complete" for subscription/standing order/etc. on purchase order in acquisitions is misleading.
Description: Visual statements in 2000 Voyager are misleading for the line item PO. Every standing order and serial gets a line item status of "Received complete" and this should not be the case.
Example: Look at any serial that has issues received but was not received complete on the PO. Previous versions showed this as Partial received which for any standing order or serial is a correct status.
Me too:
Copy anything
Problem: Operators cannot copy an invoice or a PO if it's from a previous fiscal year.
Description: Libraries should be able to create an invoice or PO by copying, regardless of fiscal year. A warning of the different fiscal year, but do not block creation!
Example: In law a book is received and invoiced in Acquisitions. Two years later a supplement shows up, but because the PO was received complete the PO did not roll over. The staff are sitting on the PO and say create invoice, but are blocked. Must then go and create and invoice and pull in the PO when they should be able to do the most efficient process.
Me too: Syracuse University College of Law, LACLL
Check in call number label without editing.
Problem: When producing a call number label as part of check-in, the system requires that you edit the call number each time a piece is checked-in, rather than saving the print form.
Description: The system should have the ability to save a print form of the call no. just as it does a display form. This would alleviate the necessity of editing the call no. each time a piece is checked in. The "print call number" should be able to be saved from cataloging as well. There is a "Display call number" version in the tables. There should be a print version as well. And even if the system attempts a better algorithm to "guess" at the format of the call number. Whatever is edited should be saved.
Example: There is not one of LACLL labels that can be printed without first editing. Take a look at California forms of pleading and practice (check in CAFOPAP). We have 13 copies of this bimonthly. Think how many times staff have to reformat this label!!!
Me too: [Wake Forest Professional center Library] YES! YES! YES!
Our check-in folks have to edit every label they print because Voyager isn't smart enough to remember how a label should be formatted. Surly, Endeavor could design the format algorithm that could correctly interpret an LC or Dewey call number and format for printing.
To this one I'd also like to add the following:
In the 2000.1.3 ACQ client, when the client seems to set a printer variable
when the print label screen that display what is to be printed is
pressed. You then format the label then press another "print
label" button. I suggest that Endeavor have the system set the
printer variable when the second "print label" button is pressed not
the first. These same things seem to occur when printing route slips. If you only have one local printer attached
it isn't a real problem. If you have two, as we do-- label printer, route
slip printer, it can cause real problems if the print job is not directed
to the right printer.
Webvoyage enhancements
Problem: Voyager does not allow for the hooking in of additional scripts to provide additional functionality.
Description: With all the new changes with the interface, I would like to suggest that Endeavor allow for the hooking in of additional scripts to provide additional functionality.
Example:
[Wake Forest Professional Center Library] We just brought up a new books script by Michael Doran of the University of Texas at Arlington. The script displays a page that mimics webvoyage. What would be nice is if the software provided hooks in the OPAC.ini file for the inclusion of extra tabs. If you wish to see what our's looks like, the URL is:
I can envision many other ways to use this capability.
Me Too: