I would like to use Tiddlywiki for Coding in Grounded Thory.
Coding here means to tag certain parts of a text.
For my example, in my interviews on "Neatness in Gardens" I have a tag
"Snail", I want to mark all sections of in the transkrips with this
tag. And then when i open this tag i want to see an overview of all
the section i marked with this tag.
I could just simply copy the whole trancript in a tiddler and copy
paste all the sections in which there is talked about "snails" into
the tiddly "snail". After a while a I would have all "snail" sections
of all lnterviews in the tiddly "snail"
But i would be nice to have it more dynamic:
That I can tag sections inside a tiddly. And then have all these
sections listed in the Tiddly of this tag, in such a way, that they
are linked to the original text tiddly and that by one click I can see
what is written before and after the tagged section.
Are there any plugins which can do that?
I hope I did formulate in english what i want to say in such a matter
that you understand it.
> But i would be nice to have it more dynamic: > That I can tag sections inside a tiddly. And then have all these > sections listed in the Tiddly of this tag, in such a way, that they > are linked to the original text tiddly and that by one click I can see > what is written before and after the tagged section.
I have noticed the use of hashtags in Twitter, perhaps they could it be used to mark up the text
Example;
Alex's garden was looking very neat. There were [[few leaves on his flowers]]#Snail and he was delighted.
or perhaps (few leaves on his flowers)#Snail * its unlikely that in natural grammer that ")#" would not be an error
I've set up an alert on Google Scholar for papers mentioning hashtags; there is a steady flow. They are becoming part of writing on the web.
I think it would be interesting to use have some support for parsing them in the wikifier. It would be usefull for making sense of Tweets..... but also I have got more into Twitter ... I have found myself using hashtags when writing notes. Recently I have been experimenting with ELS's gotoPlugin and Simon's NewHere. I type a hashtag -- or start to -- then if one popups up i add a newHere from that tiddler. Otherwise I keep typing and make a new hashtag, (or string of hashtags).
But also, wikifiing hashtags sends out a message that TW is current. No other wiki supports hashtag parsing .... to my knowledge
ALex
On 24 February 2012 15:11, Niklas Wagner <nikhilnik...@gmail.com> wrote:
> I would like to use Tiddlywiki for Coding in Grounded Thory.
> Coding here means to tag certain parts of a text.
> For my example, in my interviews on "Neatness in Gardens" I have a tag > "Snail", I want to mark all sections of in the transkrips with this > tag. And then when i open this tag i want to see an overview of all > the section i marked with this tag.
> I could just simply copy the whole trancript in a tiddler and copy > paste all the sections in which there is talked about "snails" into > the tiddly "snail". After a while a I would have all "snail" sections > of all lnterviews in the tiddly "snail"
> But i would be nice to have it more dynamic: > That I can tag sections inside a tiddly. And then have all these > sections listed in the Tiddly of this tag, in such a way, that they > are linked to the original text tiddly and that by one click I can see > what is written before and after the tagged section.
> Are there any plugins which can do that?
> I hope I did formulate in english what i want to say in such a matter > that you understand it.
> sincerely,
> Niklas wagner
> -- > You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. > To post to this group, send email to tiddlywiki@googlegroups.com. > To unsubscribe from this group, send email to tiddlywiki+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
On Friday, February 24, 2012 10:11:09 PM UTC+7, Niklas Wagner wrote:
> Coding here means to tag certain parts of a text.
Better to use the term "tagging" content then so it's clear in this context.
What I do is break a longer text down into smaller chunks, what I call "nodes", in such a way that it's easy to view the whole work in sequential, section/chapter whatever order.
However because the nodes are now individual tiddlers, they can also be "assembled for viewing" according to other criteria, including your topic tags.
> Better to use the term "tagging" content then so it's clear in this
> context.
very good, but what i mean is not tagging of tiddlers but tagging of
parts of tiddlers.
> What I do is break a longer text down into smaller chunks, what I call
> "nodes", in such a way that it's easy to view the whole work in sequential,
> section/chapter whatever order.
> However because the nodes are now individual tiddlers, they can also be
> "assembled for viewing" according to other criteria, including your topic
> tags.
Ho do you view it then in sequential order?
i think the problem with that is that certain parts of an text have at
the same time different interlocking tags:
Niklas: in my interviews on "Neatness in Gardens" I have a tag
"Snail", I want to mark all sections of in the transcripts with this
tag.
Alex: ((Alex's garden was looking very neat. There were ((few leaves
on his
flowers))#description and ((he was delighted))#emotion.
Niklas: Alex, Do you like Snails? I mean they ate all the leaves of
the your flowers.))#Snails
Perhaps we could think of the required outputs.....
| Code | Phrase | Contained in Tiddler |h | #description | "few leaves on his flowers" | [[Neatness in Gardens]] | | #emotion | "he was delighted" | [[Neatness in Gardens]] | | table showing coded phrases and locations|c
... then work out a how to produce the table
1) go to the tiddler store 2) find any tiddler that has any text surrounded by double single brackets and followed by a hash and put them into an array 3) output table
I think the Javascript RegEx Object might come in handy...
>> Better to use the term "tagging" content then so it's clear in this >> context.
> very good, but what i mean is not tagging of tiddlers but tagging of > parts of tiddlers.
>> What I do is break a longer text down into smaller chunks, what I call >> "nodes", in such a way that it's easy to view the whole work in sequential, >> section/chapter whatever order. >> However because the nodes are now individual tiddlers, they can also be >> "assembled for viewing" according to other criteria, including your topic >> tags.
> Ho do you view it then in sequential order?
> i think the problem with that is that certain parts of an text have at > the same time different interlocking tags:
> Niklas: in my interviews on "Neatness in Gardens" I have a tag > "Snail", I want to mark all sections of in the transcripts with this > tag. > Alex: ((Alex's garden was looking very neat. There were ((few leaves > on his > flowers))#description and ((he was delighted))#emotion. > Niklas: Alex, Do you like Snails? I mean they ate all the leaves of > the your flowers.))#Snails
> but what you could fill in a tiddler and define exactly with (()) what > should be displayed.
> -- > You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. > To post to this group, send email to tiddlywiki@googlegroups.com. > To unsubscribe from this group, send email to tiddlywiki+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
Sorry after i have finisht my master thesis i want to get into
JAvaskript and Tiddly, but now i dont have time for that. Can anybody
programm, what i have asked for ;)
:
tagging of parts of tiddlers, and seeing all tagged parts under the
tiddler with the title of that tag. also that both are syncronised.
On 29 Feb., 10:05, Alex Hough <r.a.ho...@gmail.com> wrote:
> Perhaps we could think of the required outputs.....
> | Code | Phrase | Contained in Tiddler |h
> | #description | "few leaves on his flowers" | [[Neatness in Gardens]] |
> | #emotion | "he was delighted" | [[Neatness in Gardens]] |
> | table showing coded phrases and locations|c
> ... then work out a how to produce the table
> 1) go to the tiddler store
> 2) find any tiddler that has any text surrounded by double single
> brackets and followed by a hash and put them into an array
> 3) output table
> I think the Javascript RegEx Object might come in handy...
> On 29 February 2012 03:04, Niklas Wagner <nikhilnik...@gmail.com> wrote:
> >> Better to use the term "tagging" content then so it's clear in this
> >> context.
> > very good, but what i mean is not tagging of tiddlers but tagging of
> > parts of tiddlers.
> >> What I do is break a longer text down into smaller chunks, what I call
> >> "nodes", in such a way that it's easy to view the whole work in sequential,
> >> section/chapter whatever order.
> >> However because the nodes are now individual tiddlers, they can also be
> >> "assembled for viewing" according to other criteria, including your topic
> >> tags.
> > Ho do you view it then in sequential order?
> > i think the problem with that is that certain parts of an text have at
> > the same time different interlocking tags:
> > Niklas: in my interviews on "Neatness in Gardens" I have a tag
> > "Snail", I want to mark all sections of in the transcripts with this
> > tag.
> > Alex: ((Alex's garden was looking very neat. There were ((few leaves
> > on his
> > flowers))#description and ((he was delighted))#emotion.
> > Niklas: Alex, Do you like Snails? I mean they ate all the leaves of
> > the your flowers.))#Snails
> > but what you could fill in a tiddler and define exactly with (()) what
> > should be displayed.
> > --
> > You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
> > To post to this group, send email to tiddlywiki@googlegroups.com.
> > To unsubscribe from this group, send email to tiddlywiki+unsubscribe@googlegroups.com.
> > For more options, visit this group athttp://groups.google.com/group/tiddlywiki?hl=en.
On Monday, March 5, 2012 8:52:23 PM UTC+7, Niklas Wagner wrote:
> Sorry after i have finisht my master thesis i want to get into > JAvaskript and Tiddly, but now i dont have time for that. Can anybody > programm, what i have asked for ;) > : > tagging of parts of tiddlers, and seeing all tagged parts under the > tiddler with the title of that tag. also that both are syncronised.
I am sure there are many people here who could do it (I couldn't), but unless you can find someone with the same desire to scratch that particular itch, you'll probably have to offer to pay for the work involved in developing such a custom plugin. If you indicate a willingness to do so, I would think you'd likely get followups via private email to discuss further details.
I wonder if there might be an opportunity in seeking some funding. Grounded Theory is not going to go away, a sound tool for coding data into a wiki could lead to more grounded theory practitioners using TW. It's a long tail...
When you've got time if you could post a more detailed description.
Alex
On 7 March 2012 03:28, HansBKK <hans...@gmail.com> wrote:
> On Monday, March 5, 2012 8:52:23 PM UTC+7, Niklas Wagner wrote:
>> Sorry after i have finisht my master thesis i want to get into >> JAvaskript and Tiddly, but now i dont have time for that. Can anybody >> programm, what i have asked for ;) >> : >> tagging of parts of tiddlers, and seeing all tagged parts under the >> tiddler with the title of that tag. also that both are syncronised.
> I am sure there are many people here who could do it (I couldn't), but > unless you can find someone with the same desire to scratch that particular > itch, you'll probably have to offer to pay for the work involved in > developing such a custom plugin. If you indicate a willingness to do so, I > would think you'd likely get followups via private email to discuss further > details.
> To post to this group, send email to tiddlywiki@googlegroups.com. > To unsubscribe from this group, send email to > tiddlywiki+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/tiddlywiki?hl=en.
On Mar 8, 12:20 pm, Alex Hough <r.a.ho...@gmail.com> wrote:
> When you've got time if you could post a more detailed description.
What should be described and who do you mean?
> > On Monday, March 5, 2012 8:52:23 PM UTC+7, Niklas Wagner wrote:
> >> tagging of parts of tiddlers, and seeing all tagged parts under the
> >> tiddler with the title of that tag. also that both are syncronised.
> I am sure there are many people here who could do it (I couldn't), but
> unless you can find someone with the same desire to scratch that particular
> itch, you'll probably have to offer to pay for the work involved in
> developing such a custom plugin. If you indicate a willingness to do so, I
> would think you'd likely get followups via private email to discuss further
> details.
right now i have no money for that.
also i am indetermined if i should tell the community all my ideas or
save them for when i have enough money to buy programmers free from
wagework ;)
On Friday, March 9, 2012 4:57:10 AM UTC+7, Niklas Wagner wrote:
> > I am sure there are many people here who could do it (I couldn't), but > unless you can find someone with the same desire to scratch that > particular itch, you'll probably have to offer to pay for the work > involved in developing such a custom plugin. If you indicate a willingness > to do so, I would think you'd likely get followups via private email to > discuss further details.
> right now i have no money for that.
> also i am indetermined if i should tell the community all my ideas or > save them for when i have enough money to buy programmers free from > wagework ;)
Sorry I don't understand that last bit - maybe try re-phrasing. "buy" = hire? "free from wagework?"
What possible disadvantage could there be in sharing your ideas? Developing them with others that might be interested here, refining what you're trying to accomplish.
You never know when someone will pop up in TWland with the same itch, and if they happen to be an experienced javascript hacker who could prototype a plugin in a spare afternoon. . .
Actually, I would think the basic approach in TiddlyWiki would be
wikilinks.
So, you would write about [[snails]].
Once you open the snails tiddler, you could easily find references.
So, if you wish, linking is a kind of tagging.
On top of that you could still use tagging for whole tiddlers.
What's missing is the ability to list references in the context of the
sections (or paragraphs) where they occur.
As of today, using Erics's RelatedTiddlersPlugin from http://tiddlytools.com you could explore those related items in a minimal spanning tree.
A flavour of RelatedTiddlersPlugin available in tbGTD is x-plore (see
toolbar).
It allows you to see such trees for the four basic relations that
are...
* tagged by
* tagging to
* referenced by
* linking to
Rather than (some special markup for)#hashtags, I would think it were
much better to index and detect either the paragraphs or the sections
where #hashtags (/or [[TiddlyLinks]]) are contained, e.g.
{{{
!A Section
Some #hashtag in the context of [[some topic]].
!Another Section
Foo bar baz.
}}}
...or...
{{{
A paragraph containing #aHashTag and some subsequent contextual
content.
This would be a new paragraph not consituting the direct context of
the above hashtag.
}}}
Besides, the syntax you suggested earlier does not so much conform to
the general use of #hashtags all over the web
So, what I think is missing is a way to index...
* [[TiddlyLinks]]
* #Hashtags
* @Tags
* <AnyPrefix>AnyTag
And then be able to list them highlighting the tag in the context of
the...
* paragraph
* section
* tiddler
....wherein they are contained.
Once you click on a list item (or a dedicated link in relation to it),
you would want the ability to jump to the corresponding element where
the [[TiddlyLink]] or #hashtag or @tag is contained. For whole
tiddlers and sections that would already work (with the additional
requirement of SectionLinksPlugin from TiddlyTools when it comes to
sections).
As for paragraphs, it would be required to first index all paragraphs
upon initial inspection when generating the list and then to open the
target element using a hijacked version of displayTiddler which
would...
# require a unique identifier for the target element to be addressed
# render the target element of the tiddler with a unique id
(checksum?) along with a special css class for highlighting it
# eventually jump to the target element upon opening
I remember that @Chris somewhere indexed all paragraphs in one of his
wikis. This would be a perfect starting point for implementing the
paragraph based solution.
All in all, this could be a perfectly generic HashTagsPlugin where not
only hashes but all kinds of prefixes could be used for indexing a
hash-tag-map.
For performance it might be beneficial to persist the hash-tag-map in
the browser memory and perhaps have it created upon startup and
updated on any tiddler change.
Eventually, some RegEx guru might be able to easily spot #hashtags in
tiddler bodies directly returning the section title (/ paragraph
checksum) to the surrounding function.
On Mar 13, 1:10 pm, Tobias Beer <beertob...@googlemail.com> wrote:
> As for paragraphs, it would be required to first index all paragraphs
> upon initial inspection when generating the list and then to open the
> target element using a hijacked version of displayTiddler which
> would...
> # require a unique identifier for the target element to be addressed
> # render the target element of the tiddler with a unique id
> (checksum?) along with a special css class for highlighting it
> # eventually jump to the target element upon opening
uique ID (checksum)?
If you change one bit in a paragraph the checksum will change ... all
references are broken, if they are not dynamically rewritten. Linking
from external sources to one of your paragraphs imo will allways be
broken after some time. (1/2 a year, 1-2 years ...)
A TW tiddler permalink with some text eg: see: "end of the text" imo
will be more stable. Due to the nature of TW you'll need to keep the
tiddler title ;)
Well, actually perhaps the most simple paragraph count actually does
the trick.
> all references are broken, if they are not dynamically rewritten.
What I have in mind is to...
* either keep a full index of hash tags updated in memory
* dynamically load something more resembling search results
> Linking from external sources to one of your paragraphs imo
> will allways be broken after some time. (1/2 a year, 1-2 years ...)
I guess the example of Chris implementation wasn't really a good one.
It might have given the idea that url-style-references and permalinks
to paragraphs were in the focus... which they are not.
So actually, what I have in mind really is a kind of search function
with perhaps a smart pre-indexing and the ability to show search
results in the context of a surrounding paragraph or section.
These search results could be invoked via macro or even by detecting
hashtags when rendering a tiddler and turning them into links, which
upon click would open a corresponding (shadow-)tiddler with the search
results for this hashtag... all on the fly and most certainly updated
with any tiddler updates.
Thinking this further, calling such a shadow tiddler via permalink
would actually display hashtag search results when a tw loads... how
cool would that be?
Again, hashtag prefixes might be any in a number of different
prefixes, not just #. So when you click on a hashtag, you might want
to not only see other contents where it is contained but also other
hash tags that start by the same prefix... perhaps by opening a slider
containing a list of all alike hastags, perhaps again as a slider
which - when opened - immediately displays the search results for a
given hashtag.
you warn not to include your plugin jet, should i experiment with it in my ongoing tagging(GroundedTheory Categorizing)and give you feedback, or even load some of my ongoing wok to some tiddlyspace? That we can dicuss it there?
> Well, actually perhaps the most simple paragraph count actually does > the trick.
>> all references are broken, if they are not dynamically rewritten.
> What I have in mind is to... > * either keep a full index of hash tags updated in memory > * dynamically load something more resembling search results
>> Linking from external sources to one of your paragraphs imo >> will allways be broken after some time. (1/2 a year, 1-2 years ...)
> I guess the example of Chris implementation wasn't really a good one. > It might have given the idea that url-style-references and permalinks > to paragraphs were in the focus... which they are not.
> So actually, what I have in mind really is a kind of search function > with perhaps a smart pre-indexing and the ability to show search > results in the context of a surrounding paragraph or section.
> These search results could be invoked via macro or even by detecting > hashtags when rendering a tiddler and turning them into links, which > upon click would open a corresponding (shadow-)tiddler with the search > results for this hashtag... all on the fly and most certainly updated > with any tiddler updates.
> Thinking this further, calling such a shadow tiddler via permalink > would actually display hashtag search results when a tw loads... how > cool would that be?
> Again, hashtag prefixes might be any in a number of different > prefixes, not just #. So when you click on a hashtag, you might want > to not only see other contents where it is contained but also other > hash tags that start by the same prefix... perhaps by opening a slider > containing a list of all alike hastags, perhaps again as a slider > which - when opened - immediately displays the search results for a > given hashtag.
> Tobias.
> -- > You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. > To post to this group, send email to tiddlywiki@googlegroups.com. > To unsubscribe from this group, send email to tiddlywiki+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
I don't remember from when on exactly jQuery was part of the TiddlyWiki core... but what version are you running? Perhaps you need to upgrade if possible. Theoretically, I could write my code without jQuery, but I'd muuuuch rather not. So I guess, I need to put up a dependency some core version.
On Apr 7, 5:54 am, Tobias Beer <beertob...@googlemail.com> wrote:
> I don't remember from when on exactly jQuery was part of the TiddlyWiki core... but what version are you running? Perhaps you need to upgrade if possible. Theoretically, I could write my code without jQuery, but I'd muuuuch rather not. So I guess, I need to put up a dependency some core version.
