Millennium 2014 SP6 Release Notes
Millennium 2014 SP6 Release Notes
Release Notes
Millennium 2014 SP6 is now in general availability.
Millennium 2014 SP6 is in general release.
With Millennium 2014 SP5, there is an OS requirement of Red Hat or Centos 6x or 7x. Libraries
running older versions will be blocked from upgrading.
Customers running Release 2011 1.5 or 1.6 or Millennium 2014 SP1-SP5 can self-upgrade to Millennium 2014 SP6 directly. Self-
upgrade instructions are available here.
CATALOGING
The User was not assigned permission 215 (Delete Resource Records) but Delete Resource
Button was enabled in Coverage Edit
Desciription: When the user who has not been assigned permission 215 found that Delete Resource
button was enabled. There was an incident with this site where one user who was not assigned this
permission, deleted resource record accidentally because this button was somehow enabled.
Reference: Mill-6304
Lucene search results limited by date are incorrect when date slice is based on MARC 008
Desciription: When the Lucene slice for document date is based on a variable length field rule
pointing to MARC 008, values for docdate in the index are just 4 characters (vs. 8 characters that
would appear in the index if the date was based on a record level rule). Because of this, Lucene
searches fail to return the correct records when a date limit is applied. Specifically, when an "after"
year limit is applied, records that have a docdate that is one year after the year specified in the limit
are not returned. (For example, if the search is limited to "after 2003," a record whose docdate is
2004 will not be returned. In order to return a record from 2004, the searcher would have to apply a
limit of "after 2002.")
Reference: Mill-5984
CIRCULATION
Bills waived at checkout not written to finespaid
Desciription: According to the manual on Adjusting Charges for Returned Billed Items, Millennium
should "write an entry for the automatically adjusted or removed charge to Fines Paid."
Reference: Mill-6100
If a checked out or held item has a volume field, it displays in duplicate in the patron record.
Desciription: The volume field should only display once in the checked-out/held item display in the
patron record, on the second line.
Reference: Mill-5970
Millennium Web Circ Report does not display complete hour periods.
Desciription: Millennium Web ALL CIRCULATION TRANSACTIONS by HOUR Reports
(Spreadsheet Interface) miss two hour periods which are the 1-2am and 2-3am and add the stats of
1-2am to 10-11am and 2-3am to 8-9pm hour periods, i.e.
Reference: Mill-6001
Patron with too many checked-out items causes Millennium client to crash
Desciription: After repeatedly viewing an item checked out a patron record with many checked out
items, Millennium session terminates.
Reference: Mill-6207
WEB ACCESS MANAGEMENT
Factiva not working with WAM if sslhost_replace option is enabled
Desciription: Unable to scroll past first set of results in Factiva database with wam_sslhost_replace
option set to true
Reference: Mill-6414
Login to WAM via SSO not working after a user logged in once.
Desciription: Login trough WAM URL to SSO server is getting 404 after local cache is set in. Normal
services through the SSO-proxy server are supposed to work, particularly if you setup your stored
WAM urls to use the SSO-proxy domain name.
Reference: Mill-6212
Unable to access certain functions such as print, email and save when accessing articles in
the new LexisNexis platform. Also unable to limit search results
Desciription: LexisNexis is rolling out a replacement for LexisNexis Academic (Nexis Uni) that utilizes
WAM HTTP1.1 methods that are not supported by WAM, specifically PATCH. This will affect all our
academic libraries that use WAM to access LexisNexis Academic. Lexis is discontinuing support for
the old platform this January and will require all libraries to move to the new platform.
Reference: Mill-6316
Emerald database ejournals that have a / encoded in the name are showing broken links via
WAM
Desciription: Emerald database ejournals that have a / encoded in the name are showing broken
links via WAM. Error message reads - page not found.
Reference: Mill-5861
WEBPAC
Problems authenticating through SSO
Desciription: SSO logins with complicated referred URLs are breaking if the URL has multiple
redirects , generating 401 errors
Reference: Mill-6231
Pathfinder Pro's handling of apostrophes in resource URLs causes target searches to fail
Desciription: When a WebPAC user launches a query that includes a term with an apostrophe, and a
resource link URL uses the USERSEARCH field selector, the apostrophe in the URL is encoded
using an HTML character entity reference – ' – which breaks queries sent to many target resources.
Since the USERSEARCH field selector cannot be customized, there is no way for customers to
remove the character from the resource link URL or otherwise deal with it so the resources work.
(And USERSEARCH is the only option for links to resources from browse screens, so there is no
workaround.)
Reference: Mill-6188
WebPAC dumps when patrons with Thai characters in their names place requests
Desciription: When a patron with Thai characters in their name tries to place a request in the
WebPAC, they see a blank screen or a proxy error and WebPAC core dumps.
Reference: Mill-6196
Phrase index searches limited by location not showing results when query term includes ñ (n-
tilde)
Desciription: When a phrase index search is limited by location, WebPAC returns the correct number
of results, but the records don't display. The behavior appears to exist only when the original search
query includes a term that includes the ñ (n-tilde) character, and the site has the stand_spanish
general rule enabled in indexrules.
Reference: Mill-6029
Keywords Millennium, Release Notes, Supportal, Information, SP5, release, notes, upgrade
Solution Properties
Solution ID
181026124322015
Last Modified Date
12/17/2018 4:48 PM
Author
[email protected]