Skip to content

Batch Attachment Uploads unable to match to catalogNumber field with catalogNumberString format #8407

Description

@bronwyncombs

Describe the bug
A clear and concise description of what the bug is.

Batch attachment upload does not match appropriately named files to collection object records, when the collection is assigned the catalogNumberString format type.

Specify no longer seems to be able to match my photos to the corresponding collection objects. It reports "no match," even though the catalog numbers exist in the database and correspond to my file names.
I have successfully imported several batches of images in the past without any issues, so this problem has only appeared recently. However, I am still able to add images manually.

Note: the last upload was March 2025, running v7.11.4.

To Reproduce
Steps to reproduce the behavior:

  1. Go to collection with catalogNumberString format
  2. Attachments > Import > New
  3. Choose CO/catalogNumber path and add attachments with file names that correspond to CO records
  4. Save then Validate
  5. See unable to match

Expected behavior

v7.11.4
https://github.com/user-attachments/assets/f399e9e5-282f-4a5e-93a0-3387e11fcbb2

Screenshots

Image Image

Please fill out the following information manually:

  • OS: macOS
  • Browser: Chrome
  • Specify 7 Version: v7.12.0.7
  • Database Name: mhnf
  • Collection name: Zoology
  • User Name: spadmin
  • URL: mhnf20260807-v71207.test.specifysystems.org

Reported By
Musée d'histoire Naturelle Fribourg (1212)

Additional context
Jason:

Maybe it's related to the changes made in Show CatalogNumberString format (#7772), which would have been introduced in v7.12.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    2 - AttachmentsIssues that are related to attachmentsregressionThis is behavior that once worked that has broken. Must be resolved before the next release.

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions