Task #568

Create a 'structured description' field

Added by Sam Boyer about 1 year ago. Updated about 1 year ago.

Status:Feedback Start date:04/12/2012
Priority:Normal Due date:
Assignee:- % Done:

80%
Category:dev Spent time: 0.50 hour
Target version:0.1

Description

Per the spec discussion over in Event, one of our key goals is to create some slightly more structured fields that are basically just a way of pulling out information that would otherwise just be jammed into the main description field. For example, "What should I bring?" is very a common question that needs addressing, and the answer deserves to be pulled out in a semi-structured way instead of being buried somewhere in a giant paragraph of general "description" text.

A lot of the way we implement this is still kinda up in the air; it's a bit predicated on some UX discussions around how we expect people to use this, to populate it, etc. For the purposes of v0.1, it's probably safe to think of it as a pair of text fields (prompt + response), and no limit on the number of these pairs that can appear. I think that kind of multi-field repetition is easier in D7 than it was in D6.

collection--filed-display-options.png (21.3 kB) Andrew Mallis, 04/20/2012 04:21 am

History

#1
Updated by Sam Boyer about 1 year ago

OK, i've taken a first stab at this - one that i think actually fulfills the barest of the functional specifications, though the UI provided is fairly horrible. i also haven't tested the efficacy of the approach, but...

http://dev.fga-events-dev.gotpantheon.com/admin/structure/types/manage/event/fields/field_moreinfo

so, we've got a field_collection field attached to the main event content type. the collection is itself an entity containing two fields - a 'prompt' (e.g., "What should people bring to this event?") and an 'info' field, where the answer to the prompt can be given. The prompt field is a taxo term reference, which means it operates using a pool of user-generated text strings. exactly what we want.

problem is, the widget seems to want to make itself editable not only at edit-time, but ALSO at view-time. i haven't checked the issue queue or tested to see if that's a perms thing (it probably is), but it's uncomfortable regardless. we may end up wanting a custom field + widget for this to really work well.

#2
Updated by Sam Boyer about 1 year ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 70

this is mostly resolved for v0.1, but i want to discuss it a bit more before totally checking it off.

#4
Updated by Andrew Mallis about 1 year ago

  • % Done changed from 70 to 80

set the display options on the event content type:

also changed the more info entity Q and A field labels and display for clarity.

--> Example node

Also available in: Atom PDF