Changeset 4487
- Timestamp:
- Sep 8, 2008, 10:52:34 AM (15 years ago)
- Location:
- trunk/doc
- Files:
-
- 24 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/src/docbook/admindoc/installation_upgrade.xml
r4477 r4487 39 39 <para> 40 40 This chapter is divided into four parts. First, the process of 41 upgrading a BASE 2server is described. Followed by set up of job41 upgrading a BASE server is described. Followed by set up of job 42 42 agents. (For these two first parts it is assumed that there is a 43 43 running server.) Then, the first time installation instructions 44 44 follows, and the chapter is concluded with information on how to 45 migrate data from a BASE 1.2.17 server to a BASE 2server.45 migrate data from a BASE 1.2.17 server to a current BASE server. 46 46 </para> 47 47 … … 49 49 The first time installation is only to be performed once, 50 50 optionally followed by a migration. The migration can only be done 51 to a pristine (empty) BASE 2 server with one exception; The51 to a pristine (empty) BASE version 2 server with one exception; The 52 52 migration can be restarted if it fails during the RawBioAssaysData 53 53 transfer. For all other failure points the migration has to be 54 restarted with an empty database. Migration from several BASE 155 installations to one BASE 2server is not supported.54 restarted with an empty database. Migration from several BASE 55 version 1 installations to one BASE server is not supported. 56 56 </para> 57 57 … … 122 122 you must also make sure that you are running Tomcat 6 or higher. 123 123 Earlier BASE versions only required Tomcat 5.5. If you are not 124 already running Tomcat 6 you need to upgrade. Other ser lvet124 already running Tomcat 6 you need to upgrade. Other servlet 125 125 engines may work if they implement the Servlet 2.5 and JSP 126 126 2.1 specifications. … … 192 192 <listitem> 193 193 <para> 194 Rename your current BASE 2installation <command>mv194 Rename your current BASE installation <command>mv 195 195 /path/to/base /path/to/base_old</command>. 196 196 </para> … … 494 494 <variablelist> 495 495 <varlistentry> 496 <term>Download and unpack a regular BASE 2distribution</term>496 <term>Download and unpack a regular BASE distribution</term> 497 497 <listitem> 498 498 <para> … … 737 737 <listitem> 738 738 <para> 739 BASE 2739 BASE 740 740 utilize <ulink 741 741 url="http://www.hibernate.org/">Hibernate</ulink> for … … 777 777 edit 778 778 your <filename><base-dir>/www/WEB-INF/classes/base.config</filename> 779 file. Uncomment the settings for Postgre sand779 file. Uncomment the settings for PostgreSQL and 780 780 comment out the settings for MySQL. 781 781 </para> … … 783 783 <note> 784 784 <para> 785 Postgre sversions prior to 8.2 have a non-optimal solution785 PostgreSQL versions prior to 8.2 have a non-optimal solution 786 786 for locking rows in certain situations. This may cause two 787 787 seemingly independent transactions to lock if they just 788 788 reference a common database row. This may happen, for example, 789 789 when importing raw data that have references to the same 790 reporters. The problem has been solved in Postgre s8.2.790 reporters. The problem has been solved in PostgreSQL 8.2. 791 791 </para> 792 792 </note> … … 815 815 <para> 816 816 If you choose to download the binary package, skip to the 817 next item. The rest of us, read on and compile BASE 2. If817 next item. The rest of us, read on and compile BASE. If 818 818 you downloaded a source distribution, unpack the 819 819 downloaded file <command>tar zxpf … … 980 980 url="http://base.thep.lu.se/chrome/site/doc/admin/extended-properties.html">document 981 981 discussing extended properties</ulink> available. If you 982 plan to perform a migration of a BASE 1.2 database you982 plan to perform a migration of a BASE version 1.2 database you 983 983 should probably not remove any extended properties 984 984 columns (this is not tested so the outcome is currently … … 1113 1113 <listitem> 1114 1114 <para> 1115 Happy BASEing. Now you can log on to your BASE 2server as1115 Happy BASEing. Now you can log on to your BASE server as 1116 1116 user <emphasis>root</emphasis> (use 1117 1117 the <emphasis>base_root_password</emphasis> from the … … 1123 1123 <para> 1124 1124 If you are planning to perform a migration of data from 1125 BASE 1.2.x please perform the steps in1125 BASE version 1.2.x please perform the steps in 1126 1126 <xref linkend="installation_upgrade.migration"/> before 1127 1127 doing anything else with your new BASE installation. … … 1159 1159 <para> 1160 1160 This is a limit of how many bytes of data that should be 1161 transfer ed per second when uploading files to BASE. Prefixes1161 transferred per second when uploading files to BASE. Prefixes 1162 1162 like k, M or G can be used for larger values, just like 1163 1163 described in the tab. The limit is per ongoing upload … … 1171 1171 <para> 1172 1172 Check this to not limit the transfer rate. In this case, the 1173 internet connection of the server is the limit.1173 Internet connection of the server is the limit. 1174 1174 </para> 1175 1175 </listitem> … … 1213 1213 <guilabel>About this server</guilabel> section on the login 1214 1214 page and in the about-dialog window. We recommend changing the 1215 default latin text to something meaningful, or remove it1215 default Latin text to something meaningful, or remove it 1216 1216 to hide the section completely. 1217 1217 </para> … … 1233 1233 an account on the particular BASE-server. This text is linked 1234 1234 to the <guilabel>Get an account!</guilabel> link on the login 1235 page. We recommend that the latin text is replaced with some useful1235 page. We recommend that the Latin text is replaced with some useful 1236 1236 information, or that it is removed to hide the link. 1237 1237 </para> … … 1250 1250 This text is linked 1251 1251 to the <guilabel>Forgot your password?</guilabel> link on the login 1252 page. We recommend that the latin text is replaced with some useful1252 page. We recommend that the Latin text is replaced with some useful 1253 1253 information, or that it is removed to hide the link. 1254 1254 </para> … … 1325 1325 <title>The disclaimer section</title> 1326 1326 <para> 1327 We have made extensive testing of the migration from BASE 1.2 1328 to BASE 2. To our knowledge the migration works but we cannot 1327 We have made extensive testing of the migration from BASE 1328 version 1.2 (BASE1.2) to BASE version 2 (BASE2). To our 1329 knowledge the migration works but we cannot 1329 1330 guarantee perfect functionality. The migration tool is 1330 1331 supplied as is and usage is done at your risk. We are 1331 1332 committed to solve migration problems at the level of 1332 transferring data from BASE 1.2 to BASE 2, but cannot resolve 1333 data loss issues in a running BASE 2 server due to imperfect 1333 transferring data from BASE1.2 to BASE2, but 1334 cannot resolve data loss issues in a running BASE2 1335 server due to imperfect 1334 1336 migration. When you start the migration tool you are required 1335 1337 to pass parameter <emphasis>"disclaimer_understood"</emphasis> … … 1349 1351 1350 1352 <para> 1351 Verify that your BASE 2installation is up and running before1353 Verify that your new BASE installation is up and running before 1352 1354 attempting migration. Preferably try to log in using the root 1353 1355 user through the web interface. … … 1355 1357 1356 1358 <para> 1357 Make sure your BASE 1359 Make sure your BASE1.2 runs with the latest 1358 1360 (<emphasis>pristine</emphasis>) schema 1359 1361 version, <emphasis>i.e.,</emphasis> the migration will only 1360 support an unmodified BASE 1.2 installation. If you have an out1361 of date schema version, please upgrade to the latest schema1362 using BASE 1.2 tools before migrating. If you have made local1363 changes to the BASE 1.2 schema you need to patch the BASE 21364 schema as well as make proper changes to the migration program.1365 If there are added columns to the reporter table in your BASE1366 1.2 database you need to transfer the additional information1367 after migration (even if you modified the BASE1368 2 <filename>extended-properties.xml</filename> file).1362 support an unmodified BASE1.2 installation. If you have 1363 an out of date schema version, please upgrade to the latest 1364 schema using BASE1.2 tools before migrating. If you 1365 have made local changes to the BASE1.2 schema you need 1366 to patch the BASE2 schema as well as make proper 1367 changes to the migration program. If there are added columns to 1368 the reporter table in your BASE1.2 database you need to 1369 transfer the additional information after migration (even if you 1370 modified the BASE2 <filename>extended-properties.xml</filename> file). 1369 1371 </para> 1370 1372 … … 1390 1392 <listitem> 1391 1393 <para> 1392 To transfer files from BASE 1393 behaviour), you must have file system access to BASE 1394 files, <emphasis>i.e.,</emphasis> the <filename1395 class="directory">/BASE 1.2/data</filename>1394 To transfer files from BASE1.2 (default migration 1395 behaviour), you must have file system access to BASE1.2 1396 files, <emphasis>i.e.,</emphasis> 1397 the <filename class="directory">/BASE 1.2/data</filename> 1396 1398 directory containing directories 1397 1399 <filename class="directory">rawdata</filename>, … … 1410 1412 <para> 1411 1413 Modify <emphasis>db1.*</emphasis> parameters to 1412 match your BASE 1414 match your BASE1.2 installation. 1413 1415 </para> 1414 1416 </listitem> … … 1418 1420 not the same parameter as 1419 1421 in <filename>base.config</filename>) to point to the 1420 directory containing the BASE 1422 directory containing the BASE1.2 files (defined in a 1421 1423 previous step above). 1422 1424 </para> … … 1425 1427 <para> 1426 1428 Set the <emphasis>pluginDir</emphasis> to point to 1427 the directory where your BASE 1429 the directory where your BASE1.2 plug-ins are 1428 1430 installed. The default is 1429 1431 <filename … … 1440 1442 Change the <emphasis>deletefiles</emphasis> setting 1441 1443 wisely. If you 1442 set <emphasis>deletefiles=yes</emphasis> all BASE 1443 1.2 files will be physically removed when copied to1444 BASE 2. Leave this options1444 set <emphasis>deletefiles=yes</emphasis> all BASE1.2 1445 files will be physically removed when copied to the 1446 BASE2 server. Leave this options 1445 1447 as <emphasis>deletefiles=no</emphasis> unless you 1446 1448 are absolutely sure of what you are doing. … … 1469 1471 <listitem> 1470 1472 <para> 1471 <emphasis>Optional, depends on your BASE 1473 <emphasis>Optional, depends on your BASE1.2 reporter 1472 1474 table.</emphasis> Additional columns (as compared with a 1473 1475 pristine database schema) in the reporter table in the 1474 BASE 1476 BASE1.2 schema are not transferred during migration. You 1475 1477 have to perform the transfer manually after 1476 1478 migration. Simply export the reporter information from 1477 BASE 1.2, and import the data into BASE 2. In BASE1.2: i)1479 BASE1.2, and import the data into the new BASE installation. In BASE1.2: i) 1478 1480 View the reporters, ii) Use `Get as tab-separated text` to 1479 1481 create a tab separated file (right click and save). In 1480 BASE 1482 BASE2, to import the file follow the instructions in 1481 1483 <xref linkend="reporters.import"/>. 1482 1484 </para> -
trunk/doc/src/docbook/admindoc/user_administration.xml
r4477 r4487 34 34 <title>Read <link linkend="project_permission"><xref linkend="project_permission" /></link></title> 35 35 <para> 36 This chapter contains important sinformation about the36 This chapter contains important information about the 37 37 permission system BASE uses. It is essential that an 38 38 administrator knows how this works to be able to set up … … 94 94 <para> 95 95 An id that is used to identify the user outside BASE (optional). 96 If a valu sis given it must be unique among all users.96 If a value is given it must be unique among all users. 97 97 </para> 98 98 </listitem> … … 158 158 or from a template, can be created if editing a new user. Select 159 159 <guilabel>- none -</guilabel> 160 if there should not be any home directory as occiated with the160 if there should not be any home directory associated with the 161 161 account. 162 162 </para> … … 194 194 password, contact information and other settings. It will 195 195 also reset all list filters, column configurations, etc. 196 when the user logs out. Normally, these settings are remem embered197 between log ins.196 when the user logs out. Normally, these settings are remembered 197 between log ins. 198 198 </para> 199 199 </listitem> … … 229 229 <helptext external_id="user.edit.contact" title="Edit user's contact information"> 230 230 <para> 231 Information about how to get in contact with the user that is as occiated231 Information about how to get in contact with the user that is associated 232 232 with the account. All fields on this tab are optional and do not necessarily 233 233 need to have a value but some can be good to set, like email or phone … … 344 344 <para> 345 345 This tab contains fields that hold various information about the user. There are 346 by default two fields in BASE 2but this could easily be changed by the346 by default two fields in BASE but this could easily be changed by the 347 347 server administrator. How this configuration is done can be read in 348 348 <xref linkend="appendix.extendedproperties" /> … … 357 357 </note> 358 358 359 These are the fields that are installed with BASE 2359 These are the fields that are installed with BASE 360 360 <variablelist> 361 361 <varlistentry> … … 377 377 <para> 378 378 Skype contact information, if the user has a registered 379 skype account. This field could be left empty.379 Skype account. This field could be left empty. 380 380 </para> 381 381 </listitem> … … 430 430 <listitem> 431 431 <para> 432 Opens a pop up window that allows you to select433 groups. In the pop up window, mark432 Opens a pop-up window that allows you to select 433 groups. In the pop-up window, mark 434 434 one or more groups and click on the &gbOk; 435 button. The pop up window will not list groups that435 button. The pop-up window will not list groups that 436 436 the user already is a member of. 437 437 </para> … … 443 443 <listitem> 444 444 <para> 445 Opens a pop up window that allows you to select446 roles. In the pop up window, mark445 Opens a pop-up window that allows you to select 446 roles. In the pop-up window, mark 447 447 one or more roles and click on the &gbOk; 448 button. The pop up window will not list roles that448 button. The pop-up window will not list roles that 449 449 the user already is a member of. 450 450 </para> … … 508 508 <guimenuitem>Users</guimenuitem> 509 509 </menuchoice> 510 page and select groups and roles in a pop up dialog.510 page and select groups and roles in a pop-up dialog. 511 511 The dialog lists all groups and roles that are currently 512 512 assigned as default. Use the <guibutton>Add groups</guibutton> … … 536 536 <para> 537 537 Groups in BASE are meant to represent the organizational structure of 538 a company or institu ion. For example, there can be one group for each538 a company or institution. For example, there can be one group for each 539 539 department and subgroups for the teams in the departments. 540 540 The group-membership is normally set when the user is added to BASE and … … 605 605 <guilabel>-none-</guilabel> 606 606 from the drop-down list if the group should not have any quota. 607 There are some presets of quotas that comes with the BASE 2607 There are some presets of quotas that comes with the BASE 608 608 installation, besides a couple with different size of total disk 609 609 space there are one called … … 666 666 <listitem> 667 667 <para> 668 Opens a pop up window that allows you to add669 users to the group. In the pop up window, mark668 Opens a pop-up window that allows you to add 669 users to the group. In the pop-up window, mark 670 670 one or more users and click on the &gbOk; 671 button. The pop up window will not list users that671 button. The pop-up window will not list users that 672 672 are already members of the group. 673 673 </para> … … 679 679 <listitem> 680 680 <para> 681 Opens a pop up window that allows you to add682 other groups to the group. In the pop up window, mark681 Opens a pop-up window that allows you to add 682 other groups to the group. In the pop-up window, mark 683 683 one or more groups and click on the &gbOk; 684 button. The pop up window will not list groups that684 button. The pop-up window will not list groups that 685 685 are already members of the group. 686 686 </para> … … 763 763 like reporters, the array lims and plug-ins. 764 764 This role can be proper for those users that are in 765 some kind of leading position over work groups or projects.765 some kind of leading position over work groups or projects. 766 766 </para> 767 767 </listitem> … … 901 901 <helptext external_id="role.edit.permissions" title="Edit role permissions"> 902 902 <para> 903 A role's permissions are defined for each item type within BASE 2. Set the903 A role's permissions are defined for each item type within BASE. Set the 904 904 role's permission on an item type by first selecting the item(s) in the list 905 905 and then tick those permissions that should be applied. Not all permissions -
trunk/doc/src/docbook/appendix/base.config.xml
r4477 r4487 59 59 <listitem> 60 60 <userinput>org.hibernate.dialect.PostgreSQLDialect</userinput> 61 for Postgre s61 for PostgreSQL 62 62 </listitem> 63 63 </itemizedlist> … … 79 79 <listitem> 80 80 <userinput>org.postgresql.Driver</userinput> 81 for Postgre s81 for PostgreSQL 82 82 </listitem> 83 83 </itemizedlist> … … 91 91 <listitem> 92 92 <para> 93 The connection URL that locates the BASE 2database. The exact syntax93 The connection URL that locates the BASE database. The exact syntax 94 94 of the string depends on the JDBC driver. Here are two examples which 95 95 leaves all other settings to their defaults: … … 101 101 <listitem> 102 102 <userinput>jdbc:postgresql:base2</userinput> 103 for Postgre s103 for PostgreSQL 104 104 </listitem> 105 105 </itemizedlist> … … 110 110 >MySQL</ulink> and 111 111 <ulink url="http://jdbc.postgresql.org/documentation/81/connect.html" 112 >Postgre s</ulink>.112 >PostgreSQL</ulink>. 113 113 114 114 … … 143 143 database is used. The exact meaning of catalog depends on the actual database. 144 144 For MySQL the catalog is the name of the database so this value is simply the 145 name of the dynamic database. Postgre sdoes not support connecting to multiple145 name of the dynamic database. PostgreSQL does not support connecting to multiple 146 146 databases with the same connection so this should have the same value as the 147 147 database in the <property>db.url</property> setting. … … 156 156 The name of the schema where the dynamic database used to store 157 157 analysed data is located. MySQL does not have schemas so this value should 158 be left empty. Postgre ssupports schemas and we recommend that the dynamic158 be left empty. PostgreSQL supports schemas and we recommend that the dynamic 159 159 part is created in it's own schema to avoid mixing the dynamic tables with 160 160 the regular ones. … … 204 204 <itemizedlist> 205 205 <listitem><userinput>/mysql-queries.xml</userinput> for MySQL</listitem> 206 <listitem><userinput>/postgres-queries.xml</userinput> for Postgre s</listitem>206 <listitem><userinput>/postgres-queries.xml</userinput> for PostgreSQL</listitem> 207 207 </itemizedlist> 208 208 See also <xref linkend="appendix.otherconfig.sql" />. … … 242 242 query. This setting exists because MySQL prior to 5.0.2 does not support scrollable 243 243 result sets, but loads all data into memory. This will result in out of memory 244 exception if exporting too many items at the same time. Postgre sdoes not have244 exception if exporting too many items at the same time. PostgreSQL does not have 245 245 this problem. Use: 246 246 247 247 <itemizedlist> 248 <listitem><para>0 for Postgre s</para></listitem>248 <listitem><para>0 for PostgreSQL</para></listitem> 249 249 <listitem> 250 250 <para> … … 286 286 <para> 287 287 The class name of the plug-in that acts as the authentication driver. 288 BASE ships with a simple plug in that checks if a user has a valid email288 BASE ships with a simple plug-in that checks if a user has a valid email 289 289 account on a POP3 server. It is not enabled by default. The class name 290 of that plug in is <classname docapi="net.sf.basedb.core.authentication">net.sf.basedb.core.authentication.POP3Authenticator</classname>.290 of that plug-in is <classname docapi="net.sf.basedb.core.authentication">net.sf.basedb.core.authentication.POP3Authenticator</classname>. 291 291 If no class is specified internal authentication is used. 292 292 </para> … … 300 300 Initialisation parameters sent to the plug-in when calling the 301 301 <methodname>init()</methodname> method. The syntax and meaning of this 302 string depends on the plug in. For the <classname docapi="net.sf.basedb.core.authentication">POP3Authenticator</classname>302 string depends on the plug-in. For the <classname docapi="net.sf.basedb.core.authentication">POP3Authenticator</classname> 303 303 this is simply the name or IP-address of the mail server. 304 304 </para> … … 404 404 Initialisation string sent to <methodname>SignalReceiver.init()</methodname>. 405 405 The syntax and meaning of the string depends on the actual implementation 406 that is used. Please see the javadoc for more information.406 that is used. Please see the Javadoc for more information. 407 407 </para> 408 408 </listitem> … … 565 565 for information about how to configure the secondary storage. Files are not 566 566 stored in the same directory structure or with the same names as in 567 the BASE file system. The internal structure may contain subdirectories.567 the BASE file system. The internal structure may contain sub-directories. 568 568 </para> 569 569 </listitem> … … 624 624 and automatically load and use the new code instead of the old code. 625 625 This setting is useful for plug-in developers since they don't have to 626 restart the web server each time the plug-in is recompiled.626 restart the web server each time the plug-in is recompiled. 627 627 <itemizedlist> 628 628 <listitem> … … 648 648 The path to the directory where jar-files for external plugins should be located 649 649 if they should be used with the auto-installer. All new plugins found in this directory, 650 or in any of it's sub directories, can be selected for installation, see650 or in any of it's sub-directories, can be selected for installation, see 651 651 <xref linkend="plugins.installation" />. 652 The plug in auto-installer will not be availble if this property isn't defined.652 The plugging auto-installer will not be available if this property isn't defined. 653 653 </para> 654 654 -
trunk/doc/src/docbook/appendix/coreplugins.xml
r4477 r4487 32 32 33 33 <para> 34 A categorized list of all plug ins installed with a pristine BASE35 installation. Some plug ins must be configured before use,34 A categorized list of all plug-ins installed with a pristine BASE 35 installation. Some plug-ins must be configured before use, 36 36 requirements are listed below and configuration samples are given 37 for for plug ins that supports/requires configurations. Use the37 for for plug-ins that supports/requires configurations. Use the 38 38 right-click menu of the mouse to download these XML files for 39 39 further import into BASE (see <xref … … 44 44 Contributed plug-ins are available at <ulink 45 45 url="http://baseplugins.thep.lu.se" >http://baseplugins.thep.lu.se 46 </ulink>. These plug ins are either developed outside the core team46 </ulink>. These plug-ins are either developed outside the core team 47 47 or require external non-Java compilers and tools. These packages 48 48 are excluded from the BASE package to make the installation … … 63 63 <emphasis>Since BASE 2.2, no configuration needed for the 64 64 Base1PluginExecuter but may be required for the underlying 65 BASE 1.2 plugins.</emphasis>65 BASE version 1.2 plug-ins.</emphasis> 66 66 </para> 67 67 </listitem> … … 81 81 82 82 <varlistentry> 83 <term>JEP filter plug in</term>83 <term>JEP filter plug-in</term> 84 84 <listitem> 85 85 <para> … … 140 140 <listitem> 141 141 <para> 142 Exports bioassay sets in different formats. See plug in142 Exports bioassay sets in different formats. See plug-in 143 143 definition in BASE for listing of supported formats. 144 144 </para> … … 189 189 <listitem> 190 190 <para> 191 Exports plug in configurations to an XML file.191 Exports plug-in configurations to an XML file. 192 192 </para> 193 193 <para> … … 238 238 in import mode from the reporter list view and from the 239 239 array design view and in verification mode from the array 240 design view. The plug in can only set the name and ID of240 design view. The plug-in can only set the name and ID of 241 241 the reporters, since the CDF file doesn't contains any 242 242 annotation information. Probesets already in BASE will not … … 253 253 <listitem> 254 254 <para> 255 Imports annotation to any annota ble item in BASE.255 Imports annotation to any annotatable item in BASE. 256 256 </para> 257 257 <para> … … 277 277 <listitem> 278 278 <para> 279 This plug in is used to import raw data from Illumina data279 This plug-in is used to import raw data from Illumina data 280 280 files. 281 281 </para> … … 318 318 <listitem> 319 319 <para> 320 Imports plug in configurations from an XML file.320 Imports plug-in configurations from an XML file. 321 321 </para> 322 322 <para> … … 591 591 <listitem> 592 592 <para> 593 Unpacks zip and jar file on the BASE 2's file system.593 Unpacks zip and jar file on the BASE's file system. 594 594 </para> 595 595 <para> -
trunk/doc/src/docbook/appendix/extended_properties.xml
r4477 r4487 43 43 <para> 44 44 The default <filename>extended-properties.xml</filename> that ships 45 with BASE is biased towards the BASE 1.2 setup for 2-spotted microarray45 with BASE is biased towards the BASE version 1.2 setup for 2-spotted microarray 46 46 data. If you want your BASE installation to be configured differently we 47 47 recommend that you do it before the first initialisation of the database. … … 69 69 Run the <filename>updatedb.sh</filename> script. New 70 70 columns will automatically be created, but the script can't delete columns that 71 have been removed, or modify columns that have changed data type. You will have to71 have been removed, or modify columns that have changed data type. You will have to 72 72 do these kind of changes by manually executing SQL against your database. Check your 73 73 database documentation for information about SQL syntax. … … 75 75 76 76 <tip> 77 <title>Create a parallel linstallation</title>77 <title>Create a parallel installation</title> 78 78 <para> 79 You can always create a new temporary parallel linstallation to check79 You can always create a new temporary parallel installation to check 80 80 what the table generated by installation script looks like. Compare the 81 81 new table to the existing one and make sure they match. … … 107 107 After installing BASE the default <filename>extended-properties.xml</filename> 108 108 is located in the <filename><basedir>/www/WEB-INF/classes</filename> directory. 109 This setup is biased towards the BASE 1.2 setup for 2-spotted cDNA arrays. 110 If you are migrating from BASE 1.2 you need to use the default setup. 109 This setup is biased towards the BASE version 1.2 setup for 110 2-spotted cDNA arrays. If you are migrating from BASE version 1.2 111 you <emphasis>must</emphasis> to use the default setup. 111 112 </para> 112 113 </listitem> … … 129 130 new columns. To remove or change existing columns you still have 130 131 to modify the original extended properties file. It is rather simple 131 to use this feature. Create a new subdirectory with the name132 to use this feature. Create a new directory with the name 132 133 <filename>extended-properties</filename> in the same directory as 133 134 the <filename>extended-properties.xml</filename>. In this directory … … 229 230 <entry> 230 231 The title of the extra property as it is displayed in client applications. 231 If not specified the value of the <sgmltag>name</sgmltag> attr biute is used.232 If not specified the value of the <sgmltag>name</sgmltag> attribute is used. 232 233 </entry> 233 234 </row> … … 385 386 <para> 386 387 If the link contains the character <constant>&</constant> it must be 387 escaped as <constant>&amp;</constant>. For example, to link to a Uni gene388 escaped as <constant>&amp;</constant>. For example, to link to a UniGene 388 389 entry: 389 390 </para> -
trunk/doc/src/docbook/appendix/incompatible.xml
r4477 r4487 51 51 <bridgehead>Type.BOOLEAN.parseString()</bridgehead> 52 52 <para> 53 This method now converts the empty string, "no", "0", and "false" (i ngoring case)53 This method now converts the empty string, "no", "0", and "false" (ignoring case) 54 54 to boolean <constant>false</constant>. A <constant>null</constant> 55 55 value as input still returns <constant>null</constant> as output. … … 98 98 <listitem> 99 99 <para> 100 The POSITION identification method will require a un qiue position number.100 The POSITION identification method will require a unique position number. 101 101 This value used to be an auto-generated sequence starting at 1. The other 102 102 identification methods will still do that, but when using the POSITION identification 103 103 method the only requirement is that the position value is a unique positive integer. 104 Client or plug-in code that depends on the position be eing a number between104 Client or plug-in code that depends on the position being a number between 105 105 1 and the number of features may fail if used with an array design using 106 106 the POSITION identification method. … … 148 148 <para> 149 149 A similar issue arises when inheriting annotations to a raw bioassay 150 which stems from a specific sub-array on a mu tli-array hybridization.150 which stems from a specific sub-array on a multi-array hybridization. 151 151 This raw bioassay should only inherit annotations from the labeled 152 152 extracts that are part of the same sub-array. For API compatibility … … 161 161 162 162 <para> 163 A related issue ari ese when querying labeled extracts and joining163 A related issue arise when querying labeled extracts and joining 164 164 the source events collection to use the linked hybridizations in 165 165 the query. Here is an example: … … 189 189 190 190 <para> 191 The good new is that the modif cations makes it possible to filter192 the query on used quantity and sub-array. See the javadoc for191 The good new is that the modifications makes it possible to filter 192 the query on used quantity and sub-array. See the Javadoc for 193 193 <classname docapi="net.sf.basedb.core">Hybridization</classname> 194 194 to get more information. … … 400 400 <para> 401 401 Changed to store information about plug-in parameters as XML in the 402 database instead of in the orig nal BASE1 plug-in definition file.403 Existing BASE 1 plug-ins must be re-configured before they can be402 database instead of in the original BASE version 1 plug-in definition file. 403 Existing BASE version 1 plug-ins must be re-configured before they can be 404 404 used. To do this: 405 405 </para> … … 418 418 <listitem> 419 419 <para> 420 Step through the configuration wizard for all BASE 1 plug-in420 Step through the configuration wizard for all BASE version 1 plug-in 421 421 configurations. You do not need to change any parameters. 422 422 Just click on the <guibutton>Next</guibutton> button … … 433 433 434 434 <para> 435 No longer provides a default mapping between BASE 1 and BASE 2 436 raw data columns. To solve this add a <guilabel>Formula</guilabel> 437 item with the same name as the BASE 1 column name and an expression 438 that picks the BASE 2 raw data property. For example: 435 No longer provides a default mapping between BASE version 1 and 436 BASE version 2 raw data columns. To solve this add 437 a <guilabel>Formula</guilabel> item with the same name as the 438 BASE version 1 column name and an expression that picks the BASE 439 version 2 raw data property. For example: 439 440 </para> 440 441 -
trunk/doc/src/docbook/appendix/menuguide.xml
r4477 r4487 31 31 <para> 32 32 This appendix covers all menu items in BASE, including submenus. You should use it as a map 33 to easily find your way through the menus. Some menu items are refer ing to other section of33 to easily find your way through the menus. Some menu items are referring to other section of 34 34 the documentation, that holds more information. The list of menu items is organized after 35 35 three different types, … … 72 72 <tbody> 73 73 <row> 74 <entry>Appearance of web client</entry>74 <entry>Appearance of web client</entry> 75 75 <entry> 76 76 <menuchoice> … … 199 199 </menuchoice> 200 200 </entry> 201 <entry>The home page of the BASE 2project</entry>201 <entry>The home page of the BASE project</entry> 202 202 </row> 203 203 <row> … … 221 221 </menuchoice> 222 222 </entry> 223 <entry>You are log ed out and redirected to the login page.</entry>223 <entry>You are logged out and redirected to the login page.</entry> 224 224 </row> 225 225 <row> … … 242 242 </entry> 243 243 <entry> 244 This updates the log ed in user's permissions. See244 This updates the logged in user's permissions. See 245 245 <xref linkend="project_permission.permissions" /> 246 246 </entry> … … 267 267 </entry> 268 268 <entry> 269 Restarts the program. Requires everyone, that were log ed in, to identify270 themsel fagain with username and password.269 Restarts the program. Requires everyone, that were logged in, to identify 270 themselves again with username and password. 271 271 </entry> 272 272 </row> -
trunk/doc/src/docbook/developerdoc/base_overview.xml
r4477 r4487 29 29 <chapter id="base_develop_overview"> 30 30 <?dbhtml dir="develop_overview"?> 31 <title>Developer overview of BASE 2</title>31 <title>Developer overview of BASE</title> 32 32 33 33 <para> -
trunk/doc/src/docbook/developerdoc/documentation.xml
r4477 r4487 35 35 36 36 <para> 37 This chapter is for those who intent to contribute to the BASE 2user documentation.37 This chapter is for those who intent to contribute to the BASE user documentation. 38 38 The chapter contains explanations of how the documentation is organized, what the 39 39 different parts is about and other things that will make it easier to know … … 43 43 The documentation is written with the docbook standard, which is a bunch of defined XML 44 44 elements and XSLT style sheets that are used to format the text. Later on in this chapter 45 is a reference, over those docbook elements that are recommended to use when writing BASE 245 is a reference, over those docbook elements that are recommended to use when writing BASE 46 46 documentation. Further information about docbook can be found in the on-line version of 47 47 O'Reilly's … … 64 64 <listitem> 65 65 <para> 66 The overview part contains, like the name says, an overview of BASE 2.67 For example an explanation about what the purpose with BASE 2is, the terms66 The overview part contains, like the name says, an overview of BASE. 67 For example an explanation about what the purpose with BASE is, the terms 68 68 that are used in the program and other general things that anyone that is 69 69 interested in the program wants/needs to know before exploring it further. … … 75 75 <listitem> 76 76 <para> 77 This part contains information that are relevant for the common BASE 2-user.77 This part contains information that are relevant for the common BASE-user. 78 78 More or less should everything that a power user role or an user role needs 79 79 to know be included here. … … 95 95 <listitem> 96 96 <para> 97 Documentation concerning the participation of BASE 2development should be placed97 Documentation concerning the participation of BASE development should be placed 98 98 in this part, e.g. coding standards, the java doc from the source code, how 99 to develop a plug in etc.99 to develop a plug-in etc. 100 100 </para> 101 101 </listitem> … … 108 108 <title>Getting started</title> 109 109 <para> 110 Before writing any documentation in BASE 2there are a couple of things, some110 Before writing any documentation in BASE there are a couple of things, some 111 111 rules and standards, to have in mind. 112 112 </para> … … 244 244 <title>Controlling chunking</title> 245 245 <para> 246 We have configured docbook to create a new sub directory for each246 We have configured docbook to create a new sub-directory for each 247 247 <sgmltag class="starttag">chapter</sgmltag> and a new output file for each 248 248 <sgmltag class="starttag">sect1</sgmltag> tag. In most cases this … … 281 281 attribute that can be used to identify the 282 282 element with. The value must be unique for the entire documentation. 283 Most of the elements that are used inside the BASE 2documentation do not283 Most of the elements that are used inside the BASE documentation do not 284 284 need to have an id if they do not are used in any cross references from other part of 285 285 the text. … … 356 356 tags. These texts will be exported to a XML-file at the same time as the 357 357 HTML-documentation is generated. The generated XML-file is compatible with the help 358 text importer in BASE 2and will be imported when running the update script or358 text importer in BASE and will be imported when running the update script or 359 359 installation script. 360 360 </para> … … 382 382 <para> 383 383 Is used to identify and to find a help text in the web client. 384 BASE2'sweb client already has several IDs to help texts defined,384 The BASE web client already has several IDs to help texts defined, 385 385 it could therefore be a good idea to have a look in the 386 386 program to see if there already is an external id to use for the … … 396 396 <para> 397 397 Is directly connected to the name/title property for a help text 398 item in BASE 2.398 item in BASE. 399 399 </para> 400 400 </listitem> … … 437 437 an image or an example, or a link to another chapter or 438 438 section. Put a <sgmltag class="starttag">nohelp</sgmltag> 439 tag around the problematic part to avoid it from be eing439 tag around the problematic part to avoid it from being 440 440 outputted to the help texts. 441 441 </para> … … 485 485 <filename class="directory">data</filename> 486 486 directory to the BASE-server's file system and then use the help text importer 487 plug in to import the help text items from that file.487 plug-in to import the help text items from that file. 488 488 </para> 489 489 … … 519 519 XsltProc but the compilation will most likely take much much longer time. 520 520 Therefore it's not recommended to be used when generating/compiling the 521 documentation in BASE 2.521 documentation in BASE. 522 522 </para> 523 523 </note> … … 533 533 <command>ant docbook</command>. This documentation is also generated with 534 534 <command>ant dist</command>, which will put the output files in the right location for distribution with 535 BASE 2.535 BASE. 536 536 </para> 537 537 </sect4> … … 636 636 </row> 637 637 <row> 638 <entry>Fi th level section</entry>638 <entry>Fifth level section</entry> 639 639 <entry> 640 640 <sgmltag class="starttag">sect5</sgmltag> … … 674 674 The name of a (Java) class. 675 675 <sgmltag class="attribute">docapi</sgmltag>-attribute 676 can be used to link the class to it's javadoc(only677 html-version). This is done by setting the attribute to the676 can be used to link the class to it's Javadoc (only 677 HTML-version). This is done by setting the attribute to the 678 678 package name of the class, like 679 679 <synopsis>net.sf.basedb.core</synopsis> … … 841 841 <title>Gui elements</title> 842 842 <para> 843 Docbook has some elements that can be used to symbolize guiitems in a program.843 Docbook has some elements that can be used to symbolize GUI items in a program. 844 844 Following list contains the ones that are most common in this document. 845 845 </para> … … 1057 1057 <listitem> 1058 1058 <simpara> 1059 The verbatim text is split tedinto several lines if the text contains1059 The verbatim text is split into several lines if the text contains 1060 1060 more then 80 characters. This could give the text an unwanted look and 1061 it's therefore recommended to manually insert new lines to have control l1061 it's therefore recommended to manually insert new lines to have control 1062 1062 over layout of the text 1063 1063 </simpara> … … 1065 1065 <listitem> 1066 1066 <simpara> 1067 We have added support for syntax highlight ning of program1067 We have added support for syntax highlighting of program 1068 1068 examples in the HTML version. To enable it add a 1069 1069 <sgmltag class="attribute">language</sgmltag> 1070 1070 attribute with one of the following values: <constant>java</constant>, 1071 <constant>xml</constant> or <constant>sql</constant>. The highlight ning engine1071 <constant>xml</constant> or <constant>sql</constant>. The highlighting engine 1072 1072 support more languages. To add support for those in docbook, change 1073 the <filename>customized.chunked.xsl</filename> file. The syntax highlight ning1073 the <filename>customized.chunked.xsl</filename> file. The syntax highlighting 1074 1074 engine doesn't handle markup inside the <sgmltag class="starttag">programlisting</sgmltag> 1075 1075 tag very well. You should avoid that. By default, java program examples … … 1270 1270 <sgmltag class="starttag">xref linkend=""</sgmltag> 1271 1271 </entry> 1272 <entry>Use this to linketo other parts of the document.</entry>1272 <entry>Use this to Link to other parts of the document.</entry> 1273 1273 </row> 1274 1274 <row> … … 1321 1321 classes in the Core API. To create the diagrams we use the community edition (version 12.5) 1322 1322 of a program called MagicDraw. This is a Java program and it should be possible 1323 to run it on any platform which has at least a Java 1.5 run time.1323 to run it on any platform which has at least a Java 1.5 run-time. 1324 1324 To get more information about MagicDraw and to download the program 1325 1325 go to their website: … … 1339 1339 Everything in MagicDraw has been organised into packages and 1340 1340 modules. At the top we have the <code>Core layer</code> and 1341 the <code>Data layer</code>. The <code>Java</code> module dis1341 the <code>Data layer</code>. The <code>Java</code> module is 1342 1342 for classes that related to the Java programming language, such 1343 1343 as <code>Map</code> and <code>Set</code> that are not pre-defined … … 1361 1361 <title>Classes</title> 1362 1362 <para> 1363 New classes should be added to one of the sub packages inside1363 New classes should be added to one of the sub-packages inside 1364 1364 the <code>Data layer/Classes</code> or <code>Core layer/Classes</code> 1365 1365 modules. It is very simple: … … 1369 1369 <listitem> 1370 1370 <para> 1371 Select the sub package in the overview and click with the right mouse button.1371 Select the sub-package in the overview and click with the right mouse button. 1372 1372 </para> 1373 1373 </listitem> … … 1437 1437 1438 1438 <para> 1439 To achi ve this we have slightly altered the meaning of some UML symbols.1439 To achieve this we have slightly altered the meaning of some UML symbols. 1440 1440 For example we use the access modified symbols (+, ~ and -) to indicate 1441 1441 if a property is updatable or not. … … 1691 1691 1692 1692 <para> 1693 New diagrams should be added to one of the sub packages inside1693 New diagrams should be added to one of the sub-packages inside 1694 1694 the <code>Data layer/Diagrams</code> or <code>Core layer/Diagrams</code> 1695 1695 modules. It is very simple: … … 1699 1699 <listitem> 1700 1700 <para> 1701 Select the sub package in the overview and click with the right mouse button.1701 Select the sub-package in the overview and click with the right mouse button. 1702 1702 </para> 1703 1703 </listitem> … … 1744 1744 <menuchoice><guimenuitem>Symbol properties</guimenuitem></menuchoice> 1745 1745 menu item. In the bottom of the 1746 pop up, use the <guilabel>Apply style</guilabel> selection list to select1746 pop-up, use the <guilabel>Apply style</guilabel> selection list to select 1747 1747 one of the predefined styles. 1748 1748 </para> … … 1757 1757 <listitem> 1758 1758 <para> 1759 External class: Use this style for related classes that are act aully part of1759 External class: Use this style for related classes that are actually part of 1760 1760 another diagram. This style will hide all information except the class name. 1761 1761 This style can be used for both data layer and core layer classes. … … 1789 1789 1790 1790 <para> 1791 Existing Javadoc documentation is available on line at:1791 Existing Javadoc documentation is available on-line at: 1792 1792 <ulink url="http://base.thep.lu.se/chrome/site/doc/api/index.html" 1793 1793 >http://base.thep.lu.se/chrome/site/doc/api/index.html</ulink>. … … 1795 1795 1796 1796 <para> 1797 The BASE API is d evided into four different parts on the package level.1797 The BASE API is divided into four different parts on the package level. 1798 1798 </para> 1799 1799 … … 1825 1825 <para> 1826 1826 Mixed Public and Internal API - Contains a mix of public and internal 1827 classes. Check the javadoc for each class/method before using it.1827 classes. Check the Javadoc for each class/method before using it. 1828 1828 </para> 1829 1829 </listitem> … … 1838 1838 1839 1839 <sect2 id="javadoc.writing"> 1840 <title>Writing javadoc</title>1840 <title>Writing Javadoc</title> 1841 1841 <para> 1842 1842 This section only covers Javadoc comments, how to write proper none-Javadoc comments … … 1860 1860 <listitem> 1861 1861 <para> 1862 General things that are common for all Javadoc scomments in Base.1862 General things that are common for all Javadoc comments in Base. 1863 1863 </para> 1864 1864 <itemizedlist> -
trunk/doc/src/docbook/faq/faqs.xml
r4477 r4487 148 148 <question> 149 149 <para> 150 What it the best way to create an array design in BASE 2when starting150 What it the best way to create an array design in BASE when starting 151 151 from a GAL file? 152 152 </para> … … 331 331 <para> 332 332 I have to create pools of samples in my experiment due to scarcity of 333 the biological material. Can I represent those pooled samples is BASE 2?333 the biological material. Can I represent those pooled samples is BASE? 334 334 </para> 335 335 </question> … … 347 347 <question> 348 348 <para> 349 I would like to add a software type in BASE 2but there is no button for349 I would like to add a software type in BASE but there is no button for 350 350 doing so. Is it possible? 351 351 </para> … … 371 371 <para> 372 372 Your privileges are not high enough and you have not been granted 373 permission to create hardware types. Contact your BASE 2administrator.373 permission to create hardware types. Contact your BASE administrator. 374 374 For more information about permissions, please refer to 375 375 <xref linkend="user_administration" />. … … 389 389 The most likely explanation is that this particular annotation 390 390 type has been declared as a protocol parameter. This means that it will 391 only be displayed in BASE 2if you have used a sample creation protocol391 only be displayed in BASE if you have used a sample creation protocol 392 392 which uses that parameter. 393 393 </para> … … 399 399 <para> 400 400 I have carried out an experiment using both Affymetrix and Agilent 401 arrays but I can not select more than one raw data type in BASE 2. What401 arrays but I can not select more than one raw data type in BASE. What 402 402 should I do? 403 403 </para> … … 424 424 <question> 425 425 <para> 426 It seems that BASE 2does not support the data files generated by my brand427 new scanner. Is it possible to add it to BASE 2?428 </para> 429 </question> 430 <answer> 431 <para> 432 Yes it is possible to extend BASE 2so that it can support your system.433 You will need to define a new raw data type for BASE 2by modifying426 It seems that BASE does not support the data files generated by my brand 427 new scanner. Is it possible to add it to BASE? 428 </para> 429 </question> 430 <answer> 431 <para> 432 Yes it is possible to extend BASE so that it can support your system. 433 You will need to define a new raw data type for BASE by modifying 434 434 the <filename>raw-datatypes.xml</filename> configuration file. 435 435 </para> … … 460 460 <answer> 461 461 <para> 462 This is normal. BASE 2 deals with Affymetrix data files differently. BASE2462 This is normal. BASE deals with Affymetrix data files differently. BASE 463 463 stores native Affymetrix file and does not load the value in tables as 464 464 it does for other platforms. See <xref linkend="experiments_analysis.rawbioassay.rawdata" /> … … 488 488 <qandaentry> 489 489 <question> 490 <para>Are Affymetrix CDT and CAB files supported by BASE 2?</para>490 <para>Are Affymetrix CDT and CAB files supported by BASE?</para> 491 491 </question> 492 492 <answer> … … 526 526 <qandaentry> 527 527 <question> 528 <para>Are Illumina data files supported by BASE 2?</para>528 <para>Are Illumina data files supported by BASE?</para> 529 529 </question> 530 530 <answer> … … 584 584 <para> 585 585 I am asked by reviewers to deposit my microarray data in a public 586 repository. How can BASE 2help me?587 </para> 588 </question> 589 <answer> 590 <para> 591 The BASE 2development team are working on a plug-in586 repository. How can BASE help me? 587 </para> 588 </question> 589 <answer> 590 <para> 591 The BASE development team are working on a plug-in 592 592 that produces a Tab2Mage file accepted by ArrayExpress. 593 593 For the plug-in to work properly, a series of rules need to be … … 662 662 compliance depends very much on the kind of annotation you have 663 663 supplied. Please refer to the previous question for more information 664 about how to check for MIAME compliance in BASE 2using the Experiment664 about how to check for MIAME compliance in BASE using the Experiment 665 665 overview function. 666 666 </para> … … 671 671 <question> 672 672 <para> 673 I have deleted the data files from BASE 2 file systemssince I have673 I have deleted the data files from BASE file system since I have 674 674 imported them in tables. So I do not have data files to send to 675 675 ArrayExpress anymore. … … 691 691 <question> 692 692 <para> 693 I have created pooled samples in BASE 2. Can I export in Tab2Mage format?693 I have created pooled samples in BASE. Can I export in Tab2Mage format? 694 694 </para> 695 695 </question> … … 730 730 <question> 731 731 <para> 732 OK, I have uploaded 40 CEL files in BASE 2but are there any tool to732 OK, I have uploaded 40 CEL files in BASE but are there any tool to 733 733 perform normalisation on Affymetrix raw data? 734 734 </para> … … 736 736 <answer> 737 737 <para> 738 Yes, there is. BASE 2team has created a plug-in based on738 Yes, there is. BASE team has created a plug-in based on 739 739 <ulink url="http://rmaexpress.bmbolstad.com/"> 740 740 RMAExpress methods from Bolstad and Irizarry</ulink> so you can normalise -
trunk/doc/src/docbook/index.xml
r4477 r4487 31 31 <pubdate/> 32 32 </bookinfo> 33 <title>BASE 2Documentation</title>33 <title>BASE Documentation</title> 34 34 <include file="overviewdoc/index.xml"/> 35 35 <include file="userdoc/index.xml"/> -
trunk/doc/src/docbook/overviewdoc/base_overview.xml
r4477 r4487 29 29 <chapter id="base_overview"> 30 30 <?dbhtml dir="overview"?> 31 <title>Overview of BASE 2</title>31 <title>Overview of BASE</title> 32 32 <sect1 id="nolabelhereyet2"> 33 33 <title></title> -
trunk/doc/src/docbook/overviewdoc/resources.xml
r4477 r4487 31 31 <title>Resources</title> 32 32 <para> 33 There are several resources available for those who are using BASE 2 or have some other34 kind of interested in the BASE 2 project. This chapter contains information about those35 resources and also some short instructions on how to use each36 one of them.33 There are several resources available for those who are using BASE 34 or have some other kind of interested in the BASE project. This 35 chapter contains information about those resources and also some 36 short instructions on how to use each one of them. 37 37 </para> 38 38 <sect1 id="resources.home_page"> … … 52 52 <guilabel><ulink url='http://base.thep.lu.se/wiki/DownloadPage' 53 53 >Download Page</ulink></guilabel>. 54 From this page you can download BASE 2releases as packaged tar.gz54 From this page you can download BASE releases as packaged tar.gz 55 55 files or checkout the source code directly from the Subversion repository. 56 56 See the separate parts on the web page to get more information how to … … 59 59 <variablelist> 60 60 <varlistentry> 61 <term>Packaged BASE 2releases</term>61 <term>Packaged BASE releases</term> 62 62 <listitem> 63 63 <para> … … 113 113 implemented. To show the list of outstanding tickets use the 114 114 <guibutton><ulink url="http://base.thep.lu.se/query" 115 >View Tickets</ulink></guibutton> button on BASE 2's home-page.115 >View Tickets</ulink></guibutton> button on BASE web site. 116 116 It is a good idea to have a look at this list before reporting a bug 117 117 or requesting a new feature. Perhaps someone has registered the issue as a ticket 118 already. This list can also be used to see how the BASE 2development is proceeding118 already. This list can also be used to see how the BASE development is proceeding 119 119 and when some particular request is planned to be fixed. 120 120 </para> … … 132 132 133 133 <para> 134 The roadmap of BASE 2is accessed from the134 The roadmap of BASE is accessed from the 135 135 <guibutton><ulink url="http://base.thep.lu.se/roadmap" 136 136 >Roadmap</ulink></guibutton> button on the home page. This page … … 175 175 <para> 176 176 Information for those who are interested to be involved in the 177 development of BASE 2.177 development of BASE. 178 178 </para> 179 179 </listitem> … … 203 203 a page that lists the core plug-ins</ulink>. 204 204 All plug-ins that are included in the installation of 205 BASE 2are listed on this page, some together with one or several examples of suitable205 BASE are listed on this page, some together with one or several examples of suitable 206 206 configuration files. These configuration files can be downloaded and imported with the 207 plug-in configuration importer in BASE 2.207 plug-in configuration importer in BASE. 208 208 </para> 209 209 </sect1> … … 211 211 <title>BASE plug-ins site</title> 212 212 <para> 213 Plug-ins which are not included in the installation of BASE 2, have their own site,213 Plug-ins which are not included in the installation of BASE, have their own site, 214 214 called 215 215 <ulink url="http://baseplugins.thep.lu.se/">BASE plug-ins web site</ulink> … … 224 224 <title>Demo server</title> 225 225 <para> 226 There is a demo server up running for anyone who wants to explore BASE 2 without having227 to install it. Follow the link on BASE 2's home page to the demo server or go directly228 to226 There is a demo server up running for anyone who wants to 227 explore BASE without having to install it. Follow the link on 228 BASE web site to the demo server or go directly to 229 229 <ulink url="http://base2.thep.lu.se/demo/"> 230 230 http://base2.thep.lu.se/demo/ … … 269 269 <title>IRC channel</title> 270 270 <para> 271 There is an ircchannel on the FreeNode network where real-time BASE271 There is an IRC channel on the FreeNode network where real-time BASE 272 272 discussion can take place twentyfour-seven. Use 273 273 <userinput>#basedb</userinput> -
trunk/doc/src/docbook/overviewdoc/why_base.xml
r4477 r4487 29 29 <chapter id="why_base"> 30 30 <?dbhtml dir="why_base"?> 31 <title>Why use BASE 2</title>31 <title>Why use BASE</title> 32 32 <sect1 id="nolabelhereyet"> 33 33 <title></title> -
trunk/doc/src/docbook/userdoc/annotations.xml
r4477 r4487 37 37 title="Annotation types"> 38 38 <para> 39 BASE 2has been engineered to closely map the39 BASE has been engineered to closely map the 40 40 <ulink 41 41 url="http://www.mged.org/Workgroups/MIAME/miame.html"> … … 43 43 However, since MIAME is focused on microarray processing 44 44 workflow, information about the description biological 45 samples themselves was left out. BASE 2users are free to46 annotate biomaterials (and most BASE 2items) as they wish,45 samples themselves was left out. BASE users are free to 46 annotate biomaterials (and most BASE items) as they wish, 47 47 from basic free text description to more advanced ontology 48 based terms. To accom odate the annotation needs of users48 based terms. To accommodate the annotation needs of users 49 49 eager with detailed sample annotations and also the needs of 50 very different communities, BASE 2provides a mechanism that51 allows a high level of annotation customization. BASE 250 very different communities, BASE provides a mechanism that 51 allows a high level of annotation customization. BASE 52 52 allows to create descriptive elements for both quantitative 53 53 annotation and qualitative annotation of Biomaterials via 54 54 the <emphasis>Annotation Type mechanism</emphasis>. 55 55 Actually, annotation types can be used to annotate not 56 only <emphasis>Biomaterials</emphasis> but almost all BASE 2items, from56 only <emphasis>Biomaterials</emphasis> but almost all BASE items, from 57 57 <emphasis>Plates</emphasis> 58 58 to … … 99 99 have a maximum length of 255 characters and can have an attached 100 100 list of predefined value. <guilabel>Text</guilabel> 101 annotation types have no practi val limit and are always101 annotation types have no practical limit and are always 102 102 free-text. 103 103 </para> … … 138 138 <para> 139 139 The <guilabel>Edit annotation type</guilabel> window is opened in a 140 pop up. It contains four different tabs.140 pop-up. It contains four different tabs. 141 141 </para> 142 142 … … 310 310 navigated especially when the 311 311 number of possible values is 312 large, and because selection list312 large, and because selection-list 313 313 and drop-down list allow use of 314 314 arrow and tab for selection. … … 585 585 <listitem> 586 586 <para> 587 <guilabel>all</guilabel>: Display all annotat ation types587 <guilabel>all</guilabel>: Display all annotation types 588 588 </para> 589 589 </listitem> … … 701 701 BASE includes a plug-in for importing annotations to multiple items 702 702 in one go. The plug-in read annotation values from a simple column-based 703 text file. Usu sally, a tab is used as the delimiter between columns.703 text file. Usually, a tab is used as the delimiter between columns. 704 704 The first row should contain the column headers. One column should contain 705 705 the name or the external ID of the item. The rest of the columns can each be -
trunk/doc/src/docbook/userdoc/biomaterials.xml
r4477 r4487 34 34 The generic term biomaterial refers to any biological material used in an experiment. 35 35 biomaterials are subdivided in 4 components, biosource, sample, extract and labeled 36 extract. The order use in presenting those entities is not inocuous as it represents the36 extract. The order used in presenting those entities is not innocuous as it represents the 37 37 sequence of transformation a source material undergoes until it is in a state compatible 38 38 with the realization of a microarray hybridization. This progression is actually 39 mimicked in the BASE 239 mimicked in the BASE 40 40 <guimenu>View</guimenu> 41 41 menu again to insist on this natural progression. … … 50 50 <listitem> 51 51 <simpara> 52 Samples are central to BASE 2to describe the sample processing. So samples can52 Samples are central to BASE to describe the sample processing. So samples can 53 53 be created from other samples if user want to track sample processing event in a 54 54 finely granular fashion. … … 70 70 </itemizedlist> 71 71 <para> 72 BASE 2allows users to create any of the these entities fairly freely, however it is72 BASE allows users to create any of the these entities fairly freely, however it is 73 73 expected that users will follow the natural path of the laboratory workflow. 74 74 </para> … … 97 97 <listitem> 98 98 <para> 99 This is the only mandatory field. BASE 2by default assigns99 This is the only mandatory field. BASE by default assigns 100 100 <replaceable>New biosource</replaceable> 101 101 as name but it is advised to provide unique sensible names. … … 138 138 <title>Annotations</title> 139 139 <para> 140 This allows BASE 2users to use annotation types to refine biosource description.140 This allows BASE users to use annotation types to refine biosource description. 141 141 More about annotating items can be read in 142 142 <xref linkend="annotations.annotating" /> … … 156 156 <para> 157 157 For every step of transformation from biosource to sample, it is possible to provide 158 information about the protocol used to perform this task. It is not enforced in BASE 2158 information about the protocol used to perform this task. It is not enforced in BASE 159 159 but it should serve as guidance when devising the granularity of the sample processing 160 160 task. Also, it is good practice to provide protocol information to ensure MIAME … … 222 222 <listitem> 223 223 <para> 224 The sample's name(required). BASE 2by default assigns names to224 The sample's name(required). BASE by default assigns names to 225 225 samples (by suffixing 226 226 <replaceable>s#</replaceable> … … 269 269 </term> 270 270 <listitem> 271 <para>The date at which the sample was entered in BASE 2.</para>271 <para>The date at which the sample was entered in BASE.</para> 272 272 </listitem> 273 273 </varlistentry> … … 309 309 <helptext external_id="sample.parents" title="Sample's parents"> 310 310 <para> 311 This is meant to keep track of the sample origin. BASE 2 distinguished312 between 2 cases which are controled by the311 This is meant to keep track of the sample origin. BASE 312 distinguished between two cases which are controlled by the 313 313 <guilabel>Pooled</guilabel> 314 314 radio-button in the edit pop-up window. … … 353 353 <para> 354 354 This tab contains a list of those annotations that are inherited from the 355 sample's parents. Information about working with in nherited annotations can be355 sample's parents. Information about working with inherited annotations can be 356 356 found in 357 357 <xref linkend="annotations.inheriting" /> … … 372 372 <para> 373 373 During the transformation from samples to extracts, it is possible to provide 374 information about the protocol used to perform this task. It is not enforced in BASE 2374 information about the protocol used to perform this task. It is not enforced in BASE 375 375 but it should serve as guidance when devising the granularity of the sample processing 376 376 task. Also, it is good practice to provide protocol information. … … 433 433 <listitem> 434 434 <para> 435 A mandatory field for providing the extract 's name. BASE2by435 A mandatory field for providing the extract name. BASE by 436 436 default assigns names to extract (by suffixing 437 437 <replaceable>e#</replaceable> … … 480 480 <para> 481 481 This is automatically populated with a date at which the sample 482 was entered in BASE 2system.482 was entered in BASE system. 483 483 </para> 484 484 </listitem> … … 524 524 <helptext external_id="extract.parents" title="Extract's parents"> 525 525 <para> 526 This important tab allows users to select the extract origin. BASE2 527 distinguished between 2 cases which are controled by the 526 This important tab allows users to select the extract 527 origin. BASE distinguished between two cases which are 528 controlled by the 528 529 <guilabel>Pooled</guilabel> 529 530 radio-button. … … 566 567 <para> 567 568 This tab contains a list of those annotations that are inherited from the 568 extract 's parents. Information about working with innherited annotations can be569 extract parents. Information about working with inherited annotations can be 569 570 found in 570 571 <xref linkend="annotations.inheriting" /> … … 579 580 <para> 580 581 Before attempting to create labeled extracts, users should make sure that the 581 appropriate label object is present in BASE 2. To browse the list of labels, go to582 appropriate label object is present in BASE. To browse the list of labels, go to 582 583 <menuchoice> 583 584 <guimenu>View</guimenu> … … 628 629 <para> 629 630 During the transformation from extracts to labeled extracts, it is possible to provide 630 information about the protocol used to perform this task. It is not enforced in BASE 2631 information about the protocol used to perform this task. It is not enforced in BASE 631 632 but it should serve as guidance when devising the granularity of the extract processing 632 633 task. Also, it is good practice to provide protocol information. … … 709 710 <listitem> 710 711 <para> 711 The name of the labeled extract (required). BASE 2by default assigns712 The name of the labeled extract (required). BASE by default assigns 712 713 names to labeled extract(by suffixing 713 714 <replaceable>lbe#</replaceable> … … 759 760 <varlistentry> 760 761 <term> 761 <guilabel>Regist red</guilabel>762 <guilabel>Registered</guilabel> 762 763 </term> 763 764 <listitem> 764 765 <para> 765 766 This is automatically populated with a date at which the labeled 766 extract was actually entered in BASE 2system.767 extract was actually entered in BASE system. 767 768 </para> 768 769 </listitem> … … 805 806 <title>Parents</title> 806 807 <para> 807 This important tab allows users to select the labeled extract origin. BASE2 808 distinguished between 2 cases which are controled by the 808 This important tab allows users to select the labeled 809 extract origin. BASE distinguished between two cases which 810 are controlled by the 809 811 <guilabel>Pooled</guilabel> 810 812 radio-button. … … 855 857 <para> 856 858 This tab contains a list of those annotations that are inherited from the 857 parents of the labeled extract. Information about dealing with in nherited859 parents of the labeled extract. Information about dealing with inherited 858 860 annotations can be found in 859 861 <xref linkend="annotations.inheriting" /> … … 872 874 <menuchoice> 873 875 <guimenu>View</guimenu> 874 <guimenuitem>Hybridizat ons</guimenuitem>876 <guimenuitem>Hybridizations</guimenuitem> 875 877 </menuchoice> 876 878 to get to the hybridizations. … … 879 881 <title>Creating hybridizations</title> 880 882 <para> 881 In BASE 2, there are 2possible routes to create an hybridization object except the883 In BASE, there are two possible routes to create an hybridization object except the 882 884 common way with the &gbNew; button at hybridization list page. 883 885 </para> … … 892 894 <para> 893 895 Click on the 894 <guibutton>New hybrid zation…</guibutton>896 <guibutton>New hybridization…</guibutton> 895 897 from the toolbar of labeled extract list view. 896 898 </para> … … 936 938 <para> 937 939 <replaceable>New hybridization</replaceable> 938 is BASE2default name but it is strongly advise to provide a940 is the BASE default name but it is strongly advise to provide a 939 941 meaningful and unique name (required). 940 942 </para> … … 975 977 <para> 976 978 This field is automatically populated with a date at which the 977 hybridization was entered in BASE 2system.979 hybridization was entered in BASE system. 978 980 </para> 979 981 </listitem> … … 1078 1080 <para> 1079 1081 This tab contains a list of those annotations that are inherited from the 1080 labeled extracts. Information about dealing with in nherited annotations can be1082 labeled extracts. Information about dealing with inherited annotations can be 1081 1083 found in 1082 1084 <xref linkend="annotations.inheriting" /> -
trunk/doc/src/docbook/userdoc/experiments.xml
r4477 r4487 167 167 The date the article was published. Use the 168 168 <guibutton>Calendar</guibutton> button to select 169 a date from a pop up window.169 a date from a pop-up window. 170 170 </para> 171 171 </listitem> … … 457 457 you have specified values for optional items. 458 458 For example, there is an option that warns you if 459 you hav not specified a protocol.459 you have not specified a protocol. 460 460 </para> 461 461 </listitem> … … 710 710 711 711 <para> 712 BASE 2has been engineered to closely map the MIAME713 concepts and a number of BASE 2entities can be mapped712 BASE has been engineered to closely map the MIAME 713 concepts and a number of BASE entities can be mapped 714 714 directly to Tab2Mage elements. However, since MIAME is 715 715 focused on microarray processing workflow, information 716 716 about the biological sample is down to the user. To 717 accom odate the annotation needs of users, BASE2provides717 accommodate the annotation needs of users, BASE provides 718 718 a mechanism that allows annotation customization to meet 719 719 user specific requirements. BASE allows to create … … 723 723 724 724 <para> 725 BASE 2can export an experiment to Tab2Mage725 BASE can export an experiment to Tab2Mage 726 726 format thanks to a dedicated export plug-in. 727 727 For the plug-in to work, it is important to understand that … … 747 747 <warning> 748 748 <para> 749 All BASE 2Annotation Types used to annotate at749 All BASE Annotation Types used to annotate at 750 750 the level of <emphasis>Sample</emphasis> and 751 751 <emphasis>Extract</emphasis> items will … … 759 759 In the context of data exchange between BASE 760 760 instances, the export function can be altered to 761 allow attach ement of annotations to items761 allow attachment of annotations to items 762 762 other than biosources, therefore avoiding loss of 763 763 information. … … 769 769 <title>Annotation units</title> 770 770 <para> 771 To associate units to BASE 2annotation types and771 To associate units to BASE annotation types and 772 772 remain compatible with Tab2Mage specifications, 773 773 users need to adhere to the following convention: … … 806 806 807 807 <para> 808 In BASE 2terms, Tab2Mage elements such as808 In BASE terms, Tab2Mage elements such as 809 809 <emphasis>BioMaterialCharacteristics</emphasis>, 810 810 <emphasis>Parameter</emphasis> or … … 850 850 Variables</emphasis> when submitting data to ArrayExpress 851 851 (provided the study is an intervention study). 852 Therefore, BASE 2users willing to use the Tab2Mage852 Therefore, BASE users willing to use the Tab2Mage 853 853 export function will have to declare <emphasis>Experimental 854 854 Factors</emphasis> using the the <guilabel>Experimental Factor</guilabel> -
trunk/doc/src/docbook/userdoc/file_system.xml
r4477 r4487 33 33 <title>File system</title> 34 34 <para> 35 Files in BASE 2are managed from the page at35 Files in BASE are managed from the page at 36 36 <menuchoice> 37 37 <guimenu>View</guimenu> 38 38 <guimenuitem>Files</guimenuitem> 39 39 </menuchoice>. The basic layout on the page is the same as for all the other list pages 40 in BASE 2but40 in BASE but 41 41 there are some differences e.g. there is a navigation tree to the left, used to browse 42 42 the directory structure, and there are some buttons in the toolbar, that are special for … … 104 104 </term> 105 105 <listitem> 106 <para>Shows the full BASE 2path to current directory.</para>106 <para>Shows the full BASE path to current directory.</para> 107 107 </listitem> 108 108 </varlistentry> … … 147 147 <title>Replace an existing file</title> 148 148 <para> 149 It is possible to re-upload file that are on line, but this149 It is possible to re-upload file that are on-line, but this 150 150 has to be done from the single-item view. 151 151 </para> … … 158 158 <title>Browse the file system</title> 159 159 <para> 160 Browsing th r BASE 2file system is done from the navigation bar by clicking on a160 Browsing the BASE file system is done from the navigation bar by clicking on a 161 161 directory in the tree to view it's contents. Both sub directories and files in the 162 162 selected directory are showed. A directory with sub directories can be expand with a … … 206 206 <title>Disk space quota</title> 207 207 <para> 208 Normally, a user is assigned limited disk space for files.208 Normally, a user is assigned limited disk space for files. 209 209 More information about how much quota the current account has and how much of it 210 210 that is occupied can be found at the account's home page, described in … … 380 380 Mark this checkbox if the compressed file should 381 381 be unpacked after it had been uploaded. The 382 files will be unpacked with the same sub directory382 files will be unpacked with the same sub-directory 383 383 structure as in the compressed file. 384 384 </para> … … 588 588 <para> 589 589 Choose a directory which the selected items should be moved to. It 590 is possible to create new sub directories with the590 is possible to create new sub-directories with the 591 591 &gbNew; button. 592 592 </para> … … 816 816 <varlistentry> 817 817 <term> 818 <guilabel>Share new files and sub directories automatically</guilabel>818 <guilabel>Share new files and sub-directories automatically</guilabel> 819 819 </term> 820 820 <listitem> … … 886 886 <title>File types</title> 887 887 <para> 888 A file can be associated with one of the file types that exists in BASE 2. File types888 A file can be associated with one of the file types that exists in BASE. File types 889 889 make it possible to filter the files depending of what kind of file it is. Here 890 890 is a list of file types that are defined in BASE. -
trunk/doc/src/docbook/userdoc/hardware.xml
r4477 r4487 42 42 <para> 43 43 <guilabel>Hardware Type</guilabel> 44 allows classification of hardware sbased on their usage45 and purpose in the laboratory workflow. By default, BASE 244 allows classification of hardware based on their usage 45 and purpose in the laboratory workflow. By default, BASE 46 46 creates the 3 main hardware types and 47 47 those correspond to the main hardware families … … 120 120 121 121 <para> 122 In BASE, hardware can be created by 2routes. Either122 In BASE, hardware can be created by two routes. Either 123 123 from the single-item view of a hardware type or from the 124 124 list view of hardware. -
trunk/doc/src/docbook/userdoc/overview.xml
r4484 r4487 30 30 <?dbhtml dir="overview"?> 31 31 <title>Overview of user documentation</title> 32 <para> The 'User documentation' part is quite extensive and covers everything from how to login on33 a BASE 2server and find your way through the program, to working with experiments and doing some32 <para> The 'User documentation' part is quite extensive and covers everything from how to Log in on 33 a BASE server and find your way through the program, to working with experiments and doing some 34 34 useful analysis. The intention with this chapter is to give an overview of the following chapters 35 35 so it will be easier for you to know where to look for certain information in case you don't want … … 51 51 The second subsection, 52 52 <xref linkend="webclient.configuration" /> 53 , describes how to person lize BASE with contact information, preferences and changing password.53 , describes how to personalize BASE with contact information, preferences and changing password. 54 54 The preferences are for instance some appearance like date format, text size or the look of the 55 55 toolbar buttons. … … 60 60 and 61 61 <xref linkend="webclient.itemlist" /> 62 , in the web client chapter explains how to work with BASE. No matter what you are going to do the62 , in the web client chapter explains how to work with BASE. No matter what you are going to do the 63 63 user interface contains a lot of common functions that works the same everywhere. For example, 64 64 how to list and search for items, how to create new items and modify and delete existing items. … … 83 83 The next thing to do is to add some relevant data to work with. Most of the different items can 84 84 be created manually from the web client, but some items and data must be imported from files. 85 Before importing a file, it has to be uploaded on the BASE-server's file system.85 Before importing a file, it has to be uploaded on the BASE-server's file system. 86 86 <xref linkend="file_system" /> 87 87 gives you information about the server's file system and how to upload the files. … … 240 240 </orderedlist> 241 241 <para> 242 This concludes the short step-by-step get going text. Far from all functional lity in BASE243 has been co nvered here. E.g. nothing about LIMS or biomaterials have been mentioned. But you242 This concludes the short step-by-step get going text. Far from all functionality in BASE 243 has been covered here. E.g. nothing about LIMS or biomaterials have been mentioned. But you 244 244 should now at least be familiar with getting to that point when it is possible to do some 245 245 analysis. -
trunk/doc/src/docbook/userdoc/protocols.xml
r4477 r4487 31 31 <para> 32 32 Information about laboratory standard operating procedure 33 and protocols can be tracked in BASE 2using two structures,33 and protocols can be tracked in BASE using two structures, 34 34 the use of which is detailed in the following sections. 35 35 </para> … … 43 43 allows classification of protocols based on their 44 44 usage and purpose in the laboratory workflow. By 45 default, BASE 2 creates the 8 main pProtocol types and45 default, BASE creates the 8 main Protocol types and 46 46 those correspond to the main protocol families 47 47 identified by MIAME requirements and applied in a … … 62 62 instance DNA binding site identification, imposes 63 63 the creation of new protocol type in addition to 64 those built-in in BASE 2.64 those built-in in BASE. 65 65 </para> 66 66 <tip> … … 124 124 <title>Protocols</title> 125 125 <para> 126 In BASE, protocols can be created by 2routes. Either126 In BASE, protocols can be created by two routes. Either 127 127 from the single-item view of a protocol type or from the 128 128 list view of protocols. … … 243 243 <listitem> 244 244 <para> 245 Use this button to open a pop up where you can select245 Use this button to open a pop-up where you can select 246 246 annotation type to use for parameters. The list only 247 247 shows annotations types which has the -
trunk/doc/src/docbook/userdoc/reporters.xml
r4477 r4487 43 43 </para> 44 44 <para> 45 In BASE 2, reporters also refer to Affymetrix Probeset ID but45 In BASE, reporters also refer to Affymetrix Probeset ID but 46 46 reporters can be used to describe genes, transcripts, exons 47 47 or any other sequence entity of biological relevance. … … 135 135 Reporters are used to represent genes, transcripts, 136 136 exons and therefore come in their thousands. To solve 137 this problem, BASE 2relies on137 this problem, BASE relies on 138 138 <emphasis>Reporter import plug-ins</emphasis>. 139 139 Those need to be specifically configured to deal with … … 152 152 As for any other plug-in, configuration parameters 153 153 can be saved as an XML file and exchanged with 154 another BASE 2instance, thereby reducing155 configuration burden (provided the 2instances have154 another BASE instance, thereby reducing 155 configuration burden (provided the two instances have 156 156 identical <filename>extended-properties.xml</filename> files). 157 157 See <xref linkend="resources.coreplugins" /> for information … … 163 163 <title>Dealing with Affymetrix probesets</title> 164 164 <para> 165 In BASE 2, Affymetrix probesets should be treated as reporters.165 In BASE, Affymetrix probesets should be treated as reporters. 166 166 The probeset ID could be stored in both the 167 167 <guilabel>Name</guilabel> and the <guilabel>External ID</guilabel> … … 304 304 is linked to the <ulink 305 305 url="http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?db=unigene" 306 >Uni gene database at NCBI</ulink>.306 >UniGene database at NCBI</ulink>. 307 307 </para> 308 308 </note> … … 369 369 <title>Reporter lists</title> 370 370 <para> 371 BASE 2allows for defining sets of reporters for a371 BASE allows for defining sets of reporters for a 372 372 particular use, for instance to define a list of 373 reporters to be used on an array. There are 2ways to do373 reporters to be used on an array. There are two ways to do 374 374 so: 375 375 </para> -
trunk/doc/src/docbook/userdoc/webclient.xml
r4477 r4487 47 47 48 48 <para> 49 You may, for example, try the BASE 2demo server. Go to the49 You may, for example, try the BASE demo server. Go to the 50 50 URL <ulink url="http://base2.thep.lu.se:8080/demo/">http://base2.thep.lu.se:8080/demo/</ulink> 51 51 and enter <userinput>base2</userinput> for the login and <userinput>base2</userinput> … … 184 184 Most of the menu is in two levels, ie. clicking on a top-level menu 185 185 will open a submenu just below it. Clicking on something in the 186 submenu will take you to another page or open a pop up dialog window.186 submenu will take you to another page or open a pop-up dialog window. 187 187 For example, the 188 188 <menuchoice><guimenu>View</guimenu><guimenuitem>Samples</guimenuitem></menuchoice> … … 285 285 <para> 286 286 Displays the name of the currently logged in user and allows 287 you to quickly log out and switch to another user.287 you to quickly log out and switch to another user. 288 288 </para> 289 289 </listitem> … … 302 302 <varlistentry> 303 303 <term> 304 On line context-sensitive help304 On-line context-sensitive help 305 305 </term> 306 306 <listitem> … … 315 315 click it to get help about the part of the page 316 316 you are currently viewing. The icon is located in the title 317 bar in most pop up dialog windows and in the toolbar in most317 bar in most pop-up dialog windows and in the toolbar in most 318 318 other pages. 319 319 </para> … … 328 328 <para> 329 329 The <menuchoice><guimenu>Help</guimenu></menuchoice> menu 330 contains links for getting on line help. These links330 contains links for getting on-line help. These links 331 331 may be configured by a server administrator, so they may be 332 332 different from server to server. By default links for reporting … … 495 495 The look of the 496 496 <guilabel>Other information</guilabel> 497 tab can differ e abit between different servers, depending on what settings498 the server is installed with. There are three inputs in a fresh BASE 2497 tab can differ a bit between different servers, depending on what settings 498 the server is installed with. There are three inputs in a fresh BASE 499 499 installation but it is only the 500 500 <guilabel>Description</guilabel> 501 text area that is static, the others can be removed or more fields can be501 text area that is static, the others can be removed or more fields can be 502 502 added (managed by the server administrator). The three fields, included in a 503 the BASE 2installation, are503 the BASE installation, are 504 504 <variablelist> 505 505 <varlistentry> … … 516 516 </term> 517 517 <listitem> 518 <para>Your skype contact information(Optional).</para>518 <para>Your Skype contact information(Optional).</para> 519 519 </listitem> 520 520 </varlistentry> … … 645 645 <listitem> 646 646 <para> 647 The scale factor affects the size of pop up windows.647 The scale factor affects the size of pop-up windows. 648 648 This setting exists because different browsers render 649 pages differently. If you often find that pop up windows649 pages differently. If you often find that pop-up windows 650 650 are too small you can change this setting to make them 651 651 bigger. … … 682 682 experiments. The default setting is blue-black-yellow. 683 683 The list of presets contains other useful color combinations 684 (for example, the BASE 1 red-yellow-green) and the most684 (for example, the BASE version 1 red-yellow-green) and the most 685 685 recently used color combinations. 686 686 </para> … … 950 950 <para> 951 951 This view is used for editing the information 952 about a single item. It is always displayed as a pop up window.952 about a single item. It is always displayed as a pop-up window. 953 953 </para> 954 954 </listitem> … … 965 965 page. Here you will find a &gbNew; button in the 966 966 toolbar. The button is disabled if you do not have permission to create new experiments. 967 Otherwise, click on it and enter any required information in the pop up dialog.967 Otherwise, click on it and enter any required information in the pop-up dialog. 968 968 Sometimes there are multiple tabs in this dialog. In the case of experiments 969 969 there are three tabs: <guilabel>Experiment</guilabel>, <guilabel>Publication</guilabel> … … 1043 1043 <para> 1044 1044 On all single-item views there is an &gbEdit; 1045 button in the toolbar that opens a pop up dialog for editing the properties1045 button in the toolbar that opens a pop-up dialog for editing the properties 1046 1046 of the item. This button is disabled if the logged in user does not have 1047 1047 write permission for the item. … … 1049 1049 1050 1050 <para> 1051 You can also open the edit pop up in most other places where1051 You can also open the edit pop-up in most other places where 1052 1052 the item appears, for example, in lists or the single-item view 1053 1053 of a related item. Press and hold one of the <keycap>CTRL</keycap>, 1054 1054 <keycap>ALT</keycap> or <keycap>SHIFT</keycap> keys while clicking 1055 on the link and the edit window will open in a pop up.1055 on the link and the edit window will open in a pop-up. 1056 1056 If you do not have write permission 1057 on the item there is no meaning to open the edit pop up and you will1057 on the item there is no meaning to open the edit pop-up and you will 1058 1058 be taken to the single-item view page instead. 1059 1059 </para> … … 1241 1241 <listitem> 1242 1242 <para> 1243 Opens a pop up window that allows you to select1244 users to share the items to. In the pop up window, mark1243 Opens a pop-up window that allows you to select 1244 users to share the items to. In the pop-up window, mark 1245 1245 one or more users and click on the &gbOk; 1246 button. The pop up window will only list users that you have1246 button. The pop-up window will only list users that you have 1247 1247 permission to read. Unless you are an administrator, this 1248 1248 usually means that you can only see users that: … … 1274 1274 <listitem> 1275 1275 <para> 1276 Opens a pop up window that allows you to select1277 groups to share the items to. In the pop up window, mark1276 Opens a pop-up window that allows you to select 1277 groups to share the items to. In the pop-up window, mark 1278 1278 one or more groups and click on the &gbOk; 1279 button. Unless you are an administrator, the pop up window1279 button. Unless you are an administrator, the pop-up window 1280 1280 will only list groups where you are a member. It will not list 1281 1281 groups that already have access to the items. … … 1288 1288 <listitem> 1289 1289 <para> 1290 Opens a pop up window that allows you to select1291 projects to share the items to. In the pop up window, mark1290 Opens a pop-up window that allows you to select 1291 projects to share the items to. In the pop-up window, mark 1292 1292 one or more projects and click on the &gbOk; 1293 button. Unless you are an administrator, the pop up window1293 button. Unless you are an administrator, the pop-up window 1294 1294 will only list projects where you are a member. It will not list 1295 1295 projects that already have access to the items. … … 1309 1309 1310 1310 <varlistentry> 1311 <term><guilabel>Apply permissions to all sub directories and their files</guilabel></term>1311 <term><guilabel>Apply permissions to all sub-directories and their files</guilabel></term> 1312 1312 <listitem> 1313 1313 <para> … … 1315 1315 is a directory. If this option is selected the permissions given 1316 1316 to the directory will recursively be copied to all files and 1317 sub directories. Existing permissions on those items will be1317 sub-directories. Existing permissions on those items will be 1318 1318 overwritten with the new permissions. 1319 1319 </para> … … 1325 1325 Use the &gbSave; button to save your 1326 1326 changes or the &gbCancel; button to 1327 close the pop up without saving.1327 close the pop-up without saving. 1328 1328 </para> 1329 1329 </helptext> … … 1440 1440 single-item view of that item. Holding down <keycap>CTRL</keycap>, 1441 1441 <keycap>ALT</keycap> or <keycap>SHIFT</keycap> while clicking, 1442 will open the edit pop up.1442 will open the edit pop-up. 1443 1443 </para> 1444 1444 </listitem> … … 1564 1564 <para> 1565 1565 The free-text filter is a bit more complex. By default, an exact match is 1566 required, use % as a wildcard that matches any character.1566 required, use % as a wildcard character that matches any character. 1567 1567 For example, the filter <informalexample>Experiment A</informalexample> 1568 1568 only matches the same exact string, but the filter … … 1709 1709 Use the &gbSave; button to apply your 1710 1710 changes or the &gbCancel; button to 1711 close the pop up without saving.1711 close the pop-up without saving. 1712 1712 </para> 1713 1713 … … 1904 1904 Use the &gbOk; button to save the preset 1905 1905 or the &gbCancel; button to 1906 close the pop up without saving.1906 close the pop-up without saving. 1907 1907 </para> 1908 1908 … … 1962 1962 <para> 1963 1963 Use the &gbClose; button to 1964 close the pop up.1964 close the pop-up. 1965 1965 </para> 1966 1966 … … 1986 1986 most significant difference is that the trashcan page can 1987 1987 contain more then one item type, actually all removable item 1988 types in BASE can be listed in the tras can. Items that neither1988 types in BASE can be listed in the trashcan. Items that neither 1989 1989 can be removed or deleted, <emphasis>i.e.,</emphasis> items 1990 1990 like sessions, nor clients' help texts since these are deleted -
trunk/doc/test/performance/index.html
r4477 r4487 4 4 5 5 Copyright (C) 2007 Nicklas Nordborg 6 Copyright (C) 2008 Jari Hakkinen 6 7 7 8 This file is part of BASE - BioArray Software Environment. … … 43 44 <p> 44 45 This document defines a procedure for testing the performance 45 of BASE. The intention is that BASE 2 should be compared to BASE 1 46 with respect to performance. The tests on a BASE 1 server must be done 47 by hand. For BASE 2, there is a test program. The current test program 46 of BASE. The intention is that BASE should be compared to the 47 earlier BASE version 1 with respect to performance. The tests on 48 a BASE version 1 server must be done by hand. For later BASE 49 versions, there is a test program. The current test program 48 50 is a prototype which includes the following tests: 49 51 </p>
Note: See TracChangeset
for help on using the changeset viewer.