Evolution of fields

[giuse]

Hi, one of the aspect where JReview may improve is flexibility in fields, also with respect to other CCKs of competition that instead have many less review features than JReviews.

Here is a possible list of enhancements (maybe in multiple releases):

 

1) Multiple Field: a field that can store multiple values of the same field type with a min and max occurences. This is much needed because in current release when multiple values are required, you are forced to create multiple fields of the same type (field1, field2, ...) and that is a problem for search because you should look for a same value in all fields... Especially for related field it would be very welcome.

 

2) Field sets: the possibility of defining a set of fields that can be repeated. For example for a hiking trail listing, a field set could be "stops" that comprises [stop name, duration] and can be replicated multiple times. Maybe this feature is not that simple.

 

3) A field can be assigned to multiple field groups: now for all fields shared between listing types you have to define small field groups to be assigned to listing types. I am ending up with more that 15 field groups. If a field could be assigned to multiple fields, then it would be easier to define field groups, that, by the way, are shown in the frontend so having many fields groups with 1-2 fields each is not so nice looking.

Of course the system should check that a field does not appear multiple times in a listing type (but it's an easy check).

 

Cheers

 

Giuse

[sebkun]

This section is only visible with a valid subscription. If you have a valid subscription, please login.

[giuse]

This section is only visible with a valid subscription. If you have a valid subscription, please login.