Version No:

3.1.1, September 2011

Highlights:
1. OvP improvements (Defects 9315, 9658, 7926, 10117, 10320, 10343,
10344, 10398,10433, 10580)
2. Deep link improvements (Defects 9719, 10009, 10061)
3. Security improvements (Defect #10016)
4. Enhancements to Statistical Reports (Defect #10144)
5. Improvements to the Find Database functionality (Defect #8946)
6. Support of left-hand truncation in searches (Defect #10572)
7. Searches for 10-digit and 13-digit ISBNs will find either type
(Defect #10575)

General Documentation for Version:

Located in the Version 3.x folder in the Ex Libris Documentation Center

3.1.1 Defect Fixes

Defect
Description
ID
7926
This item is relevant to OPAC via Primo.

Implementation Notes

Module

Related
Documentation

ILS Interface-Location
Tab

Issue
Number
16384185995

Search EngineConfiguration

16384240735

Publishing PlatformNormalization

N/A

Front End-Tags

16384195370

Previously, there was no delimiter between multiple summary

holdings statements (such as 866 fields). Now the system displays a
semicolon between every statement.
8307

Previously, if a search invoked by a deep link expired, the system

displayed an error message. Now the system behaves in the same
as when a search invoked from the Primo Front End expires.

8607

The following transformations routines have been added to

Normalization Rules editor:

be_implementation_note.4.0.0.8607.csh

1. Upper case every first letter - normalizes the first letter of every
word to uppercase. For example, "A long story" will become "A Long
Story"
2. Remove HTML tags - works on CD DATA tags in XML content. In
the following example:
"Bats Adjust Their 'Field-of-View': Use of
<test1>Biosonar</test1> Is More Advanced <test2>Than</test2>
Thought"
Will be changed to the following:
"Bats Adjust Their 'Field-of-View': Use of Biosonar Is More
Advanced Than Thought"

8879

Tags created for Primo Central, Remote Search, and Deep Search
searches were not being indexed. This has been fixed.

3.1.1 Defect Fixes

Defect
Description
ID
8911
Previously, the Search Engine treated strings with a period as a
single word. For example, if the text included a string such as
"Annals of chemistry. Part 1" and the user searched for "annals of
chemistry.part 1" (without a space), the record would not be found
because the Search Engine would omit the period and search for the
following string:

Implementation Notes

Module
Front End-Brief Results

Related
Documentation

Issue
Number
16384200517

"annals of chemistrypart 1"

This has been changed so that a period between two strings is
normalized to a space for both indexing and searching.
To fully implement this fix, it is necessary to re-index from scratch by
first deleting the database. Note that the main problem regarding a
missing space in the search query will be fixed even without such a
re-indexing.
8946

This item is relevant to the Find Database functionality.

This item requires the installation of

MetaLib SP 4.3.3.

Interoperability-MetaLib

16384200707

The link to the native resource Web page now includes a re-direct to
the proxy server if its IRD is defined to "Use proxy server." Note that
this is due to a change in MetaLib and requires the installation of
MetaLib SP 4.3.3.
8972

After the upgrade to Primo 3.0, the Custom Layout Editor did not
work properly.
This has been fixed.

BO configuration-Views
Wizard

16384196727

9088

Front End-Look and feel

9226

E-Shelf notes were saved but not displayed until 'edit' was invoked.
This has been fixed.
Some Remote Search (MetaLib) results were deduped when they
should have been different records. This happened with some
component part records, where the system used the title of the host
rather than part in the match. This has been fixed.

16384230943
16384198685

9315

This item is relevant to OPAC via Primo.

Front End-e-Shelf

Interoperability-MetaLib

16384209476

The Blocks and Messages in My Account now display the ILS

location.

3.1.1 Defect Fixes

Defect
Description
ID
9422
If the name of a saved query that included non-ASCII characters (the
query; not the name) was changed, the query became garbled. This
has been fixed.
9486

Some of the local search fields were not being normalized correctly
by the Search Engine at search time. For example, a search term
such as "UT1000 4/2+1" could be found only if it was enclosed in
parentheses. This has been fixed.

Implementation Notes

Module
Front End-e-Shelf

Related
Documentation

Issue
Number
16384225988

Search Engine-Indexing

16384222138

Interoperability-ALEPH

16384216939

Note: Because the problem occured at search time, there is no need

to perform a re-index.
9658

This item is relevant to ALEPH and Voyager RTA (Real-Time

Availability)
Until now, RTA only updated the status of Primo locations, not the
locations themselves. This meant that if a new location was added
since the last harvest, this location (and also items via OPAC via
Primo) did not display in Primo. This was especially problematic in
the case of the ALEPH reading room when items were moved
temporarily to the reading room sub-library.
The ALEPH and Voyager RTA adaptors have now been changed so
that they also update locations. In case a user clicks on the
Locations tab before the RTA completes, the system will display a
message notifying users that locations may have changed, allowing
them to update locations.
Note: the new functionality will work only if you use the
'normalization_rules' RTA method for mapping data as defined on the
Advanced Configuration > General Configuration Wizard > RTA
subsystem page in the Primo Back Office.

9703

Previously, the program that imports summaries from Syndetics only

supported files with the <sums> tag. Now it also supports the
<summaries> tag.

Publishing PlatformEnrichment

16384233037

9719

When a Deep link search was performed, the "Primo Central

Options" check box displayed even if the active search did not
include Primo Central. This has been fixed.

General-Deeplinking to
Primo

16384236690

3.1.1 Defect Fixes

Defect
Description
ID
9899
This item is relevant to customers using the Summon adaptor.
The following fields have been added to the PNX that is created from
the search results:

Implementation Notes

Module
Front End-Full results

Related
Documentation

Issue
Number
16384238414

1. Pages -> display/format

2. ISBN -> display/identifier.
3. The following Dissertation fields were added to the
display/description field with a label in $$C:
- Advisor -> display/description $$Cadvisor: <advisor>
- Category -> display/description $$Ccategory: <category>
- Degree -> display/description $$Cdegree : <degree>
- Institution -> display/description $$Cinstitution: <institution>
The following codes were added to Display Constants code table:
- default.fulldisplay.constants.advisor Advisor:
- default.fulldisplay.constants.category Category:
- default.fulldisplay.constants.degree
Degree:
- default.fulldisplay.constants.institution Institution:

9925

The results of a Find Database search "Selected Databases" did not

always display correctly. This has been fixed. "Selected Databases"
will display in a tab only if the tab is defined to display the Find
databases option or includes a Remote Search scope.

Front End-Basic Search

16384248622

10009

The window title of the Deep Link Brief Search results displayed
nothing. This has been fixed to display the query terms.

API-Deep search

16384236655

3.1.1 Defect Fixes

Defect
Description
ID
10013 It is now possible to save search results for Primo Central, Remote
Search, and Deep Search searches in the e-Shelf using WebServices and X-Services. To save the results, an additional
parameter must be added to the Add to E-shelf requests. For more
information, refer to the Implementation Notes.

Implementation Notes

Module

In order to save a remote search record

Front End-Send to
to the e-Shelf, it is necessary to include
(print, save, connotea,
the searchKey. The searchKey is returned etc.)
in the response to a Brief Search request.
The searchKey is needed only for remote
search records (the PNX ID is prefixed by
"RS") but can be add to all requests. For
example:

Related
Documentation

Issue
Number
16384238495

http://servername:port/PrimoWebServices
/xservice/eshelf/add?
institution=VOLCANO&userId=200&docId
=RS_615733599ApplebyTagoe2011rcanc
ergeneticcounselling&searchKey=10.1.23
4.170_man_2011-08-18 12:14:26.723

10016
10061
10117

The subject in the email pop-up window is now sanitized to prevent

email injection.
In the result set of a deep link search, the sort options were
duplicated in the Sort by drop-down list. This has been fixed.
This item is relevant to OPAC via Primo.

Front End-Send to
(print, save, email)
API-Deep Link
OPAC via PrimoLocations

16384254310
16384254860
16384254774

In the 'Location ITem Content' mapping table, it is possible to define

multiple values to display per column in the list of items and to define
the punctuation that will display between the various fields.
Previously, the punctuation did display even if the value was not
present. This has been fixed so that the punctuation displays only if
the value it precedes can also be displayed. For example:
X;Y
X ;Y ;Z
X;Y! Z

X and Y both present

Y not present
Z not present

=> X ; Y
=> X ; Z
=> X ! Z

3.1.1 Defect Fixes

Defect
Description
ID
10144 The following filters have been added to Click Through Statistics and
Search Statistics reports:

Implementation Notes

Module
BO monitoring-Reports

Related
Documentation
Primo Back Office
Guide

Issue
Number
164749

1. Date range (start and end date). This replaces the previous date
filters.
2. User group
3. Source of the request (Primo FE, Web Service, Deep Link, XService).
10156

Previously, the delimiter between fields that display in the brief

results was hardcoded to a space. It is now possible to define per
line any delimiter via the Views Wizard > Brief Display > Brief Results
tile in the Primo Back Office. The default delimiter is a space.

BO configuration-Views Primo Back Office

Wizard
Guide

16384244695

10157

Previously, the "Terminate Pipe" option did not work for pipes using
the OAI-PMH method. The pipe continued to send requests to the
OAI server even though it was terminated. This has been fixed.

Publishing PlatformHarvesting

16384240952

10159

Some diacritics and other non-ASCII characters were not saved

correctly when Primo URLs were book marked or emailed. This has
been fixed.

Front End-Brief results

164751

10164

The standard behavior of the Search Engine is to remove hyphens

when normalizing data for indexing and when normalizing the search
query. This is problematic for languages (such as Finnish) that have
many hyphenated words.

Search EngineLinguistic features

(DYM, synonyms)

16384260146

By default, this field is selected, keeping the current behavior of the

system. If it is cleared, the system will not remove hyphens during
normalization of indexing and search queries.
Note: Changes to this field require you to deploy the Search Engine
Configuration on the Deploy All page and re-index from scratch by
deleting the indexes before running indexing.

3.1.1 Defect Fixes

Defect
Description
ID
10170 The following changes in the Institution Wizard no longer require restart of the Front End server:

Implementation Notes

Module
BO configurationInstitutions wizard

Related
Documentation

Issue
Number
164916

1. Any change in the list of institution IP ranges

2. A change to the ILS API base_url
It is still necessary to perform deploy after making a change. The
change will take effect only in new sessions (for #1 above) and new
sign ins (for #2 above).
10184

This item is relevant to N+1 topologies.

Search Engine-Indexing

16384198431

If the slice agent fails, the failover process switches the indexer
(empty) agent to the slice agent and switches the failed agent (which
hold slice in the past) to the indexer agent when it comes back up.
The problem was that when the failed agent was restored with
"se_start" right after failover process began, it was not started
correctly. This has been fixed.
10243

PDS has been updated to version 2.1. Current customer

configurations will not be affected. For more information about PDS
2.1, refer to the PDS documentation in the Documentation Center.

General-Misc

10248

The transformation routine RemoveStringFromList (added in V3.1)

inadvertently removed spaces between words after removing the
string defined in the mapping table. For example, if the string "and"
was to be removed from the input 'A and B' - the system returned AB
instead of A B. This has been fixed.

Primo Central-PC
grouping

10264

Some special characters in the Syndetics input file caused the Import
PNX Extensions program to fail. This has been fixed.

Primo Tools-Import PNX

Extensions

16384264477

3.1.1 Defect Fixes

Defect
Description
ID
10288 The item is relevant to the RTA plug-in method that was added in
3.0.3 and is defined in the Plugins mapping table. This fix is not
relevant for RTA with regards to ALEPH, Voyager, or III.

Implementation Notes

Module

Related
Documentation

Interoperability-XServices

Issue
Number
16384270757

This item contains the following fixes:

1) The plug-in program was supposed to be stored in the following
directory, but Primo was looking for it in the Plugins/rta directory (with
an uppercase P) instead of the plugins/rta directory (with a lowercase
p):
$primo_dev/ng/primo/home/profile/publish/publish/production/conf/pl
ugins/rta
Primo has been fixed to look for the program in the plugins/rta
directory.
Note: If you created a Plugins/rta directory and moved the plug-in
program to it as a workaround, make sure that you move the plug-in
program to the plugins/rta directory.
2) There was a problem in the way that the RTA plugin interpreted
the check_holdings status. This has been fixed.

10291

Following a change in Primo v3.1.0, some Deep Search adaptors did

not work if the results did not include facets. This has been fixed.

Search Engine-Remote
Search

16384269201

10297

If the PDS_SSO_ENABLE parameter is set to false, the system will

now automatically close the PDS session (if the user is signed-in)
when the Primo session is closed. Previously, if users switched to
another view without logging out first, the system would use the
current PDS session to redirect them to the view on which they
signed in.

Front End-Sign In

16384255997

The behavior of the system in case 'PDS_SSO_ENABLE' is true has

not changed. The PDS session will remain active.

3.1.1 Defect Fixes

Defect
Description
ID
10324 In some cases, the view-specific session timeout URL was not being used. This has been fixed.
10343 This item is relevant to OPAC via Primo.

Implementation Notes

Module
BO configuration-Views
Wizard
ILS Interface-Location
Tab

Related
Documentation

Issue
Number
16384271154

Paging and the ability to request multiple locations in a single request

is now supported by ALEPH 18. This will be available in the ALEPH
18 Service Pack released in September - v.18 (2270). Refer to
defect #10580 for details on how to configure these options in Primo.
10344

For OPAC via Primo, the option to filter items was added in 3.0.3.
Due to a change in Primo v3.1, not all items displayed in some cases
if this functionality was not active. This has been fixed.

ILS Interface-Location
Tab

10354

This item is relevant if you have defined restricted search scopes.

Front End-Full results

16384274617

Previously, the restriction was active only during searches. Users

with a PNX ID could use deep linking to access the record even if
they were not part of the allowed group. This has been fixed so that
the system also checks the restricted search scope before displaying
the full record.

10

3.1.1 Defect Fixes

Defect
Description
ID
10356 The following defects were caused by the changes made for defect
#9765 to fix a security issue with Birt reports:

Implementation Notes

Module

Related
Documentation

Issue
Number

BO monitoringDashboard

1. The Back Office and BIRT sessions were not always in synch. If
the BIRT session ended before the Back office session, the Primo
dashboard displayed the Back Office login page. This has been
fixed.
2. If users attempted to access BIRT reports directly when they were
not signed on to the Back Office, the system displayed the Back
Office sign-in page. If for some reason users did not sign in, but
instead attempted to open the Back Office, the Back Office sign in
page would display. If users successfully signed in, the BIRT report
they originally tried to access would display instead of the Back
Office. This has been fixed.
In addition, if users attempted to access the listings of the
Webcontent directory, the system would block them and display the
"404 Page Not Found" message.
Important note: the host name used to define the 'Reporting Base
URL' parameter in Advanced Configuration - General Configuration Installation should be the same as the host name staff use to access
the Primo Back Office. If staff access with the Back Office with a
different host name they will get the BO sign-in page when they
invoke reports.

11

3.1.1 Defect Fixes

Defect
Description
ID
10398 The item is relevant to OPAC via Primo.

Implementation Notes

Module
Front End-Brief Results

Related
Documentation

Issue
Number
16384255660

Previously, the following problems occured when filtering by

locations:
1. In the case of deduped records, the system fetched only items
from one of the records.
2. Filtering always took the call number into account when it matched
records with Primo locations, which is not appropriate for Aleph.
These problems have been fixed.

10423

The EBSCO Deep Search adaptor will now be activated only for
users that are signed-in. If the user is not signed in, no results are
returned from Ebsco. Currently, the adaptor does not check for IP
range and will not work for on campus users that are not signed-in.

See IN #10423.

Search Engine-Remote
Search

If you implemented the Hot Fix provided before Primo v3.1.1 and
changed the adaptor name to EbscoDeepSearch2 in the following
file, it is recommended to change it back to EbscoDeepSearch:
$primo_dev/ng/primo/home/system/search/conf/thirdnodeconfig.xml
An explanation on how to set up the adaptor can be found in the
Implementation Notes.

10562

Angle brackets are now converted properly in RSS feeds to &lts&gt.

Front End-RSS

10572

See Defect #10572.

Search Engine-Indexing

10573

Primo now interoperates with Alma. This includes Alma specific

normalization rule templates as well as some additions to the out-ofthe-box delivery settings.

Interoperability-ALEPH

12

3.1.1 Defect Fixes

Defect
Description
ID
10575 It is now possible to set an option in Primo so that the Search Engine
knows how to search using ISBN10 or ISBN13 and find records with
either. If set, the Search engine will normalize the search/isbn field to
ISBN13 and also remove hyphens and spaces, which will be done at
search time, too. This means that a user can perform searches with
or without hyphens and use either format (ISBN10 or ISBN13). The
SE will also normalize ISSNs in the same way (remove hyphens and
spaces) so that a search can be done with or without hyphens.

Implementation Notes

Module

Related
Documentation

Issue
Number

Front End-Basic Search

The Normalize ISBN/ISSN option has been added to the Advanced

Configuration > Search Engine Configuration > Miscellaneous
subsystem page. Note that you will need to deploy the Search
Engine Configuration and re-index from scratch by deleting the index
before re-indexing to fully activate this feature.

10576

See Defect #10576.

Front End-Delivery
(availability and GetIt!)

Primo
Interoperability
Guide

13

3.1.1 Defect Fixes

Defect
Description
ID
10578 It is now possible to display a snippet from the Abstract, TOC, or
Fulltext fields that are stored in the PNX extensions table without
having to index these fields. The optional display of snippets in the
Brief Results was added in V3.1. To configure this enhancement in
the Primo Back Office:

Implementation Notes

Module
BO configuration-Code
& Mapping tables

Related
Documentation
Primo Back Office
Guide

Issue
Number

- Set the display of snippets option that is defined in the Brief

Results tile in the View Wizard.
- Set the display priority that is defined in the Snippet Display
Preferences mapping table in the Front End subsystem.
- Previously, the fields used for snippets were based on the
PNX_EXTENSIONS_MAPPING table, which required the fields to be
indexed. The Snippets Extensions Mapper mapping table has been
added to the Front End subsystem to define the fields and to replace
the previous implementation, which required indexing. The available
fields have not changed, and all three are defined by default in the
mapping table. Additional fields cannot be added at this time.

10579

The PNX Extension Loader tool has been added to provide a new
method for importing extensions. In order to use this feature, you
must know in advance the PNX record IDs to which you want to
associate the extensions. Use of this tool requires implementation of
a special file splitter whose input is a file containing extensions. The
responsibility of the file splitter is to parse the file and pass the
parsed extensions to the database to be saved.

Primo Tools-Import PNX

Extensions

For more information, refer to EL Commons.

14

3.1.1 Defect Fixes

Defect
Description
ID
10580 This item is relevant to OPAC via Primo for ALEPH and Voyager.
In Primo v3.1, an option was added to fetch items in bulk from
ALEPH and Voyager so that all items can be fetched from the ILS.
Because this functionality depends on a specific ILS version, the new
functionality is activated only if it has been activated per institution.
Previously, this option could not be configured by customers. With
SP 3.1.1, the OvP Functionality mapping table has been added to
the OPAC via Primo subsystem to allow customers to configure this
option.

Implementation Notes

Module

Related
Documentation

Issue
Number

BO configuration-Code
& Mapping tables

The OvP Functionality mapping table allows you to activate the

following options:
- Paging: fetching items in bulk.
- Multiple locations: enables Primo to request items for multiple
locations in a single request.
This upgrade will update the new mapping table based on the
previous configuration if these options had already been activated.
Both options are recommended as long as your ILS supports them:
ILS/Option
--------------ALEPH 18
ALEPH 20:
Paging
both
Voyager

10611

Release
------------------------------------Latest v.18 SP available (2270).
SP 20.2.3 (3488)
SP 20.2.4 (3556)
7.2.5

The interface languages are no longer limited to five languages. It is

recommended that you enable only the languages you need in the
Interface Languages code table in the Front End subsystem.

BO configuration-Code
& Mapping tables

15

3.1.0 Defect Fixes

Defect
ID

Description

Implementation Notes

Module

For multi-server Primo topologies, a new utility has been added to

allow customers to start and stop all Primo Servers (BE, FE, and SE)
centrally. For more information, see the Primo System Administration
Guide.
3984
6382

Cross-Site Scripting (XSS) was blocked on searches and other fields

that were reported.
Some fields that users can add to lines in the Brief and Full display
using the Views wizard displayed poorly in the Front End. The
following changes have been made:
- The Availibrary, AvailPnx and AvailInstitution fields have been
removed from the drop-down lists in the Brief Results and Full
Results tiles in the Views wizard.

Related
Documentation
Primo System
Administration
Guide

Issue Number

General-Misc

16384-34578

Front End-

16384-102880

- The system will display the Source field according to its mapping
in the Data Sources code table. If no mapping is provided, it will
display as is.
8669

The deploy mechanism has been changed to allow one request at a

time. All other deploy requests will be placed in a queue. If a deploy
is running, users will receive a message if they perform a deploy on
the Deploy All page.

BO configurationOngoing Configuration
Wizard

Primo Back Office

Guide

16384-211497

8671

It is now possible to harvest MARC Exchange records using

additional character sets, which were previously limited only to UTF-8
and MARC-8. If a character set does not display in the Character Set
drop-down field on the Data Source page in the Back Office, enable
the character set in the Character Set code table under the
Publishing subsystem.

Publishing PlatformHarvesting

Primo Back Office

Guide

159829

8677

The Record IDs field has been added to the Primo Home > Primo
Utilities > System Tests & Monitor > Test File Splitters page to allow
you to to test specific records. Multiple IDs must be separated by a
comma.

Publishing PlatformHarvesting

Primo Back Office

Guide

8927

An error in an SQL query sometimes caused the dedup merge

process to fail. This has been fixed.
After disabling the "Using 856 links in remote search records"
functionality for dedup records, the link to the resource was created
from the 856 link instead of SFX.
This has been fixed.

BO monitoring-Pipes

16384-199255

Front End-Remote
Search

16384-198479

9048

16

3.1.0 Defect Fixes

Defect
Description
ID
9109
Primo Central availability did not work correctly if the record included
an alphabetic character in the volume or issue - for example, in the
case of Roman numerals or supplements. This has been fixed.

Implementation Notes

Module

Related
Documentation

Issue Number

Primo Central-SFX
Availability

16384-233981

9191

Previously, the item description information was not displayed on the

'My Account' loans and requests pages even though it had been
retrieved from the ILS.
This has been fixed.

Interoperability-ALEPH

16384-210991

9194

Labels with characters that were not in ISO-8859-1 did not display
correctly in the embedded Primo search box. This has been fixed.

General-Embedding
Primo Search box

16384-214228

9198

The institution of the user has been added to the e-Shelf folders
table (U_FOLDER). During the upgrade to V3.1, the system uses the
institution of the first record that is stored in the user's e-Shelf
(U_BASKET) to populate the value for the institution. If the user's eShelf does not contain any records, the folders will be deleted.

Front End-My Account

16384-212286

9203

In some cases, the Did You Mean (DYM) mechanism looped and
continued to offer the same suggestion if the DYM index contained
punctuation. This has been fixed.

Front End-OvP

16384-215802

9220

The HTML and XML file splitters ignored the character set defined in
the data source. This has been fixed.
This enhancement integrates snippets into the search results. For
more information, refer to the Primo Back Office Guide.
It is now possible to save records from Primo Central and DeepSearch to the e-Shelf and/or create for them tags and reviews via the
Primo APIs. This works only as long as the records are in the cache.
In other words this will work in a scenario when a search is first run
and then the records are saved to the e-Shelf.

Publishing Platform-Pipe
execution
Front End-Brief results Primo Back Office
Guide
General-Primo API

16384-216196

9236
9288

Note that this is still not possible for Remote Search records (via a
MetaLib).
9293

If the first facet group did not contain any facets, the system did not
display the "Refine My Results" title.
This has been fixed.

Front End-Facets

16384-216989

9295

See Defect #9295.

Front End-Full Results

16384-206118
17

3.1.0 Defect Fixes

Defect
Description
ID
9309
Data added by a guest user in My Account (such as email or SMS)
was incorrectly saved for the next signed-in user. This has been
fixed.

Implementation Notes

Module

Related
Documentation

Front End-e-Shelf

16384-211540

9373

In some cases, local Primo records were added to the RPNX table
by mistake and not indexed. This has been fixed. In addition, the
upgrade includes a script that automatically deletes these records
from the RPNX table and changes their updated date in the PNX
table so that they can be re-indexed incrementally.

After applying the

Publishing Platformimplementation script, perform
Harvesting
an incremental re-index to make
sure that all updated PNX
records are indexed. Note that it
should not be necessary to
delete the indexes and re-index
all PNX records.

9412

See Defect #9412.

9432

This item is relevant to OPAC via Primo. If a location had multiple

holdings records, the system displayed only one of the records (such
as the summary holdings). This has been fixed.

9535

For OPAC via Primo configurations, the "Clear Selection" button will
now continue to display in the Request form after all drop-downs
have been selected. This allows users to change their selection at
any time.

OPAC via Primo-OvP

Configuration

9546

For OPAC via Primo configurations, the Location column has been
added to the list of loans and requests in My Account. In addition,
new labels have been added to the following code tables in the
OPAC via Primo subsystem:

Front End-My Account

Primo
Interoperability
Guide

Primo
Interoperability
Guide

Publishing PlatformFRBR
OPAC via PrimoLocations

Issue Number

16384-222776

Primo Technical
Guide
163609

16384-212916

- Loans List Labels:

- default.loans.brief.active.column6 Location
- default.loans.brief.history.column6 Location
- Requests List Labels:
- default.requests.brief.column7

Location

9547

See Defect #9547.

Front End-OvP

9554

Text enclosed by less-than (<) and greater-than (>) symbols did not
display in the Front End. This has been fixed.

Front End-Look and

Feel

16384-230712

18

3.1.0 Defect Fixes

Defect
Description
ID
9593
To optimize DYM indexing, all agents on N+ 1 environments will be
given a default memory allocation of 2G instead of 1G. The upgrade
to version 3.1 will automatically adjust this parameter. The additional
1G should not cause any problems in terms of resources. Note: If the
memory allocation has been modified prior to the upgrade, the
system will not update your memory allocation automatically. This fix
does not apply to all-in-one environments, where the indexer resides
on the FE.

Implementation Notes

Module

Related
Documentation

Issue Number

Search EngineLinguistic features

(DYM, synonyms)

9604

Special characters were not always encoded correctly. This has been
fixed.

Front End-Delivery
(Availability and Get It)

9629

After setting the 'Session Timeout URL' parameter for a view, the
system automaticaly copied the same value to another view if this
parameter was empty. This has been fixed.

BO configuration-Views
Wizard

9664

If any spaces were added before or after the PC Key field in the
Institution Wizard, they were taken as if they are part of the key. As a
result, searching in Primo Central did not work correctly. This has
been fixed.

Primo CentralRegistration

9676

Previously, some Primo HTML pages did not pass the W3C
validation standardization test.
This has been fixed.

Front End-Brief Results

16384-207364,
16384234953,16384234141

16384-233231

19

3.1.0 Defect Fixes

Defect
Description
ID
9697
The following fixes were included in the Summon deep-search
adaptor:

Implementation Notes

Module

Related
Documentation

Issue Number

Front End-Send to
(print, save, connotea,
etc.)

16384-238366

1. Fixed the input parsing that resulted in errors in the displayed

record.
2. The following fields are now being converted:
- Dissertation related fields (advisor, category, degree, institution)
- Pages
- ISBN
3. Sort fields have been added to sort by author, title, and year.
4. The RPNX recordid field has been enlarged to accommodate very
long Summon IDs. This allows users to save all records to e-Shelf or
to add tags and reviews.

9704

Because the RSS URL includes all of the search request

parameters, it was too long in some cases. The system now stores
the parameters in the database and includes only an identifier in the
RSS URL. RSS URLs that are created with previous Primo versions
will continue to use the old format.

Front End-RSS

16384-238132

9765

Access was incorrectly given to the Birt reports directory without

logging in to the Primo Back Office.
This has been fixed by redirecting users to the Primo login screen if
they try to access the directory.

BO monitoring-Reports

16384-241641

20

3.1.0 Defect Fixes

Defect
Description
ID
9824
Previously, it was not possible to convert two characters into one
character to enable accurate search results.
This has been fixed.

Implementation Notes

Module

Related
Documentation

Step1: Define the charachters to General-Misc

be converted in the 'SE 221
Char conversion' mapping table
in the Back Office. For example:
From
0041-0308

Issue Number
162096

To
00C4

Step 2: Click deploy > Search

Engine Configuration
Step 3: Run Index and Hotswap

9843

Previously, users were not able to send Primo records by email using
Firefox.
This has been fixed.

Front End-Send to
(print, save, email)

16384-237813

9884

Files harvested using the SFTP method did not retain their original
date. As a result, it was possible for the pipe to override a record with
an earlier update (the problem fixed in defect #8709). This has been
fixed.

Publishing PlatformHarvesting

162872

9908

The frbrgroupid and frbrtype tags were missing from the Full View Xservice and Web service responses. This has been fixed.
While performing searches in a view that had multiple blended
search scopes in which the first local Primo scope was the same, the
results came from the local Primo scopes used in the previous
search. This has been fixed.

API-Deep search

16384-234244

Front End-Basic Search

16384-227937

9960

After the installation of SP 3.0.3, it was not possible to send records

to EndNote Web.
This has been fixed.

General-Misc

16384-250102

9982

There were some problems searching Traditional and Simplified

Chinese due to errors in the character normalization tables. This has
been fixed.

Search EngineLinguistic features

(DYM, Synonyms)

16384-250054

9986

See Defect #9986.

Search Engine-Ranking Primo Back Office

Guide

9952

21

3.1.0 Defect Fixes

Defect
Description
ID
10005 The HIGHLIGHT parameter was added to the thirdnode-config.xml
file to control highlighting for third-node records. This parameter
requires the following XML format:

Implementation Notes

Module

Related
Documentation

Issue Number

Search EngineConfiguration

16384-253868

<parameters>
...
<parameter>
<key>HIGHLIGHT</key>
<val>false</val>
</parameter>
...
</parameters>
10017

The availability process returned incorrect results when different

journals had the same name. This has been fixed so that title
matching will not be performed if the incoming record has an ISSN or
ISBN and there is no match.

Interoperability-SFX

16384-250652

10034

Records sent by email from Primo included the sender's session ID,
which allowed the recipient to link to the sender's session if it was still
active. This has been fixed.

Front End-Send to
(print, save, email)

16384-255076

10037
10056

See Defect #10037.

Previously, the Primo Central availability process performed matches
on title for articles only.
This has been changed to perform matches on title for all resource
types. In addition, it checks additional data/jtitle and additional
data/btitle when matching on titles.

API-Deep search
Primo Central-SFX
Availability

10180

Previously, the http://<server>:<BO_port>/birt directory was open and The message can be changed
all reports could be accessed without providing authentication.
by changing the content of the
It has been blocked and displays an "Access Denied" message.
following file:
\
ng\primo\home\system\thirdparty
\openserver\server\publish\deplo
y\birt.war\index.jsp
In order for a consortium to allow multiple customers to access the
PCI My Profile page from the same Back Office, the Customer ID
field has been moved from from the General Configuration wizard to
the Institution wizard.

BO configurationReporting

10188

BO configurationInstitutions wizard

16384-199005

Primo Back Office

Guide

22

3.1.0 Defect Fixes

Defect
Description
ID
10191 Primo Central has been enhanced to dedup records by matching and
grouping them. In the Front End, Primo Central grouping functions
like FRBR. Users see a preferred record in the brief results list.
Preference is always given to the original publisher's record over an
aggregator record or pre-print. Additional versions can be displayed
by invoking the "View all versions" link.

Implementation Notes

Module
Primo Central-PC
grouping

Related
Documentation
PCI Configuration
Guide

Issue Number

The following labels have been added per code table:

- Results Tile:
default.pcgroup.display
- Facets Labels:
default.facets.search-box.pcgroup
default.facets.facet.pcgroup

View all versions

List of all Versions
List of all Versions

23

Defect #9295

The Linking to Google Book Search (GBS) functionality has been restored. It is now possible to add links to Google Book S
Primo uses the GBS Viewability API to dynamically create the links based on the end user's IP. Google enables access to
and a preview based on the local copyright rules. The GBS links do not need to be created in the PNX, but they need to be
to the Links to display in full results section on the Full Results Tile page in the Views wizard.
The following types of links can be added:

- GBS About (gbsabout) - This option always displays a link to the "About this Book" page in Google Book Search.
- GBS Full (gbsfull) - This option displays a link to full text or a preview of the item in Google Book Search.
- GBS About no ful (gbsaboutnofull) - This option displays a link to the "About this Book page" in Google Book Search o
full text is available.

The labels for the above links can be modified in the Full Display Labels code table in the Front End subsystem:
- default.fulldisplay.gbsabout
- default.fulldisplay.gbsaboutnofull
- default.fulldisplay.gbsfull
Primo invokes the Google API if the record has an ISBN, OCLC, or LCCN.

24

Defect #9412
This update adds the following transformation routines, which are used in the normalization rules:

1. ConvertToISBN13 - Converts an ISBN to a 13-digit ISBN. The input should be a 10- or 13-digit ISBN with or without hyp
Parameter - none
Output - A 13-digit ISBN without hyphens.
Example:
Input string: 0747599602
Output string: 9780747599609

2. ConvertISBN13ToISBN10 - Converts a 13-digit ISBN to a 10-digit ISBN if possible. The input should be a 10- or 13-digit
with or without hyphens.
Parameter - none
Output - A 10-digit ISBN without hyphens.
Example:
Input string: 9780747599609
Output string: 0747599602

3. RemoveLeadingStringFromList - Removes a leading string from the input. The leading strings (such as articles) that you
removed must be defined in a normalization mapping table.

Parameter - The code for the normalization mapping table that lists the strings to be removed from the beginning of the inp
Output - The original string without the leading string.

Example:
The normalization mapping table should include the string to remove in both the Source and Target Code columns. For ex
sourceCode1 targetCode
---------------- -------------a
a
an
an
Input string: a report to congress
Output string: report to congress

25

Defect #9412

4. NormalizeDiacritics - Normalizes the input string based on source and target codes defined in the DiacriticsConversion m
table.
Parameter - none
Output - the Unicode character to which to normalize.
The DiacriticsConversion mapping table contains the following columns:
- Source UniCode - the Unicode character from which to normalize.
- Target UniCode - the Unicode character to which to normalize.
The following example converts a Latin O with stroke to upper case O:
Source UniCode
0OD8

Target UniCode
OO4F

5. RemoveStringFromList - Removes all occurrences of a string defined in a specified normalization mapping table.
Parameter - The name of the normlaization mapping table in which the strings are defined.
Output - The original string without the strings defined in the mapping table .
For example, the routine uses the following normalization mapping table to remove "and" and "&" from the string:
Source Code
&
and

Target Code
&
and

Note: The normalization mapping table must include the string to remove in both the Source and Target Code columns
Input string: War and Peace
Output string: War Peace

6. CheckStringInMappingTable - This validation routine checks to see that the input string exists in a specified normalizatio
mapping table. You can use this table, for example, to prevent the creation of dedup or FRBR keys in the case of certain ti
Parameter - The name of the mapping table that contains the strings to check.
Output - The system will return the input string only if it does not exist.
For example, the routine uses the following mapping table to see if the file contains either the "acts" or "review" string:
Source Code
acts
review

Target Code
acts
review

Note: The normalization mapping table must include the string in both the Source and Target Code columns.
Input string: acts
Output: there will be no output because "acts" is present in the file.

26

Defect #9412
7. GetHeadTail - Returns the specified number of characters from the beginning and end of the input string. The following
used for the Parameter field, where <param1> is the number of characters taken from the beginning and <param2> is the
of characters taken from the end:
<param1>@@<param2>
If you do not specify a value for <param2>, only characters from the beginning will be taken.
If the input string has fewer characters than specified in either parameter, the system returns the entire string.

In the following example, the system will first delete the spaces from the input and then take the first 20 characters and the
five characters:
Source: MARC 245 a
Transformation:
Pack spaces
GetHeadTail/20@@5
Action: ADD
Input string: england and france during the hundred years war
Output string: The input is first transformed to "englandandfranceduringthehundredyearswar" and then to
"englandandfrancedurirswar"

8. ReplaceLastRegexpByString - Replaces the last occurence of the specified regular expression with the specified string.
The Parameter field uses the following format, where <reg_exp> is a regular expression to replace, @@ is the parameter
delimiter, and <str> is the replacement string:
<reg_exp>@@<str>
If the replacement string is omitted, the system will use an empty string.
Output: The original string with the last instance of the regular expression changed to the replacement string.

In the following example, the routine removes the matching string because the replacement string was omitted from the pa
Parameter: (\([^()]+\))$
Input string: History of Germany (online)
Output string: History of Germany

9. Get author first last name - Returns the author's first and last name.
Parameter - none
Example:
Input string: Marshall, John B
Output string: John B Marshall

27

Defect #9412
10. Get author last first name - Returns the author's first and last name in reverse order.
Parameter - none
Example:
Input string: John B Marshall
Output string: Marshall John B

28

Defect #9547
The following enhancements were added for OPAC via Primo configurations:
1. Added support for the following fields per ILS:
- ALEPH:
ILS Field
-------------item status
copy number
pages
location-2
OPAC note

Primo-U-XML Term
------------------------<item_category_name>
<copy_id>
<pages>
<call_number_2>
<note_opac>

- Voyager:
ILS Field
-------------copy number

Primo-U-XML Term
------------------------<copy_id>

2. Added the ability to expand an item in the Locations tab to display additional fields. These fields and the order in which t
listed in the expansion area are configured with the Location Item Content mapping table. The following codes have been
indicate the order of the fields in the expansion list: item.global.dataitem.1, item.global.dataitem.2, ..., and item.global.data
In addition, you can enable or disable rows, modify the content of a parameter, and display multiple fields in the same row
adding multiple fields (separated by a space) to the same code. For example:
Element
-------------------------item.global.dataitem.1

Content
--------------------------------------------------------main_location_name secondary_location_name

Note that the Location Tab code table allows you to customize the labels for each code.

29

Defect #9986

A new option has been added to boost records that belong to the user's institution. This can be relevant in a scenario wher
user is searching in a scope that includes records from many institutions. The boost works by giving a negative boost to re
that do not belong to the institution of the user.
Note: The boost affects only local Primo records and does not affect the ranking of records from Primo Central or remote
searches.
To configure this option:

1. Boost for Institution - This field has been added to the Results Boosting section on the the Search Engine Configuration
The valid values are 0 though 1. For example:
- 0 indicates that the system will not display records from other institutions at all.

- 1 indicates that the institution will not affect ranking. In other words, the boost is disabled.
- very low numbers (such as 0.00001) will, in most cases, ensure that all records belonging to other institutions will be r
lower than the lowest ranked record from the user's institution.
2. Deploy the Search Engine configuration.

3. Boost results from My Institution - This check box has been added to the VIew wizard > Edit Brief Results Attributes pag
indicates whether the settings specified in the Boost for Institution field should be enabled for this view.
4. Deploy the view.
Note: Because this feature uses the delivery/institution field in the PNX, you must perform a complete
re-index of the data prior to using this feature.

30

Defect #10037

A Deep-Search adaptor has been added to search EBSCO databases. The adaptor can search upto 15 EBSCO database
To configure the EBSCO adaptor:
1. Log on to the Back Office server.
2. Enter the following commands to edit the thirdnode-config.xml file.
fe_conf
vi thirdnode-config.xml
3. Add the following section to the file:
<adaptor_config>
<id>EbscoLocal</id>
<class_name>ebsco.local.EbscoDeepSearch</class_name>
<primo_services>
<primo_rank>false</primo_rank>
<primo_facets>false</primo_facets>
<primo_highlighting>true</primo_highlighting>
</primo_services>
<warmup>
<enable>false</enable>
</warmup>
<cache>
<enable>true</enable>
<batchSize>10</batchSize>
</cache>
<parameters>
<parameter>
<key>URL</key>
<val>http://eit.ebscohost.com/Services/SearchService.asmx/Search</val>
</parameter>
<parameter>
<key>USERNAME</key>
<val></val>
</parameter>
<parameter>
<key>PASSWORD</key>
<val></val>
</parameter>
<parameter>
<key>DB</key>
<val></val>
</parameter>

31

Defect #10037
<parameter>
<key>TIMEOUT</key>
<val>30000</val>
</parameter>
<parameter>
<key>port</key>
<val>1701</val>
</parameter>
<parameter>
<key>scope</key>
<val>none</val>
</parameter>
</parameters>
</adaptor_config>
4. Make sure that you configure the following required parameters:

- USERNAME: Enter your EBSCO user name.

- PASSWORD: Enter your EBSCO password.
- DB: Enter a list of the short EBSCO database names separated by a comma. You can list a maximum of 15 database
For example: rlh,ahl,8gh,lxh,eoh,buh,rvh,oah,rfh,reh,vah,sbh,loh,jph,rph
5. Exit and save your changes to the file.
6. Log on to the Primo Back Office UI.
7. Enter the following fields in the Create a New Code Table Row section on the Primo Home > Advanced Configuration >
Tables > Third Node Adaptors code table page:
- Enabled: select this check box to enable the new adaptor.
- Code: Enter EbscoLocal.
- Description - Enter Ebsco Adaptor.

8. Click Create to add the adaptor to the table.

9. In the Primo Home > Ongoing Configuration Wizards > Views wizard, define a search scope that includes the new EBSC
adaptor.

This is done by selecting the Ebsco Adaptor check box in the Third Node Adaptors section on the Edit Search Scope page
10. Deploy the view.

Note: The EBSCO API that the new adaptor uses does not return facets and does not support search by facets. If you blen
EBSCO adaptor with other scopes, a search on facets will not return any results from EBSCO.

32

Defect #10572

Left-hand truncation (which is peformed by placing the wildcard character to the left of the search term) is now supported.
supported by indexing every word several times, each time removing another character from the beginning. For example, t
"world" is indexed as "world" and the following additional strings:
orld
rld
ld
Note: The system will use the additional strings only when left-hand truncation is invoked by the user.

This means an increase in the size of the index. For this reason, you can limit left-hand truncation to specific fields in the P
search section. The list of fields is defined on the Advanced Configuration > Search Engine Configuration > Left wildcard s
page. Any change to this configuration requires you to deploy the Search Engine Configuration and perform a re-index from
scratch.
It is recommended not to include the Full text field for left-hand truncation. Also note that left-hand truncation of ISBN and
fields using the new normalization option (see #10575) is not supported.

Note: Left-hand truncation (and also right-hand truncation) does not work for the Additional title and Alternative title fields w
users only search the title index by selecting 'in the title' in the search box. This will be fixed in a future service pack.

Concerning sizing:

If your SE is configured to work "in memory," please contact Ex Libris Sizing Support at sizing.manager@exlibrisgroup.com
If your SE is configured to work "on disk," add additional RAM based on the table below. The additional RAM is per field
configured for left-hand truncation. and per index (all in one and 2 Tier) or per slice (N+1). The table covers the addition of
three fields. For additional fields, please contact Ex Libris Sizing Support at sizing.manager@exlibrisgroup.com.
# of records Additional RAM (1 Field)
Up to 2.5 M
No need
2.5M - 4.5M
1GB
4.5M - 6M
1GB
6M - 8M
No need
8M - 10M
No need
10M and Up
1GB

Additional RAM (2 Fields)

0.5GB
1GB
2GB
1GB
1GB
2GB

Additional RAM (3 Fields)

0.5GB
1GB
2GB
2GB
2GB
2GB

33

Defect #10576
This is relevant to RTA (Real-Time Availability) with regard to III.

The III RTA adaptor will now return a due date for locations with items that are on loan. The due date will display in the Pri
Front End in the brief and full displays. The due date will display instead of the "unavailable" status. Because the Primo dis
per location, if there are several due dates, the earliest date will display.
The following changes have been made to the Primo Back Office to configure this enhancement:
1. III Millennium RTA Statuses mapping table in the Back Office subsystem - Defines the text that displays before the due
the III page. This is done by adding a new row in which the Status column is the text and the Code column is is Due Date.
In this table, it is also necessary to define the date format. Any of the formats supported by the Java date format (See
<http://download.oracle.com/javase/1.4.2/docs/api/java/text/SimpleDateFormat.html>) can be used. The format should be
enclosed in parentheses. For example:
"dd MMM yyyy" for 25 Aug 2011

2. For the Brief Results, added the following due date codes to the Calculated Availability Status code table in the Delivery
subsystem:
- default.delivery.code.duedate
- default.delivery.class.duedate
- default.delivery.gadgetclass.duedate

Due {2} {1}

getItRed
getItRed

The placeholder {2} is used for the due date and {1} is used for the best location.
3. For the Locations tab, added the following due date code to the GetIt Tile code table in the Front End subsystem
- default.fulldisplay.availabilty.due_date

Due {0}

The placeholder {0} is for the due date.

34

IN #10423
To configure the EBSCO adaptor:
1. Log on to the Back Office server.
2. Enter the following commands to edit the thirdnode-config.xml file.
fe_conf
vi thirdnode-config.xml
3. Add the following section to the file:
<adaptor_config>
<id>EbscoLocal</id>
<class_name>ebsco.local.EbscoDeepSearch</class_name>
<primo_services>
<primo_rank>false</primo_rank>
<primo_facets>false</primo_facets>
<primo_highlighting>true</primo_highlighting>
</primo_services>
<warmup>
<enable>false</enable>
</warmup>

<cache>
<enable>true</enable>
<batchSize>10</batchSize>
</cache>
<parameters>
<parameter>
<key>URL</key>
<val>http://eit.ebscohost.com/Services/SearchService.asmx/Search</val>
</parameter>

<parameter>
<key>USERNAME</key>
<val></val>
</parameter>
<parameter>
<key>PASSWORD</key>
<val></val>
</parameter>

<parameter>
<key>DB</key>
<val></val>
</parameter>
<parameter>
<key>TIMEOUT</key>
<val>30000</val>
</parameter>

35

IN #10423
<parameter>
<key>port</key>
<val>1701</val>
</parameter>
<parameter>
<key>scope</key>
<val>none</val>
</parameter>
</parameters>

4. Make sure that you configure the following required parameters:

- USERNAME: Enter your EBSCO user name.

- PASSWORD: Enter your EBSCO password.
- DB: Enter a list of the short EBSCO database names separated by a comma. You can list a maximum of 15 database
For example: rlh,ahl,8gh,lxh,eoh,buh,rvh,oah,rfh,reh,vah,sbh,loh,jph,rph
5. Exit and save your changes to the file.
Note: In addition, this file must be updated on the FE server.
6. Log on to the Primo Back Office UI.
7. Enter the following fields in the Create a New Code Table Row section on the Primo Home > Advanced Configuration >
Tables > Third Node Adaptors code table page:
- Enabled: select this check box to enable the new adaptor.
- Code: Enter EbscoLocal.
- Description - Enter Ebsco Adaptor.
8. Click Create to add the adaptor to the table.

9. In the Primo Home > Ongoing Configuration Wizards > Views wizard, define a search scope that includes the new EBSC
adaptor.
This is done by selecting the Ebsco Adaptor check box in the Third Node Adaptors section on the Edit Search Scope pa
10. Deploy the view.

Note: The EBSCO API that the new adaptor uses does not return facets and support search by facets. If you blend the EB
adaptor with other scopes, a search on facets will not return any results from EBSCO. As noted in the release notes, it che
see if the user is signed-in before sending a request to EBSCO.

36