open text collections server & open text library management … text collections... · 2013....

Open Text Collections Server & Open Text Library Management Release Notes Version 10.3 08/16/2010

2 | Open Text Collections Server & Library Management Release Notes

Contents 1 Introduction .................................................................................................... 3

1.1 Release Notes Revision History ...................................................................... 3 2 About Collections Server .............................................................................. 4

2.1 New Features for Collections Server 10.3 ....................................................... 4 2.2 Collections Server 10.3 Application Toolkits .................................................. 10 2.3 Cautions/Warnings ......................................................................................... 12 2.4 Deprecated Features/Modules ...................................................................... 12

3 About Library Management ........................................................................ 14 3.1 New Features for Library Management 10.3 ................................................. 14 3.2 Deprecated Features ..................................................................................... 18

4 Packaging and Documentation .................................................................. 19 4.1 Documentation Errata .................................................................................... 19

5 Supported Environments ............................................................................ 20 6 Installation and Upgrade Notes .................................................................. 21

6.1 Upgrade Notes ............................................................................................... 21 6.2 Migrating to Collections Server 10.3 .............................................................. 21 6.3 Critical Patches .............................................................................................. 21

7 Fixed Issues.................................................................................................. 22 7.1 Issues Fixed in Collections Server 10.3 ......................................................... 22 7.2 Issues Fixed in Library Management 10.3 ..................................................... 27

8 Known Issues ............................................................................................... 30 8.1 Localization error (Library Management – French)........................................ 30 8.2 ODBC Driver (Windows Server 2008 R2) ...................................................... 30

9 Contact Information ..................................................................................... 31


1 Introduction These Release Notes describe new features, updates and last minute changes in Open Text Collections Server 10.3 and Open Text Library Management 10.3.

Collections Server 10.3 provides the core database and collection management service for Sun Solaris, IBM AIX, HP HP-UX, Microsoft Windows, OpenVMS, and Linux (Red Hat and SuSE). Library Management 10.3 is a specialized solution for managing library collections that is built on the core collection management service.

In order to install Version 10.3, you must have new authorization keys. If you do not have keys for your software you can request them by contacting your local Open Text support organization.

Open Text recommends that you read these Release Notes in conjunction with the documentation included with the software package. Library Management customers should read all sections. Collections Server customers can skip Section 3 – About Library Management and Section 7.2 – Issues Fixed in Library Management 10.3. If any conflicts exist, the Release Notes supersede the other documentation.

