Designing a schema for content editors to select project names

Hi everyone! I’m trying to design a schema that will accept data from a source system and allow our content editors to make a choice as to which piece of data to show on our front-end website.
For example, I have a document type called Project. In our source system, a project can have a short name, a long name and an alias. For each project in the source system, I want to push all three fields into each Project document in Sanity to be read-only and have the content editors decide which version of the project name will be published to the website.
If none of the above meet the requirements, then they can choose an “Other” field that can be selected.

Attached is a sketch of what I had in my head from a UI perspective. Has anyone tried something similar? I’m presuming it’ll require a custom input component. Any tips for making this as simple as possible from a schema/UI perspective? Thanks!

Hey User! Seems totally possible. This is effectively a string field with a few tweaks: 1. It's getting the first three radio options from an external source and 2. It's got a single input field that's pretty much just a radio option with a

<TextInput>

primitive .
You're correct in that you'll need to use a custom input component here. If you're having trouble conceptualizing it, I can mock up one that has similar functionality.

Thanks that certainly seems simple. Schema wise, I couldn’t find an example of dynamically defining the list of strings. Is that what you’re suggesting?

Correct! I wrote a guide a few months ago that can take you through dynamically getting list options.

Wonderful, I’ll take a look! Thanks again!

You're welcome!

+10 points for great looking excalidraw wireframes!

Thanks I only discovered it recently but I’m loving it!

I never even knew about it. Super cool!