Skip to content

Implement full support for auto-numbering, cross-collection incrementing #7678

@grantfitzsimmons

Description

@grantfitzsimmons

Describe the bug
When a new auto-incrementing field format is created in Specify, no corresponding records are created in the tables that are used to determine auto-numbering behavior. These tables are where Specify looks first (before falling back and auto-incrementing within the given scope):

Tables:

  • autonumberingscheme: This is the master table that defines each auto-numbering format or scheme. Each record describes how numbers are generated (e.g., format, prefix, increment rules).
  • autonumsch_coll: This table links a specific auto-numbering scheme to a particular collection.
  • autonumsch_dsp: This table links an auto-numbering scheme to a discipline.
  • autonumsch_div: This table links an auto-numbering scheme to a division.

Function:

  • Each "auto-numbering scheme" defines the rules for how numbers are created (what the starting number is, if there’s a prefix, and how numbers increment).
  • Each collection, division, or discipline can have its own auto-numbering scheme, so numbering can be customized for different parts of the organization. A single format can be shared across multiple levels.
  • When a new record is created, Specify looks up the correct scheme and automatically assigns the next available number according to the rules.

This structure enables users (currently) to set an auto-numbering sequence to one that is functional across collections. This enables a single catalog numbering scheme to be used for all Collection Objects in an entire database per-format, not just in the collection.

Denmark is using this approach already and it has been requested by other large member institutions like CSIRO.

Problem: We are not creating records in these tables anymore when using the field format editor. That leaves users unable to setup custom auto-numbering schemes that support cross-collection numbering properly. This is a requirement for many large institutions (requested by Croatia, used by NHMD, desired by CSIRO)

Metadata

Metadata

Assignees

No one assigned

    Labels

    2 - App ResourcesIssues that are related to app resources2 - Database/SchemaIssues that are related to the underlying database and schema2 - User InterfaceIssues that are related to the user interface or user experience.

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions