Home › Blogs › Jim.Beach's blog

Specify 6.2.01 Released

Wed, 06/09/2010 - 19:13 — Jim.Beach

Specify 6.2.01 Released

We are pleased to release Specify 6.2.01 which addresses about two dozen known issues, and adds some new features. Agents can now be uploaded from WorkBench data sets as standalone data, and we have released a new utility application, the Specify Localizer, for editing and updating language translations of the text strings in the Specify application interface. Also in 6.2.01 we added a number of new tables and data fields to the Specify WorkBench database schema, making data in those fields available for uploading into Specify. The fields were added in response to user requests. This release obsoletes version 6.2.0.

Release Notes
Specify 6.2.01
9 June 2010

Bugs fixed:

  1. Preparation Type on Collection Object forms can now switch from form to grid view  2010-05-11 07:49:34 -0500  (Bugzilla 6276).
  2. Yellow warning shield icon no longer displays next to grid mode in Agent form  2010-05-10 15:08:49 -0500  (6316).
  3. Information Request will no longer try to 'send email on save' to an agent without an email address  2010-05-10 14:23:10 -0500  (6370).
  4. System pick lists fields were not exported and imported for use in Schema Localizer, now they are  2010-05-11 07:51:09 -0500  (6410).
  5. Exception no longer appears when ColletionObject (CO) RecordSet is dragged to a Georeference plug-in  2010-05-11 07:34:16 -0500  (6617).
  6. Exception no longer occurs when CollectionObject is added or deleted in grid mode under Project subform  2010-05-10 13:43:20 -0500  (6808).
  7. Canceling the return of a Preparation now re-enables the Return Loan button  2010-05-11 07:52:29 -0500  (7046).
  8. Can now save or delete a CO when auto number is turned on  2010-05-10 10:35:37 -0500  (7160).
  9. Information Request can now be dragged over RecordSet entries and work properly  2010-05-10 15:10:49 -0500  (7422).
  10. Naming a new collection the same as an existing collection now creates a new renamed collection  2010-05-05 10:19:00 -0500  (7466).
  11. BackupRestore application no longer remembers the wrong username on startup  2010-05-10 10:23:40 -0500  (7499).
  12. Canceling the IT credentials dialog for a downloaded database schema (version) update upon login no longer causes Specify to quit  2010-05-10 13:29:17 -0500  (7644).
  13. Resource Import/Export, with perms enabled, is inaccessible for some Full Access User  2010-05-06 08:53:38 -0500  (7679).
  14. Switching to a user that has performed a WorkBench DataSet upload no longer causes Specify to freeze  2010-04-26 02:44:51 -0500  (7784, 7927).
  15. Can now change the type of a report after initially saving it as a Report or Label  2010-05-13 12:38:10 -0500  (7850).
  16. WorkBench no longer spits an exception on clicking Google Earth button  2010-05-13 12:20:30 -0500  (7921).
  17. If the 'last selected node' preference setting points to a deleted node, the tree viewer no longer crashes on startup  2010-04-23 00:31:31 -0500  (7924).
  18. The taxon tree editor now checks HostTaxonID relationship to see if taxon nodes are deletable  2010-04-25 23:10:45 -0500  (7925).
  19. Can now open DataSet summary for Workbench  2010-04-27 06:27:03 -0500  (7930).
  20. If CatalogNumber doesn't have a formatter, an exception no longer occurs when it is selected in a query  2010-05-07 12:08:39 -0500  (7931).
  21. FixDBAfterLogin queries to check for duplicate GeoCoordinate and LocalityDetails no longer take a long time  2010-05-07 12:42:23 -0500  (7932).
  22. Tree data display screens are now disabled during tree updates that take place during WorkBench uploads  2010-05-12 09:58:21 -0500  (7937).
  23. WorkBench Mapper prevents Agent table data fields from mixing with other tables, Agent Import uploads work now like "Taxon Import Only" uploads  2010-05-11 14:40:40 -0500  (7938).
  24. Generating an invoice for Gifts no longer causes an exception  2010-05-13 12:14:46 -0500  (7941).
  25. If a report resource is imported as a label, it will stay as a label and not mutate into a report type  2010-05-13 14:07:07 -0500  (7943).

New Agent Feature:

Agents of any type are now supported in the WorkBench for uploading. The Uploader no longer assumes agents are persons when checking for duplication against existing agents in a Specify database.  Last Name fields labeled  ' xxx Last Name' where xxx=Collector, Author, Sender, etc. can be used for Group, Organization and Other names.

New Fields and Tables added to the Specify WorkBench schema

Table: Accession
New fields:

  1. PermitNumber 2 - 4.

Table: CollectionObject
New fields:           

  1. ObjectCondition
  2. Citation Title 1
  3. Citation Remarks 1
  4. Citation is Figured 1
  5. Citation Title 2
  6. Citation Remarks 2
  7. Citation is Figured 2
  8. YesNo3
  9. YesNo4
  10. YesNo5
  11. YesNo6

Table: Determination
New fields:

  1. SubspQualifier 1,2 and 3
  2. VarQualifier 1,2 and 3 (Three determinations now allowed instead of two.)

New Table: Field Notebook
New fields:

  1. Description
  2. EndDate
  3. Storage
  4. Name
  5. StartDate
  6. Owner First Name
  7. Owner Last Name
  8. Owner Middle Initials
  9. Owner Title

New Table: FieldNotebookPage
New fields:

  1. Description
  2. PageNumber
  3. ScanDate

New Table: FieldNotebookPageSet
New Fields:

  1. Description
  2. EndDate
  3. Method
  4. OrderNumber
  5. StartDate

Table: GeoCoordDetail
New Fields:

  1. GeoRefAccuracyUnits
  2. GeoRefDetRef
  3. GeoRefVerificationStatus
  4. Max Uncertainty
  5. Max Uncertainty Unit
  6. NoGeoRefBecause
  7. Original Coord System
  8. Protocol
  9. Source

New Table: GeologicTimePeriod
New Fields:

  1. Era
  2. Period
  3. Epoch
  4. Age

Note: when uploading GeologicTimePeriod data with CollectionObject data, at least one field from PaleoContext must be mapped, even though the PaleoContext columns don't need to be filled.

New Table: Journal   
New Fields:

  1. Journal Name

New Table: Lithostrat   
New fields:

  1. Super Group
  2. Litho Group
  3. Formation
  4. Member
  5. Bed

Note: when uploading Lithostrat data with CollectionObject data, at least one field from PaleoContext must be mapped, even though the PaleoContext columns don't need to be filled.

Table: Locality
New Fields:

  1. Citation Title 2 - 4
  2. Short Name
  3. Original Elevation Unit
  4. UtmDatum
  5. UtmEasting
  6. UtmNorthing
  7. UtmFalseEasting
  8. UtmFalseNorthing
  9. UtmOrigLatitude
  10. UtmOrigLongitude
  11. UtmScale
  12. UtmZone

New Table: OtherIdentifier
New Fields:

  1. Other Identifier 1
  2. Other Identifier Institution 1
  3. Other Identifier 2
  4. Other Identifier Institution 2
  5. Other Identifier 3
  6. Other Identifier Institution 3
  7. Other Identifier 4
  8. Other Identifier Institution 4

New Table: PaleoContext
New Fields:

  1. BottomDistance
  2. Direction
  3. DistanceUnits
  4. PositionState
  5. Remarks
  6. Text1
  7. Text2
  8. TopDistance