Help:Search - Revision history

Daniel Mietchen: /* Availability of New Pages in Search Results */

Daniel Mietchen — Thu, 23 Apr 2009 15:22:46 GMT

Availability of New Pages in Search Results

←Older revision		Revision as of 15:22, 23 April 2009
Line 7:		Line 7:
	All OpenWetWare content is updated by Google on a very regular basis. All changes are provided for Google on a nightly basis. Google then uploads the changed pages during their visits to OpenWetWare multiple times per week.		All OpenWetWare content is updated by Google on a very regular basis. All changes are provided for Google on a nightly basis. Google then uploads the changed pages during their visits to OpenWetWare multiple times per week.

-	One side effect of this is that new content introduced into OWW will not be accessible to searches. The latency between adding content and having it accessible via Google can as much as 2-3 days, depending on what time of day a change is made or a new page is added.	+	One side effect of this is that new content introduced into OWW will not be accessible to searches. The latency between adding content and having it accessible via Google can be as much as 2-3 days, depending on what time of day a change is made or a new page is added.

	==Using Search Results==		==Using Search Results==

Ricardo Vidal: /* Search Operator Guide */

Ricardo Vidal — Mon, 08 Sep 2008 00:52:26 GMT

Search Operator Guide

←Older revision		Revision as of 00:52, 8 September 2008
Line 25:		Line 25:
	==Search Operator Guide==		==Search Operator Guide==

