Organization Name: EOS International, Inc.
Date: Originally submitted 06/06/2000; reconfirmed Dec. 2001
Product Name & version: Q Series Version 2.02+
Respondent Name: Karen Anspach
MARC Holdings Format Survey for CONSER Task Force on Publication Patterns & Holdings, Task 3
1. Does your serial check-in software support the USMARC Holdings Format?
Yes, the Q Series Serials module fully supports the USMARCHoldings Format.
2. Does your serials check-in software support automatic issue prediction for receipt purposes?
Yes, once the publication pattern is entered in the Serial File Maintenance title level record the holdings pattern is built and the system uses it for prediction and issue receipt purposes.
2.A If so, are data elements used to provide prediction based on or similar to those provided in the USMARC Holdings Format?
Q Serials internally stores (and displays and allows editing of) the USMARC Holdings record and its tags including 853-855, 863-865,866-868, 876-878. No mapping is required.
3. Does your system store data elements at the level of detail anticipated by the USMARC Holdings Format, especially the full range of subfield content conveyed in the 85/x fields?
All of the subfields of the 85X fields are supported.
4. Is your system able to make use of the 85X $y (Regularity pattern) to anticipate normalized irregulars (or regular receipt exceptions) in making automatic issue prediction for serials receiving?
Yes, the $y is supported as is issue prediction on irregulars and exceptions for receiving.
4.A Is this support provided for a full range of the frequencies?
We support all of the frequencies defined in the Format $w plus additional frequencies including five/week, six/week, tri-quarterly, and a number of irregular types.
5. Does your system contain the capability to import MARC tagged holdings records?
Not at this time; planned enhancement.
5.A Please briefly describe how imported MARC-based holdings records with publication patterns are matched to specific serials control records in your system?
Although not supported at present we anticipate no difficulty in matching since we support the full USMARC Holdings record. We would expect to receive a compliant record during import.
6. Does your system have the capability to export MARC tagged holdings records?
Not at this time; planned enhancement.
7. Have users of your system successfully shared exported publication patterns with users of other serials systems in any of the following ways. Please specify all of the activities (a through d that your system has been able to support.
No activities at present.
a. Exchanged generic patterns for given serial frequencies with other users of your ILS software.
b. Exchanged generic patterns for given serial frequencies with users of other ILS systems.
c. Exchanged title-specific patterns with other users of your ILS system.
d. Exchanged title-specific patterns with users of other ILS systems.
8. Is it possible for an operator to view 85X/86X fields related to prediction in the Check-in system? In the holdings record? In the holdings record?
The operator can view the Holdings record and its 85X/86X tags in the Serials File Maintenance system. They can edit these tags in a labeled format in the Check-in system. Although they cannot not view them directly in Check-in they can simultaneously open the related holdings record (if they are authorized to do so) while keeping the Check-in function open.
8.A Can the operator view check-in and holdings information in both MARC-coded format and your system's proprietary format (if any) from all technical service screens?
Yes, as described above.
8.B Can an operator make changes to values in the 85X/86X coded fields that impact expected issue descriptions emanating from the ILS prediction engine?
Yes, if authorized to do so.
(This question examines the degree of integration between coded MARC holdings values and the operation of predictive check-in. For example, I should be able to add a subfield y (*$y om07") to the 853 field of my title to cover the omission of the month of July from prediction. In the truly integrated system envisioned in 7A, such an update to the coded 85X field would cause suppression of the month of July when predicting monthly serial receipts without having to engage in separate manipulation of the check-in software.)
9. Is the check-in system able to generate MARC holdings data automatically as a by-product of establishing automated issue prediction in support of serials check-in?
Yes, the 86X is built based on check-in activity.
10. Does your system support and predict alternate chronologies such as years based on Arabic calendars?
Alternate chronologies can be described as specified in the USMARC Holdings Format (85X $g,h,m), but check-in prediction is performed on the primary chronology in the tag. We currently support only the Gregorian calendar for prediction.
11. Can you support captions that incorporate diacritics?
Yes, if it a diacritic supported in our software (we are not Unicode compliant at this time).
11.A Does your software limit the length of captions? If so, what is the limit?
No limit on the length of captions.
12. What elements have you identified as necessary for serials publication patterns that appear to be missing from the current set of fields in the MARC holdings format? Please describe in detail.
It's been a while since I thought about this, but issues that come to mind are:
1. An additional element is needed to specify the start point (month/day) for a seasonal frequency (i.e. does Winter include Dec, Jan, Feb? Jan, Feb, Mar?)
2. Additional elements may be needed for full handling of multi-year patterns, for example, a publication issued three times over the course of two years.
3. In the USMARC Holdings Format, 863-865 page 7 there is an example under $l showing "semester." There are no elements to support this (what is the length, starting point of a semester?)