User Supplied Metadata - Revision history

Dithyramble: /* What needs to be done */

2010-06-23T04:26:03Z

‎What needs to be done

Dithyramble: /* What needs to be done */

2010-06-23T04:24:02Z

‎What needs to be done

Dithyramble: /* What works */

2010-06-23T04:23:23Z

‎What works

Dithyramble at 04:22, 23 June 2010

2010-06-23T04:22:51Z

Dithyramble: /* What works */

2010-06-23T04:21:55Z

‎What works

Dithyramble at 03:40, 23 June 2010

2010-06-23T03:40:15Z

Dithyramble: /* Implementation */

2010-06-23T03:33:17Z

‎Implementation

Dithyramble: /* Implementation */

2010-06-23T03:32:10Z

‎Implementation

Dithyramble: /* The story from the user's point of view */

2010-06-23T03:31:08Z

‎The story from the user's point of view

Dithyramble: /* Implementation */

2010-06-23T02:58:34Z

‎Implementation

← Older revision		Revision as of 04:26, 23 June 2010
Line 34:		Line 34:
	== What needs to be done ==		== What needs to be done ==
	* Make <tt>org.creativecommons.learn.test.AddATag.testCheckThatResourceIsSearchableViaTag</tt> pass.		* Make <tt>org.creativecommons.learn.test.AddATag.testCheckThatResourceIsSearchableViaTag</tt> pass.
		+	* Write a test that the HTML form submits to a POST handler which adds a tag to the RdfStore. This code adds a tag: <tt>org.creativecommons.learn.Tag.add(taggerURI, resourceURI, tag);</tt>

← Older revision		Revision as of 04:24, 23 June 2010
Line 33:		Line 33:

	== What needs to be done ==		== What needs to be done ==
−	* Make testCheckThatResourceIsSearchableViaTag pass.	+	* Make <tt>org.creativecommons.learn.test.AddATag.testCheckThatResourceIsSearchableViaTag</tt> pass.

@@ Line 27: / Line 27: @@
 == What works ==
