List attributes currently display the full editing user interface for all values, existing or new. When using the hierarchy browser interface, the full browser interface is shown for existing values, which can be unwieldy.
An option is needed to render existing values as "minimized" bubbles ala relationship bundles.
This also doesn’t seem to work when the field is in a container. See “Treatment Materials” in this record: http://amnh2.whirl-i-gig.com:8084/index.php/editor/occurrences/OccurrenceEditor/Save/Screen70/occurrence_id/20601
The container is a completely different context. The revision was not intended to work here, as the change was only to a list of existing list values. If you don't want the full hierarchy browser here consider changing the rendering setting to something else. While it would be possible to have the hierarchy browser show/hide within the container, it has the potential to be messy as you never really know what other fields will be surrounding the hierarchy browser.
Isn’t the field a list of existing list values?
Ok, I wanted to make it a hierarchy because their list items were so long the were getting cut off. But I think they can deal with it. It will be fully visible on reports, displays.
In the context of a container, how would it work? Would we minimize it and have a button to show the hierarchy browser as needed? The difference between the container case and the plain-old-list-element case that is fixed is this:
• When it's just a stand-alone list element being rendered as a hierarchy browser, we show bubbles for existing items and the full browser for new ones. No problem. If you want to change the items just delete the existing ones. No need to allow editing of existing ones (which would require showing the hierarchy browser)
• For containers, we need to show the full container, and because the container has several values in it, you really do need to leave them all editable. If you didn't allow all elements in existing container values to be editable, then the only way to make changes would be to delete and recreate the entire container, which people understandably hate. For lists rendered as hierarchies editable = the hierarchy browser. If we render it as a text bubble then it's not editable... this is the problem.
I think we can disregard this for containers, at least for the purposes of amnh. I think I figured out a work-around that’s fine.