Batch Identify Features

[acwhite211]

Fixes #7764

Had some free time over the weekend...

Implements the features described in the issue.

Adds a new Batch Identify workflow to Specify 7 so users can apply one determination to many Collection Objects at once (similar to Specify 6), with record selection by catalog number input or Record Set.

If multiple types with different trees:

Create record sets on-demand:

See records in read-only 'Browse In Forms':

Checklist

• Self-review the PR after opening it to make sure the changes look good and
  self-explanatory (or properly documented)
• Add relevant issue to release milestone
• Add pr to documentation list
• Add automated tests
• Add a reverse migration if a migration is present in the PR

Testing instructions

Added by @grantfitzsimmons:

For context, this is very useful for collections that often redetermine a range of specimens with the same determination. This has been requested by various invertebrate collections, most recently KU Entomology, to make it much faster to reidentify specimens.

For testing, make sure to test in a copy of KU Entomology's database alongside various databases, particularly those featuring complex configurations (multiple COTs, trees, etc.) to make sure we handle all reasonable cases.

• Open User Tools and verify that 'Batch Identify' now appears under the new 'Tools' heading (alongside 'Locality Update Tool')
• Click on Batch Identify and read the instructions present there. You can enter a list of catalog numbers or select a record set.
  • Enter a list of catalog numbers separated by commas and verify they are parsed correctly
  • Enter a list of catalog numbers separated by random text, space, prefixes, suffixes, etc. and confirm they are treated as separators
  • Enter a list of catalog numbers not in the database and verify numbers without objects are shown in a list
  • Enter a mixed list of both catalog numbers that exist and that don't exist and verify it is handled appropriately
  • Enter a list of catalog numbers that belong to the same taxon tree (via Collection Object Type) and verify you can proceed as expected
  • Enter a mixed list of catalog numbers that belong to different taxon trees (via Collection Object Types) and verify that you are asked to choose a taxon tree-set to continue with:
    
• Begin using Batch Identify using a Record Set and verify all records are added as expected (make sure it notifies the users of the collection object counts of each tree in the record set, so they can either fix it or select a different record set)
• Make sure that the Taxon query combo box restricts the search to only names matching the types selected (if only one type in the collection, it should use the default tree)
• Make sure a new current Determination matching what you have entered is created for all records in the 'Batch Identify' set.
• Make sure when adding one-to-many relationships (Determiners, Determination Citation) that it is handled correctly (via both a button and a subview)

[grantfitzsimmons]

-- Weekend review, not @ work --

I tweaked a few things here and there:

• Reorganized the user tools menu (added 'Locality Update Tool' under the same subheading)
• Used a new icon for the tool
• Removed unnecessary padding for the 'Determination' form
• Removed redundant/misleading information (catalog number + count, since it supports ranges)
• Improved dialog sizing (small at first, large when determining, small afterwards)
• Reordered dialog buttons to match elsewhere in the app
• Made record set creation optional
• Made CO records read-only in dialogs to prevent out of sync issues

I did quite a bit of testing and had no issues with the update component. All seems to be working as expected.

funchanges.mp4

@acwhite211 Let me know what you think and I can begin large-scale testing. Would be nice to have some automatic tests if we can add them! Let me know how I can help.

[grantfitzsimmons]

Need to handle the case where there are multiple possible object types ^

[acwhite211]

-- night time commit, not @ work --

I added a filter to prevent the user for using collection object of differing types in batch identify. The user is shown exactly which catalog numbers they entered that don't fit the type of the majority of collection objects that they entered.

Let me know if that looks good, or if we want a different solution.

[acwhite211]

-- late night commit, not @ work --

I added support for CatalogNumberAlphaNumByYear catalog number formats, ex. "2025-0001". I'll need to do some more testing sometime to make sure this didn't slow down the live catalog number resolving api too much.

[acwhite211]

-- night time commits, not @ work --

Had some time to make a few commits tonight:

• I reverted the code blocking collection objects of differing types.
• Added functionality to verify record set that the user selected has collection objects of the same tree. If it doesn't, it notifies the users of the collection object counts of each tree in the record set, so they can either fix it or select a different record set.
• Did some code reorganization on the back-end.
• Added some initial unit tests on the front-end and back-end.

[grantfitzsimmons]

• Open User Tools and verify that 'Batch Identify' now appears under the new 'Tools' heading (alongside 'Locality Update Tool')
• Click on Batch Identify and read the instructions present there. You can enter a list of catalog numbers or select a record set.
  • Enter a list of catalog numbers separated by commas and verify they are parsed correctly
  • Enter a list of catalog numbers separated by random text, space, prefixes, suffixes, etc. and confirm they are treated as separators
  • Enter a list of catalog numbers not in the database and verify numbers without objects are shown in a list
  • Enter a mixed list of both catalog numbers that exist and that don't exist and verify it is handled appropriately
  • Enter a list of catalog numbers that belong to the same taxon tree (via Collection Object Type) and verify you can proceed as expected
  • Enter a mixed list of catalog numbers that belong to different taxon trees (via Collection Object Types) and verify that you are asked to choose a taxon tree-set to continue with:
• Begin using Batch Identify using a Record Set and verify all records are added as expected (make sure it notifies the users of the collection object counts of each tree in the record set, so they can either fix it or select a different record set)
• Make sure that the Taxon query combo box restricts the search to only names matching the types selected (if only one type in the collection, it should use the default tree)
• Make sure a new current Determination matching what you have entered is created for all records in the 'Batch Identify' set.
• Make sure when adding one-to-many relationships (Determiners, Determination Citation) that it is handled correctly (via both a button and a subview)