Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Catalog number format not displaying correctly in search results #6239

Open
acbentley opened this issue Feb 14, 2025 · 3 comments · May be fixed by #6245
Open

Catalog number format not displaying correctly in search results #6239

acbentley opened this issue Feb 14, 2025 · 3 comments · May be fixed by #6245
Assignees
Milestone

Comments

@acbentley
Copy link

  1. Go to kufish production database on test panel - KUFish_2025_01_02_prod
  2. Enter a collection object with the tissue COT which has the catalog number format 2025-******
  3. After saving the record, perform a search for that record
  4. Note that in the search results, the catalog number does not display in the correct format - instead of 2025-00001, I see 000002025 and the tooltip says 2025

When reporting an issue on the production branch or any development version of Specify, please try to recreate the issue on the latest tagged release (v7) and indicate if it does not occur there, indicating a regression. This is a new feature so not possible

Expected behavior
The catalog number format and tooltip should be correct for each COT type

Screenshots

Image
Image

Crash Report

If the bug resulted in an error message, please click on "Download Error Message" and attach it here. If there is no error, please follow these instructions to download your System Information.

Please fill out the following information manually:

  • OS: [e.g. Windows 10] Windows 11
  • Browser: [e.g. Chrome, Safari] Chrome
  • Specify 7 Version: [e.g. 7.6.1] production
  • Database Name: [e.g. kufish] (you can see this in the "About Specify 7" dialog) KUFish_2025_01_02_prod
  • Collection name: [e.g. KU Fish Tissue] KU fish
  • User Name: [e.g. SpAdmin] abentley
  • URL: [e.g. https://ku_fish-v7.test.specifysystems.org/specify/workbench/215/]

Reported By
KU

Additional context
Database name or any other context about the problem here.

@grantfitzsimmons grantfitzsimmons added regression This is behavior that once worked that has broken. Must be resolved before the next release. and removed regression This is behavior that once worked that has broken. Must be resolved before the next release. labels Feb 14, 2025
@grantfitzsimmons
Copy link
Member

Following up on this issue, same database, same user.

https://kufish20250102prod-production.test.specifysystems.org/specify/query/188/

Image Image

@grantfitzsimmons grantfitzsimmons modified the milestones: 7.10, 7.10.1 Feb 14, 2025
@grantfitzsimmons
Copy link
Member

This is another bug similar to #6183, which means that multiple COT catalog numbers are not a complete feature until it is resolved.

@emenslin
Copy link
Collaborator

From #6095

Describe the bug
Introduced in #5485, if you have at least 2 different COT with different catalog number formats, if you query the catalog number without filtering by COT, the non default format is formatted like the default format. If you filter the query to sort the Cat # by the non default COT all results are then formatted properly.

To Reproduce
Steps to reproduce the behavior:

  1. Make at least 2 different COT with different cat # formats (or find a db with this already)
  2. Make sure each COT has a CO record
  3. Go to queries -> CO as base table
  4. Query on the cat # and COT -> name
  5. See results are all formatted with default format
  6. Add 'equal' filter on cat #
  7. Press the gear and select a non default format
  8. Query
  9. See results are all formatted based on their correct format

Expected behavior
Query results should always appear with their correct format

Screenshots
In this db paleontology is the default COT

01-16-2025__11-44.mp4

Please fill out the following information manually:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants