[ENG-9805] Service Brands should be listed alphabetically, and include service type #11543
+16
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…s like it is not used drafts/id/metadata) for prepints in browser url so for get request is is redundant get default_license_id on draft registration creation (to get for FE after creation) and also for GET/ request to get it on drafts/id/metadata request
…nique provider types
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ticket
Purpose
Branding entries in the OSF Admin interface are difficult for admins to navigate because the list is unordered and does not indicate which service (Preprints, Collections, Registrations) each branding entry belongs to. This makes it hard to locate, confirm, and maintain branding—especially for clients who operate across multiple services (e.g., Character Lab). The lack of clarity increases setup time, introduces risk of misconfiguration, and forces admins to manually cross-reference services and branding values.
Changes
implement asc sorting for admin brand tab and showing brand related unique provider types
Side Effects
QE Notes
CE Notes
Documentation