-	{\| ~~border="1" bgcolor="#ffffff"~~	+	{\| {{table}}
	\|-		\|-
	! OPERATOR EXAMPLE		! OPERATOR EXAMPLE

Bill Flanagan: /* Search Operator Guide */

Bill Flanagan — Sun, 31 Aug 2008 03:46:25 GMT

Search Operator Guide

←Older revision		Revision as of 03:46, 31 August 2008
Line 29:		Line 29:
	! OPERATOR EXAMPLE		! OPERATOR EXAMPLE
	! FINDS PAGES CONTAINING...		! FINDS PAGES CONTAINING...
-	! ~~Example~~	+	! Try it!
	\|-		\|-
	\| enzyme genome		\| enzyme genome

Bill Flanagan: /* Search Operator Guide */

Bill Flanagan — Sun, 31 Aug 2008 03:34:23 GMT

Search Operator Guide

←Older revision		Revision as of 03:34, 31 August 2008
Line 115:		Line 115:
	type=search		type=search
	buttonlabel=Go		buttonlabel=Go
-	default=~~~nucleic acid~~	+	default=biology ~lab
	searchbuttonlabel=Search		searchbuttonlabel=Search
	</inputbox>		</inputbox>

Bill Flanagan at 03:31, 31 August 2008

Bill Flanagan — Sun, 31 Aug 2008 03:31:31 GMT

←Older revision		Revision as of 03:31, 31 August 2008
Line 1:		Line 1:
-	OpenWetWare.org uses Google's search engine to provide full text searching for our Wiki. All private wikis use the built-in MediaWiki search engine since, by design, all private wiki contents are not accessible to Google for indexing.	+	==OpenWetWare Search==

-	All ~~content~~ in ~~OWW is retrieved~~ by Google ~~on a very regular basis. All changes are provided~~ for ~~Google on a nightly basis. Google then uploads the changed pages during their visits to OpenWetWare multiple times per week~~.	+	OpenWetWare uses Google's search engine to provide full text searching for our Wiki. All private wikis use the built-in MediaWiki search engine since, by design, all private wiki contents are not accessible to Google for indexing.

-	~~Because~~ of this, new content introduced into OWW is not accessible to search. The latency between adding content and having it accessible via Google can as much as 2-3 days, depending on what time of day a change is made or a new page is added.	+	==Availability of New Pages in Search Results==

-	Google ~~returns~~ a ~~set of results within OWW pages: you will not have to move back-and-forth between OpenWetWare~~.~~org and~~ Google.~~com~~.	+	All OpenWetWare content is updated by Google on a very regular basis. All changes are provided for Google on a nightly basis. Google then uploads the changed pages during their visits to OpenWetWare multiple times per week.

-	~~Although Google is a global directory, OWW's search implementation uses features~~ of ~~Google search to limit the pages to those contained within OWW. One exception to~~ this is ~~the use of Google's 'define' operator specified below. Google~~ will ~~attempt~~ to ~~find a definition for the term specified within OpenWetWare~~.~~org. If this fails~~, ~~Google will insert~~ a ~~remote page including~~ a ~~definition into the search result~~ page.	+	One side effect of this is that new content introduced into OWW will not be accessible to searches. The latency between adding content and having it accessible via Google can as much as 2-3 days, depending on what time of day a change is made or a new page is added.

-	~~Since~~ OWW uses the same search term entry interface Google uses on the main Google search page, many of the same search operators available within the Google search box are available within ~~OWW~~.	+	==Using Search Results==
		+
		+	Google returns a set of results within OWW pages: you will not have to move back-and-forth between OpenWetWare and Google.com.
		+
		+	==Search Scope==
		+
		+	Although Google is a global directory, OpenWetWare's search implementation uses features of Google search to limit the pages to those contained within OpenWetWare. One exception to this is the use of Google's 'define' operator specified below. Google will attempt to find a definition for the term specified within OpenWetWare. If there is no definition available in in OpenWetWare, Google will insert a remote page including an appropriate definition into the OpenWetWare search result page.
		+
		+	==Search Operators==
		+
		+	Since OpenWetWare uses the same search term entry interface Google uses on the main Google search page, many of the same search operators available within the Google search box are available within OpenWetWare.

	Below is a list of the available ways to refine your search query. Feel free to try out any of the terms below in the example section for each term. Keep in mind: you can include any combination of these terms in a single query.		Below is a list of the available ways to refine your search query. Feel free to try out any of the terms below in the example section for each term. Keep in mind: you can include any combination of these terms in a single query.

		+	==Search Operator Guide==

	{\| border="1" bgcolor="#ffffff"		{\| border="1" bgcolor="#ffffff"

Bill Flanagan at 03:24, 31 August 2008

Bill Flanagan — Sun, 31 Aug 2008 03:24:09 GMT

←Older revision		Revision as of 03:24, 31 August 2008
Line 3:		Line 3:
	All content in OWW is retrieved by Google on a very regular basis. All changes are provided for Google on a nightly basis. Google then uploads the changed pages during their visits to OpenWetWare multiple times per week.		All content in OWW is retrieved by Google on a very regular basis. All changes are provided for Google on a nightly basis. Google then uploads the changed pages during their visits to OpenWetWare multiple times per week.

-	Because of this, new content introduced into OWW is not accessible to search. The latency between adding content and having it accessible via ~~our search engine~~ can as much as 2-3 days, depending on what time of day a change is made.	+	Because of this, new content introduced into OWW is not accessible to search. The latency between adding content and having it accessible via Google can as much as 2-3 days, depending on what time of day a change is made or a new page is added.

	Google returns a set of results within OWW pages: you will not have to move back-and-forth between OpenWetWare.org and Google.com.		Google returns a set of results within OWW pages: you will not have to move back-and-forth between OpenWetWare.org and Google.com.
Line 11:		Line 11:
	Since OWW uses the same search term entry interface Google uses on the main Google search page, many of the same search operators available within the Google search box are available within OWW.		Since OWW uses the same search term entry interface Google uses on the main Google search page, many of the same search operators available within the Google search box are available within OWW.

-	Below is a list of the available ways to refine your search query. Feel free to try out any of the terms below in the example section for each term.	+	Below is a list of the available ways to refine your search query. Feel free to try out any of the terms below in the example section for each term. Keep in mind: you can include any combination of these terms in a single query.

Bill Flanagan at 03:17, 31 August 2008

Bill Flanagan — Sun, 31 Aug 2008 03:17:30 GMT

←Older revision		Revision as of 03:17, 31 August 2008
Line 1:		Line 1:
		+	OpenWetWare.org uses Google's search engine to provide full text searching for our Wiki. All private wikis use the built-in MediaWiki search engine since, by design, all private wiki contents are not accessible to Google for indexing.
		+
		+	All content in OWW is retrieved by Google on a very regular basis. All changes are provided for Google on a nightly basis. Google then uploads the changed pages during their visits to OpenWetWare multiple times per week.
		+
		+	Because of this, new content introduced into OWW is not accessible to search. The latency between adding content and having it accessible via our search engine can as much as 2-3 days, depending on what time of day a change is made.
		+
		+	Google returns a set of results within OWW pages: you will not have to move back-and-forth between OpenWetWare.org and Google.com.
		+
		+	Although Google is a global directory, OWW's search implementation uses features of Google search to limit the pages to those contained within OWW. One exception to this is the use of Google's 'define' operator specified below. Google will attempt to find a definition for the term specified within OpenWetWare.org. If this fails, Google will insert a remote page including a definition into the search result page.
		+
		+	Since OWW uses the same search term entry interface Google uses on the main Google search page, many of the same search operators available within the Google search box are available within OWW.
		+
		+	Below is a list of the available ways to refine your search query. Feel free to try out any of the terms below in the example section for each term.
		+
		+
	{\| border="1" bgcolor="#ffffff"		{\| border="1" bgcolor="#ffffff"
	\|-		\|-

Bill Flanagan at 02:39, 31 August 2008

Bill Flanagan — Sun, 31 Aug 2008 02:39:19 GMT

←Older revision		Revision as of 02:39, 31 August 2008
Line 45:		Line 45:
	buttonlabel=Go		buttonlabel=Go
	type=search		type=search
-	default=enzyme OR genome	+	default=enzyme \| genome
	searchbuttonlabel=Search		searchbuttonlabel=Search
	\|align="right" cellspacing="5" cellpadding="5" frames="border" rules="all" \|<inputbox>		\|align="right" cellspacing="5" cellpadding="5" frames="border" rules="all" \|<inputbox>

Bill Flanagan at 02:38, 31 August 2008

Bill Flanagan — Sun, 31 Aug 2008 02:38:24 GMT

←Older revision		Revision as of 02:38, 31 August 2008
Line 38:		Line 38:
	</inputbox>		</inputbox>
	\|-		\|-
-	\| enzyme\|genome	+	\| enzyme<nowiki>\|</nowiki>genome
	\| Either the word enzyme or the word genome. The "<nowiki>\|</nowiki>" symbol does not need to be separated by spaces from adjacent words.		\| Either the word enzyme or the word genome. The "<nowiki>\|</nowiki>" symbol does not need to be separated by spaces from adjacent words.
	\|align="right" cellspacing="5" cellpadding="5" frames="border" rules="all"\|<inputbox>		\|align="right" cellspacing="5" cellpadding="5" frames="border" rules="all"\|<inputbox>

Bill Flanagan at 02:37, 31 August 2008

Bill Flanagan — Sun, 31 Aug 2008 02:37:40 GMT

←Older revision		Revision as of 02:37, 31 August 2008
Line 40:		Line 40:
	\| enzyme\|genome		\| enzyme\|genome
	\| Either the word enzyme or the word genome. The "<nowiki>\|</nowiki>" symbol does not need to be separated by spaces from adjacent words.		\| Either the word enzyme or the word genome. The "<nowiki>\|</nowiki>" symbol does not need to be separated by spaces from adjacent words.
-	\|align="right" cellspacing="5" cellpadding="5" frames="border" rules="all"~~<nowiki>~~\|~~</nowiki>~~<inputbox>	+	\|align="right" cellspacing="5" cellpadding="5" frames="border" rules="all"\|<inputbox>
	bgcolor=#E5F2FB		bgcolor=#E5F2FB
	width=20		width=20