-
Notifications
You must be signed in to change notification settings - Fork 41
Closed
Labels
1 - RequestA request made by a member of the communityA request made by a member of the community2 - QueriesIssues that are related to the query builder or queries in generalIssues that are related to the query builder or queries in generalgeospecify
Milestone
Description
Description:
#5232 covered the new catalog numbering configurations based on the CollectionObjectType of the CO being created, but it did not explicitly mention how this should behave in the query builder.
Acceptance Criteria:
- When a user queries on 'Collection Object → Catalog Number' from any base table:
- If there is more than one
CollectionObjectTypein the current collection with differentCatalogFormatNumNamevalues, then a button with a gear should appear to the right (similar to the gear and mechanism to choose a custom table format/aggregation).- Upon clicking the gear, the user should see a list of
CollectionObjectTypeNamevalues, along with a list item that says "None" - The user should be able to pick from any of the COTs in the current collection
- The field should now enforce the field format present in the selected COT's
CatalogFormatNumNamefield - If the user selects "None" instead of a COT Name, no format should be enforced
- Upon clicking the gear, the user should see a list of
- If there is more than one
- Other fields should not have this capability at this time.
Metadata
Metadata
Assignees
Labels
1 - RequestA request made by a member of the communityA request made by a member of the community2 - QueriesIssues that are related to the query builder or queries in generalIssues that are related to the query builder or queries in generalgeospecify