Open Text also recommends that you check the Open Text Knowledge Center (https://knowledge.opentext.com/) for any patches or documentation updates that may have been posted after the initial release of Collections Server 10.3 and Library Management 10.3

1.1 Release Notes Revision History

Topic Modifications Revision Number

All Initial version 0

8.1 Localization issue Edit thesaurus relation name

1 (08/16/2010)

8.2 ODBC Driver Program to search/edit ODBC Driver Data Sources

1 (08/16/2010)

https://knowledge.opentext.com/�



2 About Collections Server Collections Server (formerly Livelink ECM – Collections Server or BASIS) provides high-performance search and precise retrieval to increase the value and utility of managed research and archival collections. Collections Server excels at managing hybrid content consisting of documents and descriptive metadata with unified indexes to facilitate search across both types. Users of specialized content with dense subject-matter and complex terminology also benefit from rigorous data integrity standards as well as search assistants like thesaurus browsing, faceted navigation and result clustering.

2.1 New Features for Collections Server 10.3

Consistent with product priorities established through market analysis and customer surveys, Collections Server 10.3 incorporates new features to enhance information retrieval, collection management, and administration capabilities.

Collections Server 10.3 is a feature release that includes product enhancements gleaned from Product Planning Surveys and customer Requests for System Modification (RSMs) as well as code revisions to address User Reported Problems (URPs). Refer to Section 7.1 – Issues Fixed in Collections Server 10.3 for the specific revisions.

2.1.1 Default test for a multi-field index (MFI)

In order to simplify end-user access to the proximity and phrase search operations the database administrator can define the DEFAULT_TEST parameter for an MFI. Instead of being limited to the INCludes or EQual operators, multi-field indexes made up of fields that support phrase search can be searched with a phrase operator by default to improve search results and minimize syntax errors. RSM_No: 18324

The database administrator can define the DEFAULT_TEST parameter in the INDEX DDL statement for the MFI; on DMDBA Screen 81 (index) pages 2 ($CONCATENATE MFI) and Screen 3 ($COMBINE MFI).

2.1.2 Enhance concept mining

Concept mining was introduced in Collections Server 10.2 and is a powerful tool to make your collection more accessible, useful, and consequently more valuable. Concept mining refers to the automatic extraction of concepts (keywords, phrases, personal names, company names, etc.) that are significant in a set of documents or an entire collection. It gives users a context for their search results and an overview of the important topics, companies, people, and other concepts in the content without having to read any of the documents themselves. The most common application of the technology is to analyze document text on import, extract frequently occurring concepts, and store them in


special fields that have been defined to receive them. The result is automatic cataloging during document check-in. The concept-mining technology also assigns statistical weights to terms which are used by the result set clustering feature. Concept mining includes these new features:

• Support for concept extraction when using the HVU IMPORT/FORM/DOC command in addition to IMPORT/DOC. The capability extends the formats that can be used to import and extract concepts to include all forms that handle text-image fields: STREAM, DELIMITED, STANDARD, FREE, FREEB.

• Significant enhancements to the phrase extraction capabilities of concept mining: ability to define concept keywords as a single term, a 2-word or a 3-word phrase; enable stop phrases; and improve handling of the individual words that make up a phrase.

• Implement a custom word stemmer to improve term selection for specific content domains or alternate languages. The release includes template C files with the stemming interface functions to help you integrate optional stemming programs.

• Integrate with Thesaurus so that terms and relationships can be used to elaborate concept extraction.

Integrating a Thesaurus with a concept type lets you use your thesaurus in several different ways to improve the precision of term selection. Here are some of the possibilities:

• Use thesaurus relations to select the preferred form for topics or names.

If your thesaurus includes cross-references (Use/Use For, Abbreviation/Abbreviation For) the concept filter will use the lead term to populate the Topic field. For example: ECM is the abbreviation for Enterprise Content Management. In an article about Open Text there are references to both the short (ECM) and the long (Enterprise Content Management) form. The extraction filter selects Enterprise Content Management to add to the Topic field because it is the preferred form and aggregates the term weight totals of both forms to more accurately represent the importance of the concept in the article. Without thesaurus integration the redundant terms are selected with lower individual weight values.

• Use thesaurus relations to categorize content by theme.

If your collection uses a hierarchical thesaurus, concept mining can use the broad and narrow term relationships during concept extraction to refine the quality of terms selected and apply more relevant term weights. For example:

LT = FRUIT Lead Term

NT = APPLE Narrow Term


NT = CHERRY Narrow Term

NT = PEACH Narrow Term

RT = ORCHARD Related Term

For this thesaurus illustration, the concepts APPLE, PEACH and ORCHARD appear in a document. Only the lead-term, FRUIT, is extracted as the concept although APPLE, PEACH and ORCHARD (the subordinate-terms) all contribute to the Concept Weight assigned to the concept FRUIT. Configured in this way you can define a concept field to store only the primary topical themes (i.e. Top Terms) and simplify browsing and navigation.

• Thesaurus integration to fully direct term selection.

A new configuration option directs the concept mining filters to extract ONLY those terms defined as Lead Terms in the thesaurus. For example, if you have a thesaurus with the names of products your company makes, this concept category bypasses the statistical analysis so it disregards any other product names or keywords. Term selection fully determined by values in the thesaurus file is also useful with department or agency names, places, or any extensive legal list.

2.1.3 Limit result set clustering

Improve the flexibility of the cluster operation to accommodate more options. Administrators of very large databases want to be able to control performance by limiting the size of result-set that a user can cluster. The NR_MEMBERS parameter for the FQM CLUSTER command limits the number of result-set members to cluster. Specifying NR_MEMBERS=500 when clustering a result set containing 5000 members will analyze and group the first 500 members only.

2.1.4 Expand the capabilities for restructuring indexes

Organizations with very large databases requested enhancements to the DMR utility to improve performance for database and index restructuring. Smaller applications also benefit from the flexibility to perform tasks in more discrete steps.

• An individual index partition can be processed using DMR actions: DROP, CREATE, VERIFY_INDEX, SHOW. Status changes to a partition also are respected by DMHVU; document import populates only the index partitions that are available. If an index is partially created/dropped it will be skipped but can be separately reconciled via DMR.

• Several indexes or index partitions in one database can be manipulated at the same time using DMR actions: DROP, CREATE, VERIFY_INDEX, SHOW. RSM_No: 18330.


2.1.5 Improve treatment of unique indexes

Resolve several anomalies in the DMDBA module relating to managing unique fields and unique indexes. Restrictions on several changes no longer require a complete database restructure.

• Field statement: changing UNIQUE=YES to UNIQUE=NO is the less restrictive RES-INDEX; No-to-Yes remains RES-N/A. RSM_No: 18288

• Index statement: changing from TYPE=UNIQUE is the less restrictive RES-INDEX; changing to TYPE=UNIQUE remains RES-N/A.

2.1.6 Web Administrator & Web User

The user interfaces for Web Administrator and Web User have undergone a complete makeover. The Admin drop down list is replaced by a Main Menu ribbon which organizes all tasks. Clicking your mouse on a menu choice will reveal more options.

The “My Site_ID” display (circled in red below) is also new in Web Administrator. The web-based tool lets you manage multiple Collections Server instances in one place; this simple addition makes it easier for administrators to keep track of where they are.

Web Administrator 10.3 – Kernel List page

This new user experience gives you a glimpse of what is to come in Webtop 10.3 which features the same modern look and feel intended to make actions more visible and customizations easier. Webtop 10.3 will also provide new ways to


navigate a collection and manipulate a result set using faceted navigation, document clustering, and expanded thesaurus navigation.

2.1.7 Administration - General

Collections Server 10.3 includes many general revisions to improve performance, correct defects, and facilitate database and user administration.

• Capitalize on primary-key values when performing subsequent FIND operations against a result set. The optimization is especially effective with a Joined result set and improved query performance 12-30%.

• Improve performance on frequently used character comparison functions to be less CPU-intensive. The change impacts various features and propagates across the entire FIND command and may improve results by up to 45%.

2.1.8 Enhance demonstration environment

While every BASIS Administrator has come to love the TOUR and DTDEMO databases, times have changed and those examples hardly represent the extensive capabilities available in Collections Server 10.3. In order to more effectively demonstrate the differentiation as well as provide customer DBAs with a laboratory where they can experiment with new features or find examples (i.e. best practices), the release includes 3 new sample databases. New demo databases expose more features and provide more content to work with in a test environment. These features include:

• Hybrid data sets – content includes a combination of descriptive metadata with full text. Concept mining is activated to provide a combination of human assigned and system-generated content.

• Indexing – includes examples of different indexing options entire_value=yes, MFIs, break & sub-break lists, etc.

• Concept mining – includes several concept types (keyword/phrase, company and/or name).

• Thesaurus – for validation and search on structured field(s) and search assistance on text field. The concept mining thesaurus options are also demonstrated.

Meet the new databases:

• Medical Research database (MEDRES) – this database is a collection of articles related to infectious diseases from the U.S. Centers for Disease Control and Prevention (CDC) and the World Health Organization (WHO). Concept extraction (automatic cataloging) is applied to the article content so the metadata includes generated Keyword Concepts, Phrase Concepts, Company Concepts, and Person Concepts each with


associated weight. Configuration settings have been refined to learn from the content and optimize extracted values by taking advantage of features like stop words and statistical settings.

MEDRES has a demonstration thesaurus of hierarchical medical terms (with apologies to the National Library of Medicine’s Medical Subject Headings). Indexing options on the Phrase Concepts field feature term switching. The thesaurus also will be very useful to illustrate the new thesaurus informative messages and browse navigation features coming in Webtop 10.3.

• U.S. Supreme Court Opinions database (SCOPIN) – is a collection of opinions handed down by the U.S. Supreme Court. Fewer new features are included in this database so it provides a generic collection of content and a playground for experimenting with different options.

• Canadian Supreme Court (SCJUDGE) – is a collection, in French, of judgments handed down by the Canadian Supreme Court. Fewer new features are included in this database so it provides a generic collection of content and a playground for experimenting with different options.

Note: The new databases are document collections and therefore larger than the original demonstration databases: MEDRES (400MB), SCOPIN (260MB) and SCJUDGE (300MB). If you wish to minimize the install footprint you can choose a Custom Install and select the databases separately.


2.2 Collections Server 10.3 Application Toolkits

In order to provide solutions that may be deployed in a wide variety of Collections Server implementations Open Text will offer several do-it-yourself toolkits in addition to Technical Tips (Tech Tips folder) currently available on the Knowledge Center. A toolkit may include documentation clarification, implementation recommendations, configuration instructions, code samples (ddls, procs, Web pages) and can provide a starting point or a complete demonstration implementation depending on your unique context.

2.2.1 Best Practices in Concept Mining (a whitepaper)

Coming Soon! Watch the Tech Tips folder on the Knowledge Center.

Based on the experience we gathered while experimenting with the new demonstration databases and designing customer applications this ‘how to’ document offers guidance, suggestions, and things to consider gathered from the lessons learned. The preliminary table of contents:

• Getting Started

• Tuning // Training the filters

• Conceptualizing your database

• Integrating with thesaurus

• Indexing and concepts

• Implementing in Library Management

• Stemming tools and other advanced topics

• Maintaining a conceptualized application

• Other uses for concept mining

2.2.2 Current Awareness Toolkit

The Current Awareness is a method of informing users about new or newly important resources on topics of interest to them. The Toolkit provides a configurable solution that you can easily apply to your existing collections.

The Current Awareness Toolkit lets you configure automatic email alerts from your collection based on user-interest profiles. It provides:

https://knowledge.opentext.com/knowledge/llisapi.dll/open/15859144�



• Aware database – to manage details about subscribers, the current awareness enabled collection, your email server information and the form of email notifications.

• Aware thesaurus database – to manage the fieldnames and field labels in your collection that are used for saved searches in user profiles.

• Custom Webtop pages allow users to add/edit search preferences and contact details for their Aware profile.

• Sample Command procedures to process the user queries and generate email notices.

• Installation and configuration documentation along with a self-extracting software image.

2.2.3 Webtop Directory Service Integration Toolkit

Coming Soon! Watch the Tech Tips folder on the Knowledge Center.

The Webtop Directory Service Integration Toolkit enables Single Sign-on authentication in organizations that do not have Web server authentication or a third party web access management system. Rather than a synchronization utility, this solution authenticates users directly against the enterprise directory.

The architecture takes advantage of Tomcat and the Java Name and Directory Interface (JNDI), a standard API for accessing directory services like LDAP. The toolkit includes sample configuration files (e.g. server.xml, web.xml), Java class files, and documentation to help you deploy the solution in your environment.

The toolkit achieves two important objectives: to let end-users access collections with their enterprise username and password; and to reduce the need for exhaustive maintenance of the Collections Server Authority Database (ADB).

While there is considerable interest in simplifying tasks associated with maintaining the ADB, there is little consensus about the real objectives. The Webtop Directory Service Integration Toolkit is one place to start while the discussions continue. You may share your user authentication challenges in the Libraries & Collections Community (Choose Forums) or by contacting the Product Manager.


http://communities.opentext.com/communities/livelink.exe/open/8089037�

mailto:[email protected]?subject=Authentication%20challenges�

mailto:[email protected]?subject=Authentication%20challenges�


2.3 Cautions/Warnings

MIME type Warning

Office 2007/2010 uses new and larger MIME types. If in any of your databases you have defined a MIMETYPE field to manage the MIME type of the document stored be sure that the minimum size of this field is set to 127 characters.

2.4 Deprecated Features/Modules

As we refine the Collections Server product portfolio, it becomes necessary from time to time to discontinue specific product features or modules for strategic and economic reasons. Open Text’s Product Retirement Policy is designed to equip product stakeholders with sufficient advance notice of changes to product availability, support status and replacement options in order to promote local planning. Whenever possible, support status changes are announced in Release Notes at least one release prior to the pending change.

More information regarding support levels is available in the Support Policies folder on the Open Text Knowledge Center.

Please note the following changes.

2.4.1 Supplemental Tools

Supplemental Tools for Version 10.3 are available for download from the Open Text Knowledge Center in the Collections Server Patches folder. The Supplemental Tools are retired products and are no longer tested or supported. While the original retirement plan stipulated that the tools be permanently withdrawn in 2005, Open Text has deferred the full product withdrawal. In recognition of our large and prestigious customers who still use these tools, Open Text will invest commercially reasonable effort to build and test the supplemental tools to verify compatibility with subsequent releases and current operating system levels. Some or all of the tools may be withdrawn from any release when it is no longer possible to cost-effectively sustain them. Customers building new applications should use the newer interface technology like JDBC and Webtop.

The Supplemental Tools include:

• Fortran Pre-Compiler (FPC)

• Cobol Pre-Compiler (CPC)

• Document Handler Interface (DHI)




• BASIS Report Writer (RW), including DMDDBR

• BASIS Command Language (BCL)


3 About Library Management Open Text Library Management (formerly Livelink ECM - Library Management or Techlib) is a fully Web-based, integrated library system to manage library resources –including traditional print, media, and digital collections – and automate daily library operations. It provides the tools necessary to meet the rapidly changing requirements of the digital library.

3.1 New Features for Library Management 10.3

Library Management 10.3 includes product enhancements gleaned from Product Planning Surveys and customer Requests for System Modification (RSMs) as well as code revisions to address User Reported Problems (URPs). Refer to Section 7.2 – Issues Fixed in Library Management 10.3 for the specific revisions.

The new features in Library Management 10.3 focus on two recurring themes: make the library collections more useful for end-users and; make administrative tasks easier for library staff.

System enhancements and changes appear in the following areas of Library Management 10.3.

3.1.1 Implement concept mining for digital content

Concept mining was added to Collections Server 10.2 and refined in Version 10.3. The feature can now be configured for Library Management so libraries with digital content can take advantage of this automatic cataloging capability

Concept mining identifies the organizations, people and topical themes that are significant in your digital collections. An excellent way to supplement manual cataloging to relieve library staff, the feature will also provide a foundation for advanced search operations for end users.

The concept filters are fully configured to select keywords, companies, and names based on a general purpose frequency-based algorithm. Implementation options let you “teach” the mining filter about your content. You can explicitly define keywords, people, or products that are most important in your collection. You can even use your authority file to influence term selection.

Details of concept mining in Library Management:

• When enabled, the concept mining filter scans documents attached to Catalog records to extract keywords, company names and/or personal names. Concepts can be mined from an import file or the text field of existing documents. The selected terms are automatically stored in new fields in the Document record.


• Each site decides whether or not to activate conceptualization and configures which fields (keyword, company, and person) to extract, populate, and index. The release package includes a database definition file (concept.ddl) with the standard implementation.

• Concept mining is fully enabled for new sites but can be reconfigured or deactivated.

To learn more about concept mining see Section 2.1.2 – Enhance Concept Mining and watch for the forthcoming white paper described in Section 2.2.1 – Best Practices in Concept Mining.

3.1.2 Facilitate Authority Control (Cataloging)

There are several extensions to Authority Control that make it easier to deal with exceptions field.

• Include ADD and UPDATE actions on the Authority result display from a Thesaurus Update search.

• A new report that searches the catalog to find every record with details in the exceptions fields (Author Exceptions, Conference Exceptions, Subject Exceptions, etc.). The list can be used to adjust content, either by editing the Catalog record to eliminate an invalid term, or by adding terms to the Authority File (thesaurus).

• In addition to generating a simple list of exceptions, Reconcile Thesaurus Exceptions, includes a processing step to Update Catalog records. After using the list to update thesaurus terms you need to run the report again to refresh the exceptions fields. By selecting a check box on the Report Parameter page, all catalog records with exceptions field(s) are revalidated; if the term now exists in the thesaurus the exception field is cleared. There is no output from the processing step.

3.1.3 Other Cataloging Enhancements

• Provide a new parameter on the Shelf List Report so library staff can select the Material Type from the Shelf List report to get a listing of only Books, or just the DVDs. RSM_No: 18317

• Enhance the Electronic location field in the Catalog record to accommodate text descriptions (e.g. Annual Report) as well as hypertext. Only the hypertext displays as a link. RSM: 18220

• Add a Download icon on the Document Display page to launch the appropriate viewer (e.g. Adobe Reader or Microsoft Word) so that library staff can view digital content in its native form. RSM: 18212.


• Add the standard ‘Send Output log to’ options to the MARC Import log summary page so that the import results can be retained and reviewed. RSM: 18159

• Include new serials titles along with new books on the New Copy List. The implicit requirement for a Copy record previously excluded newly acquired serials along with the books. The output was restricted by using the COPY.ADD_DT which further eliminates Serials.

3.1.4 Circulation features

• Provide a “current patron” link similar to the current order links in Acquisitions. To streamline the patron registration process after adding a patron at Check Out, you can use the link to display or edit the newly added Patron details. RSM: 18206

• Add Renew Limit to the Profile record for more flexibility in defining the number of times that an item may be renewed. The library policy can use Material Type, Collection Type, or Patron Type to determine the limits. RSM: 18310

• Improve Hold processing to attend to items that have already been placed on Hold when the Hold is cancelled. A message alerts the operator to check-in the item again to update its status. RSM: 18322

3.1.5 Serials features

• Provide a report of journal issues (Prediction records) by status. The Issues by Status report helps monitor Overdue, Missing or Claimed issues. The listing is especially useful as guide for Serials Receiving in order to issue a manual claim for overdue issues. RSM: 18338

• Updates to the Add Subscription form:

o Retains user input on the form when the Vendor Search action is selected.

o Revise the Add Vendor action to respect the user’s permissions as defined in the User Security record.

• Allow issues to be predicted for titles that do not have enumeration. Libraries need the ability to predict issues without specifying volume and issue details. Issues without enumeration are distinguished by their issue date. RSM: 18237


3.1.6 Acquisitions features

• On the Request form, the Add Vendor action now respects the user’s permissions as defined in the User Security record.

• Allow actual payment amounts to be allocated across multiple funds; previously fund distribution was specified as a percentage. RSM_No: 18192

• Provide an Add copy action at Acquisitions Receiving. An Add copy icon appears on the Receiving page when the user is authorized to add copies. After you add a copy in receiving hold records are created if there is patron hold information. If the notify type is send item the copy is checked out to the first patron.

3.1.7 Administration Features

Allow staff administrator to define a default module for any user so that when they log-in they will go directly to the module they use most often. This field can be set to any module or left blank.

3.1.8 Report Features

• Update reporting to use Jasper Reports 3.5 libraries.

Add options to Report parameter pages to accommodate Office 2007/2010 documents. Due to the new file format extensions used in Office 2007/2010 (e.g. docx for Word) the reports could not open the output file generated. You need to choose the version of MS Word that you use. The new options are: MS Word 2007 (or later); MS Word 2003 (or prior).

• Enhance the Patron Notifications to include links to the OPAC. The patron notice email includes URL references to every title so the patron can click on it and go directly to the OPAC result to view/navigate and request titles. There is a new field in the System Parameter record used to store the OPAC http header in order to form appropriate URL.

• Allow library staff running reports to enter a custom message that will be used in the body of the email when they send a report as a PDF attachment. Use the input box on the Report parameter page to enter the email body for attachments; if no content is provided the notice uses a generic message.


3.2 Deprecated Features

As we refine the Libraries and Collections product portfolio, it becomes necessary from time to time to discontinue specific product modules or features for strategic and economic reasons. Open Text’s Product Retirement Policy is designed to equip product stakeholders with sufficient advance notice of changes to product availability, support status and replacement options in order to promote local planning. Whenever possible support status changes are announced in Release Notes at least one release prior. Please note the following change:

• Following the introduction of JasperReports we announced withdrawal of support for Crystal Reports. The Crystal Reports run time libraries and the .rpt files are not delivered in Library Management 10.3.

• The following reports have been removed from this release: Check-out Slips, Hold Slips, Mailing Labels, Management Statistics by Patron Type, Hold Not Available, and Administration Setup. These reports are rarely used and so eliminated based on the results of the Library Management Report Survey (April 2007).




4 Packaging and Documentation Collections Server 10.3 and Library Management 10.3 are available from the Collections Server Downloads folder on the Open Text Knowledge Center. Each product (Collections Server, Library Management, Webtop, etc.) is in a separate folder. Each folder includes the software for the different platforms in ISO-9660 format.

Before you visit the download site you must still place an upgrade order for the current version by contacting [email protected] or your local support agency. When you request the release, your permissions to the Knowledge Center will be updated to authorize you to the download folders for all product versions you have purchased. You will receive two emails: one with your Knowledge Center credentials; and one with the software license keys. If you prefer a physical delivery you may request a CD.

The Libraries and Collections products documentation can be downloaded in PDF format from the Collections Server and Library Management Documentation folder of the Open Text Knowledge Center. All product documentation is also included on the software image. These Release Notes may be revised at anytime to clarify topics or update known issues. Always check for a revision on the Knowledge Center to get the latest information. Before installing any software, you should download and review all of the release documentation.

On Windows, the installation program launches an html page with links to let you navigate to the documentation directories. On the other platforms you can review the readme or use a browser to open Index.html to access the documentation on the software image.

The latest version of the Online Documentation Database (BOLD) is delivered on the software image. The BOLD database is also accessible from the Collections Server and Library Management Documentation folder of the Open Text Knowledge Center. The Tech Tips subfolder includes useful informal, supplemental documentation and FAQs to clarify common customer issues.

4.1 Documentation Errata

No documentation errata at this time.


mailto:[email protected]�





5 Supported Environments The Collections Server 10.3 release is supported on the following server platforms:

• Microsoft Windows Server 2003 (R2), Windows Server 2008** (SP2 and R2)

• IBM AIX 5.3 – 6.1**

• HP-UX 11i v2 and 11i v3**

• OpenVMS 7.3-2 and 8.3

• Sun (SPARC) Solaris 9 and 10

• Red Hat (x86) Linux ESv5.0

• SuSE (x86) Linux ES 10

**New OS levels/Platforms since V10.2

Supported Web and application servers:

• Tomcat 6.0.26

• Java 2 Standard Edition Platform (J2SE) version 5

Supported Browsers :

• Microsoft Internet Explorer 7.x and 8.x

• Apache Firefox 3.5.x and 3.6.x

.


6 Installation and Upgrade Notes Collections Server and Library Management Installation Guides for each platform can be downloaded in PDF format from the Collections Server and Library Management Documentation folder of the Open Text Knowledge Center.

6.1 Upgrade Notes

Refer to the Installation Guide for all Upgrade Notes.

6.2 Migrating to Collections Server 10.3

There were substantial architectural changes between BASIS 9.1 and Collections Server 10 that necessitated a database migration. If you have upgraded to Collections Server 10.x, congratulations, we hope you are enjoying the improved scalability and usability. The move to Collections Server 10.3 is a standard upgrade. If you are running BASIS 9.1 or earlier, you will need to dump and reload your databases. However, you do not have to upgrade to Collections Server 10 first; you can go from BASIS 9.1 directly to Collections Server 10.3. You will find detailed migration procedures in the upgrade chapter of Installing Open Text Collections Server.

In order to minimize the impact to your applications, Global Services can help you plan your upgrade or migration. Open Text consultants are available to perform the entire migration for you or simply provide expert guidance. To learn more about consulting services contact your Account Manager or local support organization.

6.3 Critical Patches

No mandatory or critical patches at this time.




7 Fixed Issues The following tables summarize the User Reported Problems (URP), Requests for System Modification (RSM) and other issues that have been fixed via software Revision (REV) in this release.

7.1 Issues Fixed in Collections Server 10.3

MOD URP/

RSM REV Description

DBA 8531 Problem: DMDBA will not apply the definition of a view if the source record has fields with the conceptualize attributes if all such fields are not included in the view. Solution: Relaxed the requirement so that if one or more fields are missing, instead of failing the APPLY DMDBA accepts the definition but removes ADD and MOD privilege if need be.

DBA 8597 Problem: Improve DMDBA handling of a unique field/index. Solution: Revised DMDBA as follows: UNIQUE: Yes-to-No becomes the less restrictive RES-INDEX; No-to-Yes remains RES-N/A. TYPE: from-UNIQUE becomes the less restrictive RES-INDEX; to-UNIQUE remains RES-N/A. UNIQUE attributes are automatically assigned to the FIELD statement when the corresponding index is TYPE=UNIQUE. Optionally, the DBA may continue to maintain the FIELD parameters.

DMK 14626 8496 Problem: The Kernel reports SE 1542 (Reset EOI failed) when many users are active and one or more of those users has an update transaction in progress. Solution: Adjusted the routines that clear the pages of a transaction work file to protect the database page buffers from being commandeered by another Kernel process.

DMK 14591 8497 Problem: If there is a severe shortage of free buffers in the page pool during an update, the Kernel may fail to write an updated page and cause SE 1564 (Work page header information is bad). Solution: Updated the page-read routine where it finds the desired page already in the page pool and a write in progress, to wait for the write to complete.

DMK 14543 8498 Problem: Under certain conditions an area in an area distribution list may get inordinately large when loading data. Solution: Updated logic applied to determine placement of the new key when a B-tree node of an index must be split because it is full.

DMK 14537 8592 Problem: Message 14261, used on an attempt to DELETE/FILE on a protected file, is not in the vocabulary file on Windows. Solution: Reinstated message 14261.


MOD URP/ RSM

REV Description

DMK 14630 8593 Problem: When the system administrator changes via DMCCF the password of the sort module, the Kernel will not start. The Kernel's attempt to start the sort module is rejected with UE 115 (bad password). Solution: Changed the Kernel to use the password recorded in the CCF when it initiates its sort module.

DMK 14703 8635 Problem: In very rare instances, the Kernel becomes unresponsive, consuming all available CPU cycles Solution: Fixed to protect resource lock entries.

FIND 14609 8494 Problem: A complex FIND command may abort with SE 1989 (corrupted I/O queue) but dump insufficient data to diagnose. Solution: Check the integrity of the I/O queue more often to prevent the failure.

FIND 14638 8506 Problem: SE 44006 (invalid heap handle number) may occur in response to a value-view FIND command that performs an outer join, e.g. FIND temp VALUES COUNT(DISTINCT udno) FROM employee,dependent Solution: Change to differentiate between a posting set and a value-view set in certain cases when preparing the sort input file.

FIND 8508 Problem: A FIND command may return incorrect results when searching an MFI using a retrieval test that is not consistent with the search-control parameters. Solution: Fixed.

FIND 14641 8514 Problem: On a FIND command on a thesaurus controlled field where hundreds of related terms are added to the query the Kernel may expand the short-term heap repeatedly and then fail Solution: Improved how FIND command manages the short-term heap.

FIND 14634 8521 Problem: Logically equivalent joined FIND commands on a multiply occurring field with several restrictions including a not-equal (NE) retrieval test may return different results. Solution: Adjusted the optimization algorithm for processing the NE operator to guarantee correct (but not necessarily the fastest) results.

FIND 14631 8526 Problem: An improperly formed FIND command using a nested WHERE clause with an outer reference may result in a kernel crash with an access/segment violation or issue SE 1955 (memory shortage) violation. Solution: Fixed the routine that handles an outer reference for a nested WHERE clause.

FIND 14639 8533 Problem: A value-view FIND with a directed join may malfunction when the first member of the result set lacks a child record. Solution: Fixed.

FIND 14649 8561 Problem: Using an invalid phrase qualifier in a FIND command may cause a kernel malfunction. Solution: Correct the logic of the parse table for the FIND command.


MOD URP/ RSM

REV Description

FIND 14751 14651

8570 Problem: A large and complex FIND command may cause a memory management failure (most likely if an MFI is specified many times) or a Kernel crash due to a segment/access violation. Solution: Fixed to not create duplicate structures for the MFI's constituent fields and to catalog an internal data structures without expanding the directory past its maximum size.

FIND 14653 8591 Problem: FIND TEMP VALUES does not handle encrypted fields correctly. Solution: Fixed to ensure the flag that indicates the view contains one or more encrypted/compressed fields is propagated from the source data structure.

FIND 14658 14660

8599 Problem: A value-view FIND command with certain criterion fails with system error 35 (no such page) or 64 (The number of pages to be read/written is outside the range). Solution: Added a check to test for an empty result set in the FIND routine responsible for sorting.

FIND 14682 8612 Problem: A phrase search that is fragmented into many parts (i.e. using too many wild-card characters) may cause the Kernel to crash with a segment/access violation, e.g. WHERE field PHRASE WORDS ‘?B?C?D?E?F?G?H?I?J?K?L?M' Solution: Established a check to restrict the number of pattern fragments. Reject the command with UE 1860 (too many character constants in a fragmented pattern.

FIND 14675 8614 Problem: The Kernel may report I/O error I 1588 (Close file failed for RESET_EOI request) when processing multiple simultaneous FIND commands with ORDER by clauses. Solution: Fixed several reset-EOI sort-file issues.

FIND 14679 8623 Problem: A FIND command with an ORDER BY $RANK or TERM with a large result may produce a bad reference list file. Solution: Fixed.

FIND 14713 8648 Problem: As the Kernel prepares to do a sort, it incurs an I/O error attempting to perform a reset-EOI operation on the sort-input file. The error is reported on Windows, but not on UNIX. Solution: Modified the main routine of the sort module, to diagnose the problem and then repair it on the fly.

FIND 14728 8670 Problem: When presented with a FIND command containing a nested WHERE clause, the Kernel might incur a system error, which appears in the Kernel log like this: SE 1575 SE 1899 in GET_MEMBER ID=FELF STEP=2 Q=2 Solution: Fixed.

FIND 14729 8672 Problem: The Kernel incurs system error SE 1899 (An unexpected system error occurred during the FIND command. Please check the kernel output file) if the FIND command is within a transaction, returns more than 1000 references and each member has 2 or more references and the member documents have been modified during the transaction. Solution: Fixed


MOD URP/ RSM

REV Description

FIND 14736 8675 Problem: The Kernel may issue SE 44004 (maximum number of long-term heap handles exceeded) after a single user performs over 32K FIND commands, each with a restriction on a field/index with a search filter. Solution: Modified search filter routine to verify a handle to the object before requesting a new one.

FIND 14687 14712

8628 8647

Problem: The Kernel may crash with a segment/access violation when given a FIND command with a JOIN and REFERENCES=NO to search a thesaurus controlled field that is not indexed. Solution: Fixed.

FIND 14751 8680 8695

Problem: A very long FIND may generate DMSTAT 129 (No outstanding request appears on the communication facility requiring the service of the control module (Kernel)). Solution: Modified routines responsible for parsing a FIND command string.

FQM 14637 8530 Problem: The IMPORT/PLIBRARY command fails but returns no error status when the source file contains a line longer than 511 characters. It should return DMSTAT 47030. Solution: Fixed.

FQM 14676 8619 Problem: A user break (CTRL-C) entered at an inopportune time during document import may cause the Kernel to malfunction and log these errors: I 1592 File Open Error in KFFOPN.STAT=4 and I 1572 IFN=1541 HSC=... No such file or directory. Solution: Fixed.

FQM 14714 8651 Problem: When replacing one or more long-text documents with documents where the new text is shorter, the Kernel may incur SE 1562 STAT=1212 (area full) during the ABORT of an update transaction and consequently marks the database damaged. Solution: Fixed

HVU 14633 8523 Problem: A field with usage DATE_KEY allows a maximum of 16,383 instances for the same date. The Kernel rejects the 16,383rd document having the same date with UE 1234 (maximum system-generated key exceeded). Solution: Fixed.

HVU 14614 8547 Problem: Import errors may occur when using a BGML converter, e.g. SYS_BLOB_HARD_INDIRECT, where the text of a text-image field contains instances of the character defined to be the opening delimiter of a markup tag. The import might be rejected, or if not rejected, entire fields might be skipped. Solution: Fixed.

HVU 14500 14586 14640

8558 Problem: If an IMPORT/FORM/xxx or EXPORT/FORM/xxx command fails because the form cannot be opened, e.g. UE 8647 (form not found in form library), then any subsequent attempt to import/export within the same HVU session is rejected with UE 47508 (bad style-guide number). Solution: Fixed.


MOD URP/ RSM

REV Description

HVU 14695 8637 Problem: The import/form/doc process only supports line numbers up to 999,999 in the input file. If the input file has more than 1,000,000 lines any error reports contain asterisks instead of a line number. Solution: Modified the definition of message 8749 to increase the width of its line-number parameter from 6 to 9 digits.

HVU 14732 8676 Problem: Under extraordinary conditions HVU open/direct fails due to a buffer overrun when the input file contains a thesaurus and REVL controlled field that exceeds the maximum (230) term length. Solution: Modified routine to protect itself from a buffer overrun.

HVU 14749 8691 Problem: Under complex conditions HVU may crash with general status 8573 (error updating non-unique index) and specific status 980 (key not found in B-tree) during the indexing phase of a REPLACE/PUT of a document. Solution: Fixed and included new essential details in dump file.


7.2 Issues Fixed in Library Management 10.3

MOD URP/

RSM REV Description

ACQ R18325 8595 Problem: You cannot cancel one request on an order without cancelling the whole order. Solution: You can selectively cancel a request without cancelling the order but the button is misleading. It says Cancel Order. Changed the button to just say Cancel.

8664 Problem: Incorrect logic to identify a standing order in receiving. Solution: Changed the if statement to check for SO_COPY_NUM.

Problem: The wrong Title field displays for standing orders on the Receiving Order form. Solutions: Revised to display CAT.TI when PO.SO_NEW_CAT_FLG=Yes, or display the ACQ.SO_UPDATES title when the value is No.

ACQ/ SER

14667 8617 Problem: The Staff Security setting to deny access to Vendor record maintenance removes the Vendor menu task but does not disable other links to vendor update pages (e.g. Add Request). Solution: Revised to check the vendor flag on every page with a link to vendor update pages to determine if the link should be active.

ALL Problem: Various errors in online help and documentation. Solution: Revised for current functionality.

CAT 8573 Problem: You can remove trailing periods from fields under authority control by changing the call to MaintainThesaurus on the auth.asp page from FALSE to TRUE. The setting does not work on all relation-types. Solution: Changed the code to remove the trailing period from the lead term and the values in the AUTH record.

CAT R18159 8564 Problem: The MARC Import Report does not have any output options. It displays to the screen only making it difficult to reconcile errors. Solution: Added an output parameter to the page so user can select output format.

CAT R18220 8563 Problem: Electronic location field (M856) in the Catalog record converts the entire value to hypertext. Current MARC standards allow for explanatory text such as "Table of Contents" and "Publisher description" in selected subfields of the 856 field. The field should be modified so allow descriptive notes as well as the URL. Solution: Check each sub-element and only display it as a hyperlink if it starts with http or ftp.


MOD URP/ RSM

REV Description

CAT 8587 Problem: There is no Delete action on the Authority record in Authority Control Thesaurus Update. Solution: Changed the toolbar options to include add/update/delete. Also added an "Update Thesaurus" button to toolbar options on the Thesaurus Update display page so you can retry the thesaurus update if it was not successful when the Authority record was added or modified.

CAT 8607 Problem: The temporary cat/copy report does not include temporary cat records without copies. Solution: Revised to include all 4 combinations (just temp cat, temp cat and temp copy, regular cat with temp copy; temp cat with regular copy).

CAT R18317 8566 Problem: User wants to be able to select the Material Type when running a Shelf List report, i.e. to be able to get a listing of just the Books. Solution: Added the mtype field on the parameters screen. If populated, it will be added to the query.

CIRC 8579

Problem: Copy availability is not updated when you cancel a Hold where the copy was already been trapped. Solution: Added a warning message that the item should be checked in to update status and check for additional holds if the current hold was cancelled.

CIRC SER

8688 8689

Problem: Patron Id's containing an apostrophe cause problems on checkout, check-in, and in Serials routing. Solution: Fixed the quoting of the patron ids.

CIRC 14744 8693 Problem: Circ Trans record is not updated when a copy with Status=In Transit is checked in. Solution: Fixed

CIRC 14721 8658 Problem: Circulation Request report. Date test for future dates fails if start date month or day is single digit (e.g. 8/1/2010) Solution: Changed the date test to return the number of days between the two dates.

SER R18237 8582

Problem: We need the ability to predict without specifying a Vol., Issue, or E3. We receive many items that have no enumeration. Solution: Added a flag to the Catalog record to indicate a serial with no enumeration. If the flag is set to yes the prediction does not calculate enumeration.

SER 8700 Problem: Repredict creates invalid enumerations if the Prediction Cycle changes and Next Value is provided (does not start at 1). Solution: Determine how many issues to create by subtracting the start value from the number of issues you want.

SER 14666 8629 Problem: Using Vendor Search on the Add Subscription form populates the Vendor field but clears all other user input on the screen. Solution: Reset variable to maintain the data on the screen.


MOD URP/ RSM

REV Description

SER 14756 8699 Problem: Enumeration is incorrect for issues predicted when Item Type for Volume=Season Solution: Fixed.

SER R18215 Problem: The Subscription SUB_TYPE is not changed when you cancel a subscription. As a result a cancelled subscription may still appear as routed. Solution: Change SUB_TYPE to closed on cancel.

SER 14674 8615 Problem: Null fields in the Prediction record may cause program errors running the Routing Slips report. Solution: Added test for null values and return a user error if a null is found..

SER 14635 14636 14718

8527 Problem: Errors in issue prediction when using the relative Start Value. Solution: Changed the conditions to reset the counter.


8 Known Issues

8.1 Localization error (Library Management – French)

The French name for a thesaurus lead term is not available to the localized version. After you install the French version of Library Management 10.3 you need to edit the file \BASISclient\Techlib\include\TlGlobal.inc with the following change:

Locate the 2 lines in the file as shown below:

Const THES_LEAD_TERM = “LT”

‘Const THES_LEAD_TERM = “TE”

Now, add the comment character (‘) to the first line and remove the comment from the second line so it reads like this:

‘Const THES_LEAD_TERM = “LT”

Const THES_LEAD_TERM = “TE”

Save the file.

8.2 ODBC Driver (Windows Server 2008 R2)

On Windows Server 2008 R2 the Windows Administrative Tools utility does not use the correct Collections Server ODBC Data Sources option. If you need to search for or edit the Data Sources used by the ODBC driver, you must run:

%WINDIR%\SysWOW64\odbcad32.exe


www.opentex t . com/ l ib ra ry

For more information about Open Text products and services, visit www.opentext.com. Open Text is a publicly traded company on both NASDAQ (OTEX) and the TSX (OTC).

Copyright © 2010 by Open Text Corporation. Open Text and The Content Experts are trademarks or registered trademarks of Open Text Corporation. This list is not exhaustive. All other trademarks or registered trademarks are the property of their respective owners. All rights reserved.

9 Contact Information Open Text Corporation 275 Frank Tompa Drive Waterloo, Ontario, Canada, N2L 0A1

Tel: +1-519-888-7111 Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440 Fax: +1-519-888-0677

FTP: ftp://ftp.opentext.com

Knowledge Center: https://knowledge.opentext.com/

For more information, visit http://www.opentext.com

Customer Support:

Toll Free Canada/USA: 1-800-540-7292

Global Customer Support Contacts: http://www.opentext.com/2/global/services-home/services-support-contact.htm

E-mail: mailto:[email protected]

ftp://ftp.opentext.com/�


http://www.opentext.com/�

http://www.opentext.com/2/global/services-home/services-support-contact.htm�

http://www.opentext.com/2/global/services-home/services-support-contact.htm�

mailto:[email protected]�

open text collections server & open text library management … text collections... · 2013....

Documents