Specify Solstice Release: 6.4.09

Release Notes
Specify 6.4.09
25 June 2012

The Specify 6.4.09 Solstice Release includes fixes for various reported issues. Updating to Specify 6.4.09 does not modify the Specify database schema, but all workstations sharing a common database need to upgrade to the new release level.

List of changes:

  1. In the Data Exporter application, the Build/Update button (properly) does not activate before the status is calculated.  2012-06-18  (Bugzilla 8857)
  2. In a Specify database installation with multiple Collections, the GUID field now correctly creates an LSID value with the appropriate Collection code.  2012-06-15  (8853)
  3. A query containing aggregated fields which finds a large number of matching records no longer displays an error message upon closing the results tab.  2012-06-15  (8837)
  4. When using the Uploader to bring WorkBench DataSets into Specify, a hidden RecordSet is created for each uploaded DataSet. Those hidden RecordSets are normally not used and are now deleted after 30 days. This does not affect the actual data records uploaded into Specify or the actual, visible WorkBench data sets. 2012-06-14  (8855)
  5. Display of the tree levels in all tree-structured data windows is now much faster. 2012-06-14  (8835)
  6. The Attachment Manager pop-up window no longer appears for users who were getting it for no good reason.  2012-06-13  (8808)
  7. The Specify WorkBench now flags unrecognized date formats.  2012-06-13  (8802)
  8. Creating a new botanical collection will now add default "Matchers" to Scatter Gather Reconcile for searching for specimen duplicate records in GBIF. 2012-06-06  (8683)
  9. Deleting a WorkBench completely removes all information associated with it and does not leave any lingering file residue. 2012-06-04  (8781)
  10. The Lifemapper "Show My Data" button now works correctly. 2012-06-01  (8657)
  11. Google Earth now works splendidly when called from within the Specify WorkBench. 2012-05-11  (7921)
  12. The Latitude/Longitude data form component now shows the correct Source format. 2012-05-11 (8795)