[Dev-flock] Consumer Gadget rendering test for Make IT Fair

[wesa aapro]

Hi,

Was the research you did manually entered, or was some aspect of node,
> label, relationship or social impact issue automated in some way?
> After this experience, do you have any advice or plans for automation?


All information is manually entered using Consumer Gadget admin interface. I
think this is pretty common problem when working with researchers: We
receive Word documents written by FinnWatch, who actually just dig out the
important stuff from longer documents, written by the other organizations.

We are trying to get the researchers understand structural ethical
information and find out a better way to communicate. I believe the
researchers create their own mindmaps of the related issues, but eventually
flatten them as unparsable long documents.

At the moment we have to communicate through examples over the current user
interface. I believe the more interface examples we have, the better I can
explain the underlaying information model?

Are shorter labels always shortened because of redundancy within the
> context? Are there other rules? For performance we might want to store
> short labels anyway, but I was just curious about the extent of logic
> neede were that to be automated.
>

Not just because or redundancy, but because of limited space on mobile
screen. The rendering logic uses long labels only when showing the first
node, since it should state the context.



Wesa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/dev-flock/attachments/20080929/b2a10094/attachment.htm