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

Add support for entering a range for bulk carry forward #6276

Open
grantfitzsimmons opened this issue Feb 24, 2025 · 0 comments
Open

Add support for entering a range for bulk carry forward #6276

grantfitzsimmons opened this issue Feb 24, 2025 · 0 comments
Labels
2 - User Interface Issues that are related to the user interface or user experience. SeparationFrom6

Comments

@grantfitzsimmons
Copy link
Member

This issue outlines the requirements for implementing the series data entry functionality for collection objects (CO). The proposed feature is essential for users like the Louisiana State Arthropod Museum and KU Entomology, who require the ability to specify a range of catalog numbers during the carry forward process. Catalog numbers are allocated to particular groups/individuals for specific projects, and that means they cannot reliably or increment off the last highest catalog number in the collection.

Requirements

  1. Entering a Range

    • Users must be able to enter a range next to bulk carry forward (e.g., from 100 to 200) instead of just incrementing from the last highest catalog number.
  2. Validation of Catalog Numbers

  3. Proceeding with Bulk Carry Forward

    • If the validation passes for the first catalog object, the system must proceed with the bulk carry forward for the specified series.
  4. Record Set Creation

    • Upon successful completion of the carry forward process, the system must automatically create a record set named "Batch {first catalog #} - {last catalog #}".

Non-Functional Requirements

  • The system must ensure that the validation process is efficient and does not significantly delay the user experience.
  • Error messages must be clear and user-friendly to facilitate understanding and corrective actions by users.

**Requested By:**KU Entomology and Louisiana State Arthropod Museum

Discussed in #5969

Originally posted by grantfitzsimmons July 16, 2024
From #545 (comment)

  • Create CO.
  • Click Carry forward button
  • Set carry forward to the desired configuration.
  • Enter the range of bulk carry amount.
  • Click the "Save" button. This will carry forward the CO data while incrementing the catalog number within the range and save them.
    ( no need with new implementation - Before the bulk carry forward, the system will check if the category numbers already exist. For example, if COs with # 1 to # 3 and # 6 to # 7 exist, attempting to create a new CO starting at # 4 with a request for 4 carry forwards will throw an error: "Cat # in this range already exists." This validation is one of the save blockers.)
  • If the validation passes on the first collection object, the system will proceed with the bulk carry forward for the specified series.
  • Automatically, a record set named "Batch {first cat #} - {last cat #}" will be created when this process is completed.

Being able to enter a range is important to some users, such as the Louisiana State Arthropod Museum:

They ONLY number specimens before they go into the database, so there's no such thing as adding a number that doesn't exist. This means that they need to be able to enter a range (e.g. go from 100 to 200) rather than just incrementing from the last highest.

@grantfitzsimmons grantfitzsimmons added 2 - User Interface Issues that are related to the user interface or user experience. SeparationFrom6 labels Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 - User Interface Issues that are related to the user interface or user experience. SeparationFrom6
Projects
None yet
Development

No branches or pull requests

1 participant