-Look in the branch <pre>add_tagging_form</pre> (at time of writing, this pointed to [http://gitorious.org/discovered/repo/commit/a2af4aea3270e4a663abc2eb89c310e1ab5148c8 a2af4aea3270e4a663abc2eb89c310e1ab5148c8]).
+Look in the branch <tt>add_tagging_form</tt> (at time of writing, this pointed to [http://gitorious.org/discovered/repo/commit/a2af4aea3270e4a663abc2eb89c310e1ab5148c8 a2af4aea3270e4a663abc2eb89c310e1ab5148c8]).
 * We can add a tag to the RdfStore and retrieve it, using the bean api for both adding and retrieving. (Nothing crazy-special.)

← Older revision		Revision as of 04:22, 23 June 2010
Line 34:		Line 34:
	== What needs to be done ==		== What needs to be done ==
	* Make testCheckThatResourceIsSearchableViaTag pass.		* Make testCheckThatResourceIsSearchableViaTag pass.
−
−	~~== What remains to be done ==~~

@@ Line 27: / Line 27: @@
 == What works ==
-In the branch <pre>add_tagging_form</pre> ([http://gitorious.org/discovered/repo/commit/a2af4aea3270e4a663abc2eb89c310e1ab5148c8 a2af4aea3270e4a663abc2eb89c310e1ab5148c8])
+Look in the branch <pre>add_tagging_form</pre> (at time of writing, this pointed to [http://gitorious.org/discovered/repo/commit/a2af4aea3270e4a663abc2eb89c310e1ab5148c8 a2af4aea3270e4a663abc2eb89c310e1ab5148c8]).
-* "Add a tag"
+* We can add a tag to the RdfStore and retrieve it, using the bean api for both adding and retrieving. (Nothing crazy-special.)
 == What remains to be done ==

← Older revision		Revision as of 03:40, 23 June 2010
Line 24:		Line 24:

	So there'll be a bit of a code that runs whenever you ask DiscoverEd to perform a crawl. During the crawl, when we are inserting information about a particular URL into the Lucene database, this bit of code looks in all the Jena triple stores for any tags associated with that URL. It then inserts these tags into Lucene as well. In the parlance of Lucene, it adds a new column (or you could say, a new kind of field). The column is named something like 18__dct_subject. The number 18 signifies the user who submitted a tag via the brightly colored box mentioned above. It then adds a new field to the Lucene document associated with the URL we're crawling.		So there'll be a bit of a code that runs whenever you ask DiscoverEd to perform a crawl. During the crawl, when we are inserting information about a particular URL into the Lucene database, this bit of code looks in all the Jena triple stores for any tags associated with that URL. It then inserts these tags into Lucene as well. In the parlance of Lucene, it adds a new column (or you could say, a new kind of field). The column is named something like 18__dct_subject. The number 18 signifies the user who submitted a tag via the brightly colored box mentioned above. It then adds a new field to the Lucene document associated with the URL we're crawling.
		+
		+	== What works ==
		+
		+	In the branch <pre>add_tagging_form</pre> ([http://gitorious.org/discovered/repo/commit/a2af4aea3270e4a663abc2eb89c310e1ab5148c8 a2af4aea3270e4a663abc2eb89c310e1ab5148c8])
		+
		+	* "Add a tag"
		+
		+	== What remains to be done ==

← Older revision		Revision as of 03:33, 23 June 2010
Line 23:		Line 23:
	We want to ensure that this new tag appears whenever anybody now or in the future chances upon the search result in question using this particular installation of the DiscoverEd search engine. Here's how the engine will do that. From time to time, a webmaster asks his copy of DiscoverEd to "crawl" — that is, to download copies of web pages from the internet and put their text, and other information about them, into the search engine's Lucene database. We want to make sure that the user-submitted tag is included among that information we store in Lucene.		We want to ensure that this new tag appears whenever anybody now or in the future chances upon the search result in question using this particular installation of the DiscoverEd search engine. Here's how the engine will do that. From time to time, a webmaster asks his copy of DiscoverEd to "crawl" — that is, to download copies of web pages from the internet and put their text, and other information about them, into the search engine's Lucene database. We want to make sure that the user-submitted tag is included among that information we store in Lucene.

−	So there'll be a bit of a code that runs whenever you ask DiscoverEd to perform a crawl. During the crawl, when we are inserting information about a particular URL into the Lucene database, this bit of code looks in all the Jena triple stores for any tags associated with that URL. It then inserts these tags into Lucene as well. In the parlance of Lucene, it adds a new column (or you could say, a new kind of field). The column is named something like 18__dct_subject. 18 signifies the user who submitted a tag via the brightly colored box mentioned above. It then adds a new field to the Lucene document associated with the URL we're crawling.	+	So there'll be a bit of a code that runs whenever you ask DiscoverEd to perform a crawl. During the crawl, when we are inserting information about a particular URL into the Lucene database, this bit of code looks in all the Jena triple stores for any tags associated with that URL. It then inserts these tags into Lucene as well. In the parlance of Lucene, it adds a new column (or you could say, a new kind of field). The column is named something like 18__dct_subject. The number 18 signifies the user who submitted a tag via the brightly colored box mentioned above. It then adds a new field to the Lucene document associated with the URL we're crawling.

@@ Line 19: / Line 19: @@
   result_uri, dct:subject, tag
-(Side note: The word "subject" above might confuse you a bit if you are into RDF. In RDF, "subject" usually means the subject of a triple (subject, predicate, object). In the Dublin Core terms (DCT), subject means a ''topic''. We use it to pick out the concept, 'is tagged with'.)
+(Side note: The word "subject" above might confuse you a bit if you are into RDF. In RDF, "subject" usually means the subject of a triple (subject, predicate, object). In the Dublin Core terms (DCT), subject means a ''topic''. We use it here to mean "is tagged with".)
 We want to ensure that this new tag appears whenever anybody now or in the future chances upon the search result in question using this particular installation of the DiscoverEd search engine. Here's how the engine will do that. From time to time, a webmaster asks his copy of DiscoverEd to "crawl" &mdash; that is, to download copies of web pages from the internet and put their text, and other information about them, into the search engine's Lucene database. We want to make sure that the user-submitted tag is included among that information we store in Lucene.
 So there'll be a bit of a code that runs whenever you ask DiscoverEd to perform a crawl. During the crawl, when we are inserting information about a particular URL into the Lucene database, this bit of code looks in all the Jena triple stores for any tags associated with that URL. It then inserts these tags into Lucene as well. In the parlance of Lucene, it adds a new column (or you could say, a new kind of field). The column is named something like 18__dct_subject. 18 signifies the user who submitted a tag via the brightly colored box mentioned above. It then adds a new field to the Lucene document associated with the URL we're crawling.

@@ Line 7: / Line 7: @@
 == The story from the user's point of view ==
-A moment a bit like this is fairly common. You've asked a search engine to tell you what it knows about a particular query; "sustainability water" for instance. When the engine returns with its listing of results, you see a particular result that could be categorized more effectively. You want to teach the engine a new fact about one of those ecological pages.
+A moment a bit like this is fairly common. You've asked a search engine to tell you what it knows about a particular query. When the engine returns with its listing of results, you see a particular result that could be categorized more usefully. You want to tell the search engine, bring up this result when the user searches for such-and-such a word.
 == Requirements ==

@@ Line 15: / Line 15: @@
 == Implementation ==
-The brightly colored box mentioned above is an HTML form. The POST handler which accepts the user's submission writes a new RDFa triple to the Jena quad store, consisting of four strings:
+The brightly colored box mentioned above is an HTML form. The POST handler which accepts the user's submission creates (if necessary) a new Jena triple store whose URI represents the person who filled in the form. The handler then inserts a new RDFa triple into this triple store:
-  submitter_uri, result_uri, dct:subject, tag
+  result_uri, dct:subject, tag
-Note that the word "subject" above might confuse you a bit if you are into RDF. In RDF, "subject" usually means the subject of a triple (subject, predicate, object). In the Dublin Core terms (DCT), subject means a ''topic''. We use it to pick out the concept, 'is tagged with'.
+(Side note: The word "subject" above might confuse you a bit if you are into RDF. In RDF, "subject" usually means the subject of a triple (subject, predicate, object). In the Dublin Core terms (DCT), subject means a ''topic''. We use it to pick out the concept, 'is tagged with'.)
 We want to ensure that this new tag appears whenever anybody now or in the future chances upon the search result in question using this particular installation of the DiscoverEd search engine. Here's how the engine will do that. From time to time, a webmaster asks his copy of DiscoverEd to "crawl" &mdash; that is, to download copies of web pages from the internet and put their text, and other information about them, into the search engine's Lucene database. We want to make sure that the user-submitted tag is included among that information we store in Lucene.
-So there'll be a bit of a code that runs whenever you ask DiscoverEd to perform a crawl. This code looks in the Jena quad store for any tags stored there. It then adds these tags to Lucene. In the parlance of Lucene, it adds a new column (or you could say, a new kind of field). The column is named something like 18__dct_subject. 18 signifies the user who submitted a tag via the brightly colored box mentioned above.
+So there'll be a bit of a code that runs whenever you ask DiscoverEd to perform a crawl. During the crawl, when we are inserting information about a particular URL into the Lucene database, this bit of code looks in all the Jena triple stores for any tags associated with that URL. It then inserts these tags into Lucene as well. In the parlance of Lucene, it adds a new column (or you could say, a new kind of field). The column is named something like 18__dct_subject. 18 signifies the user who submitted a tag via the brightly colored box mentioned above. It then adds a new field to the Lucene document associated with the URL we're crawling.