User can designate one value of a repeated field as the "primary" value

User Story

A user can designate one value of a repeated field as the "primary" value via the radio button to the left of the field. The default value should be the first instance of a field. The primary value of a field should appear in basic search results, and should eventually become a limiting value in reporting (e.g. return only primary values vs. return all values).

For release 0.7, the user interface for repeatability should apply to the two fields currently implemented as repeatable: Acquisition>Acquisition Source and Cataloging>Responsible Department.

Related User Stories:

• <link to a related User Story>
• <link to a related User Story>
• ...

Derived Stories:

These related stories are created or derived from the User Story described on this page. For example, Service Stories describe bits of functionality that a service might need to provide in order for the User Story requirement to be fulfilled. These stories are used to create, plan, and track specific development tasks in JIRA. If development has begun on one of these stories, there should be a link into JIRA describing the story and the related development tasks.