Describe the bug

Currently, adding the "Age" field to a query creates a column displaying the CollectionObjectID. This identifier is likely unfamiliar to users and may cause confusion in the interface. This is not a catalog number (identifiable) or any other useful information.

To Reproduce

Steps to reproduce the behavior:

1. Build a "Collection Object" query in a paleo/invertpaleo/geology discipline's collection
2. Add the "Age" field to the query
3. Run the query
4. See that the Collection Object ID is all that is shown in the results

Expected behavior

Two possibilities cross my mind:

1. Show Searched Name & Range

The user should see the name and the range in each row rather than the CollectionObjectID

It should look like this when a name is selected:

and maybe it should show the name and range in the pick list itself.

If you enter a range rather than a name, the query results should show the range:

155-123 rather than CollectionObjectID, but the name in that case would not be necessary.

2. Show Object Age Range

Since we are calculating the age range for an object based on

• Absolute Age
• Relative Age
• Paleo Context (start and end)

We already are returning an age range. We could simply return that in the query builder to give the user an idea of how this search is being constructed.

Now it is

• Easy for the user to see the range associated with a given Chronostratigraphic name
• Easy for the user to understand why the results are being returned
• Simple for our team to test and verify that it is working as expected

System Information

https://calvertmarinemuseum20241114-production.test.specifysystems.org/specify/query/19/
spadmin, Invertebrates collection