Duplicating Information for Incidents
Michael Howden
Hey,
Just shifting conversation from:
http://eden.sahanafoundation.org/ticket/506
and
https://code.launchpad.net/~keitheis/sahana-eden/edentrunk/+merge/33323
to the email list (I would personally prefer that when more discussion is required on features/enhancements it happens on the main list to avoid looking in multiple places…)
I don’t think that duplicating information is the correct thing to do. Instead, we should allow incidents (and perhaps assessments) have multiple locations.
Possibly using the multiple select widget. Would this case issues for the mapping?
Cheers
Michael
Fran Boon
> Just shifting conversation from:
> http://eden.sahanafoundation.org/ticket/506
> and
> https://code.launchpad.net/~keitheis/sahana-eden/edentrunk/+merge/33323
> to the email list (I would personally prefer that when more discussion is
> required on features/enhancements it happens on the main list to avoid
> looking in multiple places…)
I don't think we can force that &, in fact, it's easier for people who
are using the Wiki/Tracker to see all info there.
If you do start an email thread about it, please copy the URL to the
thread into the Ticket/Wiki to ensure that all relevant discussion is
in one place.
> I don’t think that duplicating information is the correct thing to do.
The templating functionality is of much wider applicability & I don't
think the idea is for *all* fields to be copied across verbatim just
to put it to a second location.
The idea is to copy /some/ of the data then edit as-appropriate.
> Instead, we should allow incidents (and perhaps assessments) have multiple
> locations.
>Possibly using the multiple select widget.
The Locations widget is already a behemoth - I *really* don't want to
extend it right now for this kind of support.
You're free to log it as a feature request in Trac as I do see that it
is useful longer-term.
>Would this case issues for the mapping?
Longer-term. I don't think so.
Right now it would be a *lot* of extra work, just when we're already
*incredibly* overloaded on mapping issues...
F