• Selective purging has been added.
• Fields used for duplicate detection for authority and bib records are now configurable in Cataloging.ini. Patron overlay now supports matching on more than one field.
• Cataloging now handles multiple authority tables and multiple schemes (LC, Sears, etc.)

• Cataloging allows a user without access to delete selected bib records that belong to another organization.
• Find/Replace is slow. This was caused by how the implementation of operating on selected records had been handled in 1.5. Find/Replace is much faster in this release.
• Cataloging would hang when performing a Retrieve from MARC Magician. This was caused by a pointer being incorrectly set in the read buffer.
• When importing records using the Do Not Allow Duplicates flag in Step 3 of the Import, the duplicate records are not wtitten to Duplicates.txt in the ImportLogs\Bibliographic folder.
• Cataloging crashes when attempting to purge deleted patron who have open transactions. This occurred when Cataloging was in a view other than the patron view. Fixed by a revision to Cataloging.ini.
• Find/Replace may cause Cataloging to crash under certain circumstances. The immediate cause has been fixed and Find/Replace finishes in the example data. If a similar unhandled condition arises in the future, the exception will be handled and Find/Replace will complete with the message ‘At least 1 record has failed to update.’
• Select Authority dialog may hang. This was caused by a very long data stream in a 1xx field that was not handled by the scan grid.
• Find/Replace ignores the INACCESSIBLE_FIELDS keys in Cataloging.ini. This allowed Find/Replace to run on fields, such as the barcode (852#p)  and group (991#a) fields.
• During propagtion of authority data after an authority record has been saved, the subfields specified in AuthorityVerifier.ini REMOVEFROMMATCHING key are stripped from the bib fields.
• In a scoped environment, field 995 (Organization) in the bib record is not updated on import when the option Do Not Allow Duplicates is selected in Step 3.

• Circulation now supports centralized scheduling. Circulation will propagate CircSchd.cfg to the server on first run, then reads the file from the server thereafter. The Circulation schedule file is differentiated according to site and organization. The file is written into the Registry\Common folder using the following format: Site-Organization-CircSchd.cfg.REG. This allows different sites and organizations to use different schedules, while maintaining the global aspect of the schedule.
• Can now sort the columns in the Transaction display.
• In a scoped environment, ‘Renew All’ and ‘Return All’ functions work only on transactions of the current organization (as defined by organization_key in startup.ini). Selected transactions can always be renewed/returned, if the user has access.
• When email notification is turned on, the sender is no longer cc’d. If cc’ing is desired, multiple cc recipients can be defined in Global.ini.REG (the cc email addresses must be comma-separated).
• Circulation now handles multiple authority tables and multiple schemes (LC, Sears, etc.).

• The Group Hierarchy override flag was reversed in the original 1.6 release. The correct handling is as follows: ‘override=on’ means the group hierarchy will not be enforced; ‘override=off’ means the group hierarchy will be enforced.
• When adding a date column in the transaction view, if the transaction type does not include the data, the column will be empty rather than reflect today’s date.
• When returning as lost or damaged, the fine based on 852#9 will not be created if the value of the ‘generate’ key in the Fine Transaction section of Global.ini.REG in M3 Server\Registry\COMMON is equal to ‘no’.
• Circulation ignores repeating Global Recall in case of 365-day loan period.
• Expired reserves may not be removed from a patrons transactions. This can happen if a patron has both a reserve transaction and a hold, and the reserve is first in the list of transactions. The reserve transaction will not be expired the first time Circulation starts up after the reserve expiry date. Circulation now expires both transactions after the first start-up.
• Circulation may login slowly. This is caused by a very large transaction table and the query Circ sends to expire holds, bookings, and reserves. In SP1, the query has been optimized for performance.
• ‘View Library transactions’ returns transactions for all databases. In SP1, in order to get transactions for Equipment, it is necessary to switch the current database to Equipment.
• Status allows backdoor to transactions when the scanned patron has a privilege block (overdue, fine, etc.).
• Hold email message contains incorrect due date. The date is the original reserve due date, not the due date of the hold.
• In a scoped environment, Circulation ignores organization membership when converting reserves to holds.

• Inventory crashes on clicking Invalid Items and No Barcodes tabs. Caused by icons being turned on for these lists. The hasIcons key has been hardcode to off for the Invalid Items list, and the issue affecting No Barcodes has been fixed.
• During partial inventories, Inventory sometimes shows a discrepancy in the number of missing items on the Inventory Statistics page. This was caused by getting the total number of missing items for the range.
• Second title column in the Misplaced list repeats the title from the first line of the No Barcode list successively. Caused by memory error.
• Barcodes appended to Out-of-Sequence Items cause the count to increment incorrectly.
• Inventory may crash while the lists are being populated, if there is no range and a large number of barcodes are absent from the inventory. Caused by a memory access violation.

• In the case where the Scoping flag is off for the selected database, OPAC no longer sends queries with scope restrictions.
• The massive OR query with scope restrictions has been eliminated. This issue was introduced by fixes in OPAC to recognize organizations default scope restrictions. If all organizations are selected, OPAC now sends the query with no restrictions.

• Picture Manager inserts empty 996#a when using bitmaps. Bitmaps may not be moved into the Pictures folder.
• Picture Manager hangs on browsing a hierarchical folder structure that contains no files.

• In a scoped environment, if all organizations’ default scope restriction was set to unselected, Search Dialog deselected all restrictions. Search Dialog now allows the Startup.ini’s organization key to override the organization’s default scope restriction. The organization in Startup.ini is always selected, regardless of the organization’s default scope restriction.
• Organizations that have a relationship only to a database of type ‘online’ no longer appear in the list of restrictions.

• The Clear button does not work after the query is submitted.
• In a multi-database environment, when more than one database is selected in Preferences, the first database’s holding table is queried for all other databases. When you click the Other databases link, the wrong holdings will be attached to the bib records when you view details. 
• The login username and the site key are case-sensitive.
• ILL requires the presence of organization records in the Configuration table.
• Holding symbols will be handled as phrases. This prevents features, such as ILL, from failing because of spaces in the holding symbol.
• Bib-level availability is incorrectly set. If one or a few holdings are on loan or missing, but the remaining holdings are available, the graphic in the Record List displays as red.
•  When Renew, Reserve, and ILL links are all active, they overlap in the multiple holdings display.
• If you set a password on an installation that is different from the m3opac-setup password and modify that installation, when you click Save, you are prompted for the m3opac-setup password, followed by the installation password,  followed again by the m3opac-setup password. If you follow the correct sequence, this means at least three password entries. If not, it will require four or more.
• The Search button has been disabled for more than one click until results are displayed. This prevents multiple clicks from running the service into the ground.