<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic SYSTEM "../../../../lib/pkp/dtd/helpTopic.dtd">
<!--
  * 000028.xml
  *
  * Aquesta traducció al català de l’OJS (versió 2.2.3) fou realitzada per Judith Rodriguez
  * amb el suport de la revista Athenea Digital i el Departament de Psicologia Social de la
  * Universitat Autònoma de Barcelona.
  * La traducció amplia la tasca previament realitzada per a la UOC i l'IEC incorporant les
  * eines de lectura i l’ajuda.
  *
  * Copyright (c) 2013-2019 Simon Fraser University
  * Copyright (c) 2003-2019 John Willinsky
  * Distributed under the GNU GPL v2. For full terms see the file docs/COPYING.
  *
  * Credits: http://pkp.sfu.ca/wiki/index.php?title=OJS:_Catalan_%28ca_ES%29
  *
  * Management Pages - Reading Tools - Contexts
  *
  -->

<topic id="journal/topic/000028" locale="ca_ES" title="Contexts" toc="journal/toc/000005" key="journal.managementPages.readingTools.contexts">
	<section>
		<![CDATA[<p>Each set of Reading Items is made up of individual tools (e.g., Related Studies, Online Forums, etc.) with each tool consisting of a number of relevant databases grouped into a context. These databases, and the contexts they are organized into, can be created, edited or deleted.</p><p><em>Metadata for items in a context</em>. The Journal Manager can alter the title of the tool. It also provides an option to determine whether the author's keywords (the default), the author's name (e.g., for use with Author's Other Works), or geographical indexing terms will be used for the searching of the database. Another option, used with Define Terms, allows the reader to select the search term by double clicking on any word in the text of the item being read in the journal. Journal Managers can use these options in building their own reading tools.</p><p><em>Edit searches for each tool</em>. Using Searches, the Journal Manager can edit or delete the search URL for each database in a tool, as well as reorder the databases that appear in the tool. For each database, a URL is provided that will enable the reader to learn more about the database, and a URL for that enables the search to be conducted. There are two types of searches that can be set up, a GET search, and if that will not work with the database, a POST search is also supported.</p>]]>
	</section>
	<section title="GET Searches">
		<![CDATA[<p>For GET searches, run a search and look at the resulting URL. E.g., on Google, a search for "FOOBAR" gives the URL</p><p><samp class="code">http://www.google.ca/search?hl=en&q=FOOBAR&meta=</samp></p><p>Replace the search term, FOOBAR, with the variable &#123;$formKeywords&#125;. When OJS encounters this variable, it will be replaced with the appropriate value from the item's metadata. This gives us a search URL of</p><p><samp class="code">http://www.google.ca/search?hl=en&q=&#123;$formKeywords&#125;&meta=</samp></p><p>for the RT. However, since the other parameters are unnecessary in this case, we can use a simplified URL of</p><p><samp class="code">http://www.google.ca/search?q=&#123;$formKeywords&#125;</samp></p><p>for the RT.</p>]]>
	</section>
	<section title="POST Searches">
		<![CDATA[<p>For POST forms, it is more complicated. Again, looking at Google, you can view the page's source, and notice<samp class="code">&lt;form action="/search" ...&gt;</samp>, giving us a starting base URL of<samp class="code">http://www.google.com/search</samp>. You can then look at each of the<samp class="code">&lt;input ...&gt;</samp> and<samp class="code">&lt;select ... &gt;</samp> elements in the form, and add them as<samp class="code">name=value</samp> pairs separated by<samp class="code">&</samp> to the end of the URL. The element that specifies the textbox that accepts user-entered text (in Google's case, named<samp class="code">q</samp>), should once again have a value of &#123;$formKeywords&#125;, which will be replaced with the appropriate value.</p><p>A somewhat easier way for POST forms is to copy the HTML source to a file, change<samp class="code">method=post</samp> to<samp class="code">method=get</samp> in the appropriate form field, and change the form's<samp class="code">action=</samp> value such that it is a complete URL, e.g.,<samp class="code">http://www.google.com/search</samp> rather than just<samp class="code">/search</samp>. You can then view the modified HTML file in your browser and use the GET method above to construct the URL.</p><p>As some search engines do not support GET queries, if you find that the above method does not work, you can enter POST form data in the "Search post data" field. If the example given above required that the data be posted, you would enter<samp class="code">http://www.google.com/search</samp> for the search URL and<samp class="code">q=&#123;$formKeywords&#125;</samp> for the post data.</p><p>Make sure you test the URLs make sure they work correctly, by replacing &#123;$formKeywords&#125; with a term in the URL and testing it to see if it shows the expected search results. Note that with POST forms this might not always be possible, depending on the site. For URLs that don't have proper search engines another possibility is to use Google and restrict by site. You can use a query like<samp class="code">site:mysite.com FOOBAR</samp> in Google to search for the term "FOOBAR" only within mysite.com. This is used in the current RTs for several sites.</p>]]>
	</section>
</topic>