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

COG Inheritance: Data Entry Form Display for Catalog Numbers #6312

Open
grantfitzsimmons opened this issue Mar 10, 2025 · 0 comments · May be fixed by #6320
Open

COG Inheritance: Data Entry Form Display for Catalog Numbers #6312

grantfitzsimmons opened this issue Mar 10, 2025 · 0 comments · May be fixed by #6320
Assignees
Milestone

Comments

@grantfitzsimmons
Copy link
Member

This issue addresses the enhancement of the data entry form for Collection Objects (COs) that belong to Collection Object Groups (COGs) when they lack an assigned catalog number and inherit the catalog number from the primary CO within their COG.

Display Logic for Catalog Numbers

  • When a CO is part of a COG and does not have a defined catalog number, the system should display the catalog number of the primary CO belonging to the parent COG as a placeholder in the catalog number field.

    Screen.Recording.2025-03-10.at.2.34.50.PM.mov

Logic Flow

  • The display logic will follow these conditions:
  • If a CO has no catalog number,
  • And the CO belongs to a COG,
  • And the COG has a designated primary CO child,
  • Then the catalog number of that primary CO child will be shown as a placeholder in the Catalog Number field.

User Interaction

  • Users should be able to override the placeholder by entering a new catalog number. Once a new value is entered, it should replace the placeholder, indicating that the catalog number is now user-defined.

Visual Indications

  • The placeholder should be visually distinct (e.g., grayed out) to indicate that it is an inherited value. The field must remain editable, allowing users to input a new catalog number.
@grantfitzsimmons grantfitzsimmons added this to the 7.10.3 milestone Mar 10, 2025
@CarolineDenis CarolineDenis self-assigned this Mar 13, 2025
@CarolineDenis CarolineDenis linked a pull request Mar 13, 2025 that will close this issue
6 tasks
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.

2 participants