More (patternish) tags on explorations

[GoogleCodeExporter]

In as much detail as possible, please describe what you would like to see.

1. It would be nice to have extra (shall we call it) pedagogical info on an 
exploration via tags similar to "published" 
2. I have written a few and have somewhat taken different approaches to the 
feedback/design/patterns cf your Design Tips section (whence I have followed 
the links)
3. Maybe this request should be elsewhere (comment at the base of Design Tips 
section) to encourage conversation in the idea that the designer of an 
exploration could add more meta (crisply taggable) or discussion behind the 
motives of a particular exploration. Just a thought

What operating system are you using? Chromebook & Windows 7

Please provide any additional information below.

Original issue reported on code.google.com by paulmart...@gmail.com on 16 Mar 2014 at 8:20

• Merged into: #146

[GoogleCodeExporter]

I think that having more tags is a good idea. It strikes me that we could have 
the following categories of tags (and use them to implement search in the 
galleries):

 - the language the exploration is written in
 - the skill(s) the exploration is meant to teach
 - (others?)

This probably doesn't really cover what you meant by 'patternish' tags, though. 
Would you mind giving a couple of examples of such tags, and why they might be 
of interest to people who are browsing through explorations?

Another possible idea is to have a 'Talk page' or 'Notes page' for each 
exploration, similar to what is done for Wikipedia articles. The creator could 
use this space to explain the exploration's intent and design philosophy. What 
do you think of this idea?

Thanks!

Original comment by s...@seanlip.org on 19 Mar 2014 at 4:49

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Tag flavours:
(1) Learning Model Theory: There was a comment on another thread that the
appearance of an exploration's design can be "brambly". One reason is that
there are often exceptions that have to be accounted for that lead to a
clouding of the underlying simplicity of a learning approach trying to be
outlined.

For example, in my first Tree Identifying exploration I designed a Q and
multibranch answer pathway attempting to stick to a fairly shallow question
set so that a picture solution was quickly reached. This actually results
in some (inconsequential, maybe) inaccuracy & for the Evergreen version I
am taking a slightly different approach which is difficult to discern from
the 2d box layout. So I concur with your Talk page suggestion since I would
have been able to give a reference or two; this would be more useful than
the current "comment on save" model which is retrospective, and in my case
usually skipped.

By contrast I will quickly mention: the cascading flow chart (fig 2) from
the Seeley Brown & Burton "Buggy" paper (CogSci 2 1978 pp 155) on math
teaching & the Finite State Machine approach I experimented with in my Lift
example.

In conclusion, echoing the new "Making Sense of Data" Google course it
usually extends appreciation if a representation of data can be
re-interpreted in a slightly different (visual) way. However, an
alternative pithy structured (tag based) narrative of what the aim &
learning philosophy of the exploration at the outset would be more useful
and easier to implement ...

Original comment by paulmart...@gmail.com on 19 Mar 2014 at 5:36

[GoogleCodeExporter]

Thank you for the elaboration!

I do agree that having a talk page would be useful for this. I'll merge this 
into issue 146, which covers a similar idea, and will file a new issue for the 
'talk page' suggestion.

Original comment by s...@seanlip.org on 23 Mar 2014 at 7:41

• Changed state: Duplicate