diff --git a/modules/websearch/doc/Makefile.am b/modules/websearch/doc/Makefile.am
index cab77b7f5..f898db4c2 100644
--- a/modules/websearch/doc/Makefile.am
+++ b/modules/websearch/doc/Makefile.am
@@ -1,60 +1,66 @@
## $Id$
## This file is part of CDS Invenio.
## Copyright (C) 2002, 2003, 2004, 2005, 2006, 2007 CERN.
##
## CDS Invenio is free software; you can redistribute it and/or
## modify it under the terms of the GNU General Public License as
## published by the Free Software Foundation; either version 2 of the
## License, or (at your option) any later version.
##
## CDS Invenio is distributed in the hope that it will be useful, but
## WITHOUT ANY WARRANTY; without even the implied warranty of
## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-## General Public License for more details.
+## General Public License for more details.
##
## You should have received a copy of the GNU General Public License
## along with CDS Invenio; if not, write to the Free Software Foundation, Inc.,
## 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.
SUBDIRS = admin hacking
docdir = $(localstatedir)/www/help/search
doc_DATA=index.en.html index.fr.html index.de.html index.es.html index.ca.html index.pl.html index.pt.html index.hr.html index.it.html index.ja.html index.ru.html index.sk.html index.cs.html index.no.html index.sv.html index.el.html index.bg.html index.zh_CN.html index.zh_TW.html index.uk.html \
tips.en.html tips.fr.html tips.de.html tips.pl.html tips.pt.html tips.es.html tips.ca.html tips.hr.html tips.it.html tips.ja.html tips.ru.html tips.sk.html tips.cs.html tips.no.html tips.sv.html tips.el.html tips.bg.html tips.zh_CN.html tips.zh_TW.html tips.uk.html \
guide.en.html guide.fr.html guide.de.html guide.pl.html guide.pt.html guide.es.html guide.ca.html guide.hr.html guide.it.html guide.ja.html guide.ru.html guide.sk.html guide.cs.html guide.no.html guide.sv.html guide.el.html guide.bg.html guide.zh_CN.html guide.zh_TW.html guide.uk.html
+webdoclibdir = $(libdir)/webdoc/help
+webdoclib_DATA = \
+ search-help.webdoc \
+ search-tips.webdoc \
+ search-guide.webdoc
+
FILESWML = $(wildcard $(srcdir)/*.wml)
EXTRA_DIST = $(FILESWML:$(srcdir)/%=%)
CLEANFILES = $(doc_DATA) *~ *.tmp
LINGUAS = $(shell grep -v '^\#' $(top_srcdir)/po/LINGUAS)
MO = $(LINGUAS:%=$(top_builddir)/po/%.gmo)
%.en.html %.fr.html %.de.html %.es.html %.ca.html %.pl.html %.pt.html %.hr.html %.it.html %.ja.html %.ru.html %.sk.html %.cs.html %.no.html %.sv.html %.el.html %.bg.html %.zh_CN.html %.zh_TW.html %.uk.html: %.html.wml $(top_srcdir)/config/config.wml $(top_builddir)/config/configbis.wml $(MO)
$(WML) -o\(ALL-LANG_*\)+LANG_EN:$*.en.html \
-o\(ALL-LANG_*\)+LANG_FR:$*.fr.html \
-o\(ALL-LANG_*\)+LANG_DE:$*.de.html \
-o\(ALL-LANG_*\)+LANG_ES:$*.es.html \
-o\(ALL-LANG_*\)+LANG_CA:$*.ca.html \
-o\(ALL-LANG_*\)+LANG_PT:$*.pt.html \
-o\(ALL-LANG_*\)+LANG_PL:$*.pl.html \
-o\(ALL-LANG_*\)+LANG_HR:$*.hr.html \
-o\(ALL-LANG_*\)+LANG_IT:$*.it.html \
-o\(ALL-LANG_*\)+LANG_JA:$*.ja.html \
-o\(ALL-LANG_*\)+LANG_RU:$*.ru.html \
-o\(ALL-LANG_*\)+LANG_SK:$*.sk.html \
-o\(ALL-LANG_*\)+LANG_CS:$*.cs.html \
-o\(ALL-LANG_*\)+LANG_NO:$*.no.html \
-o\(ALL-LANG_*\)+LANG_SV:$*.sv.html \
-o\(ALL-LANG_*\)+LANG_EL:$*.el.html \
-o\(ALL-LANG_*\)+LANG_BG:$*.bg.html \
-o\(ALL-LANG_*\)+LANG_ZH_CN:$*.zh_CN.html \
-o\(ALL-LANG_*\)+LANG_ZH_TW:$*.zh_TW.html \
-o\(ALL-LANG_*\)+LANG_UK:$*.uk.html $<
for lang in $(LINGUAS); do \
$(PYTHON) $(top_srcdir)/po/i18n_update_wml_target.py $${lang} "$*.$${lang}.html" ; \
done
diff --git a/modules/websearch/doc/admin/Makefile.am b/modules/websearch/doc/admin/Makefile.am
index e401f2549..797c60e8a 100644
--- a/modules/websearch/doc/admin/Makefile.am
+++ b/modules/websearch/doc/admin/Makefile.am
@@ -1,31 +1,37 @@
## $Id$
## This file is part of CDS Invenio.
## Copyright (C) 2002, 2003, 2004, 2005, 2006, 2007 CERN.
##
## CDS Invenio is free software; you can redistribute it and/or
## modify it under the terms of the GNU General Public License as
## published by the Free Software Foundation; either version 2 of the
## License, or (at your option) any later version.
##
## CDS Invenio is distributed in the hope that it will be useful, but
## WITHOUT ANY WARRANTY; without even the implied warranty of
## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-## General Public License for more details.
+## General Public License for more details.
##
## You should have received a copy of the GNU General Public License
## along with CDS Invenio; if not, write to the Free Software Foundation, Inc.,
## 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.
docdir = $(localstatedir)/www/admin/websearch
doc_DATA = index.html guide.html
+webdoclibdir = $(libdir)/webdoc/admin
+
+webdoclib_DATA = \
+ websearch-admin.webdoc \
+ websearch-admin-guide.webdoc
+
FILESWML = $(wildcard $(srcdir)/*.wml)
EXTRA_DIST = $(FILESWML:$(srcdir)/%=%)
CLEANFILES = $(doc_DATA) *~ *.tmp
%.html: %.html.wml $(top_srcdir)/config/config.wml $(top_builddir)/config/configbis.wml $(top_srcdir)/config/cdsnavbar.wml
$(WML) -o\(ALL-LANG_*\)+LANG_EN:$@ $<
$(PYTHON) $(top_srcdir)/po/i18n_update_wml_target.py en $@
\ No newline at end of file
diff --git a/modules/websearch/doc/admin/websearch-admin-guide.webdoc b/modules/websearch/doc/admin/websearch-admin-guide.webdoc
index 5beb8e1b1..b6403761c 100644
--- a/modules/websearch/doc/admin/websearch-admin-guide.webdoc
+++ b/modules/websearch/doc/admin/websearch-admin-guide.webdoc
@@ -1,580 +1,580 @@
## -*- mode: html; coding: utf-8; -*-
## $Id$
## This file is part of CDS Invenio.
## Copyright (C) 2002, 2003, 2004, 2005, 2006, 2007 CERN.
##
## CDS Invenio is free software; you can redistribute it and/or
## modify it under the terms of the GNU General Public License as
## published by the Free Software Foundation; either version 2 of the
## License, or (at your option) any later version.
##
## CDS Invenio is distributed in the hope that it will be useful, but
## WITHOUT ANY WARRANTY; without even the implied warranty of
## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
## General Public License for more details.
##
## You should have received a copy of the GNU General Public License
## along with CDS Invenio; if not, write to the Free Software Foundation, Inc.,
## 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.
-
+
This Admin Guide is not yet completed. Moreover, some
admin-level functionality for this module exists only in the form of
manual recipes. We are in the process of developing both the
guide as well as the web admin interface. If you are interested
in seeing some specific things implemented with high priority,
please contact us at . Thanks for your interest!
|
Version <: print generate_pretty_revision_date_string('$Id$'); :>
Contents
1. Overview
2. Edit Collection Tree
2.1 Add new collection
2.2 Add collection to tree
2.3 Modify existing tree
3. Edit Collection Parameters
3.1. Modify collection query
3.2. Modify access restrictions
3.3. Modify translations
3.4. Delete collection
3.5. Modify portalboxes
3.6. Modify search fields
3.7. Modify search options
3.8. Modify sort options
3.9. Modify rank options
3.10. Modify output formats
3.11. Configuration of related external collections
3.12. Detailed record page options
4. Webcoll Status
5. Collections Status
6. Edit Search Engine Parameters
7. Search Engine Cache
8. Additional Information
1. Overview
WebSearch Admin interface will help you to configure the search
collections that the end-users see. The WebSearch Admin functionality
can be basically separated into several parts: (i) how to organize
collections into collection tree; (ii) how to define
and edit collection parameters; (iii) how to update
collection cache via the webcoll daemon; and (iv) how
to influence the search engine behaviour and set various search engine parameters. These issues will be
subsequently described in the rest of this guide.
2. Edit Collection Tree
Metadata corpus in CDS Invenio is organized into collections. The
collections are organized in a tree. The collection tree is what the
end-users see when they start to navigate at . The collection tree is similar to what
other sites call Web Directories that organize Web into topical
categories, such as Google
Directory.
Note that CDS Invenio permits every collection in the tree to have
either "regular" or "virtual" sons. In other words, every node in the
collection tree may see either regular or virtual branches growing out
of it. This permits to create a tree with very complex, multi-level,
nested structures of regular and virtual branches, if needed, with the
aim to ease navigation to end-users from one branch to another. The
difference between a regular and a virtual branch will be explained in
detail further below in the section 2.2.
2.1 Add new collection
To add a new collection, enter its default name in the default
language of the installation () and click on the ADD button
to add it. There are two important actions that you have to perform
after adding a collection:
- You have to define the set of records that belong to this
collection. This is done by defining a search engine query
that would return all records belonging to this collection.
See hints on modify collection query below.
- In order for the collection to appear in the collection
navigation tree, you will have to attach it to some existing
collection in the tree. See hints on add
collection to tree below.
After you edit these two things, the collection is fully usable for
the search interface. It will appear in the search interface after
the next run of the WebColl Daemon.
However, you will probably want to customize further things, like
define collection name translation in various languages, define
collection web page portalboxes, define search options, etc, as
explained in this guide under the section Edit
Collection Parameters.
2.2 Add collection to tree
To attach a collection to the tree, choose first which collection
do you want to attach, then choose the father collection to attach to,
and then choose the fathership relation type between them (regular,
virtual).
The difference between the regular and the virtual relationship
goes as follows:
- regular relationship: If collection A is
composed of B and C, in a way that every document belonging to
A is either B or C, then this schema corresponds to the
regular type of relationship. For example, let A equals to
"Multimedia" and B and C to "Photos" and "Videos",
respectively. The latter collections would then be declared
as regular sons of "Multimedia" and they would appear in the
left-hand-side regular navigation tree entitled "Narrow by
Collection" in the collection tree.
- virtual relationship: In addition to the
regular decomposition of "Multimedia" into "Photos" and
"Videos", it may be advantageous to present a different,
orthogonal point of view on "Multimedia", based not on the
document type as seen above, but rather on the document
creator information. Let us consider that some (large) part
of the multimedia material was created by the "University
Multimedia Service" and some (small) part by an external TV
company such as BBC. It may be advantageous to advertize this
point of view to the end users too, so they they would be able
to easily navigate down to the kind of multimedia material
they are looking for. We can create two more collections
named "University Multimedia Service" and "BBC Pictures and
Videos" and declare them as virtual sons of the "Multimedia"
collection. These collections would then appear in the
right-hand-side virtual navigation tree entitled "Focus on" in
the collection tree.
The example presented above would then give us the following picture:
M u l t i m e d i a
Narrow by Collection: Focus on:
-------------------- ---------
[ ] Photos University Multimedia Service
[ ] Videos BBC Pictures and Videos
It is important to note that if a collection A is composed of B and
C as its regular sons, and offers X and Y as its virtual sons, then
every document belonging to A must also belong to either B or C. This
requirement does not apply for X and Y, because X and Y offer only a
"focus-on" orthogonal view on a (possibly small) part of the document
corpus of A. If end-users search the collection A, then they are
actually searching inside B and C, not X and Y. If they want to
search inside X or Y, they have to click upon X or Y first. One can
consider virtual branches as a sort of non-essential searching aid to
the end-user that is activated only when users are interested in a
particular "focus-on" relationship, provided that this "virtual" point
of view on A interests her.
2.3 Modify existing tree
To modify existing tree by WebSearch Admin Interface, click on
icons displayed next to collections. The meaning of icons is as
follows:
|
Remove chosen collection with its subcollections from the collection tree,
but do not delete the collection itself.
(For full deletion of a collection, see section 3.4.)
|
|
Move chosen collection up or down among its brothers and sisters, i.e.
change the order of collections inside the same level of the tree.
|
|
Move chosen collection among branches of the tree.
Press the first icon ()
to choose a collection to move, and the second icon
()
to select a new father collection that the chosen collection should be attached to.
|
3. Edit Collection Parameters
To finalize setting up of a collection, you could and should edit
many parameters, such as define list of records belonging to a
collection, define search fields, define search interface page
portalboxes, etc. In this section we will subsequently describe all
the various possibilities as they are presented in the Edit
Collection pages of the WebSearch Admin Interface.
3.1 Modify collection query
The collection query defines which documents belong to the
given collection. It is equal to the search term that retrieves all
documents belonging to the given collection, exactly as you would have
typed it into the search interface. For example, to define a
collection of all papers written by Ellis, you could set up your
collection query to be author:Ellis
.
Usually, the collection query is chosen on the basis of the
collection identifier that we store in MARC tag 980. This tag is
indexed in a logical field called collection
so that a
collection of Theses could be defined via
collection:THESIS
, supposing that every thesis metadata
record has got the text THESIS
in MARC tag 980.
(Nitpick: we use the term `collection' in two contexts here: once as a
collection of metadata documents, but also and as a logical field
name. We should have probably called the latter
collectionidentifier
or somesuch instead, but we hope the
difference is clear from... the context.)
If a collection does not have any collection query defined, then
its content is defined by means of the content of its descendants
(subcollections). This is the case for composed collections. For
example, the composed collection Articles & Preprints (no
query defined) will be defined as a father of Articles
(query: collection:ARTICLE
) and Preprints
(query: collection:PREPRINT
). In this case the
collection query for Articles & Preprints can stay empty.
Note that you should avoid defining non-empty collection query in
cases the collection has descendants, since it will prevail and the
descendants may not be taken into account. In the same way, if a
collection doesn't have any query nor any descendants defined, then
its contents will be empty.
To remove the collection query, set the parameter empty.
3.2 Modify access restrictions
If there is a need to restrict access to certain collections, you
can configure which Apache group the access should be granted to.
Users will then be prompted to enter Apache user and password. The
search engine will check whether user has entered appropriate
credentials and whether the user belongs to the Apache group that can
access this restricted collection.
So, from the admin point of view, you should set up corresponding
Apache user and group files, and you should have specified their
location in the appropriate section of CDS Invenio config.wml
file during CDS Invenio compilation.
(Note that in the future we may use CDS Invenio user identities in
order to avoid the Apache way of authentication.)
To remove any access restrictions, set the parameter empty.
3.3 Modify translations
You may define translations of collection names into the languages
of your CDS Invenio installation. Moreover, a collection name may be
different in different contexts (e.g. long name, short name, etc), so
that prior to modifying translations you will be asked to select which
name type you want to change.
The translations aren't mandatory to define. If a translation does
not exist in a language chosen by the end user, the end user will be
shown the collection name in the default language of this
installation.
Note also that the list of available languages depends on the
compile-time configuration (see the general config.wml
file).
3.4 Delete collection
The collection to be deleted must be first removed from the
collection tree. Any metametadata associated with the collection
(such as association to portalboxes, association to records belonging
to this collection, etc) will be lost, but the metadata itself will be
preserved (such as portalboxes themselves, records themselves, etc).
In total, association to records, output formats, translations, search
options, sort options, search fields, ranking method, and access
restriction will be lost. Use with care!
It may be a good idea only to remove the collection from the end
users interface, but to keep it "hidden" in a corner they don't see
and that they can't search when they search from Home. To achieve
this, do not delete the collection but simply remove it from the
collection tree so that it won't be attached to any father collection.
In this case the search interface page for this collection will stay
updated, but won't be neither shown in the tree nor searchable from
Home page. It will only be accessible via bookmarked URL, for
example.
3.5 Modify portalboxes
The search interface HTML page for a given collection may be
customized by what we call portalboxes. Portalboxes are used
to show various kinds of information to the end user, such as a text
box with some inline help information about the given collection, an
illustrative picture, etc.
To create a new portalbox, a title and a body must be given, where
the body can contain HTML if necessary.
To add a portalbox to the collection, you must choose an existing
portalbox, the language for which the portalbox should be shown, the
position of the portalbox on the screen, and the ordering score of
portalboxes.
- The language could be chosen depending on the language
used in the portalbox body. Since a portalbox is not necessarily
bound to one particular language, one portalbox may be reused for
several languages, which is particularly suitable for portalboxes
containing language-independent content such as images.
- The position of the portalbox on the screen is chosen
from several predefined positions, such as right-top, before-title,
after-title, before-narrow-by-collection-box, etc. You may present
several portalboxes on the same position in the same language, in
which case they will be shown by the order of decreasing score.
- The score defines the order of portalboxes that are to be
presented in the same position and in the same language context.
3.6 Modify search fields
The search field is a logical field (such as author,
title, etc) that will be proposed to the end users in Simple and
Advanced Search interface pages. If you do not set any search fields
for a collection, then a default list (author, title, year, etc) will
be shown.
Note that if you want to add a new logical field or modify existing
physical MARC tags for a logical field, you have to use the BibIndex Admin interface.
3.7 Modify search options
The search option is like search field
in a way that it permits the end user to narrow down his search to
some logical field such as "subject", but unlike with the search field
the user is not required to type his query in a free text form;
rather, the search interface proposes to the end user several
interesting predefined values prepared by the administrators that the
end user may choose from. For example, an "author search" concept is
a good example of search field usage, since there is plenty of author
names to be matched, so that the end users would usually type the name
they wish to find in free text form; while a "subject search" concept
is a good example for search option usage, since usually there is a
limited number of subjects in the system given by local subject
classification scheme, that the end users do not necessarily know
about and that they are free to choose from a list. As a rule of
thumb, the search field concept denotes the case of unlimited number
possibilites of distinct values to be matched in a given field
(e.g. author, title, keyword); while the search option concept denotes
the case of only a handful or so distinct values to be matched in a
given field (e.g. subject, division, year).
Search options are shown in the "Advanced Search" interfaces only,
while search fields are shown both in "Simple Search" and "Advanced
Search" interface. (Although if you want to add a search option to
the "Simple Search" interface, you can achieve it by creating
appropriate HTML code in a portalbox.) The search
options order, as well as the order of search option values, may be
defined by means of 'move' arrows in the WebSearch Admin interface.
To add a new search option, a field name must first be chosen (for
example "subject") and then a list of possible field values must be
entered (for example "Mathematics", "Physics", "Chemistry", "Biology",
etc). Note that if you want to add a new logical field or modify
existing physical MARC tags for a logical field, you have to use the
BibIndex Admin interface.
3.8 Modify sort options
You may define a list of logical fields that the end users will be
able to choose for the sorting purposes. For example, "first author"
or "year". If you don't select anything, a default list (author,
title, year, etc) will be shown.
Note that if you want to add a new logical field or modify existing
physical MARC tags for a logical field, you have to use the BibIndex Admin interface.
3.9 Modify rank options
To enable a certain rank method for a collection, select the method
from the "enable rank method" box and add it. The documents in this
collection will then be included in the ranking sets the next time the
BibRank daemon will run. To disable a method the process is the same,
but select the method from the 'disable rank method' box.
Note that if you want to add new ranking method or modify existing
ranking method, you have to use the BibRank Admin interface.
3.10 Modify output formats
Each collection may have several output formats defined. The end
users will be able to choose a format they want to see their search
results list in. Most formats like HTML brief or XML Dublin Core are
interesting for each collection, but some formats like HTML portfolio
are only interesting for Photographs collection, not for Articles
collection. The interface will permit you to choose the formats
appropriate for a given collection. The order of formats can be
changed using the 'move' arrows.
Note that if you want to add new output format ('behaviour') or
modify existing output format, you have to use the BibFormat Admin interface.
3.11 Configuration of related external collections
You can customize each collection to provide your users an
additional source of information external to your repository: in a
book collection you might want for example to provide a link to
Amazon items corresponding to the user's query. Futhermore, for
some external services only, you can set the collection to display the
results directly in CDS Invenio search results page.
The following settings are available:
- Disabled
- The external collection is not shown to the user.
-
- See also
- A link to the external collection listing the items corresponding to user's query is displayed (only once a query has been performed).
- External search
- User can ask to perform a search in parallel on your repository and on the external collection. Results are shown in the CDS Invenio search results page. Not available for all external collections.
-
- External search checked
- Same as above, but the external collection is searched by default. Not available for all external collections.
You can also apply the settings to sub-collections, by checking the
"Apply also to daughter collections" checkboxes when you apply
your modifications.
3.12 Detailed record page options
These settings let you define how the detailed view (such as /record/1) of records in this
collection will look like.
More details are available in the WebStyle admin
guide.
Please note that since a record might belong to several
collections, conflicts between collection settings might occur. This
is especially true in the case of virtual collections. It is
therefore the settings of the primary collection of the record
which are applied.
4. Webcoll Status
WebColl is the daemon that normally periodically runs via BibSched and that updates the
collection cache with the collection parameters configured in the
previous section. Alternatively to running webcoll via BibSched, you
can also run it any time you want from the command line, either for
all collections or for selected collection only. See the --help
option.
The WebSearch Admin interface has got a WebColl Status menu that
shows when the collection cache was last updated and when the next
update is scheduled. It warns in case something suspicious was
discovered.
5. Collections Status
The Collection Status menu of the WebSearch Admin interface shows
the list of all collections and checks if there is anything wrong
regarding configuration of collections, together with the languages
the collection name has been translated into, etc. Here is the
detailed explanation of the functionality:
- ID
- ID of the collection.
- Name
- Name of the collection.
- Query
- The collection definition query. Note that it should be empty if
a collection got subcollections. If not, then a query is needed.
- Subcollections
- The subcollections that the collection is composed of. Note that
a collection which got defined by a query should not have any
subcollections.
- Restricted
- A restricted collection can only be accessed by users belonging to
the Apache groups mentioned in this column.
- I18N
- Show which languages the collection name has been translated into.
- Status
- If no errors was found, OK is displayed for each
collection. If an error was found, then an error number and short
message are shown. The meaning of the error messages is the
following: 1:Query means that the collection was defined via
a query but also via subcollections too; 2:Query means that
the collection wasn't defined neither via query nor via
subcollections.
6. Edit Search Engine Parameters
7. Search Engine Cache
8. Additional Information
WebSearch Internals
diff --git a/modules/websearch/doc/admin/websearch-admin.webdoc b/modules/websearch/doc/admin/websearch-admin.webdoc
index 505fbedcc..d834264d1 100644
--- a/modules/websearch/doc/admin/websearch-admin.webdoc
+++ b/modules/websearch/doc/admin/websearch-admin.webdoc
@@ -1,31 +1,31 @@
## $Id$
## This file is part of CDS Invenio.
## Copyright (C) 2002, 2003, 2004, 2005, 2006, 2007 CERN.
##
## CDS Invenio is free software; you can redistribute it and/or
## modify it under the terms of the GNU General Public License as
## published by the Free Software Foundation; either version 2 of the
## License, or (at your option) any later version.
##
## CDS Invenio is distributed in the hope that it will be useful, but
## WITHOUT ANY WARRANTY; without even the implied warranty of
## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
## General Public License for more details.
##
## You should have received a copy of the GNU General Public License
## along with CDS Invenio; if not, write to the Free Software Foundation, Inc.,
## 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.
-
+
- WebSearch Admin Interface
- Start area for WebSearch administration.
- WebSearch Admin Guide
- Everything you want to know about WebSearch administration
diff --git a/modules/websearch/doc/hacking/Makefile.am b/modules/websearch/doc/hacking/Makefile.am
index d00b9e787..d09e926bc 100644
--- a/modules/websearch/doc/hacking/Makefile.am
+++ b/modules/websearch/doc/hacking/Makefile.am
@@ -1,31 +1,38 @@
## $Id$
## This file is part of CDS Invenio.
## Copyright (C) 2002, 2003, 2004, 2005, 2006, 2007 CERN.
##
## CDS Invenio is free software; you can redistribute it and/or
## modify it under the terms of the GNU General Public License as
## published by the Free Software Foundation; either version 2 of the
## License, or (at your option) any later version.
##
## CDS Invenio is distributed in the hope that it will be useful, but
## WITHOUT ANY WARRANTY; without even the implied warranty of
## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
## General Public License for more details.
##
## You should have received a copy of the GNU General Public License
## along with CDS Invenio; if not, write to the Free Software Foundation, Inc.,
## 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.
docdir = $(localstatedir)/www/hacking/websearch
doc_DATA=api.html stages.html index.html
+webdoclibdir = $(libdir)/webdoc/hacking
+
+webdoclib_DATA = \
+ search-engine-internals.webdoc \
+ search-engine-api.webdoc \
+ search-engine-stages.webdoc
+
FILESWML = $(wildcard $(srcdir)/*.wml)
EXTRA_DIST = $(FILESWML:$(srcdir)/%=%)
CLEANFILES = $(doc_DATA) *~ *.tmp
%.html: %.html.wml $(top_srcdir)/config/config.wml $(top_builddir)/config/configbis.wml
$(WML) -o\(ALL-LANG_*\)+LANG_EN:$@ $<
$(PYTHON) $(top_srcdir)/po/i18n_update_wml_target.py en $@
\ No newline at end of file
diff --git a/modules/websearch/doc/search-guide.webdoc b/modules/websearch/doc/search-guide.webdoc
index 6df27c7f8..9ca0642b1 100644
--- a/modules/websearch/doc/search-guide.webdoc
+++ b/modules/websearch/doc/search-guide.webdoc
@@ -1,22294 +1,22294 @@
## -*- mode: html; coding: utf-8; -*-
## $Id$
##
## This file is part of CDS Invenio.
## Copyright (C) 2002, 2003, 2004, 2005, 2006, 2007 CERN.
##
## CDS Invenio is free software; you can redistribute it and/or
## modify it under the terms of the GNU General Public License as
## published by the Free Software Foundation; either version 2 of the
## License, or (at your option) any later version.
##
## CDS Invenio is distributed in the hope that it will be useful, but
## WITHOUT ANY WARRANTY; without even the implied warranty of
## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
## General Public License for more details.
##
## You should have received a copy of the GNU General Public License
## along with CDS Invenio; if not, write to the Free Software Foundation, Inc.,
## 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.
-
+
Our search engine tries to offer today's typical web searching
experience, as gained with popular search engines such as Google. The nature of bibliographic
searching differs from that of a web page searching, though. We
provide many extensions to enable a complex and precise structured
search, including an combined metadata, fulltext and reference search
in one go. This page lists several tips and tricks that you may find
useful to this effect.
Our search engine tries to offer today's typical web searching
experience, as gained with popular search engines such as Google. The nature of bibliographic
searching differs from that of a web page searching, though. We
provide many extensions to enable a complex and precise structured
search, including an combined metadata, fulltext and reference search
in one go. This page lists several tips and tricks that you may find
useful to this effect.
Unsere Suchmaschine bietet den heutigen Stand der Web-Such
Technologie, die auch von bekannten Suchmaschinen wie zum Beispiel
Google angeboten werden. Im Detail
unterscheidet sich jedoch die bibliographische Suche von einer
Web-Suche. Wir bieten mehrere Erweiterungen an, damit eine komplexe
und genau strukturierte Suche möglich wird, inklusiv einer
kombinierten Metadatensuche, Volltextsuche und Referenzsuche. Diese
Seite stellt Tipps und Tricks vor, die für eine effektive Suche
nützlich sind.
El motor de búsqueda de este sistema trata de ofrecer la
tecnología más actual de búsqueda web, desarrollada por buscadores tan
populares como Google . Sin
embargo, la naturaleza de una búsqueda bibliográfica difiere
considerablemente de la de una página Web. La alternativa propuesta
es la de proporcionar numerosas extensiones que hagan
posible búsquedas de estructura compleja y precisa, incluso combinando
metadatos, texto completo y citas bibliográficas en una misma
consulta. Esta página ofrece una serie consejos útiles para conseguir
una búsqueda más eficaz.
El motor de cerca d'aquest sistema tracta d'oferir la tecnologia
més actual de cerca web, desenvolupada per cercadors tant populars com
Google . La naturalesa d'una
cerca bibliogràfica, però, difereix considerablement de la d'una
página Web. L'alternativa proposada és la de proporcionar
nombroses extensions que permetin cerques d'estructura complexa i
precisa, inclosa la combinació de metadades, text complet i
referències bibliogràfiques a una mateixa cerca. Aquesta pàgina
ofereix una sèrie de consells útils per aconseguir una cerca més
eficaç.
Our search engine tries to offer today's typical web searching
experience, as gained with popular search engines such as Google. The nature of bibliographic
searching differs from that of a web page searching, though. We
provide many extensions to enable a complex and precise structured
search, including an combined metadata, fulltext and reference search
in one go. This page lists several tips and tricks that you may find
useful to this effect.
Our search engine tries to offer today's typical web searching
experience, as gained with popular search engines such as Google. The nature of bibliographic
searching differs from that of a web page searching, though. We
provide many extensions to enable a complex and precise structured
search, including an combined metadata, fulltext and reference search
in one go. This page lists several tips and tricks that you may find
useful to this effect.
Our search engine tries to offer today's typical web searching
experience, as gained with popular search engines such as Google. The nature of bibliographic
searching differs from that of a web page searching, though. We
provide many extensions to enable a complex and precise structured
search, including an combined metadata, fulltext and reference search
in one go. This page lists several tips and tricks that you may find
useful to this effect.
Our search engine tries to offer today's typical web searching
experience, as gained with popular search engines such as Google. The nature of bibliographic
searching differs from that of a web page searching, though. We
provide many extensions to enable a complex and precise structured
search, including an combined metadata, fulltext and reference search
in one go. This page lists several tips and tricks that you may find
useful to this effect.
Our search engine tries to offer today's typical web searching
experience, as gained with popular search engines such as Google. The nature of bibliographic
searching differs from that of a web page searching, though. We
provide many extensions to enable a complex and precise structured
search, including an combined metadata, fulltext and reference search
in one go. This page lists several tips and tricks that you may find
useful to this effect.
Our search engine tries to offer today's typical web searching
experience, as gained with popular search engines such as Google. The nature of bibliographic
searching differs from that of a web page searching, though. We
provide many extensions to enable a complex and precise structured
search, including an combined metadata, fulltext and reference search
in one go. This page lists several tips and tricks that you may find
useful to this effect.
Our search engine tries to offer today's typical web searching
experience, as gained with popular search engines such as Google. The nature of bibliographic
searching differs from that of a web page searching, though. We
provide many extensions to enable a complex and precise structured
search, including an combined metadata, fulltext and reference search
in one go. This page lists several tips and tricks that you may find
useful to this effect.
Our search engine tries to offer today's typical web searching
experience, as gained with popular search engines such as Google. The nature of bibliographic
searching differs from that of a web page searching, though. We
provide many extensions to enable a complex and precise structured
search, including an combined metadata, fulltext and reference search
in one go. This page lists several tips and tricks that you may find
useful to this effect.
Our search engine tries to offer today's typical web searching
experience, as gained with popular search engines such as Google. The nature of bibliographic
searching differs from that of a web page searching, though. We
provide many extensions to enable a complex and precise structured
search, including an combined metadata, fulltext and reference search
in one go. This page lists several tips and tricks that you may find
useful to this effect.
Our search engine tries to offer today's typical web searching
experience, as gained with popular search engines such as Google. The nature of bibliographic
searching differs from that of a web page searching, though. We
provide many extensions to enable a complex and precise structured
search, including an combined metadata, fulltext and reference search
in one go. This page lists several tips and tricks that you may find
useful to this effect.
Our search engine tries to offer today's typical web searching
experience, as gained with popular search engines such as Google. The nature of bibliographic
searching differs from that of a web page searching, though. We
provide many extensions to enable a complex and precise structured
search, including an combined metadata, fulltext and reference search
in one go. This page lists several tips and tricks that you may find
useful to this effect.
Our search engine tries to offer today's typical web searching
experience, as gained with popular search engines such as Google. The nature of bibliographic
searching differs from that of a web page searching, though. We
provide many extensions to enable a complex and precise structured
search, including an combined metadata, fulltext and reference search
in one go. This page lists several tips and tricks that you may find
useful to this effect.
Our search engine tries to offer today's typical web searching
experience, as gained with popular search engines such as Google. The nature of bibliographic
searching differs from that of a web page searching, though. We
provide many extensions to enable a complex and precise structured
search, including an combined metadata, fulltext and reference search
in one go. This page lists several tips and tricks that you may find
useful to this effect.
Our search engine tries to offer today's typical web searching
experience, as gained with popular search engines such as Google. The nature of bibliographic
searching differs from that of a web page searching, though. We
provide many extensions to enable a complex and precise structured
search, including an combined metadata, fulltext and reference search
in one go. This page lists several tips and tricks that you may find
useful to this effect.
Our search engine tries to offer today's typical web searching
experience, as gained with popular search engines such as Google. The nature of bibliographic
searching differs from that of a web page searching, though. We
provide many extensions to enable a complex and precise structured
search, including an combined metadata, fulltext and reference search
in one go. This page lists several tips and tricks that you may find
useful to this effect.
Index
Simple versus advanced search
Search guidance
Searching for words versus phrases
Boolean queries
Special characters and punctuation
International characters
Word truncation/stemming
Structured metadata search
Regular expressions
Span queries
Combined metadata/fulltext/citation search
Frequently asked questions
How to wisely choose your search terms (speed-wise)
How to search for publications by a given author
How to sort according to a certain pattern
How to get documents from other servers (Google, SPIRES, KEK)
How to search in fulltext files
How to search for citations
Index
Simple versus advanced search
Search guidance
Searching for words versus phrases
Boolean queries
Special characters and punctuation
International characters
Word truncation/stemming
Structured metadata search
Regular expressions
Span queries
Combined metadata/fulltext/citation search
Frequently asked questions
How to wisely choose your search terms (speed-wise)
How to search for publications by a given author
How to sort according to a certain pattern
How to get documents from other servers (Google, SPIRES, KEK)
How to search in fulltext files
How to search for citations
Inhaltsverzeichnis
Einfache versus erweiterte Suche
Grundlagen
Suche nach Wörtern und Wortgruppen
Boolsche Suche
Spezielle Zeichen und Notation
Internationale Zeichen
Trunkierung
Strukturierte Metadatensuche
Regular expressions
Bereichs-Recherche
Kombinierte Metadaten-/Volltext-/Zitatsuche
FAQ
Wie wähle ich am geschicktesten meinen Suchbegriff
Wie suche ich nach Publikationen eines bestimmten Autors
Wie lasse ich Ergebnisse auf eine bestimmte Weise sortieren
Wie bekomme ich Dokumente anderer Server (Google, SPIRES, KEK)
Wie kann ich in verknüpften Volltextdateien suchen
Wie kann ich nach Zitaten suchen
Índice
Búsqueda simple versus avanzada
Búsqueda guiada
Búsqueda por palabras versus búsqueda por frases
Consultas booleanas
Caracteres especiales y puntuación
Caracteres internacionales
Truncamientos y búsquedas por raíz
Búsqueda por metadatos estructurados
Expresiones regulares
Consultas por rango
Combinación de metadatos/texto completo/cita bibliográfica
Preguntas frecuentes
Elegir correctamente los términos de búsqueda (speed-wise)
¿Cómo localizar publicaciones a partir del autor?
¿Cómo ordenar acorde a cierto patrón de ordenación?
¿Cómo obtener documentos de otros servidores? (Google, SPIRES, KEK)
¿Cómo buscar en ficheros a texto completo?
¿Cómo buscar citas bibliogáficas?
Índex
Cerca simple versus avançada
Cerca guiada
Cerca per paraules versus cerca per frases
Consultes booleanes
Caracters especials i puntuació
Caracters internacionals
Truncaments i cercques per arrel
Cerca por metadadess estructurades
Expressions regulars
Consultes per rang
Combinació de metadades/text complet/referència bibliogràfica
Preguntes freqüents
Escollir correctament els térmes de cerca (speed-wise)
Com localitzar publicacions a partir de l'autor?
Com ordenar d'acord a un patró d'ordenació?
Com obtenir documents d'altres servidors? (Google, SPIRES, KEK)
Cómo cercar a fitxers a text complet?
Cómo cercar referències bibliogàfiques?
Index
Simple versus advanced search
Search guidance
Searching for words versus phrases
Boolean queries
Special characters and punctuation
International characters
Word truncation/stemming
Structured metadata search
Regular expressions
Span queries
Combined metadata/fulltext/citation search
Frequently asked questions
How to wisely choose your search terms (speed-wise)
How to search for publications by a given author
How to sort according to a certain pattern
How to get documents from other servers (Google, SPIRES, KEK)
How to search in fulltext files
How to search for citations
Index
Simple versus advanced search
Search guidance
Searching for words versus phrases
Boolean queries
Special characters and punctuation
International characters
Word truncation/stemming
Structured metadata search
Regular expressions
Span queries
Combined metadata/fulltext/citation search
Frequently asked questions
How to wisely choose your search terms (speed-wise)
How to search for publications by a given author
How to sort according to a certain pattern
How to get documents from other servers (Google, SPIRES, KEK)
How to search in fulltext files
How to search for citations
Index
Simple versus advanced search
Search guidance
Searching for words versus phrases
Boolean queries
Special characters and punctuation
International characters
Word truncation/stemming
Structured metadata search
Regular expressions
Span queries
Combined metadata/fulltext/citation search
Frequently asked questions
How to wisely choose your search terms (speed-wise)
How to search for publications by a given author
How to sort according to a certain pattern
How to get documents from other servers (Google, SPIRES, KEK)
How to search in fulltext files
How to search for citations
Index
Simple versus advanced search
Search guidance
Searching for words versus phrases
Boolean queries
Special characters and punctuation
International characters
Word truncation/stemming
Structured metadata search
Regular expressions
Span queries
Combined metadata/fulltext/citation search
Frequently asked questions
How to wisely choose your search terms (speed-wise)
How to search for publications by a given author
How to sort according to a certain pattern
How to get documents from other servers (Google, SPIRES, KEK)
How to search in fulltext files
How to search for citations
Index
Simple versus advanced search
Search guidance
Searching for words versus phrases
Boolean queries
Special characters and punctuation
International characters
Word truncation/stemming
Structured metadata search
Regular expressions
Span queries
Combined metadata/fulltext/citation search
Frequently asked questions
How to wisely choose your search terms (speed-wise)
How to search for publications by a given author
How to sort according to a certain pattern
How to get documents from other servers (Google, SPIRES, KEK)
How to search in fulltext files
How to search for citations
Index
Simple versus advanced search
Search guidance
Searching for words versus phrases
Boolean queries
Special characters and punctuation
International characters
Word truncation/stemming
Structured metadata search
Regular expressions
Span queries
Combined metadata/fulltext/citation search
Frequently asked questions
How to wisely choose your search terms (speed-wise)
How to search for publications by a given author
How to sort according to a certain pattern
How to get documents from other servers (Google, SPIRES, KEK)
How to search in fulltext files
How to search for citations
Index
Simple versus advanced search
Search guidance
Searching for words versus phrases
Boolean queries
Special characters and punctuation
International characters
Word truncation/stemming
Structured metadata search
Regular expressions
Span queries
Frequently asked questions
Combined metadata/fulltext/citation search
How to wisely choose your search terms (speed-wise)
How to search for publications by a given author
How to sort according to a certain pattern
How to get documents from other servers (Google, SPIRES, KEK)
How to search in fulltext files
How to search for citations
Index
Simple versus advanced search
Search guidance
Searching for words versus phrases
Boolean queries
Special characters and punctuation
International characters
Word truncation/stemming
Structured metadata search
Regular expressions
Span queries
Combined metadata/fulltext/citation search
Frequently asked questions
How to wisely choose your search terms (speed-wise)
How to search for publications by a given author
How to sort according to a certain pattern
How to get documents from other servers (Google, SPIRES, KEK)
How to search in fulltext files
How to search for citations
Index
Simple versus advanced search
Search guidance
Searching for words versus phrases
Boolean queries
Special characters and punctuation
International characters
Word truncation/stemming
Structured metadata search
Regular expressions
Span queries
Combined metadata/fulltext/citation search
Frequently asked questions
How to wisely choose your search terms (speed-wise)
How to search for publications by a given author
How to sort according to a certain pattern
How to get documents from other servers (Google, SPIRES, KEK)
How to search in fulltext files
How to search for citations
Index
Simple versus advanced search
Search guidance
Searching for words versus phrases
Boolean queries
Special characters and punctuation
International characters
Word truncation/stemming
Structured metadata search
Regular expressions
Span queries
Combined metadata/fulltext/citation search
Frequently asked questions
How to wisely choose your search terms (speed-wise)
How to search for publications by a given author
How to sort according to a certain pattern
How to get documents from other servers (Google, SPIRES, KEK)
How to search in fulltext files
How to search for citations
Index
Simple versus advanced search
Search guidance
Searching for words versus phrases
Boolean queries
Special characters and punctuation
International characters
Word truncation/stemming
Structured metadata search
Regular expressions
Span queries
Combined metadata/fulltext/citation search
Frequently asked questions
How to wisely choose your search terms (speed-wise)
How to search for publications by a given author
How to sort according to a certain pattern
How to get documents from other servers (Google, SPIRES, KEK)
How to search in fulltext files
How to search for citations
Index
Simple versus advanced search
Search guidance
Searching for words versus phrases
Boolean queries
Special characters and punctuation
International characters
Word truncation/stemming
Structured metadata search
Regular expressions
Span queries
Combined metadata/fulltext/citation search
Frequently asked questions
How to wisely choose your search terms (speed-wise)
How to search for publications by a given author
How to sort according to a certain pattern
How to get documents from other servers (Google, SPIRES, KEK)
How to search in fulltext files
How to search for citations
Index
Simple versus advanced search
Search guidance
Searching for words versus phrases
Boolean queries
Special characters and punctuation
International characters
Word truncation/stemming
Structured metadata search
Regular expressions
Span queries
Combined metadata/fulltext/citation search
Frequently asked questions
How to wisely choose your search terms (speed-wise)
How to search for publications by a given author
How to sort according to a certain pattern
How to get documents from other servers (Google, SPIRES, KEK)
How to search in fulltext files
How to search for citations
Index
Simple versus advanced search
Search guidance
Searching for words versus phrases
Boolean queries
Special characters and punctuation
International characters
Word truncation/stemming
Structured metadata search
Regular expressions
Span queries
Combined metadata/fulltext/citation search
Frequently asked questions
How to wisely choose your search terms (speed-wise)
How to search for publications by a given author
How to sort according to a certain pattern
How to get documents from other servers (Google, SPIRES, KEK)
How to search in fulltext files
How to search for citations
Index
Simple versus advanced search
Search guidance
Searching for words versus phrases
Boolean queries
Special characters and punctuation
International characters
Word truncation/stemming
Structured metadata search
Regular expressions
Span queries
Combined metadata/fulltext/citation search
Frequently asked questions
How to wisely choose your search terms (speed-wise)
How to search for publications by a given author
How to sort according to a certain pattern
How to get documents from other servers (Google, SPIRES, KEK)
How to search in fulltext files
How to search for citations
The default search mode is simple search that
basically provides you with one input box where you can type your
query, followed by a possibility to choose one of the common indexes
to search within. You would usually simply type the keywords you are
interested in and hit return. For example, if you are interested in
documents on standard model that are written by (or mention)
Ellis, you would type:
and on the search results page you could further add/remove keywords
to get more precisely at what you are looking for, as is mentioned below.
The default search mode is simple search that
basically provides you with one input box where you can type your
query, followed by a possibility to choose one of the common indexes
to search within. You would usually simply type the keywords you are
interested in and hit return. For example, if you are interested in
documents on standard model that are written by (or mention)
Ellis, you would type:
and on the search results page you could further add/remove keywords
to get more precisely at what you are looking for, as is mentioned below.
The default search mode is simple search that
basically provides you with one input box where you can type your
query, followed by a possibility to choose one of the common indexes
to search within. You would usually simply type the keywords you are
interested in and hit return. For example, if you are interested in
documents on standard model that are written by (or mention)
Ellis, you would type:
and on the search results page you could further add/remove keywords
to get more precisely at what you are looking for, as is mentioned below.
The default search mode is simple search that
basically provides you with one input box where you can type your
query, followed by a possibility to choose one of the common indexes
to search within. You would usually simply type the keywords you are
interested in and hit return. For example, if you are interested in
documents on standard model that are written by (or mention)
Ellis, you would type:
and on the search results page you could further add/remove keywords
to get more precisely at what you are looking for, as is mentioned below.
The default search mode is simple search that
basically provides you with one input box where you can type your
query, followed by a possibility to choose one of the common indexes
to search within. You would usually simply type the keywords you are
interested in and hit return. For example, if you are interested in
documents on standard model that are written by (or mention)
Ellis, you would type:
and on the search results page you could further add/remove keywords
to get more precisely at what you are looking for, as is mentioned below.
The default search mode is simple search that
basically provides you with one input box where you can type your
query, followed by a possibility to choose one of the common indexes
to search within. You would usually simply type the keywords you are
interested in and hit return. For example, if you are interested in
documents on standard model that are written by (or mention)
Ellis, you would type:
and on the search results page you could further add/remove keywords
to get more precisely at what you are looking for, as is mentioned below.
The default search mode is simple search that
basically provides you with one input box where you can type your
query, followed by a possibility to choose one of the common indexes
to search within. You would usually simply type the keywords you are
interested in and hit return. For example, if you are interested in
documents on standard model that are written by (or mention)
Ellis, you would type:
and on the search results page you could further add/remove keywords
to get more precisely at what you are looking for, as is mentioned below.
The default search mode is simple search that
basically provides you with one input box where you can type your
query, followed by a possibility to choose one of the common indexes
to search within. You would usually simply type the keywords you are
interested in and hit return. For example, if you are interested in
documents on standard model that are written by (or mention)
Ellis, you would type:
and on the search results page you could further add/remove keywords
to get more precisely at what you are looking for, as is mentioned below.
The default search mode is simple search that
basically provides you with one input box where you can type your
query, followed by a possibility to choose one of the common indexes
to search within. You would usually simply type the keywords you are
interested in and hit return. For example, if you are interested in
documents on standard model that are written by (or mention)
Ellis, you would type:
and on the search results page you could further add/remove keywords
to get more precisely at what you are looking for, as is mentioned below.
The default search mode is simple search that
basically provides you with one input box where you can type your
query, followed by a possibility to choose one of the common indexes
to search within. You would usually simply type the keywords you are
interested in and hit return. For example, if you are interested in
documents on standard model that are written by (or mention)
Ellis, you would type:
and on the search results page you could further add/remove keywords
to get more precisely at what you are looking for, as is mentioned below.
The default search mode is simple search that
basically provides you with one input box where you can type your
query, followed by a possibility to choose one of the common indexes
to search within. You would usually simply type the keywords you are
interested in and hit return. For example, if you are interested in
documents on standard model that are written by (or mention)
Ellis, you would type:
and on the search results page you could further add/remove keywords
to get more precisely at what you are looking for, as is mentioned below.
The default search mode is simple search that
basically provides you with one input box where you can type your
query, followed by a possibility to choose one of the common indexes
to search within. You would usually simply type the keywords you are
interested in and hit return. For example, if you are interested in
documents on standard model that are written by (or mention)
Ellis, you would type:
and on the search results page you could further add/remove keywords
to get more precisely at what you are looking for, as is mentioned below.
The default search mode is simple search that
basically provides you with one input box where you can type your
query, followed by a possibility to choose one of the common indexes
to search within. You would usually simply type the keywords you are
interested in and hit return. For example, if you are interested in
documents on standard model that are written by (or mention)
Ellis, you would type:
and on the search results page you could further add/remove keywords
to get more precisely at what you are looking for, as is mentioned below.
The default search mode is simple search that
basically provides you with one input box where you can type your
query, followed by a possibility to choose one of the common indexes
to search within. You would usually simply type the keywords you are
interested in and hit return. For example, if you are interested in
documents on standard model that are written by (or mention)
Ellis, you would type:
and on the search results page you could further add/remove keywords
to get more precisely at what you are looking for, as is mentioned below.
The default search mode is simple search that
basically provides you with one input box where you can type your
query, followed by a possibility to choose one of the common indexes
to search within. You would usually simply type the keywords you are
interested in and hit return. For example, if you are interested in
documents on standard model that are written by (or mention)
Ellis, you would type:
and on the search results page you could further add/remove keywords
to get more precisely at what you are looking for, as is mentioned below.
The default search mode is simple search that
basically provides you with one input box where you can type your
query, followed by a possibility to choose one of the common indexes
to search within. You would usually simply type the keywords you are
interested in and hit return. For example, if you are interested in
documents on standard model that are written by (or mention)
Ellis, you would type:
and on the search results page you could further add/remove keywords
to get more precisely at what you are looking for, as is mentioned below.
The default search mode is simple search that
basically provides you with one input box where you can type your
query, followed by a possibility to choose one of the common indexes
to search within. You would usually simply type the keywords you are
interested in and hit return. For example, if you are interested in
documents on standard model that are written by (or mention)
Ellis, you would type:
and on the search results page you could further add/remove keywords
to get more precisely at what you are looking for, as is mentioned below.
The default search mode is simple search that
basically provides you with one input box where you can type your
query, followed by a possibility to choose one of the common indexes
to search within. You would usually simply type the keywords you are
interested in and hit return. For example, if you are interested in
documents on standard model that are written by (or mention)
Ellis, you would type:
and on the search results page you could further add/remove keywords
to get more precisely at what you are looking for, as is mentioned below.
El modo de búsqueda por defecto es la búsqueda
simple que permite, en términos generales, escribir una
consulta en el campo de texto, acompañado de la posibilidad de
seleccionar uno de los índices comunes sobre los que efectuar la
consulta. Se introducen las palabras clave a buscar y se acciona la
consulta mediante la tecla de retorno (o intro). Por ejemplo, si
interesa recuperar documentos sobre modelos estándar que han
sido escritos por (o que mencionan a) Ellis, debemos
escribir:
y en la página de resultados de la búsqueda podemos volver a añadir o
quitar palabras clave para obtener mayor precisión en los resultados,
tal y como se especifica en más adelante.
La cerca per defecte és la cerca simple, que
fonamentalment permet escriure la consulta dins un camp de text,
seguit de la possibilitat d'escollir un dels índexs comuns sobre els
que realitzar la consulta. S'introdueixen les paraules clau a buscar
i s'acciona la consulta mitjançant la tecla de retorn (intro). Per
exemple, si interessa recuperar documents sobre models
estàndard que han estat escrits per (o que fan esment a)
Ellis, haurem d'escriure:
i a la pàgina dels resultats de la cerca podem tornar a afegir o
treure paraules clau per tal d'obtenir més precisió als resultats, tal
i com s'especifica més endavant.
The advanced search interface provides you with
explicit tools to play with: you can change the matching type from the
default word matching to phrase searching or the regular matching; you
can use boolean queries in several indexes, etc. For example, to find
all the documents written by Ellis, J spelled exactly that
way that contain either of the words muon or
neutrino in the title and that were published in
2001, you would type:
Note that Simple Search can provide you basically the same
functionality, if you make use of special syntax that is explained in
the text below. The simple-versus-advanced does not refer to the
functionality that is being provided but rather to the amount of
parametrization you can "tweak". We conform to the common
use of the simple/advanced terms as found in other search engines.
Much of what follows will deal with a question on "how a power user
would use the simple search interface". Recall that you can always go
to the Advanced Search for more query assistance.
The advanced search interface provides you with
explicit tools to play with: you can change the matching type from the
default word matching to phrase searching or the regular matching; you
can use boolean queries in several indexes, etc. For example, to find
all the documents written by Ellis, J spelled exactly that
way that contain either of the words muon or
neutrino in the title and that were published in
2001, you would type:
Note that Simple Search can provide you basically the same
functionality, if you make use of special syntax that is explained in
the text below. The simple-versus-advanced does not refer to the
functionality that is being provided but rather to the amount of
parametrization you can "tweak". We conform to the common
use of the simple/advanced terms as found in other search engines.
Much of what follows will deal with a question on "how a power user
would use the simple search interface". Recall that you can always go
to the Advanced Search for more query assistance.
The advanced search interface provides you with
explicit tools to play with: you can change the matching type from the
default word matching to phrase searching or the regular matching; you
can use boolean queries in several indexes, etc. For example, to find
all the documents written by Ellis, J spelled exactly that
way that contain either of the words muon or
neutrino in the title and that were published in
2001, you would type:
Note that Simple Search can provide you basically the same
functionality, if you make use of special syntax that is explained in
the text below. The simple-versus-advanced does not refer to the
functionality that is being provided but rather to the amount of
parametrization you can "tweak". We conform to the common
use of the simple/advanced terms as found in other search engines.
Much of what follows will deal with a question on "how a power user
would use the simple search interface". Recall that you can always go
to the Advanced Search for more query assistance.
The advanced search interface provides you with
explicit tools to play with: you can change the matching type from the
default word matching to phrase searching or the regular matching; you
can use boolean queries in several indexes, etc. For example, to find
all the documents written by Ellis, J spelled exactly that
way that contain either of the words muon or
neutrino in the title and that were published in
2001, you would type:
Note that Simple Search can provide you basically the same
functionality, if you make use of special syntax that is explained in
the text below. The simple-versus-advanced does not refer to the
functionality that is being provided but rather to the amount of
parametrization you can "tweak". We conform to the common
use of the simple/advanced terms as found in other search engines.
Much of what follows will deal with a question on "how a power user
would use the simple search interface". Recall that you can always go
to the Advanced Search for more query assistance.
The advanced search interface provides you with
explicit tools to play with: you can change the matching type from the
default word matching to phrase searching or the regular matching; you
can use boolean queries in several indexes, etc. For example, to find
all the documents written by Ellis, J spelled exactly that
way that contain either of the words muon or
neutrino in the title and that were published in
2001, you would type:
Note that Simple Search can provide you basically the same
functionality, if you make use of special syntax that is explained in
the text below. The simple-versus-advanced does not refer to the
functionality that is being provided but rather to the amount of
parametrization you can "tweak". We conform to the common
use of the simple/advanced terms as found in other search engines.
Much of what follows will deal with a question on "how a power user
would use the simple search interface". Recall that you can always go
to the Advanced Search for more query assistance.
The advanced search interface provides you with
explicit tools to play with: you can change the matching type from the
default word matching to phrase searching or the regular matching; you
can use boolean queries in several indexes, etc. For example, to find
all the documents written by Ellis, J spelled exactly that
way that contain either of the words muon or
neutrino in the title and that were published in
2001, you would type:
Note that Simple Search can provide you basically the same
functionality, if you make use of special syntax that is explained in
the text below. The simple-versus-advanced does not refer to the
functionality that is being provided but rather to the amount of
parametrization you can "tweak". We conform to the common
use of the simple/advanced terms as found in other search engines.
Much of what follows will deal with a question on "how a power user
would use the simple search interface". Recall that you can always go
to the Advanced Search for more query assistance.
The advanced search interface provides you with
explicit tools to play with: you can change the matching type from the
default word matching to phrase searching or the regular matching; you
can use boolean queries in several indexes, etc. For example, to find
all the documents written by Ellis, J spelled exactly that
way that contain either of the words muon or
neutrino in the title and that were published in
2001, you would type:
Note that Simple Search can provide you basically the same
functionality, if you make use of special syntax that is explained in
the text below. The simple-versus-advanced does not refer to the
functionality that is being provided but rather to the amount of
parametrization you can "tweak". We conform to the common
use of the simple/advanced terms as found in other search engines.
Much of what follows will deal with a question on "how a power user
would use the simple search interface". Recall that you can always go
to the Advanced Search for more query assistance.
The advanced search interface provides you with
explicit tools to play with: you can change the matching type from the
default word matching to phrase searching or the regular matching; you
can use boolean queries in several indexes, etc. For example, to find
all the documents written by Ellis, J spelled exactly that
way that contain either of the words muon or
neutrino in the title and that were published in
2001, you would type:
Note that Simple Search can provide you basically the same
functionality, if you make use of special syntax that is explained in
the text below. The simple-versus-advanced does not refer to the
functionality that is being provided but rather to the amount of
parametrization you can "tweak". We conform to the common
use of the simple/advanced terms as found in other search engines.
Much of what follows will deal with a question on "how a power user
would use the simple search interface". Recall that you can always go
to the Advanced Search for more query assistance.
The advanced search interface provides you with
explicit tools to play with: you can change the matching type from the
default word matching to phrase searching or the regular matching; you
can use boolean queries in several indexes, etc. For example, to find
all the documents written by Ellis, J spelled exactly that
way that contain either of the words muon or
neutrino in the title and that were published in
2001, you would type:
Note that Simple Search can provide you basically the same
functionality, if you make use of special syntax that is explained in
the text below. The simple-versus-advanced does not refer to the
functionality that is being provided but rather to the amount of
parametrization you can "tweak". We conform to the common
use of the simple/advanced terms as found in other search engines.
Much of what follows will deal with a question on "how a power user
would use the simple search interface". Recall that you can always go
to the Advanced Search for more query assistance.
The advanced search interface provides you with
explicit tools to play with: you can change the matching type from the
default word matching to phrase searching or the regular matching; you
can use boolean queries in several indexes, etc. For example, to find
all the documents written by Ellis, J spelled exactly that
way that contain either of the words muon or
neutrino in the title and that were published in
2001, you would type:
Note that Simple Search can provide you basically the same
functionality, if you make use of special syntax that is explained in
the text below. The simple-versus-advanced does not refer to the
functionality that is being provided but rather to the amount of
parametrization you can "tweak". We conform to the common
use of the simple/advanced terms as found in other search engines.
Much of what follows will deal with a question on "how a power user
would use the simple search interface". Recall that you can always go
to the Advanced Search for more query assistance.
The advanced search interface provides you with
explicit tools to play with: you can change the matching type from the
default word matching to phrase searching or the regular matching; you
can use boolean queries in several indexes, etc. For example, to find
all the documents written by Ellis, J spelled exactly that
way that contain either of the words muon or
neutrino in the title and that were published in
2001, you would type:
Note that Simple Search can provide you basically the same
functionality, if you make use of special syntax that is explained in
the text below. The simple-versus-advanced does not refer to the
functionality that is being provided but rather to the amount of
parametrization you can "tweak". We conform to the common
use of the simple/advanced terms as found in other search engines.
Much of what follows will deal with a question on "how a power user
would use the simple search interface". Recall that you can always go
to the Advanced Search for more query assistance.
The advanced search interface provides you with
explicit tools to play with: you can change the matching type from the
default word matching to phrase searching or the regular matching; you
can use boolean queries in several indexes, etc. For example, to find
all the documents written by Ellis, J spelled exactly that
way that contain either of the words muon or
neutrino in the title and that were published in
2001, you would type:
Note that Simple Search can provide you basically the same
functionality, if you make use of special syntax that is explained in
the text below. The simple-versus-advanced does not refer to the
functionality that is being provided but rather to the amount of
parametrization you can "tweak". We conform to the common
use of the simple/advanced terms as found in other search engines.
Much of what follows will deal with a question on "how a power user
would use the simple search interface". Recall that you can always go
to the Advanced Search for more query assistance.
The advanced search interface provides you with
explicit tools to play with: you can change the matching type from the
default word matching to phrase searching or the regular matching; you
can use boolean queries in several indexes, etc. For example, to find
all the documents written by Ellis, J spelled exactly that
way that contain either of the words muon or
neutrino in the title and that were published in
2001, you would type:
Note that Simple Search can provide you basically the same
functionality, if you make use of special syntax that is explained in
the text below. The simple-versus-advanced does not refer to the
functionality that is being provided but rather to the amount of
parametrization you can "tweak". We conform to the common
use of the simple/advanced terms as found in other search engines.
Much of what follows will deal with a question on "how a power user
would use the simple search interface". Recall that you can always go
to the Advanced Search for more query assistance.
The advanced search interface provides you with
explicit tools to play with: you can change the matching type from the
default word matching to phrase searching or the regular matching; you
can use boolean queries in several indexes, etc. For example, to find
all the documents written by Ellis, J spelled exactly that
way that contain either of the words muon or
neutrino in the title and that were published in
2001, you would type:
Note that Simple Search can provide you basically the same
functionality, if you make use of special syntax that is explained in
the text below. The simple-versus-advanced does not refer to the
functionality that is being provided but rather to the amount of
parametrization you can "tweak". We conform to the common
use of the simple/advanced terms as found in other search engines.
Much of what follows will deal with a question on "how a power user
would use the simple search interface". Recall that you can always go
to the Advanced Search for more query assistance.
The advanced search interface provides you with
explicit tools to play with: you can change the matching type from the
default word matching to phrase searching or the regular matching; you
can use boolean queries in several indexes, etc. For example, to find
all the documents written by Ellis, J spelled exactly that
way that contain either of the words muon or
neutrino in the title and that were published in
2001, you would type:
Note that Simple Search can provide you basically the same
functionality, if you make use of special syntax that is explained in
the text below. The simple-versus-advanced does not refer to the
functionality that is being provided but rather to the amount of
parametrization you can "tweak". We conform to the common
use of the simple/advanced terms as found in other search engines.
Much of what follows will deal with a question on "how a power user
would use the simple search interface". Recall that you can always go
to the Advanced Search for more query assistance.
The advanced search interface provides you with
explicit tools to play with: you can change the matching type from the
default word matching to phrase searching or the regular matching; you
can use boolean queries in several indexes, etc. For example, to find
all the documents written by Ellis, J spelled exactly that
way that contain either of the words muon or
neutrino in the title and that were published in
2001, you would type:
Note that Simple Search can provide you basically the same
functionality, if you make use of special syntax that is explained in
the text below. The simple-versus-advanced does not refer to the
functionality that is being provided but rather to the amount of
parametrization you can "tweak". We conform to the common
use of the simple/advanced terms as found in other search engines.
Much of what follows will deal with a question on "how a power user
would use the simple search interface". Recall that you can always go
to the Advanced Search for more query assistance.
The advanced search interface provides you with
explicit tools to play with: you can change the matching type from the
default word matching to phrase searching or the regular matching; you
can use boolean queries in several indexes, etc. For example, to find
all the documents written by Ellis, J spelled exactly that
way that contain either of the words muon or
neutrino in the title and that were published in
2001, you would type:
Note that Simple Search can provide you basically the same
functionality, if you make use of special syntax that is explained in
the text below. The simple-versus-advanced does not refer to the
functionality that is being provided but rather to the amount of
parametrization you can "tweak". We conform to the common
use of the simple/advanced terms as found in other search engines.
Much of what follows will deal with a question on "how a power user
would use the simple search interface". Recall that you can always go
to the Advanced Search for more query assistance.
The advanced search interface provides you with
explicit tools to play with: you can change the matching type from the
default word matching to phrase searching or the regular matching; you
can use boolean queries in several indexes, etc. For example, to find
all the documents written by Ellis, J spelled exactly that
way that contain either of the words muon or
neutrino in the title and that were published in
2001, you would type:
Note that Simple Search can provide you basically the same
functionality, if you make use of special syntax that is explained in
the text below. The simple-versus-advanced does not refer to the
functionality that is being provided but rather to the amount of
parametrization you can "tweak". We conform to the common
use of the simple/advanced terms as found in other search engines.
Much of what follows will deal with a question on "how a power user
would use the simple search interface". Recall that you can always go
to the Advanced Search for more query assistance.
El interfaz de búsqueda avanzada ofrece
herramientas específicas con las que configurar la búsqueda: podemos
cambiar el tipo de búsqueda por defecto (de alguna palabra a todas,
buscar por frase exacta, por expresión regular, etc.); nos permite
utilizar las expresiones booleanas combinando varios índices, etc.
Por ejemplo, para recuperar todos los documentos escritos por
EM>Ellis, J -transcrito exactamente de ese modo- y también las
palabras muons o neutrino en el título de la
publicación y 2001 en el año, escribiremos lo siguiente:
Obsérvese que si utilizamos una sintaxis especial, la Búsqueda
Simple ofrece prácticamente la misma funcionalidad que la avanzada,
tal y como se indica en las siguientes secciones de esta guía. Este
apartado de búsqueda simple-versus-avanzada no se refiere tanto a las
funcionalidades disponibles, sino a la forma de búsqueda que podemos
configurar mediante pequeñas modificaciones. El sistema se ha adaptado
al uso común de los términos de simple/avanzado que podemos encontrar
en otros motores de búsqueda.
En realidad, gran parte de la explicación que sigue a continuación,
responde a la cuestión de "cómo un usuario avanzado puede utilizar la
interficie de búsqueda simple". Recordamos que en cualquier momento
es posible recurrir a la ayuda de la búsqueda avanzada para conseguir
más asistencia.
La interficie de cerca avançada ofereix eines
específiques amb les que configurar la cerca: podem canviar el tipus
de cerca a realitzar per defecte (d'alguna paraula a totes les
paraules, cerca per frase exacta, per expressió regular, etc.); ens
permet emprar la combinació booleana a nombrosos índexs, etc. Per
exemple, per localitzar tots els documents escrits per EM>Ellis,
J -transcrit exactament d'aquesta manera- i també les paraules
muon o neutrino al títol de la publicació i
2001 a l'any, escriurem:
Observis que si fem servir una sintaxi especial, la Cerca Simple
ofereix pràcticament la mateixa funcionalitat que l'avançada, tal i
com s'explica a les següents seccions d'aquesta guia. Aquest apartat
de cerca simple-versus-avançada no es refereix tant a les
funcionalitats disponibles, com a la forma de cerca que podem
configurar mitjançant petites modificacions. El sistema s'ha adaptat
a l'ús comú dels termes simple/avançat que podem trobar a altres
motors de cerca.
En realitat, gran part de l'explicació que segueix a continuació,
respòn a la qüestió de "com un usuari avançat pot utilitzar la
interficie de cerca simple". Recordem que en qualsevol moment és
posible recòrrer a l'ajuda de la cerca avanzada per aconseguir més
assistència.
After you submit your query, the search engine will analyze it and
will try to always guide you in case no exact match could be found.
For example, it would print you a list of closest indexed terms in
case of spelling troubles:
Alternative choices will be printed in red. The search engine
will similarly warn you when your search terms could not be
found, or when they could but your boolean query couldn't be met. The
search engine will also silently try to search for alternative forms
(e.g. remove punctuation), etc.
Thanks to multiple search stages and the guidance provided at each
stage, it is usually sufficient to simple type what you are looking
for and see what the system says in return. If you aren't satisfied,
you would then add/remove words from your query until the satisfactory
reply.
After you submit your query, the search engine will analyze it and
will try to always guide you in case no exact match could be found.
For example, it would print you a list of closest indexed terms in
case of spelling troubles:
Alternative choices will be printed in red. The search engine
will similarly warn you when your search terms could not be
found, or when they could but your boolean query couldn't be met. The
search engine will also silently try to search for alternative forms
(e.g. remove punctuation), etc.
Thanks to multiple search stages and the guidance provided at each
stage, it is usually sufficient to simple type what you are looking
for and see what the system says in return. If you aren't satisfied,
you would then add/remove words from your query until the satisfactory
reply.
After you submit your query, the search engine will analyze it and
will try to always guide you in case no exact match could be found.
For example, it would print you a list of closest indexed terms in
case of spelling troubles:
Alternative choices will be printed in red. The search engine
will similarly warn you when your search terms could not be
found, or when they could but your boolean query couldn't be met. The
search engine will also silently try to search for alternative forms
(e.g. remove punctuation), etc.
Thanks to multiple search stages and the guidance provided at each
stage, it is usually sufficient to simple type what you are looking
for and see what the system says in return. If you aren't satisfied,
you would then add/remove words from your query until the satisfactory
reply.
After you submit your query, the search engine will analyze it and
will try to always guide you in case no exact match could be found.
For example, it would print you a list of closest indexed terms in
case of spelling troubles:
Alternative choices will be printed in red. The search engine
will similarly warn you when your search terms could not be
found, or when they could but your boolean query couldn't be met. The
search engine will also silently try to search for alternative forms
(e.g. remove punctuation), etc.
Thanks to multiple search stages and the guidance provided at each
stage, it is usually sufficient to simple type what you are looking
for and see what the system says in return. If you aren't satisfied,
you would then add/remove words from your query until the satisfactory
reply.
After you submit your query, the search engine will analyze it and
will try to always guide you in case no exact match could be found.
For example, it would print you a list of closest indexed terms in
case of spelling troubles:
Alternative choices will be printed in red. The search engine
will similarly warn you when your search terms could not be
found, or when they could but your boolean query couldn't be met. The
search engine will also silently try to search for alternative forms
(e.g. remove punctuation), etc.
Thanks to multiple search stages and the guidance provided at each
stage, it is usually sufficient to simple type what you are looking
for and see what the system says in return. If you aren't satisfied,
you would then add/remove words from your query until the satisfactory
reply.
After you submit your query, the search engine will analyze it and
will try to always guide you in case no exact match could be found.
For example, it would print you a list of closest indexed terms in
case of spelling troubles:
Alternative choices will be printed in red. The search engine
will similarly warn you when your search terms could not be
found, or when they could but your boolean query couldn't be met. The
search engine will also silently try to search for alternative forms
(e.g. remove punctuation), etc.
Thanks to multiple search stages and the guidance provided at each
stage, it is usually sufficient to simple type what you are looking
for and see what the system says in return. If you aren't satisfied,
you would then add/remove words from your query until the satisfactory
reply.
After you submit your query, the search engine will analyze it and
will try to always guide you in case no exact match could be found.
For example, it would print you a list of closest indexed terms in
case of spelling troubles:
Alternative choices will be printed in red. The search engine
will similarly warn you when your search terms could not be
found, or when they could but your boolean query couldn't be met. The
search engine will also silently try to search for alternative forms
(e.g. remove punctuation), etc.
Thanks to multiple search stages and the guidance provided at each
stage, it is usually sufficient to simple type what you are looking
for and see what the system says in return. If you aren't satisfied,
you would then add/remove words from your query until the satisfactory
reply.
After you submit your query, the search engine will analyze it and
will try to always guide you in case no exact match could be found.
For example, it would print you a list of closest indexed terms in
case of spelling troubles:
Alternative choices will be printed in red. The search engine
will similarly warn you when your search terms could not be
found, or when they could but your boolean query couldn't be met. The
search engine will also silently try to search for alternative forms
(e.g. remove punctuation), etc.
Thanks to multiple search stages and the guidance provided at each
stage, it is usually sufficient to simple type what you are looking
for and see what the system says in return. If you aren't satisfied,
you would then add/remove words from your query until the satisfactory
reply.
After you submit your query, the search engine will analyze it and
will try to always guide you in case no exact match could be found.
For example, it would print you a list of closest indexed terms in
case of spelling troubles:
Alternative choices will be printed in red. The search engine
will similarly warn you when your search terms could not be
found, or when they could but your boolean query couldn't be met. The
search engine will also silently try to search for alternative forms
(e.g. remove punctuation), etc.
Thanks to multiple search stages and the guidance provided at each
stage, it is usually sufficient to simple type what you are looking
for and see what the system says in return. If you aren't satisfied,
you would then add/remove words from your query until the satisfactory
reply.
After you submit your query, the search engine will analyze it and
will try to always guide you in case no exact match could be found.
For example, it would print you a list of closest indexed terms in
case of spelling troubles:
Alternative choices will be printed in red. The search engine
will similarly warn you when your search terms could not be
found, or when they could but your boolean query couldn't be met. The
search engine will also silently try to search for alternative forms
(e.g. remove punctuation), etc.
Thanks to multiple search stages and the guidance provided at each
stage, it is usually sufficient to simple type what you are looking
for and see what the system says in return. If you aren't satisfied,
you would then add/remove words from your query until the satisfactory
reply.
After you submit your query, the search engine will analyze it and
will try to always guide you in case no exact match could be found.
For example, it would print you a list of closest indexed terms in
case of spelling troubles:
Alternative choices will be printed in red. The search engine
will similarly warn you when your search terms could not be
found, or when they could but your boolean query couldn't be met. The
search engine will also silently try to search for alternative forms
(e.g. remove punctuation), etc.
Thanks to multiple search stages and the guidance provided at each
stage, it is usually sufficient to simple type what you are looking
for and see what the system says in return. If you aren't satisfied,
you would then add/remove words from your query until the satisfactory
reply.
After you submit your query, the search engine will analyze it and
will try to always guide you in case no exact match could be found.
For example, it would print you a list of closest indexed terms in
case of spelling troubles:
Alternative choices will be printed in red. The search engine
will similarly warn you when your search terms could not be
found, or when they could but your boolean query couldn't be met. The
search engine will also silently try to search for alternative forms
(e.g. remove punctuation), etc.
Thanks to multiple search stages and the guidance provided at each
stage, it is usually sufficient to simple type what you are looking
for and see what the system says in return. If you aren't satisfied,
you would then add/remove words from your query until the satisfactory
reply.
After you submit your query, the search engine will analyze it and
will try to always guide you in case no exact match could be found.
For example, it would print you a list of closest indexed terms in
case of spelling troubles:
Alternative choices will be printed in red. The search engine
will similarly warn you when your search terms could not be
found, or when they could but your boolean query couldn't be met. The
search engine will also silently try to search for alternative forms
(e.g. remove punctuation), etc.
Thanks to multiple search stages and the guidance provided at each
stage, it is usually sufficient to simple type what you are looking
for and see what the system says in return. If you aren't satisfied,
you would then add/remove words from your query until the satisfactory
reply.
After you submit your query, the search engine will analyze it and
will try to always guide you in case no exact match could be found.
For example, it would print you a list of closest indexed terms in
case of spelling troubles:
Alternative choices will be printed in red. The search engine
will similarly warn you when your search terms could not be
found, or when they could but your boolean query couldn't be met. The
search engine will also silently try to search for alternative forms
(e.g. remove punctuation), etc.
Thanks to multiple search stages and the guidance provided at each
stage, it is usually sufficient to simple type what you are looking
for and see what the system says in return. If you aren't satisfied,
you would then add/remove words from your query until the satisfactory
reply.
After you submit your query, the search engine will analyze it and
will try to always guide you in case no exact match could be found.
For example, it would print you a list of closest indexed terms in
case of spelling troubles:
Alternative choices will be printed in red. The search engine
will similarly warn you when your search terms could not be
found, or when they could but your boolean query couldn't be met. The
search engine will also silently try to search for alternative forms
(e.g. remove punctuation), etc.
Thanks to multiple search stages and the guidance provided at each
stage, it is usually sufficient to simple type what you are looking
for and see what the system says in return. If you aren't satisfied,
you would then add/remove words from your query until the satisfactory
reply.
After you submit your query, the search engine will analyze it and
will try to always guide you in case no exact match could be found.
For example, it would print you a list of closest indexed terms in
case of spelling troubles:
Alternative choices will be printed in red. The search engine
will similarly warn you when your search terms could not be
found, or when they could but your boolean query couldn't be met. The
search engine will also silently try to search for alternative forms
(e.g. remove punctuation), etc.
Thanks to multiple search stages and the guidance provided at each
stage, it is usually sufficient to simple type what you are looking
for and see what the system says in return. If you aren't satisfied,
you would then add/remove words from your query until the satisfactory
reply.
After you submit your query, the search engine will analyze it and
will try to always guide you in case no exact match could be found.
For example, it would print you a list of closest indexed terms in
case of spelling troubles:
Alternative choices will be printed in red. The search engine
will similarly warn you when your search terms could not be
found, or when they could but your boolean query couldn't be met. The
search engine will also silently try to search for alternative forms
(e.g. remove punctuation), etc.
Thanks to multiple search stages and the guidance provided at each
stage, it is usually sufficient to simple type what you are looking
for and see what the system says in return. If you aren't satisfied,
you would then add/remove words from your query until the satisfactory
reply.
After you submit your query, the search engine will analyze it and
will try to always guide you in case no exact match could be found.
For example, it would print you a list of closest indexed terms in
case of spelling troubles:
Alternative choices will be printed in red. The search engine
will similarly warn you when your search terms could not be
found, or when they could but your boolean query couldn't be met. The
search engine will also silently try to search for alternative forms
(e.g. remove punctuation), etc.
Thanks to multiple search stages and the guidance provided at each
stage, it is usually sufficient to simple type what you are looking
for and see what the system says in return. If you aren't satisfied,
you would then add/remove words from your query until the satisfactory
reply.
Gracias al sistema de búsqueda en múltiples etapas y a la ayuda
que se proporciona en cada una de estas etapas, por lo general resulta
suficiente escribir la palabra de búsqueda y revisar los resultados
qué nos devuelve el sistema. Si los resultados no son pertinentes, o
son excesivos o insuficientes, es posible añadir o quitar palabras de
la consulta hasta conseguir resultados más satisfactorios.
Después de recibir una consulta, el motor de búsqueda la analiza
y, en caso de no localizar ninguna coincidencia en la base de datos,
el sistema tratará de guiar al usuario. Un ejemplo de ello son las
listas de los términos indexados que se encuentran más cercanos al
término introducido, en caso de que se produzacan errores ortográficos
o de transcripción al efectuar la consulta:
Las opciones alternativas se muestran en rojo. El motor de
búsqueda avisa de forma similar cuando detecta que los términos de
búsqueda no se encuentran, o cuando detecta que sí que existen pero la
fórmula de consulta booleana utilizada no puede localizarlos. Así
mismo, el motor de búsqueda también realiza de forma oculta acciones
alternativas para mejorar los resultados, como por ejemplo eliminar
puntuación, etc.
Gràcies al sistema de cerca en múltiples etapes i a l'ajuda que es
va proporcionant a cadascuna d'aquestes etapes, pel general resulta
suficient teclejar l'objetcte de cerca i observar que ens retorna el
sistema. Si no quedem satisfets, podem afegir/treure paraules de la
nostra consulta fins aconseguir uns resultats satisfactoris.
Després de rebre una consulta, el motor de cerca l'analizarà i
tractarà sempre de guiar a l'usuari en cas de que no localitzi cap
coincidència a la base de dades. Un exemple d'això son les llistes
dels termes indexats que es troben més propers al terme introduït a la
consulta en cas que no es trobin coincidències per errors ortogràfics
o de transcripció:
Les opcions alternatives es mostren en vermell. El motor de cerca
avisa de forma similar quan detecta que els termes de cerca no es
troben, o quan detecta que si que existeixen però la fórmula de
consulta booleana emprada no aconsegueix localitzar-los. Així mateix,
el motor de cerca també realitza de forma oculta accions alternatives
per a millorar els resultat,s com, per exemple, eliminar puntuació,
etc.
The default search mode is a search for words. This
means that any whitespace you type is not significant, but is rather
interpreted to mean "add an automatic boolean AND between words", like
Google does. For example, to find all records that contain both the
word ellis and the word muon anywhere in the record,
type:
The whitespace would be significant if you include it within quotes.
There are two phrase searching modes:
- The double quotes instruct the search engine to search for
exact phrase. This phrase search mode will match if and
only if the given metadata field is exactly equal to the input
pattern. For example, to find all documents written by Ellis,
J spelled exactly that way, type:
- The single quotes instruct the search engine to search for
partial phrase. Unlike the exact phrase search, this
mode allows for an extra text appearing before/after given
pattern. This is somewhat similar to the "phrase search mode"
common on Google and other fulltext engines that search for phrase
expressions inside Web pages. For example, to find all the titles
containing the expression muon decay regardless of the
position of the expression in the title, type:
Now you see how to search for an author spelled sometimes as
Ellis, J and sometimes as Ellis, Jonathan
Richard (and other authors, such as De Lellis, Jim)
at the same time:
(See also our specific author
searching tips.)
The difference between exact and partial phrase searching modes may
not be obvious upon first look. While the latter is more similar to
what ``phrase search'' usually means in the context of web page search
engines, the former one is usually an order of magnitude faster if you
know the precise values you are looking for.
Another interesting searching mode besides the word and phrase
searches is the regular expression search, introduced
by slashes instead of quotes. For example, the above partial phrase
query 'muon decay'
is fully equivalent to the regular
expression query /muon decay/
. The regular expression
syntax is very powerful and permits you to construct very complex
queries. For more information, please consult the regular expression section of this guide.
The default search mode is a search for words. This
means that any whitespace you type is not significant, but is rather
interpreted to mean "add an automatic boolean AND between words", like
Google does. For example, to find all records that contain both the
word ellis and the word muon anywhere in the record,
type:
The whitespace would be significant if you include it within quotes.
There are two phrase searching modes:
- The double quotes instruct the search engine to search for
exact phrase. This phrase search mode will match if and
only if the given metadata field is exactly equal to the input
pattern. For example, to find all documents written by Ellis,
J spelled exactly that way, type:
- The single quotes instruct the search engine to search for
partial phrase. Unlike the exact phrase search, this
mode allows for an extra text appearing before/after given
pattern. This is somewhat similar to the "phrase search mode"
common on Google and other fulltext engines that search for phrase
expressions inside Web pages. For example, to find all the titles
containing the expression muon decay regardless of the
position of the expression in the title, type:
Now you see how to search for an author spelled sometimes as
Ellis, J and sometimes as Ellis, Jonathan
Richard (and other authors, such as De Lellis, Jim)
at the same time:
(See also our specific author
searching tips.)
The difference between exact and partial phrase searching modes may
not be obvious upon first look. While the latter is more similar to
what ``phrase search'' usually means in the context of web page search
engines, the former one is usually an order of magnitude faster if you
know the precise values you are looking for.
Another interesting searching mode besides the word and phrase
searches is the regular expression search, introduced
by slashes instead of quotes. For example, the above partial phrase
query 'muon decay'
is fully equivalent to the regular
expression query /muon decay/
. The regular expression
syntax is very powerful and permits you to construct very complex
queries. For more information, please consult the regular expression section of this guide.
The default search mode is a search for words. This
means that any whitespace you type is not significant, but is rather
interpreted to mean "add an automatic boolean AND between words", like
Google does. For example, to find all records that contain both the
word ellis and the word muon anywhere in the record,
type:
The whitespace would be significant if you include it within quotes.
There are two phrase searching modes:
- The double quotes instruct the search engine to search for
exact phrase. This phrase search mode will match if and
only if the given metadata field is exactly equal to the input
pattern. For example, to find all documents written by Ellis,
J spelled exactly that way, type:
- The single quotes instruct the search engine to search for
partial phrase. Unlike the exact phrase search, this
mode allows for an extra text appearing before/after given
pattern. This is somewhat similar to the "phrase search mode"
common on Google and other fulltext engines that search for phrase
expressions inside Web pages. For example, to find all the titles
containing the expression muon decay regardless of the
position of the expression in the title, type:
Now you see how to search for an author spelled sometimes as
Ellis, J and sometimes as Ellis, Jonathan
Richard (and other authors, such as De Lellis, Jim)
at the same time:
(See also our specific author
searching tips.)
The difference between exact and partial phrase searching modes may
not be obvious upon first look. While the latter is more similar to
what ``phrase search'' usually means in the context of web page search
engines, the former one is usually an order of magnitude faster if you
know the precise values you are looking for.
Another interesting searching mode besides the word and phrase
searches is the regular expression search, introduced
by slashes instead of quotes. For example, the above partial phrase
query 'muon decay'
is fully equivalent to the regular
expression query /muon decay/
. The regular expression
syntax is very powerful and permits you to construct very complex
queries. For more information, please consult the regular expression section of this guide.
The default search mode is a search for words. This
means that any whitespace you type is not significant, but is rather
interpreted to mean "add an automatic boolean AND between words", like
Google does. For example, to find all records that contain both the
word ellis and the word muon anywhere in the record,
type:
The whitespace would be significant if you include it within quotes.
There are two phrase searching modes:
- The double quotes instruct the search engine to search for
exact phrase. This phrase search mode will match if and
only if the given metadata field is exactly equal to the input
pattern. For example, to find all documents written by Ellis,
J spelled exactly that way, type:
- The single quotes instruct the search engine to search for
partial phrase. Unlike the exact phrase search, this
mode allows for an extra text appearing before/after given
pattern. This is somewhat similar to the "phrase search mode"
common on Google and other fulltext engines that search for phrase
expressions inside Web pages. For example, to find all the titles
containing the expression muon decay regardless of the
position of the expression in the title, type:
Now you see how to search for an author spelled sometimes as
Ellis, J and sometimes as Ellis, Jonathan
Richard (and other authors, such as De Lellis, Jim)
at the same time:
(See also our specific author
searching tips.)
The difference between exact and partial phrase searching modes may
not be obvious upon first look. While the latter is more similar to
what ``phrase search'' usually means in the context of web page search
engines, the former one is usually an order of magnitude faster if you
know the precise values you are looking for.
Another interesting searching mode besides the word and phrase
searches is the regular expression search, introduced
by slashes instead of quotes. For example, the above partial phrase
query 'muon decay'
is fully equivalent to the regular
expression query /muon decay/
. The regular expression
syntax is very powerful and permits you to construct very complex
queries. For more information, please consult the regular expression section of this guide.
The default search mode is a search for words. This
means that any whitespace you type is not significant, but is rather
interpreted to mean "add an automatic boolean AND between words", like
Google does. For example, to find all records that contain both the
word ellis and the word muon anywhere in the record,
type:
The whitespace would be significant if you include it within quotes.
There are two phrase searching modes:
- The double quotes instruct the search engine to search for
exact phrase. This phrase search mode will match if and
only if the given metadata field is exactly equal to the input
pattern. For example, to find all documents written by Ellis,
J spelled exactly that way, type:
- The single quotes instruct the search engine to search for
partial phrase. Unlike the exact phrase search, this
mode allows for an extra text appearing before/after given
pattern. This is somewhat similar to the "phrase search mode"
common on Google and other fulltext engines that search for phrase
expressions inside Web pages. For example, to find all the titles
containing the expression muon decay regardless of the
position of the expression in the title, type:
Now you see how to search for an author spelled sometimes as
Ellis, J and sometimes as Ellis, Jonathan
Richard (and other authors, such as De Lellis, Jim)
at the same time:
(See also our specific author
searching tips.)
The difference between exact and partial phrase searching modes may
not be obvious upon first look. While the latter is more similar to
what ``phrase search'' usually means in the context of web page search
engines, the former one is usually an order of magnitude faster if you
know the precise values you are looking for.
Another interesting searching mode besides the word and phrase
searches is the regular expression search, introduced
by slashes instead of quotes. For example, the above partial phrase
query 'muon decay'
is fully equivalent to the regular
expression query /muon decay/
. The regular expression
syntax is very powerful and permits you to construct very complex
queries. For more information, please consult the regular expression section of this guide.
The default search mode is a search for words. This
means that any whitespace you type is not significant, but is rather
interpreted to mean "add an automatic boolean AND between words", like
Google does. For example, to find all records that contain both the
word ellis and the word muon anywhere in the record,
type:
The whitespace would be significant if you include it within quotes.
There are two phrase searching modes:
- The double quotes instruct the search engine to search for
exact phrase. This phrase search mode will match if and
only if the given metadata field is exactly equal to the input
pattern. For example, to find all documents written by Ellis,
J spelled exactly that way, type:
- The single quotes instruct the search engine to search for
partial phrase. Unlike the exact phrase search, this
mode allows for an extra text appearing before/after given
pattern. This is somewhat similar to the "phrase search mode"
common on Google and other fulltext engines that search for phrase
expressions inside Web pages. For example, to find all the titles
containing the expression muon decay regardless of the
position of the expression in the title, type:
Now you see how to search for an author spelled sometimes as
Ellis, J and sometimes as Ellis, Jonathan
Richard (and other authors, such as De Lellis, Jim)
at the same time:
(See also our specific author
searching tips.)
The difference between exact and partial phrase searching modes may
not be obvious upon first look. While the latter is more similar to
what ``phrase search'' usually means in the context of web page search
engines, the former one is usually an order of magnitude faster if you
know the precise values you are looking for.
Another interesting searching mode besides the word and phrase
searches is the regular expression search, introduced
by slashes instead of quotes. For example, the above partial phrase
query 'muon decay'
is fully equivalent to the regular
expression query /muon decay/
. The regular expression
syntax is very powerful and permits you to construct very complex
queries. For more information, please consult the regular expression section of this guide.
The default search mode is a search for words. This
means that any whitespace you type is not significant, but is rather
interpreted to mean "add an automatic boolean AND between words", like
Google does. For example, to find all records that contain both the
word ellis and the word muon anywhere in the record,
type:
The whitespace would be significant if you include it within quotes.
There are two phrase searching modes:
- The double quotes instruct the search engine to search for
exact phrase. This phrase search mode will match if and
only if the given metadata field is exactly equal to the input
pattern. For example, to find all documents written by Ellis,
J spelled exactly that way, type:
- The single quotes instruct the search engine to search for
partial phrase. Unlike the exact phrase search, this
mode allows for an extra text appearing before/after given
pattern. This is somewhat similar to the "phrase search mode"
common on Google and other fulltext engines that search for phrase
expressions inside Web pages. For example, to find all the titles
containing the expression muon decay regardless of the
position of the expression in the title, type:
Now you see how to search for an author spelled sometimes as
Ellis, J and sometimes as Ellis, Jonathan
Richard (and other authors, such as De Lellis, Jim)
at the same time:
(See also our specific author
searching tips.)
The difference between exact and partial phrase searching modes may
not be obvious upon first look. While the latter is more similar to
what ``phrase search'' usually means in the context of web page search
engines, the former one is usually an order of magnitude faster if you
know the precise values you are looking for.
Another interesting searching mode besides the word and phrase
searches is the regular expression search, introduced
by slashes instead of quotes. For example, the above partial phrase
query 'muon decay'
is fully equivalent to the regular
expression query /muon decay/
. The regular expression
syntax is very powerful and permits you to construct very complex
queries. For more information, please consult the regular expression section of this guide.
The default search mode is a search for words. This
means that any whitespace you type is not significant, but is rather
interpreted to mean "add an automatic boolean AND between words", like
Google does. For example, to find all records that contain both the
word ellis and the word muon anywhere in the record,
type:
The whitespace would be significant if you include it within quotes.
There are two phrase searching modes:
- The double quotes instruct the search engine to search for
exact phrase. This phrase search mode will match if and
only if the given metadata field is exactly equal to the input
pattern. For example, to find all documents written by Ellis,
J spelled exactly that way, type:
- The single quotes instruct the search engine to search for
partial phrase. Unlike the exact phrase search, this
mode allows for an extra text appearing before/after given
pattern. This is somewhat similar to the "phrase search mode"
common on Google and other fulltext engines that search for phrase
expressions inside Web pages. For example, to find all the titles
containing the expression muon decay regardless of the
position of the expression in the title, type:
Now you see how to search for an author spelled sometimes as
Ellis, J and sometimes as Ellis, Jonathan
Richard (and other authors, such as De Lellis, Jim)
at the same time:
(See also our specific author
searching tips.)
The difference between exact and partial phrase searching modes may
not be obvious upon first look. While the latter is more similar to
what ``phrase search'' usually means in the context of web page search
engines, the former one is usually an order of magnitude faster if you
know the precise values you are looking for.
Another interesting searching mode besides the word and phrase
searches is the regular expression search, introduced
by slashes instead of quotes. For example, the above partial phrase
query 'muon decay'
is fully equivalent to the regular
expression query /muon decay/
. The regular expression
syntax is very powerful and permits you to construct very complex
queries. For more information, please consult the regular expression section of this guide.
The default search mode is a search for words. This
means that any whitespace you type is not significant, but is rather
interpreted to mean "add an automatic boolean AND between words", like
Google does. For example, to find all records that contain both the
word ellis and the word muon anywhere in the record,
type:
The whitespace would be significant if you include it within quotes.
There are two phrase searching modes:
- The double quotes instruct the search engine to search for
exact phrase. This phrase search mode will match if and
only if the given metadata field is exactly equal to the input
pattern. For example, to find all documents written by Ellis,
J spelled exactly that way, type:
- The single quotes instruct the search engine to search for
partial phrase. Unlike the exact phrase search, this
mode allows for an extra text appearing before/after given
pattern. This is somewhat similar to the "phrase search mode"
common on Google and other fulltext engines that search for phrase
expressions inside Web pages. For example, to find all the titles
containing the expression muon decay regardless of the
position of the expression in the title, type:
Now you see how to search for an author spelled sometimes as
Ellis, J and sometimes as Ellis, Jonathan
Richard (and other authors, such as De Lellis, Jim)
at the same time:
(See also our specific author
searching tips.)
The difference between exact and partial phrase searching modes may
not be obvious upon first look. While the latter is more similar to
what ``phrase search'' usually means in the context of web page search
engines, the former one is usually an order of magnitude faster if you
know the precise values you are looking for.
Another interesting searching mode besides the word and phrase
searches is the regular expression search, introduced
by slashes instead of quotes. For example, the above partial phrase
query 'muon decay'
is fully equivalent to the regular
expression query /muon decay/
. The regular expression
syntax is very powerful and permits you to construct very complex
queries. For more information, please consult the regular expression section of this guide.
The default search mode is a search for words. This
means that any whitespace you type is not significant, but is rather
interpreted to mean "add an automatic boolean AND between words", like
Google does. For example, to find all records that contain both the
word ellis and the word muon anywhere in the record,
type:
The whitespace would be significant if you include it within quotes.
There are two phrase searching modes:
- The double quotes instruct the search engine to search for
exact phrase. This phrase search mode will match if and
only if the given metadata field is exactly equal to the input
pattern. For example, to find all documents written by Ellis,
J spelled exactly that way, type:
- The single quotes instruct the search engine to search for
partial phrase. Unlike the exact phrase search, this
mode allows for an extra text appearing before/after given
pattern. This is somewhat similar to the "phrase search mode"
common on Google and other fulltext engines that search for phrase
expressions inside Web pages. For example, to find all the titles
containing the expression muon decay regardless of the
position of the expression in the title, type:
Now you see how to search for an author spelled sometimes as
Ellis, J and sometimes as Ellis, Jonathan
Richard (and other authors, such as De Lellis, Jim)
at the same time:
(See also our specific author
searching tips.)
The difference between exact and partial phrase searching modes may
not be obvious upon first look. While the latter is more similar to
what ``phrase search'' usually means in the context of web page search
engines, the former one is usually an order of magnitude faster if you
know the precise values you are looking for.
Another interesting searching mode besides the word and phrase
searches is the regular expression search, introduced
by slashes instead of quotes. For example, the above partial phrase
query 'muon decay'
is fully equivalent to the regular
expression query /muon decay/
. The regular expression
syntax is very powerful and permits you to construct very complex
queries. For more information, please consult the regular expression section of this guide.
The default search mode is a search for words. This
means that any whitespace you type is not significant, but is rather
interpreted to mean "add an automatic boolean AND between words", like
Google does. For example, to find all records that contain both the
word ellis and the word muon anywhere in the record,
type:
The whitespace would be significant if you include it within quotes.
There are two phrase searching modes:
- The double quotes instruct the search engine to search for
exact phrase. This phrase search mode will match if and
only if the given metadata field is exactly equal to the input
pattern. For example, to find all documents written by Ellis,
J spelled exactly that way, type:
- The single quotes instruct the search engine to search for
partial phrase. Unlike the exact phrase search, this
mode allows for an extra text appearing before/after given
pattern. This is somewhat similar to the "phrase search mode"
common on Google and other fulltext engines that search for phrase
expressions inside Web pages. For example, to find all the titles
containing the expression muon decay regardless of the
position of the expression in the title, type:
Now you see how to search for an author spelled sometimes as
Ellis, J and sometimes as Ellis, Jonathan
Richard (and other authors, such as De Lellis, Jim)
at the same time:
(See also our specific author
searching tips.)
The difference between exact and partial phrase searching modes may
not be obvious upon first look. While the latter is more similar to
what ``phrase search'' usually means in the context of web page search
engines, the former one is usually an order of magnitude faster if you
know the precise values you are looking for.
Another interesting searching mode besides the word and phrase
searches is the regular expression search, introduced
by slashes instead of quotes. For example, the above partial phrase
query 'muon decay'
is fully equivalent to the regular
expression query /muon decay/
. The regular expression
syntax is very powerful and permits you to construct very complex
queries. For more information, please consult the regular expression section of this guide.
The default search mode is a search for words. This
means that any whitespace you type is not significant, but is rather
interpreted to mean "add an automatic boolean AND between words", like
Google does. For example, to find all records that contain both the
word ellis and the word muon anywhere in the record,
type:
The whitespace would be significant if you include it within quotes.
There are two phrase searching modes:
- The double quotes instruct the search engine to search for
exact phrase. This phrase search mode will match if and
only if the given metadata field is exactly equal to the input
pattern. For example, to find all documents written by Ellis,
J spelled exactly that way, type:
- The single quotes instruct the search engine to search for
partial phrase. Unlike the exact phrase search, this
mode allows for an extra text appearing before/after given
pattern. This is somewhat similar to the "phrase search mode"
common on Google and other fulltext engines that search for phrase
expressions inside Web pages. For example, to find all the titles
containing the expression muon decay regardless of the
position of the expression in the title, type:
Now you see how to search for an author spelled sometimes as
Ellis, J and sometimes as Ellis, Jonathan
Richard (and other authors, such as De Lellis, Jim)
at the same time:
(See also our specific author
searching tips.)
The difference between exact and partial phrase searching modes may
not be obvious upon first look. While the latter is more similar to
what ``phrase search'' usually means in the context of web page search
engines, the former one is usually an order of magnitude faster if you
know the precise values you are looking for.
Another interesting searching mode besides the word and phrase
searches is the regular expression search, introduced
by slashes instead of quotes. For example, the above partial phrase
query 'muon decay'
is fully equivalent to the regular
expression query /muon decay/
. The regular expression
syntax is very powerful and permits you to construct very complex
queries. For more information, please consult the regular expression section of this guide.
The default search mode is a search for words. This
means that any whitespace you type is not significant, but is rather
interpreted to mean "add an automatic boolean AND between words", like
Google does. For example, to find all records that contain both the
word ellis and the word muon anywhere in the record,
type:
The whitespace would be significant if you include it within quotes.
There are two phrase searching modes:
- The double quotes instruct the search engine to search for
exact phrase. This phrase search mode will match if and
only if the given metadata field is exactly equal to the input
pattern. For example, to find all documents written by Ellis,
J spelled exactly that way, type:
- The single quotes instruct the search engine to search for
partial phrase. Unlike the exact phrase search, this
mode allows for an extra text appearing before/after given
pattern. This is somewhat similar to the "phrase search mode"
common on Google and other fulltext engines that search for phrase
expressions inside Web pages. For example, to find all the titles
containing the expression muon decay regardless of the
position of the expression in the title, type:
Now you see how to search for an author spelled sometimes as
Ellis, J and sometimes as Ellis, Jonathan
Richard (and other authors, such as De Lellis, Jim)
at the same time:
(See also our specific author
searching tips.)
The difference between exact and partial phrase searching modes may
not be obvious upon first look. While the latter is more similar to
what ``phrase search'' usually means in the context of web page search
engines, the former one is usually an order of magnitude faster if you
know the precise values you are looking for.
Another interesting searching mode besides the word and phrase
searches is the regular expression search, introduced
by slashes instead of quotes. For example, the above partial phrase
query 'muon decay'
is fully equivalent to the regular
expression query /muon decay/
. The regular expression
syntax is very powerful and permits you to construct very complex
queries. For more information, please consult the regular expression section of this guide.
The default search mode is a search for words. This
means that any whitespace you type is not significant, but is rather
interpreted to mean "add an automatic boolean AND between words", like
Google does. For example, to find all records that contain both the
word ellis and the word muon anywhere in the record,
type:
The whitespace would be significant if you include it within quotes.
There are two phrase searching modes:
- The double quotes instruct the search engine to search for
exact phrase. This phrase search mode will match if and
only if the given metadata field is exactly equal to the input
pattern. For example, to find all documents written by Ellis,
J spelled exactly that way, type:
- The single quotes instruct the search engine to search for
partial phrase. Unlike the exact phrase search, this
mode allows for an extra text appearing before/after given
pattern. This is somewhat similar to the "phrase search mode"
common on Google and other fulltext engines that search for phrase
expressions inside Web pages. For example, to find all the titles
containing the expression muon decay regardless of the
position of the expression in the title, type:
Now you see how to search for an author spelled sometimes as
Ellis, J and sometimes as Ellis, Jonathan
Richard (and other authors, such as De Lellis, Jim)
at the same time:
(See also our specific author
searching tips.)
The difference between exact and partial phrase searching modes may
not be obvious upon first look. While the latter is more similar to
what ``phrase search'' usually means in the context of web page search
engines, the former one is usually an order of magnitude faster if you
know the precise values you are looking for.
Another interesting searching mode besides the word and phrase
searches is the regular expression search, introduced
by slashes instead of quotes. For example, the above partial phrase
query 'muon decay'
is fully equivalent to the regular
expression query /muon decay/
. The regular expression
syntax is very powerful and permits you to construct very complex
queries. For more information, please consult the regular expression section of this guide.
The default search mode is a search for words. This
means that any whitespace you type is not significant, but is rather
interpreted to mean "add an automatic boolean AND between words", like
Google does. For example, to find all records that contain both the
word ellis and the word muon anywhere in the record,
type:
The whitespace would be significant if you include it within quotes.
There are two phrase searching modes:
- The double quotes instruct the search engine to search for
exact phrase. This phrase search mode will match if and
only if the given metadata field is exactly equal to the input
pattern. For example, to find all documents written by Ellis,
J spelled exactly that way, type:
- The single quotes instruct the search engine to search for
partial phrase. Unlike the exact phrase search, this
mode allows for an extra text appearing before/after given
pattern. This is somewhat similar to the "phrase search mode"
common on Google and other fulltext engines that search for phrase
expressions inside Web pages. For example, to find all the titles
containing the expression muon decay regardless of the
position of the expression in the title, type:
Now you see how to search for an author spelled sometimes as
Ellis, J and sometimes as Ellis, Jonathan
Richard (and other authors, such as De Lellis, Jim)
at the same time:
(See also our specific author
searching tips.)
The difference between exact and partial phrase searching modes may
not be obvious upon first look. While the latter is more similar to
what ``phrase search'' usually means in the context of web page search
engines, the former one is usually an order of magnitude faster if you
know the precise values you are looking for.
Another interesting searching mode besides the word and phrase
searches is the regular expression search, introduced
by slashes instead of quotes. For example, the above partial phrase
query 'muon decay'
is fully equivalent to the regular
expression query /muon decay/
. The regular expression
syntax is very powerful and permits you to construct very complex
queries. For more information, please consult the regular expression section of this guide.
The default search mode is a search for words. This
means that any whitespace you type is not significant, but is rather
interpreted to mean "add an automatic boolean AND between words", like
Google does. For example, to find all records that contain both the
word ellis and the word muon anywhere in the record,
type:
The whitespace would be significant if you include it within quotes.
There are two phrase searching modes:
- The double quotes instruct the search engine to search for
exact phrase. This phrase search mode will match if and
only if the given metadata field is exactly equal to the input
pattern. For example, to find all documents written by Ellis,
J spelled exactly that way, type:
- The single quotes instruct the search engine to search for
partial phrase. Unlike the exact phrase search, this
mode allows for an extra text appearing before/after given
pattern. This is somewhat similar to the "phrase search mode"
common on Google and other fulltext engines that search for phrase
expressions inside Web pages. For example, to find all the titles
containing the expression muon decay regardless of the
position of the expression in the title, type:
Now you see how to search for an author spelled sometimes as
Ellis, J and sometimes as Ellis, Jonathan
Richard (and other authors, such as De Lellis, Jim)
at the same time:
(See also our specific author
searching tips.)
The difference between exact and partial phrase searching modes may
not be obvious upon first look. While the latter is more similar to
what ``phrase search'' usually means in the context of web page search
engines, the former one is usually an order of magnitude faster if you
know the precise values you are looking for.
Another interesting searching mode besides the word and phrase
searches is the regular expression search, introduced
by slashes instead of quotes. For example, the above partial phrase
query 'muon decay'
is fully equivalent to the regular
expression query /muon decay/
. The regular expression
syntax is very powerful and permits you to construct very complex
queries. For more information, please consult the regular expression section of this guide.
The default search mode is a search for words. This
means that any whitespace you type is not significant, but is rather
interpreted to mean "add an automatic boolean AND between words", like
Google does. For example, to find all records that contain both the
word ellis and the word muon anywhere in the record,
type:
The whitespace would be significant if you include it within quotes.
There are two phrase searching modes:
- The double quotes instruct the search engine to search for
exact phrase. This phrase search mode will match if and
only if the given metadata field is exactly equal to the input
pattern. For example, to find all documents written by Ellis,
J spelled exactly that way, type:
- The single quotes instruct the search engine to search for
partial phrase. Unlike the exact phrase search, this
mode allows for an extra text appearing before/after given
pattern. This is somewhat similar to the "phrase search mode"
common on Google and other fulltext engines that search for phrase
expressions inside Web pages. For example, to find all the titles
containing the expression muon decay regardless of the
position of the expression in the title, type:
Now you see how to search for an author spelled sometimes as
Ellis, J and sometimes as Ellis, Jonathan
Richard (and other authors, such as De Lellis, Jim)
at the same time:
(See also our specific author
searching tips.)
The difference between exact and partial phrase searching modes may
not be obvious upon first look. While the latter is more similar to
what ``phrase search'' usually means in the context of web page search
engines, the former one is usually an order of magnitude faster if you
know the precise values you are looking for.
Another interesting searching mode besides the word and phrase
searches is the regular expression search, introduced
by slashes instead of quotes. For example, the above partial phrase
query 'muon decay'
is fully equivalent to the regular
expression query /muon decay/
. The regular expression
syntax is very powerful and permits you to construct very complex
queries. For more information, please consult the regular expression section of this guide.
The default search mode is a search for words. This
means that any whitespace you type is not significant, but is rather
interpreted to mean "add an automatic boolean AND between words", like
Google does. For example, to find all records that contain both the
word ellis and the word muon anywhere in the record,
type:
The whitespace would be significant if you include it within quotes.
There are two phrase searching modes:
- The double quotes instruct the search engine to search for
exact phrase. This phrase search mode will match if and
only if the given metadata field is exactly equal to the input
pattern. For example, to find all documents written by Ellis,
J spelled exactly that way, type:
- The single quotes instruct the search engine to search for
partial phrase. Unlike the exact phrase search, this
mode allows for an extra text appearing before/after given
pattern. This is somewhat similar to the "phrase search mode"
common on Google and other fulltext engines that search for phrase
expressions inside Web pages. For example, to find all the titles
containing the expression muon decay regardless of the
position of the expression in the title, type:
Now you see how to search for an author spelled sometimes as
Ellis, J and sometimes as Ellis, Jonathan
Richard (and other authors, such as De Lellis, Jim)
at the same time:
(See also our specific author
searching tips.)
The difference between exact and partial phrase searching modes may
not be obvious upon first look. While the latter is more similar to
what ``phrase search'' usually means in the context of web page search
engines, the former one is usually an order of magnitude faster if you
know the precise values you are looking for.
Another interesting searching mode besides the word and phrase
searches is the regular expression search, introduced
by slashes instead of quotes. For example, the above partial phrase
query 'muon decay'
is fully equivalent to the regular
expression query /muon decay/
. The regular expression
syntax is very powerful and permits you to construct very complex
queries. For more information, please consult the regular expression section of this guide.
El modo de búsqueda por defecto es la búsqueda por
palabras. Ello significa que se ignoran los espacios en
blanco, pero también que el motor de búsqueda lo interpreta por
defecto como "añade automáticamente una Y booleana entre las palabras
introducidas", del mismo modo que hace Google. Por ejemplo, para
recuperar todos los registros que contengan tanto la palabra
ellis como muon en cualquier parte del
registro, debemos escribir:
Si queremos que el espacio en blanco sea significativo, debemos
escribir la sentencia entrecomillada. Existen dos formas de búsqueda
por frases:
- La introducción de dobles comillas le indica al motor de búsqueda
buscar la frase exacta. Esta forma de búsqueda
por frase devolverá resultados sólo si los campos de metadatos
localizados son exactamente iguales al patrón solicitado. Por
ejemplo, para recuperar todos los documentos escritos por
Ellis, J escrito exactamente de ese modo, debemos
escribir:
- La introducción de comillas simples le indica al motor de búsqueda
buscar alguna parte de la frase. A diferencia de
la búsqueda de frase exacta este método permite que exista texto
antes/después del patrón solicitado. Sería algo similar al método
de "búsqueda por frase" que utilizan Google y otros motores de
búsqueda cuando buscan expresiones dentro del texto completo de
las páginas web. Por ejemplo, para localizar todos los títulos
que contengan la expresión muon decay independientemente
de la posición que ocupe la expresión en el título, escribiremos:
Observemos como se introduciría la búsqueda de un autor que a
veces aparece escrito como Ellis, J y otras como
Ellis, Jonathan Richard (incluyendo otros autores, como
De Lellis, Jim) en una misma acción de búsqueda:
(Para más información, se recomienda ver también la búsqueda
específica por autor.)
La diferencia entre buscar por frase exacta o buscar en parte de la
frase puede parecer poco obvia en un primer momento. Sin embargo,
mientras que la búsqueda en parte de la frase se asemeja a la búsqueda
por frase que suele utilizarse en el contexto de los buscadores web,
el uso de la búsqueda por frase exacta resulta mucho más efectiva y
rápida cuanto más se conocen y especifican los valores a recuperar.
Otro interesante modo de búsqueda aparte de la búsqueda por palabra
o por frase es el uso de la expresión regular de
búsqueda, que se efectúa a partir del uso de parentesis en
lugar de entrecomillado. Por ejemplo, la búsqueda anterior según el
modo de en parte de la frase 'muon decay'
es equivalente a
la expresión regular/muon decay/
. La sintaxis de las
expresiones regulares es muy potente, y permite construir búsquedas
muy complejas. Para obtener más información, recomendamos la consulta
de la sección expresión regular de esta guia.
El mode de cerca per defecte es la cerca per
paraules. Aquest mode implica s'ignorian els espais en
blanc, però també que el motor de cerca els interpreti per defecte com
a "afegeis automàticament una I booleana entre les paraules
introduïdes", de la mateixa forma que fa Google. Per exemple, per
recuperar tots els registres que continguin tant la paraula
ellis com muon a qualsevol part del registre,
haurem d'escriure:
Si volem que l'espai en blanc sigui significatiu, hem d'escriure la
sentència entre cometes. Existeixen dues formes de cerca per frase:
- La introducció de cometes dobles indica al motor de cerca
cerca la frase exacta. Aquesta forma de cerca per
frase retornara resultats només en el cas que els camps de metadades
localitzats siguin exactament igual al patró sol·licitat. Per exemple,
per recuperar tots els documents escrits per Ellis, J escrit
exactament d'aquesta manera, hem d'escriure:
- La introducció de comentes simples indica al motor de cerca
l'acció de cercar a alguna part de la frase. A
diferència de la cerca per frase exacta aquest mètode permet que
existeixi text abans/desprès del patró sol•licitat. Aquest métode és
similar al de "cerca per frase" que utilitzen Google i altres motors
de cerca quan cerquen expressions dins del text complet de les pàgines
web. Per exemple, per localitzar tots els títols que continguin
l'expressió muon decay independentment de la posició que
aquesta ocupi dins el títol, escriurem:
Observem como s’introduiria la cerca d’un autor que de vegades
apareix escrit com Ellis, J y altres com Ellis,
Jonathan Richard (incloent altres autors com De Lellis,
Jim) en una mateixa acció de cerca:
(Per més informació, es recomana veure també la cerca específica
per autor.)
La diferència entre cercar per frase exacta o cercar per part de la
frase Pot semblar poc evident a primera vista. Ara bé, mentre que la
cerca per part de la frase s’equipara a la cerca per frase que
acostuma a aplicar-se dins el context dels cercadors web, l’ús de la
cerca per frase exacta resulta molt més efectiva i ràpida com més es
coneguin i especifiquin els valors a recuperar.
Un altra interessant forma de cerca apart de la cerca per paraula o
frase, és l’ús de la expressió regular de cerca, que
es realitza a partir del ús de barres inclinades en lloc de cometes.
Per exemple, la cerca anterior segons el mode de ‘part de la frase’ de
l’expressió 'muon decay'
és equivalent a l’expressió
regular/muon decay/
. La sintaxi de les expressions
regulars és molt potent, i permet construir cerques molt complexes.
Per obtenir més informació, recomanem la consulta de la secció expressió regular d’aquesta guia.
We have already seen how whitespace adds a silent boolean AND in the
search for words. The other boolean operators include:
+ AND
|
ellis +muon
|
matches all records that contain both the word
ellis and the the word muon
|
ellis muon
|
ditto, syntactic sugar
|
ellis and muon
|
ditto, syntactic sugar
|
- NOT
|
ellis -muon
|
matches all records that contain the word
ellis but that do not contain the word
muon
|
ellis not muon
|
ditto, syntactic sugar
|
| OR
|
ellis |muon
|
matches all records that contain at least one
of the words
|
ellis or muon
|
ditto, syntactic sugar
|
We have already seen how whitespace adds a silent boolean AND in the
search for words. The other boolean operators include:
+ AND
|
ellis +muon
|
matches all records that contain both the word
ellis and the the word muon
|
ellis muon
|
ditto, syntactic sugar
|
ellis and muon
|
ditto, syntactic sugar
|
- NOT
|
ellis -muon
|
matches all records that contain the word
ellis but that do not contain the word
muon
|
ellis not muon
|
ditto, syntactic sugar
|
| OR
|
ellis |muon
|
matches all records that contain at least one
of the words
|
ellis or muon
|
ditto, syntactic sugar
|
We have already seen how whitespace adds a silent boolean AND in the
search for words. The other boolean operators include:
+ AND
|
ellis +muon
|
matches all records that contain both the word
ellis and the the word muon
|
ellis muon
|
ditto, syntactic sugar
|
ellis and muon
|
ditto, syntactic sugar
|
- NOT
|
ellis -muon
|
matches all records that contain the word
ellis but that do not contain the word
muon
|
ellis not muon
|
ditto, syntactic sugar
|
| OR
|
ellis |muon
|
matches all records that contain at least one
of the words
|
ellis or muon
|
ditto, syntactic sugar
|
We have already seen how whitespace adds a silent boolean AND in the
search for words. The other boolean operators include:
+ AND
|
ellis +muon
|
matches all records that contain both the word
ellis and the the word muon
|
ellis muon
|
ditto, syntactic sugar
|
ellis and muon
|
ditto, syntactic sugar
|
- NOT
|
ellis -muon
|
matches all records that contain the word
ellis but that do not contain the word
muon
|
ellis not muon
|
ditto, syntactic sugar
|
| OR
|
ellis |muon
|
matches all records that contain at least one
of the words
|
ellis or muon
|
ditto, syntactic sugar
|
We have already seen how whitespace adds a silent boolean AND in the
search for words. The other boolean operators include:
+ AND
|
ellis +muon
|
matches all records that contain both the word
ellis and the the word muon
|
ellis muon
|
ditto, syntactic sugar
|
ellis and muon
|
ditto, syntactic sugar
|
- NOT
|
ellis -muon
|
matches all records that contain the word
ellis but that do not contain the word
muon
|
ellis not muon
|
ditto, syntactic sugar
|
| OR
|
ellis |muon
|
matches all records that contain at least one
of the words
|
ellis or muon
|
ditto, syntactic sugar
|
We have already seen how whitespace adds a silent boolean AND in the
search for words. The other boolean operators include:
+ AND
|
ellis +muon
|
matches all records that contain both the word
ellis and the the word muon
|
ellis muon
|
ditto, syntactic sugar
|
ellis and muon
|
ditto, syntactic sugar
|
- NOT
|
ellis -muon
|
matches all records that contain the word
ellis but that do not contain the word
muon
|
ellis not muon
|
ditto, syntactic sugar
|
| OR
|
ellis |muon
|
matches all records that contain at least one
of the words
|
ellis or muon
|
ditto, syntactic sugar
|
We have already seen how whitespace adds a silent boolean AND in the
search for words. The other boolean operators include:
+ AND
|
ellis +muon
|
matches all records that contain both the word
ellis and the the word muon
|
ellis muon
|
ditto, syntactic sugar
|
ellis and muon
|
ditto, syntactic sugar
|
- NOT
|
ellis -muon
|
matches all records that contain the word
ellis but that do not contain the word
muon
|
ellis not muon
|
ditto, syntactic sugar
|
| OR
|
ellis |muon
|
matches all records that contain at least one
of the words
|
ellis or muon
|
ditto, syntactic sugar
|
We have already seen how whitespace adds a silent boolean AND in the
search for words. The other boolean operators include:
+ AND
|
ellis +muon
|
matches all records that contain both the word
ellis and the the word muon
|
ellis muon
|
ditto, syntactic sugar
|
ellis and muon
|
ditto, syntactic sugar
|
- NOT
|
ellis -muon
|
matches all records that contain the word
ellis but that do not contain the word
muon
|
ellis not muon
|
ditto, syntactic sugar
|
| OR
|
ellis |muon
|
matches all records that contain at least one
of the words
|
ellis or muon
|
ditto, syntactic sugar
|
We have already seen how whitespace adds a silent boolean AND in the
search for words. The other boolean operators include:
+ AND
|
ellis +muon
|
matches all records that contain both the word
ellis and the the word muon
|
ellis muon
|
ditto, syntactic sugar
|
ellis and muon
|
ditto, syntactic sugar
|
- NOT
|
ellis -muon
|
matches all records that contain the word
ellis but that do not contain the word
muon
|
ellis not muon
|
ditto, syntactic sugar
|
| OR
|
ellis |muon
|
matches all records that contain at least one
of the words
|
ellis or muon
|
ditto, syntactic sugar
|
We have already seen how whitespace adds a silent boolean AND in the
search for words. The other boolean operators include:
+ AND
|
ellis +muon
|
matches all records that contain both the word
ellis and the the word muon
|
ellis muon
|
ditto, syntactic sugar
|
ellis and muon
|
ditto, syntactic sugar
|
- NOT
|
ellis -muon
|
matches all records that contain the word
ellis but that do not contain the word
muon
|
ellis not muon
|
ditto, syntactic sugar
|
| OR
|
ellis |muon
|
matches all records that contain at least one
of the words
|
ellis or muon
|
ditto, syntactic sugar
|
We have already seen how whitespace adds a silent boolean AND in the
search for words. The other boolean operators include:
+ AND
|
ellis +muon
|
matches all records that contain both the word
ellis and the the word muon
|
ellis muon
|
ditto, syntactic sugar
|
ellis and muon
|
ditto, syntactic sugar
|
- NOT
|
ellis -muon
|
matches all records that contain the word
ellis but that do not contain the word
muon
|
ellis not muon
|
ditto, syntactic sugar
|
| OR
|
ellis |muon
|
matches all records that contain at least one
of the words
|
ellis or muon
|
ditto, syntactic sugar
|
We have already seen how whitespace adds a silent boolean AND in the
search for words. The other boolean operators include:
+ AND
|
ellis +muon
|
matches all records that contain both the word
ellis and the the word muon
|
ellis muon
|
ditto, syntactic sugar
|
ellis and muon
|
ditto, syntactic sugar
|
- NOT
|
ellis -muon
|
matches all records that contain the word
ellis but that do not contain the word
muon
|
ellis not muon
|
ditto, syntactic sugar
|
| OR
|
ellis |muon
|
matches all records that contain at least one
of the words
|
ellis or muon
|
ditto, syntactic sugar
|
We have already seen how whitespace adds a silent boolean AND in the
search for words. The other boolean operators include:
+ AND
|
ellis +muon
|
matches all records that contain both the word
ellis and the the word muon
|
ellis muon
|
ditto, syntactic sugar
|
ellis and muon
|
ditto, syntactic sugar
|
- NOT
|
ellis -muon
|
matches all records that contain the word
ellis but that do not contain the word
muon
|
ellis not muon
|
ditto, syntactic sugar
|
| OR
|
ellis |muon
|
matches all records that contain at least one
of the words
|
ellis or muon
|
ditto, syntactic sugar
|
We have already seen how whitespace adds a silent boolean AND in the
search for words. The other boolean operators include:
+ AND
|
ellis +muon
|
matches all records that contain both the word
ellis and the the word muon
|
ellis muon
|
ditto, syntactic sugar
|
ellis and muon
|
ditto, syntactic sugar
|
- NOT
|
ellis -muon
|
matches all records that contain the word
ellis but that do not contain the word
muon
|
ellis not muon
|
ditto, syntactic sugar
|
| OR
|
ellis |muon
|
matches all records that contain at least one
of the words
|
ellis or muon
|
ditto, syntactic sugar
|
We have already seen how whitespace adds a silent boolean AND in the
search for words. The other boolean operators include:
+ AND
|
ellis +muon
|
matches all records that contain both the word
ellis and the the word muon
|
ellis muon
|
ditto, syntactic sugar
|
ellis and muon
|
ditto, syntactic sugar
|
- NOT
|
ellis -muon
|
matches all records that contain the word
ellis but that do not contain the word
muon
|
ellis not muon
|
ditto, syntactic sugar
|
| OR
|
ellis |muon
|
matches all records that contain at least one
of the words
|
ellis or muon
|
ditto, syntactic sugar
|
We have already seen how whitespace adds a silent boolean AND in the
search for words. The other boolean operators include:
+ AND
|
ellis +muon
|
matches all records that contain both the word
ellis and the the word muon
|
ellis muon
|
ditto, syntactic sugar
|
ellis and muon
|
ditto, syntactic sugar
|
- NOT
|
ellis -muon
|
matches all records that contain the word
ellis but that do not contain the word
muon
|
ellis not muon
|
ditto, syntactic sugar
|
| OR
|
ellis |muon
|
matches all records that contain at least one
of the words
|
ellis or muon
|
ditto, syntactic sugar
|
We have already seen how whitespace adds a silent boolean AND in the
search for words. The other boolean operators include:
+ AND
|
ellis +muon
|
matches all records that contain both the word
ellis and the the word muon
|
ellis muon
|
ditto, syntactic sugar
|
ellis and muon
|
ditto, syntactic sugar
|
- NOT
|
ellis -muon
|
matches all records that contain the word
ellis but that do not contain the word
muon
|
ellis not muon
|
ditto, syntactic sugar
|
| OR
|
ellis |muon
|
matches all records that contain at least one
of the words
|
ellis or muon
|
ditto, syntactic sugar
|
We have already seen how whitespace adds a silent boolean AND in the
search for words. The other boolean operators include:
+ AND
|
ellis +muon
|
matches all records that contain both the word
ellis and the the word muon
|
ellis muon
|
ditto, syntactic sugar
|
ellis and muon
|
ditto, syntactic sugar
|
- NOT
|
ellis -muon
|
matches all records that contain the word
ellis but that do not contain the word
muon
|
ellis not muon
|
ditto, syntactic sugar
|
| OR
|
ellis |muon
|
matches all records that contain at least one
of the words
|
ellis or muon
|
ditto, syntactic sugar
|
Ya hemos visto como la inclusión de un espacio en blanco es
equivalente a la adición de un operador booleano en la búsqueda por
palabras. El resto de operadores booleanos son:
+ AND
|
ellis +muon
|
recupera todos los registros que contengan ambas palabras:
ellis y la palabra muon
|
ellis muon
|
ídem, "syntactic sugar"(*ver nota)
|
ellis and muon
|
ídem, "syntactic sugar"
|
- NOT
|
ellis -muon
|
recupera todos los registros que contengan la palabra
ellis pero que no contenga la palabra muon
|
ellis not muon
|
ditto, "syntactic sugar"
|
| OR
|
ellis |acelerador
|
recupera todos los registros que contengan al menos, una de las dos palabras
|
ellis or muon
|
ídem, "syntactic sugar"
|
(*)Nota de la traducción española: syntactic sugar es una espresión
utilizada en inglés para describir "otra forma similar de llamar a una función" |
Hem vist com la inclusió d’un espai en blanc és equivalent a l’adició
d’un operador booleà a la cerca per paraules. La resta d’operadors
booleans són:
+ AND
|
ellis +muon
|
Recupera tots els registres que contenen ambdues paraules:
ellis i la paraula muon
|
ellis muon
|
ídem, "syntactic sugar" (*veure nota)
|
ellis and muon
|
ídem, "syntactic sugar"
|
- NOT
|
ellis -muon
|
recupera tots els registres que contenen la paraula ellis però que no contenen la paraula muon
|
ellis not muon
|
ídem, "syntactic sugar"
|
| OR
|
ellis |muon
|
recupera tots els registres que contenen, com a mínim, una de les dues paraules
|
ellis or muon
|
ídem, "syntactic sugar"
|
(*)Nota de la traducció catalana: syntactic sugar es una espressió
emprada en anglès per a descriure "altre forma similar de cridar una funció" |
Logical operations are automatically chained from left to right.
For example, if you want to search for documents written by Ellis on
muons or kaons, write:
which looks for (muon or kaon) and ellis
. Note that this
gives different results from:
which would search for (ellis and muon) or kaon
.
The left-to-right chaining behaviour permits you to easily refine
your search by adding/removing words with and/not or +/- operators.
For example, to exclude the documents on decay from the above search,
append -decay
:
to get a refined list. Keep adding/removing terms until you are
satisfied.
Logical operations are automatically chained from left to right.
For example, if you want to search for documents written by Ellis on
muons or kaons, write:
which looks for (muon or kaon) and ellis
. Note that this
gives different results from:
which would search for (ellis and muon) or kaon
.
The left-to-right chaining behaviour permits you to easily refine
your search by adding/removing words with and/not or +/- operators.
For example, to exclude the documents on decay from the above search,
append -decay
:
to get a refined list. Keep adding/removing terms until you are
satisfied.
Logical operations are automatically chained from left to right.
For example, if you want to search for documents written by Ellis on
muons or kaons, write:
which looks for (muon or kaon) and ellis
. Note that this
gives different results from:
which would search for (ellis and muon) or kaon
.
The left-to-right chaining behaviour permits you to easily refine
your search by adding/removing words with and/not or +/- operators.
For example, to exclude the documents on decay from the above search,
append -decay
:
to get a refined list. Keep adding/removing terms until you are
satisfied.
Logical operations are automatically chained from left to right.
For example, if you want to search for documents written by Ellis on
muons or kaons, write:
which looks for (muon or kaon) and ellis
. Note that this
gives different results from:
which would search for (ellis and muon) or kaon
.
The left-to-right chaining behaviour permits you to easily refine
your search by adding/removing words with and/not or +/- operators.
For example, to exclude the documents on decay from the above search,
append -decay
:
to get a refined list. Keep adding/removing terms until you are
satisfied.
Logical operations are automatically chained from left to right.
For example, if you want to search for documents written by Ellis on
muons or kaons, write:
which looks for (muon or kaon) and ellis
. Note that this
gives different results from:
which would search for (ellis and muon) or kaon
.
The left-to-right chaining behaviour permits you to easily refine
your search by adding/removing words with and/not or +/- operators.
For example, to exclude the documents on decay from the above search,
append -decay
:
to get a refined list. Keep adding/removing terms until you are
satisfied.
Logical operations are automatically chained from left to right.
For example, if you want to search for documents written by Ellis on
muons or kaons, write:
which looks for (muon or kaon) and ellis
. Note that this
gives different results from:
which would search for (ellis and muon) or kaon
.
The left-to-right chaining behaviour permits you to easily refine
your search by adding/removing words with and/not or +/- operators.
For example, to exclude the documents on decay from the above search,
append -decay
:
to get a refined list. Keep adding/removing terms until you are
satisfied.
Logical operations are automatically chained from left to right.
For example, if you want to search for documents written by Ellis on
muons or kaons, write:
which looks for (muon or kaon) and ellis
. Note that this
gives different results from:
which would search for (ellis and muon) or kaon
.
The left-to-right chaining behaviour permits you to easily refine
your search by adding/removing words with and/not or +/- operators.
For example, to exclude the documents on decay from the above search,
append -decay
:
to get a refined list. Keep adding/removing terms until you are
satisfied.
Logical operations are automatically chained from left to right.
For example, if you want to search for documents written by Ellis on
muons or kaons, write:
which looks for (muon or kaon) and ellis
. Note that this
gives different results from:
which would search for (ellis and muon) or kaon
.
The left-to-right chaining behaviour permits you to easily refine
your search by adding/removing words with and/not or +/- operators.
For example, to exclude the documents on decay from the above search,
append -decay
:
to get a refined list. Keep adding/removing terms until you are
satisfied.
Logical operations are automatically chained from left to right.
For example, if you want to search for documents written by Ellis on
muons or kaons, write:
which looks for (muon or kaon) and ellis
. Note that this
gives different results from:
which would search for (ellis and muon) or kaon
.
The left-to-right chaining behaviour permits you to easily refine
your search by adding/removing words with and/not or +/- operators.
For example, to exclude the documents on decay from the above search,
append -decay
:
to get a refined list. Keep adding/removing terms until you are
satisfied.
Logical operations are automatically chained from left to right.
For example, if you want to search for documents written by Ellis on
muons or kaons, write:
which looks for (muon or kaon) and ellis
. Note that this
gives different results from:
which would search for (ellis and muon) or kaon
.
The left-to-right chaining behaviour permits you to easily refine
your search by adding/removing words with and/not or +/- operators.
For example, to exclude the documents on decay from the above search,
append -decay
:
to get a refined list. Keep adding/removing terms until you are
satisfied.
Logical operations are automatically chained from left to right.
For example, if you want to search for documents written by Ellis on
muons or kaons, write:
which looks for (muon or kaon) and ellis
. Note that this
gives different results from:
which would search for (ellis and muon) or kaon
.
The left-to-right chaining behaviour permits you to easily refine
your search by adding/removing words with and/not or +/- operators.
For example, to exclude the documents on decay from the above search,
append -decay
:
to get a refined list. Keep adding/removing terms until you are
satisfied.
Logical operations are automatically chained from left to right.
For example, if you want to search for documents written by Ellis on
muons or kaons, write:
which looks for (muon or kaon) and ellis
. Note that this
gives different results from:
which would search for (ellis and muon) or kaon
.
The left-to-right chaining behaviour permits you to easily refine
your search by adding/removing words with and/not or +/- operators.
For example, to exclude the documents on decay from the above search,
append -decay
:
to get a refined list. Keep adding/removing terms until you are
satisfied.
Logical operations are automatically chained from left to right.
For example, if you want to search for documents written by Ellis on
muons or kaons, write:
which looks for (muon or kaon) and ellis
. Note that this
gives different results from:
which would search for (ellis and muon) or kaon
.
The left-to-right chaining behaviour permits you to easily refine
your search by adding/removing words with and/not or +/- operators.
For example, to exclude the documents on decay from the above search,
append -decay
:
to get a refined list. Keep adding/removing terms until you are
satisfied.
Logical operations are automatically chained from left to right.
For example, if you want to search for documents written by Ellis on
muons or kaons, write:
which looks for (muon or kaon) and ellis
. Note that this
gives different results from:
which would search for (ellis and muon) or kaon
.
The left-to-right chaining behaviour permits you to easily refine
your search by adding/removing words with and/not or +/- operators.
For example, to exclude the documents on decay from the above search,
append -decay
:
to get a refined list. Keep adding/removing terms until you are
satisfied.
Logical operations are automatically chained from left to right.
For example, if you want to search for documents written by Ellis on
muons or kaons, write:
which looks for (muon or kaon) and ellis
. Note that this
gives different results from:
which would search for (ellis and muon) or kaon
.
The left-to-right chaining behaviour permits you to easily refine
your search by adding/removing words with and/not or +/- operators.
For example, to exclude the documents on decay from the above search,
append -decay
:
to get a refined list. Keep adding/removing terms until you are
satisfied.
Logical operations are automatically chained from left to right.
For example, if you want to search for documents written by Ellis on
muons or kaons, write:
which looks for (muon or kaon) and ellis
. Note that this
gives different results from:
which would search for (ellis and muon) or kaon
.
The left-to-right chaining behaviour permits you to easily refine
your search by adding/removing words with and/not or +/- operators.
For example, to exclude the documents on decay from the above search,
append -decay
:
to get a refined list. Keep adding/removing terms until you are
satisfied.
Logical operations are automatically chained from left to right.
For example, if you want to search for documents written by Ellis on
muons or kaons, write:
which looks for (muon or kaon) and ellis
. Note that this
gives different results from:
which would search for (ellis and muon) or kaon
.
The left-to-right chaining behaviour permits you to easily refine
your search by adding/removing words with and/not or +/- operators.
For example, to exclude the documents on decay from the above search,
append -decay
:
to get a refined list. Keep adding/removing terms until you are
satisfied.
Logical operations are automatically chained from left to right.
For example, if you want to search for documents written by Ellis on
muons or kaons, write:
which looks for (muon or kaon) and ellis
. Note that this
gives different results from:
which would search for (ellis and muon) or kaon
.
The left-to-right chaining behaviour permits you to easily refine
your search by adding/removing words with and/not or +/- operators.
For example, to exclude the documents on decay from the above search,
append -decay
:
to get a refined list. Keep adding/removing terms until you are
satisfied.
Los operadores lógicos se disponen de forma automática de izquierda
a derecha. Logical operations are automatically chained from left to
right. Por ejemplo, si queremos buscar documentos escritos por Ellis
sobre muon o kaon, escribiremos:
ello nos realizará una búsqueda equivalente a (muon O
kaon) Y ellis
. Nótese también que se obtienen
resultados diferentes si introducimos
que si introducimos (ellis AND muon) OR kaon
.
La disposición de los elementos de izquierda a derecha permite
refinar fácilmente una búsqueda añadiendo o quitando palabras
utilizanto los operadores AND/NOT +/-.
Por ejemplo, para excluir los documentos sobre desintegración en la
búsqueda anterior, sólo hay que añadir -decay
:
y con ello obtendremos una lista más filtrada. Se pueden añadir o
quitar tantos elementos como sea conveniente hasta conseguir mayor
precisión en la búsqueda.
Els operadors lògics es disposen de forma automàtica d’esquerre
a dreta. Per exemple, si es volen recuperar documents escrits per Ellis
sobre muon o kaon, escriurem:
es realitzarà una cerca equivalent a (muon OR kaon)
AND ellis
. Notis també que s’obtenen resultats diferents si
s’introdueix
que si s’introdueix (ellis AND muon) OR kaon
.
La disposició dels elements d’esquerre a dreta permet refinar
fàcilment una cerca afegint o traient paraules utilitzant els
operadors AND/NOT +/-.
Per exemple, per excloure els documents sobre desintegració a la cerca
anterior, només cal afegir -decay
:
Amb el que s’obtindria una llista més filtrada. Es poden afegir o
traure tants elements com sigui convenient, fins aconseguir més
precisió a la cerca.
When indexing words, an attention is paid to index it both with and
without punctuation, so that you should be able to search for terms
containing special characters, such as C++, verbatim:
For example, to find records containing the LaTeX expression
$e^{+}e^{-}$
in the title, type:
For example, to find document with the report number
hep-ph/0204133, type:
Note that the search is case-insensitive:
When indexing words, an attention is paid to index it both with and
without punctuation, so that you should be able to search for terms
containing special characters, such as C++, verbatim:
For example, to find records containing the LaTeX expression
$e^{+}e^{-}$
in the title, type:
For example, to find document with the report number
hep-ph/0204133, type:
Note that the search is case-insensitive:
When indexing words, an attention is paid to index it both with and
without punctuation, so that you should be able to search for terms
containing special characters, such as C++, verbatim:
For example, to find records containing the LaTeX expression
$e^{+}e^{-}$
in the title, type:
For example, to find document with the report number
hep-ph/0204133, type:
Note that the search is case-insensitive:
When indexing words, an attention is paid to index it both with and
without punctuation, so that you should be able to search for terms
containing special characters, such as C++, verbatim:
For example, to find records containing the LaTeX expression
$e^{+}e^{-}$
in the title, type:
For example, to find document with the report number
hep-ph/0204133, type:
Note that the search is case-insensitive:
When indexing words, an attention is paid to index it both with and
without punctuation, so that you should be able to search for terms
containing special characters, such as C++, verbatim:
For example, to find records containing the LaTeX expression
$e^{+}e^{-}$
in the title, type:
For example, to find document with the report number
hep-ph/0204133, type:
Note that the search is case-insensitive:
When indexing words, an attention is paid to index it both with and
without punctuation, so that you should be able to search for terms
containing special characters, such as C++, verbatim:
For example, to find records containing the LaTeX expression
$e^{+}e^{-}$
in the title, type:
For example, to find document with the report number
hep-ph/0204133, type:
Note that the search is case-insensitive:
When indexing words, an attention is paid to index it both with and
without punctuation, so that you should be able to search for terms
containing special characters, such as C++, verbatim:
For example, to find records containing the LaTeX expression
$e^{+}e^{-}$
in the title, type:
For example, to find document with the report number
hep-ph/0204133, type:
Note that the search is case-insensitive:
When indexing words, an attention is paid to index it both with and
without punctuation, so that you should be able to search for terms
containing special characters, such as C++, verbatim:
For example, to find records containing the LaTeX expression
$e^{+}e^{-}$
in the title, type:
For example, to find document with the report number
hep-ph/0204133, type:
Note that the search is case-insensitive:
When indexing words, an attention is paid to index it both with and
without punctuation, so that you should be able to search for terms
containing special characters, such as C++, verbatim:
For example, to find records containing the LaTeX expression
$e^{+}e^{-}$
in the title, type:
For example, to find document with the report number
hep-ph/0204133, type:
Note that the search is case-insensitive:
When indexing words, an attention is paid to index it both with and
without punctuation, so that you should be able to search for terms
containing special characters, such as C++, verbatim:
For example, to find records containing the LaTeX expression
$e^{+}e^{-}$
in the title, type:
For example, to find document with the report number
hep-ph/0204133, type:
Note that the search is case-insensitive:
When indexing words, an attention is paid to index it both with and
without punctuation, so that you should be able to search for terms
containing special characters, such as C++, verbatim:
For example, to find records containing the LaTeX expression
$e^{+}e^{-}$
in the title, type:
For example, to find document with the report number
hep-ph/0204133, type:
Note that the search is case-insensitive:
When indexing words, an attention is paid to index it both with and
without punctuation, so that you should be able to search for terms
containing special characters, such as C++, verbatim:
For example, to find records containing the LaTeX expression
$e^{+}e^{-}$
in the title, type:
For example, to find document with the report number
hep-ph/0204133, type:
Note that the search is case-insensitive:
When indexing words, an attention is paid to index it both with and
without punctuation, so that you should be able to search for terms
containing special characters, such as C++, verbatim:
For example, to find records containing the LaTeX expression
$e^{+}e^{-}$
in the title, type:
For example, to find document with the report number
hep-ph/0204133, type:
Note that the search is case-insensitive:
When indexing words, an attention is paid to index it both with and
without punctuation, so that you should be able to search for terms
containing special characters, such as C++, verbatim:
For example, to find records containing the LaTeX expression
$e^{+}e^{-}$
in the title, type:
For example, to find document with the report number
hep-ph/0204133, type:
Note that the search is case-insensitive:
When indexing words, an attention is paid to index it both with and
without punctuation, so that you should be able to search for terms
containing special characters, such as C++, verbatim:
For example, to find records containing the LaTeX expression
$e^{+}e^{-}$
in the title, type:
For example, to find document with the report number
hep-ph/0204133, type:
Note that the search is case-insensitive:
When indexing words, an attention is paid to index it both with and
without punctuation, so that you should be able to search for terms
containing special characters, such as C++, verbatim:
For example, to find records containing the LaTeX expression
$e^{+}e^{-}$
in the title, type:
For example, to find document with the report number
hep-ph/0204133, type:
Note that the search is case-insensitive:
When indexing words, an attention is paid to index it both with and
without punctuation, so that you should be able to search for terms
containing special characters, such as C++, verbatim:
For example, to find records containing the LaTeX expression
$e^{+}e^{-}$
in the title, type:
For example, to find document with the report number
hep-ph/0204133, type:
Note that the search is case-insensitive:
When indexing words, an attention is paid to index it both with and
without punctuation, so that you should be able to search for terms
containing special characters, such as C++, verbatim:
For example, to find records containing the LaTeX expression
$e^{+}e^{-}$
in the title, type:
For example, to find document with the report number
hep-ph/0204133, type:
Note that the search is case-insensitive:
Cuando se indexan las palabras, se pone especial atención en indexarlas
con y sin puntuación. Ello hace posible la búsqueda de términos que contienen
caracteres especiales, como por ejemplo C++, textualmente:
Por ejemplo, para recuperar registros que contengan la expresión LaTeX
$e^{+}e^{-}$
en el título, debemos escribir:
Por ejemplo, para recuperar un documento con el número de informe
hep-ph/0204133, debemos escribir:
Nótese que esta búsqueda es sensible a las mayúsculas:
Quan s’indexen les paraules, es posa especial atenció en que siguin
indexades amb i sense puntuació. Això fa possible la cerca de termes
que contenen caràcters especials, com per exemple C++,
textualment:
Per exemple, per recuperar registres que contenen l’expresió LaTeX
$e^{+}e^{-}$
al títol, cal escriure:
Per exemple, per recuperar un document amb número d'informe
hep-ph/0204133, cal escriure:
Observis que aquesta cerca és sensible a les majúscules:
The search engine works with Unicode UTF-8 so you can type your
query strings in any language stored in the database. For
example, to find the documents written by (or on) Пушкин, type:
Note that you don't have to type accents to find accented results. For example,
type Lemaitre
to find papers by Lemaître:
" ""1" ""1""
Currently, words that include accented characters can only be retrieved by entering
accented characters in the query.
|
">
The search engine works with Unicode UTF-8 so you can type your
query strings in any language stored in the database. For
example, to find the documents written by (or on) Пушкин, type:
Note that you don't have to type accents to find accented results. For example,
type Lemaitre
to find papers by Lemaître:
" ""1" ""1""
Currently, words that include accented characters can only be retrieved by entering
accented characters in the query.
|
">
The search engine works with Unicode UTF-8 so you can type your
query strings in any language stored in the database. For
example, to find the documents written by (or on) Пушкин, type:
Note that you don't have to type accents to find accented results. For example,
type Lemaitre
to find papers by Lemaître:
" ""1" ""1""
Currently, words that include accented characters can only be retrieved by entering
accented characters in the query.
|
">
The search engine works with Unicode UTF-8 so you can type your
query strings in any language stored in the database. For
example, to find the documents written by (or on) Пушкин, type:
Note that you don't have to type accents to find accented results. For example,
type Lemaitre
to find papers by Lemaître:
" ""1" ""1""
Currently, words that include accented characters can only be retrieved by entering
accented characters in the query.
|
">
The search engine works with Unicode UTF-8 so you can type your
query strings in any language stored in the database. For
example, to find the documents written by (or on) Пушкин, type:
Note that you don't have to type accents to find accented results. For example,
type Lemaitre
to find papers by Lemaître:
" ""1" ""1""
Currently, words that include accented characters can only be retrieved by entering
accented characters in the query.
|
">
The search engine works with Unicode UTF-8 so you can type your
query strings in any language stored in the database. For
example, to find the documents written by (or on) Пушкин, type:
Note that you don't have to type accents to find accented results. For example,
type Lemaitre
to find papers by Lemaître:
" ""1" ""1""
Currently, words that include accented characters can only be retrieved by entering
accented characters in the query.
|
">
The search engine works with Unicode UTF-8 so you can type your
query strings in any language stored in the database. For
example, to find the documents written by (or on) Пушкин, type:
Note that you don't have to type accents to find accented results. For example,
type Lemaitre
to find papers by Lemaître:
" ""1" ""1""
Currently, words that include accented characters can only be retrieved by entering
accented characters in the query.
|
">
The search engine works with Unicode UTF-8 so you can type your
query strings in any language stored in the database. For
example, to find the documents written by (or on) Пушкин, type:
Note that you don't have to type accents to find accented results. For example,
type Lemaitre
to find papers by Lemaître:
" ""1" ""1""
Currently, words that include accented characters can only be retrieved by entering
accented characters in the query.
|
">
The search engine works with Unicode UTF-8 so you can type your
query strings in any language stored in the database. For
example, to find the documents written by (or on) Пушкин, type:
Note that you don't have to type accents to find accented results. For example,
type Lemaitre
to find papers by Lemaître:
" ""1" ""1""
Currently, words that include accented characters can only be retrieved by entering
accented characters in the query.
|
">
The search engine works with Unicode UTF-8 so you can type your
query strings in any language stored in the database. For
example, to find the documents written by (or on) Пушкин, type:
Note that you don't have to type accents to find accented results. For example,
type Lemaitre
to find papers by Lemaître:
" ""1" ""1""
Currently, words that include accented characters can only be retrieved by entering
accented characters in the query.
|
">
The search engine works with Unicode UTF-8 so you can type your
query strings in any language stored in the database. For
example, to find the documents written by (or on) Пушкин, type:
Note that you don't have to type accents to find accented results. For example,
type Lemaitre
to find papers by Lemaître:
" ""1" ""1""
Currently, words that include accented characters can only be retrieved by entering
accented characters in the query.
|
">
The search engine works with Unicode UTF-8 so you can type your
query strings in any language stored in the database. For
example, to find the documents written by (or on) Пушкин, type:
Note that you don't have to type accents to find accented results. For example,
type Lemaitre
to find papers by Lemaître:
" ""1" ""1""
Currently, words that include accented characters can only be retrieved by entering
accented characters in the query.
|
">
The search engine works with Unicode UTF-8 so you can type your
query strings in any language stored in the database. For
example, to find the documents written by (or on) Пушкин, type:
Note that you don't have to type accents to find accented results. For example,
type Lemaitre
to find papers by Lemaître:
" ""1" ""1""
Currently, words that include accented characters can only be retrieved by entering
accented characters in the query.
|
">
The search engine works with Unicode UTF-8 so you can type your
query strings in any language stored in the database. For
example, to find the documents written by (or on) Пушкин, type:
Note that you don't have to type accents to find accented results. For example,
type Lemaitre
to find papers by Lemaître:
" ""1" ""1""
Currently, words that include accented characters can only be retrieved by entering
accented characters in the query.
|
">
The search engine works with Unicode UTF-8 so you can type your
query strings in any language stored in the database. For
example, to find the documents written by (or on) Пушкин, type:
Note that you don't have to type accents to find accented results. For example,
type Lemaitre
to find papers by Lemaître:
" ""1" ""1""
Currently, words that include accented characters can only be retrieved by entering
accented characters in the query.
|
">
The search engine works with Unicode UTF-8 so you can type your
query strings in any language stored in the database. For
example, to find the documents written by (or on) Пушкин, type:
Note that you don't have to type accents to find accented results. For example,
type Lemaitre
to find papers by Lemaître:
" ""1" ""1""
Currently, words that include accented characters can only be retrieved by entering
accented characters in the query.
|
">
The search engine works with Unicode UTF-8 so you can type your
query strings in any language stored in the database. For
example, to find the documents written by (or on) Пушкин, type:
Note that you don't have to type accents to find accented results. For example,
type Lemaitre
to find papers by Lemaître:
" ""1" ""1""
Currently, words that include accented characters can only be retrieved by entering
accented characters in the query.
|
">
The search engine works with Unicode UTF-8 so you can type your
query strings in any language stored in the database. For
example, to find the documents written by (or on) Пушкин, type:
Note that you don't have to type accents to find accented results. For example,
type Lemaitre
to find papers by Lemaître:
" ""1" ""1""
Currently, words that include accented characters can only be retrieved by entering
accented characters in the query.
|
">
El motor de búsqueda se basa en el estandar Unicode UTF-8, lo que
hace posible introducir cadenas de búsqueda en cualquier idioma que se
encuentre en la base de datos. Por ejemplo, para recuperar documentos
escritos por (o sobre) Пушкин, debemos escribir:
Obsérvese que no es necesario introducir acentos para conseguir registros que contienen palabras acentuadas.
Por ejemplo, escribiremos Lemaitre
para buscar artículos de Lemaître:
" ""1" ""1""
En estos momentos, las palabras que incluyen caracteres acentuados sólo pueden
recuperarse entrando los caracteres acentuados en la consulta.
|
">
El motor de cerca es basa en l’estàndard Unicode UTF-8, lo que fa
possible introduir cadenes de cerca en qualsevol llengua que es trobi
a la base de dades. Per exemple, per recuperar documents escrits per
(o sobre) Пушкин, cal escriure:
Notis que no és necessari introduir accents per aconseguir registres
que contenen paraules accentuades. Per exemple, escriurem Lemaitre
para recuperar articles de Lemaître:
" ""1" ""1""
En aquests moments, les paraules que inclouen caràcters accentuats només es poden
recuperar entrant els caràcters accentuats a la consulta.
|
">
The word truncation is supported via asterisk (*) wildcard
character. The wildcard instructs the search engine to match any
number of characters in that place. For example, to find records
that contain words muon, muons, muonic
etc, type:
The wildcard query works both in prefix and infix position. For
example, to get all the words that start by CERN-TH and
end by 31, type:
Note that the wildcard will be ignored if you try to apply it to
very short words, such as a*:
The wildcard character can be used also in the phrase searching
mode. For example, to find all the documents whose title starts by
"Neutrino mass", type:
Recall that we have introduced exact and partial phrase search
modes. Actually, a partial phrase search mode launches an exact
search enclosed within wildcards: we could say that 'foo bar
baz'
equals to "*foo bar baz*"
. Now you can
see why the partial phrase search is slow: due to the usage of two
asterisks in front and after the text, each and every title in the
database has to be looked up to determine whether it matches or
not. (There are currently no partial phrase indexes.)
The word truncation is supported via asterisk (*) wildcard
character. The wildcard instructs the search engine to match any
number of characters in that place. For example, to find records
that contain words muon, muons, muonic
etc, type:
The wildcard query works both in prefix and infix position. For
example, to get all the words that start by CERN-TH and
end by 31, type:
Note that the wildcard will be ignored if you try to apply it to
very short words, such as a*:
The wildcard character can be used also in the phrase searching
mode. For example, to find all the documents whose title starts by
"Neutrino mass", type:
Recall that we have introduced exact and partial phrase search
modes. Actually, a partial phrase search mode launches an exact
search enclosed within wildcards: we could say that 'foo bar
baz'
equals to "*foo bar baz*"
. Now you can
see why the partial phrase search is slow: due to the usage of two
asterisks in front and after the text, each and every title in the
database has to be looked up to determine whether it matches or
not. (There are currently no partial phrase indexes.)
The word truncation is supported via asterisk (*) wildcard
character. The wildcard instructs the search engine to match any
number of characters in that place. For example, to find records
that contain words muon, muons, muonic
etc, type:
The wildcard query works both in prefix and infix position. For
example, to get all the words that start by CERN-TH and
end by 31, type:
Note that the wildcard will be ignored if you try to apply it to
very short words, such as a*:
The wildcard character can be used also in the phrase searching
mode. For example, to find all the documents whose title starts by
"Neutrino mass", type:
Recall that we have introduced exact and partial phrase search
modes. Actually, a partial phrase search mode launches an exact
search enclosed within wildcards: we could say that 'foo bar
baz'
equals to "*foo bar baz*"
. Now you can
see why the partial phrase search is slow: due to the usage of two
asterisks in front and after the text, each and every title in the
database has to be looked up to determine whether it matches or
not. (There are currently no partial phrase indexes.)
The word truncation is supported via asterisk (*) wildcard
character. The wildcard instructs the search engine to match any
number of characters in that place. For example, to find records
that contain words muon, muons, muonic
etc, type:
The wildcard query works both in prefix and infix position. For
example, to get all the words that start by CERN-TH and
end by 31, type:
Note that the wildcard will be ignored if you try to apply it to
very short words, such as a*:
The wildcard character can be used also in the phrase searching
mode. For example, to find all the documents whose title starts by
"Neutrino mass", type:
Recall that we have introduced exact and partial phrase search
modes. Actually, a partial phrase search mode launches an exact
search enclosed within wildcards: we could say that 'foo bar
baz'
equals to "*foo bar baz*"
. Now you can
see why the partial phrase search is slow: due to the usage of two
asterisks in front and after the text, each and every title in the
database has to be looked up to determine whether it matches or
not. (There are currently no partial phrase indexes.)
The word truncation is supported via asterisk (*) wildcard
character. The wildcard instructs the search engine to match any
number of characters in that place. For example, to find records
that contain words muon, muons, muonic
etc, type:
The wildcard query works both in prefix and infix position. For
example, to get all the words that start by CERN-TH and
end by 31, type:
Note that the wildcard will be ignored if you try to apply it to
very short words, such as a*:
The wildcard character can be used also in the phrase searching
mode. For example, to find all the documents whose title starts by
"Neutrino mass", type:
Recall that we have introduced exact and partial phrase search
modes. Actually, a partial phrase search mode launches an exact
search enclosed within wildcards: we could say that 'foo bar
baz'
equals to "*foo bar baz*"
. Now you can
see why the partial phrase search is slow: due to the usage of two
asterisks in front and after the text, each and every title in the
database has to be looked up to determine whether it matches or
not. (There are currently no partial phrase indexes.)
The word truncation is supported via asterisk (*) wildcard
character. The wildcard instructs the search engine to match any
number of characters in that place. For example, to find records
that contain words muon, muons, muonic
etc, type:
The wildcard query works both in prefix and infix position. For
example, to get all the words that start by CERN-TH and
end by 31, type:
Note that the wildcard will be ignored if you try to apply it to
very short words, such as a*:
The wildcard character can be used also in the phrase searching
mode. For example, to find all the documents whose title starts by
"Neutrino mass", type:
Recall that we have introduced exact and partial phrase search
modes. Actually, a partial phrase search mode launches an exact
search enclosed within wildcards: we could say that 'foo bar
baz'
equals to "*foo bar baz*"
. Now you can
see why the partial phrase search is slow: due to the usage of two
asterisks in front and after the text, each and every title in the
database has to be looked up to determine whether it matches or
not. (There are currently no partial phrase indexes.)
The word truncation is supported via asterisk (*) wildcard
character. The wildcard instructs the search engine to match any
number of characters in that place. For example, to find records
that contain words muon, muons, muonic
etc, type:
The wildcard query works both in prefix and infix position. For
example, to get all the words that start by CERN-TH and
end by 31, type:
Note that the wildcard will be ignored if you try to apply it to
very short words, such as a*:
The wildcard character can be used also in the phrase searching
mode. For example, to find all the documents whose title starts by
"Neutrino mass", type:
Recall that we have introduced exact and partial phrase search
modes. Actually, a partial phrase search mode launches an exact
search enclosed within wildcards: we could say that 'foo bar
baz'
equals to "*foo bar baz*"
. Now you can
see why the partial phrase search is slow: due to the usage of two
asterisks in front and after the text, each and every title in the
database has to be looked up to determine whether it matches or
not. (There are currently no partial phrase indexes.)
The word truncation is supported via asterisk (*) wildcard
character. The wildcard instructs the search engine to match any
number of characters in that place. For example, to find records
that contain words muon, muons, muonic
etc, type:
The wildcard query works both in prefix and infix position. For
example, to get all the words that start by CERN-TH and
end by 31, type:
Note that the wildcard will be ignored if you try to apply it to
very short words, such as a*:
The wildcard character can be used also in the phrase searching
mode. For example, to find all the documents whose title starts by
"Neutrino mass", type:
Recall that we have introduced exact and partial phrase search
modes. Actually, a partial phrase search mode launches an exact
search enclosed within wildcards: we could say that 'foo bar
baz'
equals to "*foo bar baz*"
. Now you can
see why the partial phrase search is slow: due to the usage of two
asterisks in front and after the text, each and every title in the
database has to be looked up to determine whether it matches or
not. (There are currently no partial phrase indexes.)
The word truncation is supported via asterisk (*) wildcard
character. The wildcard instructs the search engine to match any
number of characters in that place. For example, to find records
that contain words muon, muons, muonic
etc, type:
The wildcard query works both in prefix and infix position. For
example, to get all the words that start by CERN-TH and
end by 31, type:
Note that the wildcard will be ignored if you try to apply it to
very short words, such as a*:
The wildcard character can be used also in the phrase searching
mode. For example, to find all the documents whose title starts by
"Neutrino mass", type:
Recall that we have introduced exact and partial phrase search
modes. Actually, a partial phrase search mode launches an exact
search enclosed within wildcards: we could say that 'foo bar
baz'
equals to "*foo bar baz*"
. Now you can
see why the partial phrase search is slow: due to the usage of two
asterisks in front and after the text, each and every title in the
database has to be looked up to determine whether it matches or
not. (There are currently no partial phrase indexes.)
The word truncation is supported via asterisk (*) wildcard
character. The wildcard instructs the search engine to match any
number of characters in that place. For example, to find records
that contain words muon, muons, muonic
etc, type:
The wildcard query works both in prefix and infix position. For
example, to get all the words that start by CERN-TH and
end by 31, type:
Note that the wildcard will be ignored if you try to apply it to
very short words, such as a*:
The wildcard character can be used also in the phrase searching
mode. For example, to find all the documents whose title starts by
"Neutrino mass", type:
Recall that we have introduced exact and partial phrase search
modes. Actually, a partial phrase search mode launches an exact
search enclosed within wildcards: we could say that 'foo bar
baz'
equals to "*foo bar baz*"
. Now you can
see why the partial phrase search is slow: due to the usage of two
asterisks in front and after the text, each and every title in the
database has to be looked up to determine whether it matches or
not. (There are currently no partial phrase indexes.)
The word truncation is supported via asterisk (*) wildcard
character. The wildcard instructs the search engine to match any
number of characters in that place. For example, to find records
that contain words muon, muons, muonic
etc, type:
The wildcard query works both in prefix and infix position. For
example, to get all the words that start by CERN-TH and
end by 31, type:
Note that the wildcard will be ignored if you try to apply it to
very short words, such as a*:
The wildcard character can be used also in the phrase searching
mode. For example, to find all the documents whose title starts by
"Neutrino mass", type:
Recall that we have introduced exact and partial phrase search
modes. Actually, a partial phrase search mode launches an exact
search enclosed within wildcards: we could say that 'foo bar
baz'
equals to "*foo bar baz*"
. Now you can
see why the partial phrase search is slow: due to the usage of two
asterisks in front and after the text, each and every title in the
database has to be looked up to determine whether it matches or
not. (There are currently no partial phrase indexes.)
The word truncation is supported via asterisk (*) wildcard
character. The wildcard instructs the search engine to match any
number of characters in that place. For example, to find records
that contain words muon, muons, muonic
etc, type:
The wildcard query works both in prefix and infix position. For
example, to get all the words that start by CERN-TH and
end by 31, type:
Note that the wildcard will be ignored if you try to apply it to
very short words, such as a*:
The wildcard character can be used also in the phrase searching
mode. For example, to find all the documents whose title starts by
"Neutrino mass", type:
Recall that we have introduced exact and partial phrase search
modes. Actually, a partial phrase search mode launches an exact
search enclosed within wildcards: we could say that 'foo bar
baz'
equals to "*foo bar baz*"
. Now you can
see why the partial phrase search is slow: due to the usage of two
asterisks in front and after the text, each and every title in the
database has to be looked up to determine whether it matches or
not. (There are currently no partial phrase indexes.)
The word truncation is supported via asterisk (*) wildcard
character. The wildcard instructs the search engine to match any
number of characters in that place. For example, to find records
that contain words muon, muons, muonic
etc, type:
The wildcard query works both in prefix and infix position. For
example, to get all the words that start by CERN-TH and
end by 31, type:
Note that the wildcard will be ignored if you try to apply it to
very short words, such as a*:
The wildcard character can be used also in the phrase searching
mode. For example, to find all the documents whose title starts by
"Neutrino mass", type:
Recall that we have introduced exact and partial phrase search
modes. Actually, a partial phrase search mode launches an exact
search enclosed within wildcards: we could say that 'foo bar
baz'
equals to "*foo bar baz*"
. Now you can
see why the partial phrase search is slow: due to the usage of two
asterisks in front and after the text, each and every title in the
database has to be looked up to determine whether it matches or
not. (There are currently no partial phrase indexes.)
The word truncation is supported via asterisk (*) wildcard
character. The wildcard instructs the search engine to match any
number of characters in that place. For example, to find records
that contain words muon, muons, muonic
etc, type:
The wildcard query works both in prefix and infix position. For
example, to get all the words that start by CERN-TH and
end by 31, type:
Note that the wildcard will be ignored if you try to apply it to
very short words, such as a*:
The wildcard character can be used also in the phrase searching
mode. For example, to find all the documents whose title starts by
"Neutrino mass", type:
Recall that we have introduced exact and partial phrase search
modes. Actually, a partial phrase search mode launches an exact
search enclosed within wildcards: we could say that 'foo bar
baz'
equals to "*foo bar baz*"
. Now you can
see why the partial phrase search is slow: due to the usage of two
asterisks in front and after the text, each and every title in the
database has to be looked up to determine whether it matches or
not. (There are currently no partial phrase indexes.)
The word truncation is supported via asterisk (*) wildcard
character. The wildcard instructs the search engine to match any
number of characters in that place. For example, to find records
that contain words muon, muons, muonic
etc, type:
The wildcard query works both in prefix and infix position. For
example, to get all the words that start by CERN-TH and
end by 31, type:
Note that the wildcard will be ignored if you try to apply it to
very short words, such as a*:
The wildcard character can be used also in the phrase searching
mode. For example, to find all the documents whose title starts by
"Neutrino mass", type:
Recall that we have introduced exact and partial phrase search
modes. Actually, a partial phrase search mode launches an exact
search enclosed within wildcards: we could say that 'foo bar
baz'
equals to "*foo bar baz*"
. Now you can
see why the partial phrase search is slow: due to the usage of two
asterisks in front and after the text, each and every title in the
database has to be looked up to determine whether it matches or
not. (There are currently no partial phrase indexes.)
The word truncation is supported via asterisk (*) wildcard
character. The wildcard instructs the search engine to match any
number of characters in that place. For example, to find records
that contain words muon, muons, muonic
etc, type:
The wildcard query works both in prefix and infix position. For
example, to get all the words that start by CERN-TH and
end by 31, type:
Note that the wildcard will be ignored if you try to apply it to
very short words, such as a*:
The wildcard character can be used also in the phrase searching
mode. For example, to find all the documents whose title starts by
"Neutrino mass", type:
Recall that we have introduced exact and partial phrase search
modes. Actually, a partial phrase search mode launches an exact
search enclosed within wildcards: we could say that 'foo bar
baz'
equals to "*foo bar baz*"
. Now you can
see why the partial phrase search is slow: due to the usage of two
asterisks in front and after the text, each and every title in the
database has to be looked up to determine whether it matches or
not. (There are currently no partial phrase indexes.)
The word truncation is supported via asterisk (*) wildcard
character. The wildcard instructs the search engine to match any
number of characters in that place. For example, to find records
that contain words muon, muons, muonic
etc, type:
The wildcard query works both in prefix and infix position. For
example, to get all the words that start by CERN-TH and
end by 31, type:
Note that the wildcard will be ignored if you try to apply it to
very short words, such as a*:
The wildcard character can be used also in the phrase searching
mode. For example, to find all the documents whose title starts by
"Neutrino mass", type:
Recall that we have introduced exact and partial phrase search
modes. Actually, a partial phrase search mode launches an exact
search enclosed within wildcards: we could say that 'foo bar
baz'
equals to "*foo bar baz*"
. Now you can
see why the partial phrase search is slow: due to the usage of two
asterisks in front and after the text, each and every title in the
database has to be looked up to determine whether it matches or
not. (There are currently no partial phrase indexes.)
The word truncation is supported via asterisk (*) wildcard
character. The wildcard instructs the search engine to match any
number of characters in that place. For example, to find records
that contain words muon, muons, muonic
etc, type:
The wildcard query works both in prefix and infix position. For
example, to get all the words that start by CERN-TH and
end by 31, type:
Note that the wildcard will be ignored if you try to apply it to
very short words, such as a*:
The wildcard character can be used also in the phrase searching
mode. For example, to find all the documents whose title starts by
"Neutrino mass", type:
Recall that we have introduced exact and partial phrase search
modes. Actually, a partial phrase search mode launches an exact
search enclosed within wildcards: we could say that 'foo bar
baz'
equals to "*foo bar baz*"
. Now you can
see why the partial phrase search is slow: due to the usage of two
asterisks in front and after the text, each and every title in the
database has to be looked up to determine whether it matches or
not. (There are currently no partial phrase indexes.)
El truncamiento de una palabra se efectua a través del uso del
asterisco (*). Este comodín indica al motor de búsqueda que
retorne cualquier número de carácteres en su lugar. Por ejemplo,
para recuperar registros que contengan las palabras
muon, muonic, muons
etc, debemos escribir:
La búsqueda por comodín puede utilizarse tanto en posición de
prefijo como de sufijo. Por ejemplo, para recuperar todas las
palabras que comiencen por CERN-TH y acaben con
31, debemos escribir:
Obsérvese que el comodín se ignorará si tratamos de utilizarlo en
palabras demasiado cortas, como por ejemplo a*:
El carácter comodín también puede usarse en el modo de búsqueda por
frase. Por ejemplo, para recuperar todos los documentos cuyo título
comience con "Neutrino mass", debemos escribir:
Recordamos que en esta búsqueda hemos introducido las formas de
'frase exacta' y 'parte de la frase'. En realidad, el modo de
búsqueda de 'parte de la frase' lanzará una búsqueda exacta sin
necesidad de utilizar los comodines: tanto podemos utilizar
'foo bar baz'
como "*foo bar baz*"
.
Esto ayuda a comprender porqué la búsqueda de
palabras en una parte de la frase es lenta: debido al uso de dos
asteriscos delante y detrás del texto, todos y cada de los
registros de la base de datos son comprobados para determinar si se
corresponden a la búsqueda o no. Actualmente no hay ningún índice
de búsqueda que indexe partes de frase.
El truncament d’una paraula es realitza a través de l’ús del símbol
asterisc (*). Aquest comodí indica al motor de cerca que retorni
qualsevol número de caràcters en el seu lloc. Per exemple, per
recuperar registres que continguin les paraules astronomia,
astrònoms, astronòmics etc, cal escriure:
La cerca por comodí pot utilitzar-se tant en posició de prefix com
de sufix. Per exemple, per recuperar totes les paraules que
comencin per CERN-TH i acabin amb 31, cal
escriure:
Notis que el comodí s’ignora si es tracta d’utilitzar-lo amb
paraules massa curtes, com per exemple a*:
El caràcter comodí també pot utilitzar-se al mode de cerca per
frase. Per exemple, per recuperar tots els documents el títol dels
quals comenci per "Neutrino mass", cal escriure:
Recordem que a aquesta cerca hem introduït les formes de 'frase
exacta' i 'part de la frase'. En realitat, el mode de cerca per
'part de la frase' ens llençarà una cerca exacta sense necessitat
de fer servir els comodins: tant podem utilitzar 'foo bar
baz'
com "*foo bar baz*"
.
Això ajuda a comprendre perquè la cerca de
paraules a una part de la frase és lenta: degut a l’ús de dos
asteriscs davant i darrera del text, tots i cadascun dels registres
de la base de dades es comproven per determinar si es corresponen o
no amb la cerca introduïda. Actualment no hi ha cap índex de cerca
que indexi parts de frase.
Searching within various bibliograpic fields (such as title,
author) is supported via Google's "site:"
like syntax.
If a search term is preceded by a field name and a colon, then the
term is searched for inside this field only. For example, to find
documents containing the word ellis within author index,
type:
To select documents written by Ellis that contain words
like muon, muons, muonic within title,
type:
To select documents written by the NA60 experiment from
the year 2001, type:
The most common fields you may want to use are
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
Searching within various bibliograpic fields (such as title,
author) is supported via Google's "site:"
like syntax.
If a search term is preceded by a field name and a colon, then the
term is searched for inside this field only. For example, to find
documents containing the word ellis within author index,
type:
To select documents written by Ellis that contain words
like muon, muons, muonic within title,
type:
To select documents written by the NA60 experiment from
the year 2001, type:
The most common fields you may want to use are
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
Searching within various bibliograpic fields (such as title,
author) is supported via Google's "site:"
like syntax.
If a search term is preceded by a field name and a colon, then the
term is searched for inside this field only. For example, to find
documents containing the word ellis within author index,
type:
To select documents written by Ellis that contain words
like muon, muons, muonic within title,
type:
To select documents written by the NA60 experiment from
the year 2001, type:
The most common fields you may want to use are
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
Searching within various bibliograpic fields (such as title,
author) is supported via Google's "site:"
like syntax.
If a search term is preceded by a field name and a colon, then the
term is searched for inside this field only. For example, to find
documents containing the word ellis within author index,
type:
To select documents written by Ellis that contain words
like muon, muons, muonic within title,
type:
To select documents written by the NA60 experiment from
the year 2001, type:
The most common fields you may want to use are
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
Searching within various bibliograpic fields (such as title,
author) is supported via Google's "site:"
like syntax.
If a search term is preceded by a field name and a colon, then the
term is searched for inside this field only. For example, to find
documents containing the word ellis within author index,
type:
To select documents written by Ellis that contain words
like muon, muons, muonic within title,
type:
To select documents written by the NA60 experiment from
the year 2001, type:
The most common fields you may want to use are
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
Searching within various bibliograpic fields (such as title,
author) is supported via Google's "site:"
like syntax.
If a search term is preceded by a field name and a colon, then the
term is searched for inside this field only. For example, to find
documents containing the word ellis within author index,
type:
To select documents written by Ellis that contain words
like muon, muons, muonic within title,
type:
To select documents written by the NA60 experiment from
the year 2001, type:
The most common fields you may want to use are
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
Searching within various bibliograpic fields (such as title,
author) is supported via Google's "site:"
like syntax.
If a search term is preceded by a field name and a colon, then the
term is searched for inside this field only. For example, to find
documents containing the word ellis within author index,
type:
To select documents written by Ellis that contain words
like muon, muons, muonic within title,
type:
To select documents written by the NA60 experiment from
the year 2001, type:
The most common fields you may want to use are
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
Searching within various bibliograpic fields (such as title,
author) is supported via Google's "site:"
like syntax.
If a search term is preceded by a field name and a colon, then the
term is searched for inside this field only. For example, to find
documents containing the word ellis within author index,
type:
To select documents written by Ellis that contain words
like muon, muons, muonic within title,
type:
To select documents written by the NA60 experiment from
the year 2001, type:
The most common fields you may want to use are
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
Searching within various bibliograpic fields (such as title,
author) is supported via Google's "site:"
like syntax.
If a search term is preceded by a field name and a colon, then the
term is searched for inside this field only. For example, to find
documents containing the word ellis within author index,
type:
To select documents written by Ellis that contain words
like muon, muons, muonic within title,
type:
To select documents written by the NA60 experiment from
the year 2001, type:
The most common fields you may want to use are
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
Searching within various bibliograpic fields (such as title,
author) is supported via Google's "site:"
like syntax.
If a search term is preceded by a field name and a colon, then the
term is searched for inside this field only. For example, to find
documents containing the word ellis within author index,
type:
To select documents written by Ellis that contain words
like muon, muons, muonic within title,
type:
To select documents written by the NA60 experiment from
the year 2001, type:
The most common fields you may want to use are
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
Searching within various bibliograpic fields (such as title,
author) is supported via Google's "site:"
like syntax.
If a search term is preceded by a field name and a colon, then the
term is searched for inside this field only. For example, to find
documents containing the word ellis within author index,
type:
To select documents written by Ellis that contain words
like muon, muons, muonic within title,
type:
To select documents written by the NA60 experiment from
the year 2001, type:
The most common fields you may want to use are
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
Searching within various bibliograpic fields (such as title,
author) is supported via Google's "site:"
like syntax.
If a search term is preceded by a field name and a colon, then the
term is searched for inside this field only. For example, to find
documents containing the word ellis within author index,
type:
To select documents written by Ellis that contain words
like muon, muons, muonic within title,
type:
To select documents written by the NA60 experiment from
the year 2001, type:
The most common fields you may want to use are
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
Searching within various bibliograpic fields (such as title,
author) is supported via Google's "site:"
like syntax.
If a search term is preceded by a field name and a colon, then the
term is searched for inside this field only. For example, to find
documents containing the word ellis within author index,
type:
To select documents written by Ellis that contain words
like muon, muons, muonic within title,
type:
To select documents written by the NA60 experiment from
the year 2001, type:
The most common fields you may want to use are
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
Searching within various bibliograpic fields (such as title,
author) is supported via Google's "site:"
like syntax.
If a search term is preceded by a field name and a colon, then the
term is searched for inside this field only. For example, to find
documents containing the word ellis within author index,
type:
To select documents written by Ellis that contain words
like muon, muons, muonic within title,
type:
To select documents written by the NA60 experiment from
the year 2001, type:
The most common fields you may want to use are
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
Searching within various bibliograpic fields (such as title,
author) is supported via Google's "site:"
like syntax.
If a search term is preceded by a field name and a colon, then the
term is searched for inside this field only. For example, to find
documents containing the word ellis within author index,
type:
To select documents written by Ellis that contain words
like muon, muons, muonic within title,
type:
To select documents written by the NA60 experiment from
the year 2001, type:
The most common fields you may want to use are
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
Searching within various bibliograpic fields (such as title,
author) is supported via Google's "site:"
like syntax.
If a search term is preceded by a field name and a colon, then the
term is searched for inside this field only. For example, to find
documents containing the word ellis within author index,
type:
To select documents written by Ellis that contain words
like muon, muons, muonic within title,
type:
To select documents written by the NA60 experiment from
the year 2001, type:
The most common fields you may want to use are
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
Searching within various bibliograpic fields (such as title,
author) is supported via Google's "site:"
like syntax.
If a search term is preceded by a field name and a colon, then the
term is searched for inside this field only. For example, to find
documents containing the word ellis within author index,
type:
To select documents written by Ellis that contain words
like muon, muons, muonic within title,
type:
To select documents written by the NA60 experiment from
the year 2001, type:
The most common fields you may want to use are
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
Searching within various bibliograpic fields (such as title,
author) is supported via Google's "site:"
like syntax.
If a search term is preceded by a field name and a colon, then the
term is searched for inside this field only. For example, to find
documents containing the word ellis within author index,
type:
To select documents written by Ellis that contain words
like muon, muons, muonic within title,
type:
To select documents written by the NA60 experiment from
the year 2001, type:
The most common fields you may want to use are
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
La búsqueda realizada utilizando varios campos bibliográficos
(tales como título, autor) se realiza a través de una sintaxis
similar a la que utiliza Google en sus búsquedas tipo
"site:"
. Si un término de búsqueda es precedido por
un nombre de campo seguido por dos puntos este término se buscará
únicamente en el campo especificado. Por ejemplo, para recuperar
documentos que contienen la palabra ellis dentro del
índice de autores, debemos escribir:
Para recuperar documentos escritos por Ellis que contengan
palabras tales como muon, muonic,
muons dentro del título, debemos escribir:
Para recuperar documentos escritos por el experimento NA60
del año 2001, debemos escribir:
Los campos de uso más común son los siguientes:
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
La cerca realitzada utilitzant diversos camps bibliogràfics (Tals
com títol, autor) es realitza a través d’una sintaxi similar a
l’emprada per Google en les Seves cerques tipus "site:"
.
Si un terme de cerca es precedit per un nom de camp seguit per dos
punts aquest terme es cerca únicament dins el camp especificat. Per
exemple, per recuperar documents que contenen la paraula
ellis dins l’índex d’autors, cal escriure:
Per recuperar documents escrits per Ellis que continguin
paraules tals com muon, muonic,
muons dins el títol, cal escriure:
Per recuperar documents escrits per l’experiment NA60 de l’any 2001, cal escriure:
Els camps d’ús comú amb aquesta tècnica són:
author
, title
,
reportnumber
, abstract
,
keyword
, year
, experiment
,
fulltext
, and reference
.
The regular expression searching mode is mostly for the power users
acquainted with the traditional Unix/POSIX regexp syntax. In the
Simple Search interface you can trigger it by using slashes instead of
quotes:
while in the Advanced Search interface you can select the matching
type explicitely by using the selection box menu. The above example
will find all the titles that start by the letter E, followed
by any number of any characters, and end by the letter s.
The regular expression searching mode is mostly for the power users
acquainted with the traditional Unix/POSIX regexp syntax. In the
Simple Search interface you can trigger it by using slashes instead of
quotes:
while in the Advanced Search interface you can select the matching
type explicitely by using the selection box menu. The above example
will find all the titles that start by the letter E, followed
by any number of any characters, and end by the letter s.
The regular expression searching mode is mostly for the power users
acquainted with the traditional Unix/POSIX regexp syntax. In the
Simple Search interface you can trigger it by using slashes instead of
quotes:
while in the Advanced Search interface you can select the matching
type explicitely by using the selection box menu. The above example
will find all the titles that start by the letter E, followed
by any number of any characters, and end by the letter s.
The regular expression searching mode is mostly for the power users
acquainted with the traditional Unix/POSIX regexp syntax. In the
Simple Search interface you can trigger it by using slashes instead of
quotes:
while in the Advanced Search interface you can select the matching
type explicitely by using the selection box menu. The above example
will find all the titles that start by the letter E, followed
by any number of any characters, and end by the letter s.
The regular expression searching mode is mostly for the power users
acquainted with the traditional Unix/POSIX regexp syntax. In the
Simple Search interface you can trigger it by using slashes instead of
quotes:
while in the Advanced Search interface you can select the matching
type explicitely by using the selection box menu. The above example
will find all the titles that start by the letter E, followed
by any number of any characters, and end by the letter s.
The regular expression searching mode is mostly for the power users
acquainted with the traditional Unix/POSIX regexp syntax. In the
Simple Search interface you can trigger it by using slashes instead of
quotes:
while in the Advanced Search interface you can select the matching
type explicitely by using the selection box menu. The above example
will find all the titles that start by the letter E, followed
by any number of any characters, and end by the letter s.
The regular expression searching mode is mostly for the power users
acquainted with the traditional Unix/POSIX regexp syntax. In the
Simple Search interface you can trigger it by using slashes instead of
quotes:
while in the Advanced Search interface you can select the matching
type explicitely by using the selection box menu. The above example
will find all the titles that start by the letter E, followed
by any number of any characters, and end by the letter s.
The regular expression searching mode is mostly for the power users
acquainted with the traditional Unix/POSIX regexp syntax. In the
Simple Search interface you can trigger it by using slashes instead of
quotes:
while in the Advanced Search interface you can select the matching
type explicitely by using the selection box menu. The above example
will find all the titles that start by the letter E, followed
by any number of any characters, and end by the letter s.
The regular expression searching mode is mostly for the power users
acquainted with the traditional Unix/POSIX regexp syntax. In the
Simple Search interface you can trigger it by using slashes instead of
quotes:
while in the Advanced Search interface you can select the matching
type explicitely by using the selection box menu. The above example
will find all the titles that start by the letter E, followed
by any number of any characters, and end by the letter s.
The regular expression searching mode is mostly for the power users
acquainted with the traditional Unix/POSIX regexp syntax. In the
Simple Search interface you can trigger it by using slashes instead of
quotes:
while in the Advanced Search interface you can select the matching
type explicitely by using the selection box menu. The above example
will find all the titles that start by the letter E, followed
by any number of any characters, and end by the letter s.
The regular expression searching mode is mostly for the power users
acquainted with the traditional Unix/POSIX regexp syntax. In the
Simple Search interface you can trigger it by using slashes instead of
quotes:
while in the Advanced Search interface you can select the matching
type explicitely by using the selection box menu. The above example
will find all the titles that start by the letter E, followed
by any number of any characters, and end by the letter s.
The regular expression searching mode is mostly for the power users
acquainted with the traditional Unix/POSIX regexp syntax. In the
Simple Search interface you can trigger it by using slashes instead of
quotes:
while in the Advanced Search interface you can select the matching
type explicitely by using the selection box menu. The above example
will find all the titles that start by the letter E, followed
by any number of any characters, and end by the letter s.
The regular expression searching mode is mostly for the power users
acquainted with the traditional Unix/POSIX regexp syntax. In the
Simple Search interface you can trigger it by using slashes instead of
quotes:
while in the Advanced Search interface you can select the matching
type explicitely by using the selection box menu. The above example
will find all the titles that start by the letter E, followed
by any number of any characters, and end by the letter s.
The regular expression searching mode is mostly for the power users
acquainted with the traditional Unix/POSIX regexp syntax. In the
Simple Search interface you can trigger it by using slashes instead of
quotes:
while in the Advanced Search interface you can select the matching
type explicitely by using the selection box menu. The above example
will find all the titles that start by the letter E, followed
by any number of any characters, and end by the letter s.
The regular expression searching mode is mostly for the power users
acquainted with the traditional Unix/POSIX regexp syntax. In the
Simple Search interface you can trigger it by using slashes instead of
quotes:
while in the Advanced Search interface you can select the matching
type explicitely by using the selection box menu. The above example
will find all the titles that start by the letter E, followed
by any number of any characters, and end by the letter s.
The regular expression searching mode is mostly for the power users
acquainted with the traditional Unix/POSIX regexp syntax. In the
Simple Search interface you can trigger it by using slashes instead of
quotes:
while in the Advanced Search interface you can select the matching
type explicitely by using the selection box menu. The above example
will find all the titles that start by the letter E, followed
by any number of any characters, and end by the letter s.
The regular expression searching mode is mostly for the power users
acquainted with the traditional Unix/POSIX regexp syntax. In the
Simple Search interface you can trigger it by using slashes instead of
quotes:
while in the Advanced Search interface you can select the matching
type explicitely by using the selection box menu. The above example
will find all the titles that start by the letter E, followed
by any number of any characters, and end by the letter s.
The regular expression searching mode is mostly for the power users
acquainted with the traditional Unix/POSIX regexp syntax. In the
Simple Search interface you can trigger it by using slashes instead of
quotes:
while in the Advanced Search interface you can select the matching
type explicitely by using the selection box menu. The above example
will find all the titles that start by the letter E, followed
by any number of any characters, and end by the letter s.
El uso del modo de búsqueda por expresión regular está dirigida
sobre todo a usuarios avanzados que conocen la sintaxis tradicional
Unix/POSIX regexp. En el interfaz de consulta simple se puede forzar
este modo usando barras inclinadas en lugar de comillas:
mientras que en el modo de búsqueda Avanzado se puede seleccionar
explícitamente este modo de búsqueda seleccionandolo en el menú
desplegable. En el ejemplo anterior se recuperarían todos los títulos
que comienzan por la letra E, seguida de cualquier número o
cualquier carácter, y que terminen por la letra s.
L’ ús del mode de cerca per expressió regular està dirigida
sobretot a usuaris avançats que coneixen la sintaxi tradicional
Unix/POSIX regexp. A l’interficie de consulta simple es pot forçar
aquest mode utilitzant les Barres inclinades enlloc de comentes:
Al mode de cerca Avançada es pot seleccionar explícitament aquest mode
de cerca seleccionant-lo al menú desplegable. a l’exemple anterior es
recuperarien tots els títols que comencen per la lletra E,
seguida de qualsevol número o qualsevol caràcter, i que acabin per la
lletra s.
Another example could be an author search for an author expressed
in the database as either Ellis, J or Ellis, John:
Another example could be an author search for an author expressed
in the database as either Ellis, J or Ellis, John:
Another example could be an author search for an author expressed
in the database as either Ellis, J or Ellis, John:
Another example could be an author search for an author expressed
in the database as either Ellis, J or Ellis, John:
Another example could be an author search for an author expressed
in the database as either Ellis, J or Ellis, John:
Another example could be an author search for an author expressed
in the database as either Ellis, J or Ellis, John:
Another example could be an author search for an author expressed
in the database as either Ellis, J or Ellis, John:
Another example could be an author search for an author expressed
in the database as either Ellis, J or Ellis, John:
Another example could be an author search for an author expressed
in the database as either Ellis, J or Ellis, John:
Another example could be an author search for an author expressed
in the database as either Ellis, J or Ellis, John:
Another example could be an author search for an author expressed
in the database as either Ellis, J or Ellis, John:
Another example could be an author search for an author expressed
in the database as either Ellis, J or Ellis, John:
Another example could be an author search for an author expressed
in the database as either Ellis, J or Ellis, John:
Another example could be an author search for an author expressed
in the database as either Ellis, J or Ellis, John:
Another example could be an author search for an author expressed
in the database as either Ellis, J or Ellis, John:
Another example could be an author search for an author expressed
in the database as either Ellis, J or Ellis, John:
Another example could be an author search for an author expressed
in the database as either Ellis, J or Ellis, John:
Another example could be an author search for an author expressed
in the database as either Ellis, J or Ellis, John:
Otro ejemplo similar es el de la búsqueda por autor de un autor que
se ha introducido en la base de datos como Ellis, J o bien
como Ellis, John:
Un altre exemple similar és el de la cerca per autor d’un autor que
ha estat introduït a la base de dades com Ellis, J o bé com
Ellis, John:
The regular expression search enables you to formulate very
specific word proximity queries. For example, let us find all titles
containing words dense and matter that are separated
by at most one word that doesn't contain the letter l:
The regular expression search enables you to formulate very
specific word proximity queries. For example, let us find all titles
containing words dense and matter that are separated
by at most one word that doesn't contain the letter l:
The regular expression search enables you to formulate very
specific word proximity queries. For example, let us find all titles
containing words dense and matter that are separated
by at most one word that doesn't contain the letter l:
The regular expression search enables you to formulate very
specific word proximity queries. For example, let us find all titles
containing words dense and matter that are separated
by at most one word that doesn't contain the letter l:
The regular expression search enables you to formulate very
specific word proximity queries. For example, let us find all titles
containing words dense and matter that are separated
by at most one word that doesn't contain the letter l:
The regular expression search enables you to formulate very
specific word proximity queries. For example, let us find all titles
containing words dense and matter that are separated
by at most one word that doesn't contain the letter l:
The regular expression search enables you to formulate very
specific word proximity queries. For example, let us find all titles
containing words dense and matter that are separated
by at most one word that doesn't contain the letter l:
The regular expression search enables you to formulate very
specific word proximity queries. For example, let us find all titles
containing words dense and matter that are separated
by at most one word that doesn't contain the letter l:
The regular expression search enables you to formulate very
specific word proximity queries. For example, let us find all titles
containing words dense and matter that are separated
by at most one word that doesn't contain the letter l:
The regular expression search enables you to formulate very
specific word proximity queries. For example, let us find all titles
containing words dense and matter that are separated
by at most one word that doesn't contain the letter l:
The regular expression search enables you to formulate very
specific word proximity queries. For example, let us find all titles
containing words dense and matter that are separated
by at most one word that doesn't contain the letter l:
The regular expression search enables you to formulate very
specific word proximity queries. For example, let us find all titles
containing words dense and matter that are separated
by at most one word that doesn't contain the letter l:
The regular expression search enables you to formulate very
specific word proximity queries. For example, let us find all titles
containing words dense and matter that are separated
by at most one word that doesn't contain the letter l:
The regular expression search enables you to formulate very
specific word proximity queries. For example, let us find all titles
containing words dense and matter that are separated
by at most one word that doesn't contain the letter l:
The regular expression search enables you to formulate very
specific word proximity queries. For example, let us find all titles
containing words dense and matter that are separated
by at most one word that doesn't contain the letter l:
The regular expression search enables you to formulate very
specific word proximity queries. For example, let us find all titles
containing words dense and matter that are separated
by at most one word that doesn't contain the letter l:
The regular expression search enables you to formulate very
specific word proximity queries. For example, let us find all titles
containing words dense and matter that are separated
by at most one word that doesn't contain the letter l:
The regular expression search enables you to formulate very
specific word proximity queries. For example, let us find all titles
containing words dense and matter that are separated
by at most one word that doesn't contain the letter l:
La búsqueda por expresión regular permite formular consultas de
palabras muy específicas por su proximidad. Por ejemplo, permite
recuperar registros cuyos títulos contienen las palabras
dense y matter y que estén separadas al menos por
una palabra que no contenga la letra l:
La cerca per expressió regular permet formular consultes de
paraules Molt específiques per proximitat. Per exemple, permet
recuperar registres Els títols dels quals contenen les paraules
dense i matter i que estiguin separades, al menys,
per una paraula que no contingui la lletra l:
Note that you can also use character intervals such as
[a-k]
and occurrence counts such as {3}
.
For example, let us find all preprints that do not follow the year
cataloguing policy, that is YYYY to denote year, optionally
followed by ? or by another -YYYY:
You can use also character classes such [:alnum:]
, so
that the above query is equivalent to:
Note that you can also use character intervals such as
[a-k]
and occurrence counts such as {3}
.
For example, let us find all preprints that do not follow the year
cataloguing policy, that is YYYY to denote year, optionally
followed by ? or by another -YYYY:
You can use also character classes such [:alnum:]
, so
that the above query is equivalent to:
Note that you can also use character intervals such as
[a-k]
and occurrence counts such as {3}
.
For example, let us find all preprints that do not follow the year
cataloguing policy, that is YYYY to denote year, optionally
followed by ? or by another -YYYY:
You can use also character classes such [:alnum:]
, so
that the above query is equivalent to:
Note that you can also use character intervals such as
[a-k]
and occurrence counts such as {3}
.
For example, let us find all preprints that do not follow the year
cataloguing policy, that is YYYY to denote year, optionally
followed by ? or by another -YYYY:
You can use also character classes such [:alnum:]
, so
that the above query is equivalent to:
Note that you can also use character intervals such as
[a-k]
and occurrence counts such as {3}
.
For example, let us find all preprints that do not follow the year
cataloguing policy, that is YYYY to denote year, optionally
followed by ? or by another -YYYY:
You can use also character classes such [:alnum:]
, so
that the above query is equivalent to:
Note that you can also use character intervals such as
[a-k]
and occurrence counts such as {3}
.
For example, let us find all preprints that do not follow the year
cataloguing policy, that is YYYY to denote year, optionally
followed by ? or by another -YYYY:
You can use also character classes such [:alnum:]
, so
that the above query is equivalent to:
Note that you can also use character intervals such as
[a-k]
and occurrence counts such as {3}
.
For example, let us find all preprints that do not follow the year
cataloguing policy, that is YYYY to denote year, optionally
followed by ? or by another -YYYY:
You can use also character classes such [:alnum:]
, so
that the above query is equivalent to:
Note that you can also use character intervals such as
[a-k]
and occurrence counts such as {3}
.
For example, let us find all preprints that do not follow the year
cataloguing policy, that is YYYY to denote year, optionally
followed by ? or by another -YYYY:
You can use also character classes such [:alnum:]
, so
that the above query is equivalent to:
Note that you can also use character intervals such as
[a-k]
and occurrence counts such as {3}
.
For example, let us find all preprints that do not follow the year
cataloguing policy, that is YYYY to denote year, optionally
followed by ? or by another -YYYY:
You can use also character classes such [:alnum:]
, so
that the above query is equivalent to:
Note that you can also use character intervals such as
[a-k]
and occurrence counts such as {3}
.
For example, let us find all preprints that do not follow the year
cataloguing policy, that is YYYY to denote year, optionally
followed by ? or by another -YYYY:
You can use also character classes such [:alnum:]
, so
that the above query is equivalent to:
Note that you can also use character intervals such as
[a-k]
and occurrence counts such as {3}
.
For example, let us find all preprints that do not follow the year
cataloguing policy, that is YYYY to denote year, optionally
followed by ? or by another -YYYY:
You can use also character classes such [:alnum:]
, so
that the above query is equivalent to:
Note that you can also use character intervals such as
[a-k]
and occurrence counts such as {3}
.
For example, let us find all preprints that do not follow the year
cataloguing policy, that is YYYY to denote year, optionally
followed by ? or by another -YYYY:
You can use also character classes such [:alnum:]
, so
that the above query is equivalent to:
Note that you can also use character intervals such as
[a-k]
and occurrence counts such as {3}
.
For example, let us find all preprints that do not follow the year
cataloguing policy, that is YYYY to denote year, optionally
followed by ? or by another -YYYY:
You can use also character classes such [:alnum:]
, so
that the above query is equivalent to:
Note that you can also use character intervals such as
[a-k]
and occurrence counts such as {3}
.
For example, let us find all preprints that do not follow the year
cataloguing policy, that is YYYY to denote year, optionally
followed by ? or by another -YYYY:
You can use also character classes such [:alnum:]
, so
that the above query is equivalent to:
Note that you can also use character intervals such as
[a-k]
and occurrence counts such as {3}
.
For example, let us find all preprints that do not follow the year
cataloguing policy, that is YYYY to denote year, optionally
followed by ? or by another -YYYY:
You can use also character classes such [:alnum:]
, so
that the above query is equivalent to:
Note that you can also use character intervals such as
[a-k]
and occurrence counts such as {3}
.
For example, let us find all preprints that do not follow the year
cataloguing policy, that is YYYY to denote year, optionally
followed by ? or by another -YYYY:
You can use also character classes such [:alnum:]
, so
that the above query is equivalent to:
Note that you can also use character intervals such as
[a-k]
and occurrence counts such as {3}
.
For example, let us find all preprints that do not follow the year
cataloguing policy, that is YYYY to denote year, optionally
followed by ? or by another -YYYY:
You can use also character classes such [:alnum:]
, so
that the above query is equivalent to:
Note that you can also use character intervals such as
[a-k]
and occurrence counts such as {3}
.
For example, let us find all preprints that do not follow the year
cataloguing policy, that is YYYY to denote year, optionally
followed by ? or by another -YYYY:
You can use also character classes such [:alnum:]
, so
that the above query is equivalent to:
Obsérvese que también pueden utilizarse carácteres de intervalo
como [a-k]
y contadores de ocurrencia como
{3}
. Por ejemplo, podemos recuperar todos los pre-prints
que no se corresponden con la política de catalogación AAAA
para describir los años, opcionalmente seguida por ? o por
otro -AAAA:
También pueden utilizarse otras clases de caracteres como
[:alnum:]
, el cual en el ejemplo anterior sería
equivalente a:
Observis que també poden emprar-se caràcters d’interval com
[a-k]
i contadors de concurrència com {3}
.
Per ejemple, podem recuperar tots els pre-prints que no es
corresponguin amb la política de catalogació AAAA per
descriure anys, opcionalment seguida per ? o per altre
-AAAA:
També poden emprar-se altres classe de caràcters com
[:alnum:]
, que a l’exemple anterior seria
equivalent a:
To learn more about POSIX regular expressions, please consult the
Wikipedia
regexp article and the MySQL regexp
documentation.
To learn more about POSIX regular expressions, please consult the
Wikipedia
regexp article and the MySQL regexp
documentation.
To learn more about POSIX regular expressions, please consult the
Wikipedia
regexp article and the MySQL regexp
documentation.
To learn more about POSIX regular expressions, please consult the
Wikipedia
regexp article and the MySQL regexp
documentation.
To learn more about POSIX regular expressions, please consult the
Wikipedia
regexp article and the MySQL regexp
documentation.
To learn more about POSIX regular expressions, please consult the
Wikipedia
regexp article and the MySQL regexp
documentation.
To learn more about POSIX regular expressions, please consult the
Wikipedia
regexp article and the MySQL regexp
documentation.
To learn more about POSIX regular expressions, please consult the
Wikipedia
regexp article and the MySQL regexp
documentation.
To learn more about POSIX regular expressions, please consult the
Wikipedia
regexp article and the MySQL regexp
documentation.
To learn more about POSIX regular expressions, please consult the
Wikipedia
regexp article and the MySQL regexp
documentation.
To learn more about POSIX regular expressions, please consult the
Wikipedia
regexp article and the MySQL regexp
documentation.
To learn more about POSIX regular expressions, please consult the
Wikipedia
regexp article and the MySQL regexp
documentation.
To learn more about POSIX regular expressions, please consult the
Wikipedia
regexp article and the MySQL regexp
documentation.
To learn more about POSIX regular expressions, please consult the
Wikipedia
regexp article and the MySQL regexp
documentation.
To learn more about POSIX regular expressions, please consult the
Wikipedia
regexp article and the MySQL regexp
documentation.
To learn more about POSIX regular expressions, please consult the
Wikipedia
regexp article and the MySQL regexp
documentation.
To learn more about POSIX regular expressions, please consult the
Wikipedia
regexp article and the MySQL regexp
documentation.
To learn more about POSIX regular expressions, please consult the
Wikipedia
regexp article and the MySQL regexp
documentation.
Para conocer más acerca de las expresiones regulares POSIX, se
recomienda la consulta de Wikipedia
regexp article y MySQL regexp
documentation.
Per conèixer més sobre les expressions regulars POSIX, es recomana
la Consulta de Wikipedia
regexp article i MySQL regexp
documentation.
The span query is provided via a ->
sign. For
example, to search for all documents on muon decay published
between 1983 and 1992, type:
To find all documents by authors with names ranging from Ellis,
J to Ellis, Qqq, type:
The span query is provided via a ->
sign. For
example, to search for all documents on muon decay published
between 1983 and 1992, type:
To find all documents by authors with names ranging from Ellis,
J to Ellis, Qqq, type:
The span query is provided via a ->
sign. For
example, to search for all documents on muon decay published
between 1983 and 1992, type:
To find all documents by authors with names ranging from Ellis,
J to Ellis, Qqq, type:
The span query is provided via a ->
sign. For
example, to search for all documents on muon decay published
between 1983 and 1992, type:
To find all documents by authors with names ranging from Ellis,
J to Ellis, Qqq, type:
The span query is provided via a ->
sign. For
example, to search for all documents on muon decay published
between 1983 and 1992, type:
To find all documents by authors with names ranging from Ellis,
J to Ellis, Qqq, type:
The span query is provided via a ->
sign. For
example, to search for all documents on muon decay published
between 1983 and 1992, type:
To find all documents by authors with names ranging from Ellis,
J to Ellis, Qqq, type:
The span query is provided via a ->
sign. For
example, to search for all documents on muon decay published
between 1983 and 1992, type:
To find all documents by authors with names ranging from Ellis,
J to Ellis, Qqq, type:
The span query is provided via a ->
sign. For
example, to search for all documents on muon decay published
between 1983 and 1992, type:
To find all documents by authors with names ranging from Ellis,
J to Ellis, Qqq, type:
The span query is provided via a ->
sign. For
example, to search for all documents on muon decay published
between 1983 and 1992, type:
To find all documents by authors with names ranging from Ellis,
J to Ellis, Qqq, type:
The span query is provided via a ->
sign. For
example, to search for all documents on muon decay published
between 1983 and 1992, type:
To find all documents by authors with names ranging from Ellis,
J to Ellis, Qqq, type:
The span query is provided via a ->
sign. For
example, to search for all documents on muon decay published
between 1983 and 1992, type:
To find all documents by authors with names ranging from Ellis,
J to Ellis, Qqq, type:
The span query is provided via a ->
sign. For
example, to search for all documents on muon decay published
between 1983 and 1992, type:
To find all documents by authors with names ranging from Ellis,
J to Ellis, Qqq, type:
The span query is provided via a ->
sign. For
example, to search for all documents on muon decay published
between 1983 and 1992, type:
To find all documents by authors with names ranging from Ellis,
J to Ellis, Qqq, type:
The span query is provided via a ->
sign. For
example, to search for all documents on muon decay published
between 1983 and 1992, type:
To find all documents by authors with names ranging from Ellis,
J to Ellis, Qqq, type:
The span query is provided via a ->
sign. For
example, to search for all documents on muon decay published
between 1983 and 1992, type:
To find all documents by authors with names ranging from Ellis,
J to Ellis, Qqq, type:
The span query is provided via a ->
sign. For
example, to search for all documents on muon decay published
between 1983 and 1992, type:
To find all documents by authors with names ranging from Ellis,
J to Ellis, Qqq, type:
The span query is provided via a ->
sign. For
example, to search for all documents on muon decay published
between 1983 and 1992, type:
To find all documents by authors with names ranging from Ellis,
J to Ellis, Qqq, type:
The span query is provided via a ->
sign. For
example, to search for all documents on muon decay published
between 1983 and 1992, type:
To find all documents by authors with names ranging from Ellis,
J to Ellis, Qqq, type:
La consulta por rango se realiza a través del signo
->
. Por ejemplo, para recuperar todos los documentos
sobre par motor publicados entre 1983 y
1992, debemos escribir:
Para recuperar todos los documentos de autores cuyos nombres estén
dentro del rango que va de Ellis, J a Ellis, Qqq,
debemos escribir:
La consulta por rang es realitza a través del signe
->
. Per exemple, per recuperar tots els documents sobre
par motor publicats entre 1983 i 1992, cal
escriure:
Per recuperar tots els documents d’autors els noms dels quals estiguin
dins El rang que va des de Ellis, J fins Ellis, Qqq,
cal escriure:
All the syntax mentioned above can be combined together in one
query. For example, to find documents that have the word
ellis inside author fields, that do not contain words like
muon, 'muonic' etc in any field, that contain the phrase
(or the substring, to be more precise) 'dense quark matter' inside
abstract fields, and that were published in year starting by digits
'200', type:
Note that the default "any field" global index does contain only the metadata terms,
not the citation nor fulltext terms. You have to explicitely mention fulltext
or reference
index to search there. For example, to find the term Higgs
in either metadata, references or fulltext files, type:
This permits an interesting combination of metadata, fulltext and citation search in
the same query. For example, to get all documents written by
Lin whose fulltext files contain the words
Schwarzschild and AdS, and who cite journal
Adv. Theor. Math. Phys., type:
" "1" "
Currently, fulltext files and references are not fully searchable on the CERN site.
Assumed operational time: Q1 2007.
|
">
All the syntax mentioned above can be combined together in one
query. For example, to find documents that have the word
ellis inside author fields, that do not contain words like
muon, 'muonic' etc in any field, that contain the phrase
(or the substring, to be more precise) 'dense quark matter' inside
abstract fields, and that were published in year starting by digits
'200', type:
Note that the default "any field" global index does contain only the metadata terms,
not the citation nor fulltext terms. You have to explicitely mention fulltext
or reference
index to search there. For example, to find the term Higgs
in either metadata, references or fulltext files, type:
This permits an interesting combination of metadata, fulltext and citation search in
the same query. For example, to get all documents written by
Lin whose fulltext files contain the words
Schwarzschild and AdS, and who cite journal
Adv. Theor. Math. Phys., type:
" "1" "
Currently, fulltext files and references are not fully searchable on the CERN site.
Assumed operational time: Q1 2007.
|
">
All the syntax mentioned above can be combined together in one
query. For example, to find documents that have the word
ellis inside author fields, that do not contain words like
muon, 'muonic' etc in any field, that contain the phrase
(or the substring, to be more precise) 'dense quark matter' inside
abstract fields, and that were published in year starting by digits
'200', type:
Note that the default "any field" global index does contain only the metadata terms,
not the citation nor fulltext terms. You have to explicitely mention fulltext
or reference
index to search there. For example, to find the term Higgs
in either metadata, references or fulltext files, type:
This permits an interesting combination of metadata, fulltext and citation search in
the same query. For example, to get all documents written by
Lin whose fulltext files contain the words
Schwarzschild and AdS, and who cite journal
Adv. Theor. Math. Phys., type:
" "1" "
Currently, fulltext files and references are not fully searchable on the CERN site.
Assumed operational time: Q1 2007.
|
">
All the syntax mentioned above can be combined together in one
query. For example, to find documents that have the word
ellis inside author fields, that do not contain words like
muon, 'muonic' etc in any field, that contain the phrase
(or the substring, to be more precise) 'dense quark matter' inside
abstract fields, and that were published in year starting by digits
'200', type:
Note that the default "any field" global index does contain only the metadata terms,
not the citation nor fulltext terms. You have to explicitely mention fulltext
or reference
index to search there. For example, to find the term Higgs
in either metadata, references or fulltext files, type:
This permits an interesting combination of metadata, fulltext and citation search in
the same query. For example, to get all documents written by
Lin whose fulltext files contain the words
Schwarzschild and AdS, and who cite journal
Adv. Theor. Math. Phys., type:
" "1" "
Currently, fulltext files and references are not fully searchable on the CERN site.
Assumed operational time: Q1 2007.
|
">
All the syntax mentioned above can be combined together in one
query. For example, to find documents that have the word
ellis inside author fields, that do not contain words like
muon, 'muonic' etc in any field, that contain the phrase
(or the substring, to be more precise) 'dense quark matter' inside
abstract fields, and that were published in year starting by digits
'200', type:
Note that the default "any field" global index does contain only the metadata terms,
not the citation nor fulltext terms. You have to explicitely mention fulltext
or reference
index to search there. For example, to find the term Higgs
in either metadata, references or fulltext files, type:
This permits an interesting combination of metadata, fulltext and citation search in
the same query. For example, to get all documents written by
Lin whose fulltext files contain the words
Schwarzschild and AdS, and who cite journal
Adv. Theor. Math. Phys., type:
" "1" "
Currently, fulltext files and references are not fully searchable on the CERN site.
Assumed operational time: Q1 2007.
|
">
All the syntax mentioned above can be combined together in one
query. For example, to find documents that have the word
ellis inside author fields, that do not contain words like
muon, 'muonic' etc in any field, that contain the phrase
(or the substring, to be more precise) 'dense quark matter' inside
abstract fields, and that were published in year starting by digits
'200', type:
Note that the default "any field" global index does contain only the metadata terms,
not the citation nor fulltext terms. You have to explicitely mention fulltext
or reference
index to search there. For example, to find the term Higgs
in either metadata, references or fulltext files, type:
This permits an interesting combination of metadata, fulltext and citation search in
the same query. For example, to get all documents written by
Lin whose fulltext files contain the words
Schwarzschild and AdS, and who cite journal
Adv. Theor. Math. Phys., type:
" "1" "
Currently, fulltext files and references are not fully searchable on the CERN site.
Assumed operational time: Q1 2007.
|
">
All the syntax mentioned above can be combined together in one
query. For example, to find documents that have the word
ellis inside author fields, that do not contain words like
muon, 'muonic' etc in any field, that contain the phrase
(or the substring, to be more precise) 'dense quark matter' inside
abstract fields, and that were published in year starting by digits
'200', type:
Note that the default "any field" global index does contain only the metadata terms,
not the citation nor fulltext terms. You have to explicitely mention fulltext
or reference
index to search there. For example, to find the term Higgs
in either metadata, references or fulltext files, type:
This permits an interesting combination of metadata, fulltext and citation search in
the same query. For example, to get all documents written by
Lin whose fulltext files contain the words
Schwarzschild and AdS, and who cite journal
Adv. Theor. Math. Phys., type:
" "1" "
Currently, fulltext files and references are not fully searchable on the CERN site.
Assumed operational time: Q1 2007.
|
">
All the syntax mentioned above can be combined together in one
query. For example, to find documents that have the word
ellis inside author fields, that do not contain words like
muon, 'muonic' etc in any field, that contain the phrase
(or the substring, to be more precise) 'dense quark matter' inside
abstract fields, and that were published in year starting by digits
'200', type:
Note that the default "any field" global index does contain only the metadata terms,
not the citation nor fulltext terms. You have to explicitely mention fulltext
or reference
index to search there. For example, to find the term Higgs
in either metadata, references or fulltext files, type:
This permits an interesting combination of metadata, fulltext and citation search in
the same query. For example, to get all documents written by
Lin whose fulltext files contain the words
Schwarzschild and AdS, and who cite journal
Adv. Theor. Math. Phys., type:
" "1" "
Currently, fulltext files and references are not fully searchable on the CERN site.
Assumed operational time: Q1 2007.
|
">
All the syntax mentioned above can be combined together in one
query. For example, to find documents that have the word
ellis inside author fields, that do not contain words like
muon, 'muonic' etc in any field, that contain the phrase
(or the substring, to be more precise) 'dense quark matter' inside
abstract fields, and that were published in year starting by digits
'200', type:
Note that the default "any field" global index does contain only the metadata terms,
not the citation nor fulltext terms. You have to explicitely mention fulltext
or reference
index to search there. For example, to find the term Higgs
in either metadata, references or fulltext files, type:
This permits an interesting combination of metadata, fulltext and citation search in
the same query. For example, to get all documents written by
Lin whose fulltext files contain the words
Schwarzschild and AdS, and who cite journal
Adv. Theor. Math. Phys., type:
" "1" "
Currently, fulltext files and references are not fully searchable on the CERN site.
Assumed operational time: Q1 2007.
|
">
All the syntax mentioned above can be combined together in one
query. For example, to find documents that have the word
ellis inside author fields, that do not contain words like
muon, 'muonic' etc in any field, that contain the phrase
(or the substring, to be more precise) 'dense quark matter' inside
abstract fields, and that were published in year starting by digits
'200', type:
Note that the default "any field" global index does contain only the metadata terms,
not the citation nor fulltext terms. You have to explicitely mention fulltext
or reference
index to search there. For example, to find the term Higgs
in either metadata, references or fulltext files, type:
This permits an interesting combination of metadata, fulltext and citation search in
the same query. For example, to get all documents written by
Lin whose fulltext files contain the words
Schwarzschild and AdS, and who cite journal
Adv. Theor. Math. Phys., type:
" "1" "
Currently, fulltext files and references are not fully searchable on the CERN site.
Assumed operational time: Q1 2007.
|
">
All the syntax mentioned above can be combined together in one
query. For example, to find documents that have the word
ellis inside author fields, that do not contain words like
muon, 'muonic' etc in any field, that contain the phrase
(or the substring, to be more precise) 'dense quark matter' inside
abstract fields, and that were published in year starting by digits
'200', type:
Note that the default "any field" global index does contain only the metadata terms,
not the citation nor fulltext terms. You have to explicitely mention fulltext
or reference
index to search there. For example, to find the term Higgs
in either metadata, references or fulltext files, type:
This permits an interesting combination of metadata, fulltext and citation search in
the same query. For example, to get all documents written by
Lin whose fulltext files contain the words
Schwarzschild and AdS, and who cite journal
Adv. Theor. Math. Phys., type:
" "1" "
Currently, fulltext files and references are not fully searchable on the CERN site.
Assumed operational time: Q1 2007.
|
">
All the syntax mentioned above can be combined together in one
query. For example, to find documents that have the word
ellis inside author fields, that do not contain words like
muon, 'muonic' etc in any field, that contain the phrase
(or the substring, to be more precise) 'dense quark matter' inside
abstract fields, and that were published in year starting by digits
'200', type:
Note that the default "any field" global index does contain only the metadata terms,
not the citation nor fulltext terms. You have to explicitely mention fulltext
or reference
index to search there. For example, to find the term Higgs
in either metadata, references or fulltext files, type:
This permits an interesting combination of metadata, fulltext and citation search in
the same query. For example, to get all documents written by
Lin whose fulltext files contain the words
Schwarzschild and AdS, and who cite journal
Adv. Theor. Math. Phys., type:
" "1" "
Currently, fulltext files and references are not fully searchable on the CERN site.
Assumed operational time: Q1 2007.
|
">
All the syntax mentioned above can be combined together in one
query. For example, to find documents that have the word
ellis inside author fields, that do not contain words like
muon, 'muonic' etc in any field, that contain the phrase
(or the substring, to be more precise) 'dense quark matter' inside
abstract fields, and that were published in year starting by digits
'200', type:
Note that the default "any field" global index does contain only the metadata terms,
not the citation nor fulltext terms. You have to explicitely mention fulltext
or reference
index to search there. For example, to find the term Higgs
in either metadata, references or fulltext files, type:
This permits an interesting combination of metadata, fulltext and citation search in
the same query. For example, to get all documents written by
Lin whose fulltext files contain the words
Schwarzschild and AdS, and who cite journal
Adv. Theor. Math. Phys., type:
" "1" "
Currently, fulltext files and references are not fully searchable on the CERN site.
Assumed operational time: Q1 2007.
|
">
All the syntax mentioned above can be combined together in one
query. For example, to find documents that have the word
ellis inside author fields, that do not contain words like
muon, 'muonic' etc in any field, that contain the phrase
(or the substring, to be more precise) 'dense quark matter' inside
abstract fields, and that were published in year starting by digits
'200', type:
Note that the default "any field" global index does contain only the metadata terms,
not the citation nor fulltext terms. You have to explicitely mention fulltext
or reference
index to search there. For example, to find the term Higgs
in either metadata, references or fulltext files, type:
This permits an interesting combination of metadata, fulltext and citation search in
the same query. For example, to get all documents written by
Lin whose fulltext files contain the words
Schwarzschild and AdS, and who cite journal
Adv. Theor. Math. Phys., type:
" "1" "
Currently, fulltext files and references are not fully searchable on the CERN site.
Assumed operational time: Q1 2007.
|
">
All the syntax mentioned above can be combined together in one
query. For example, to find documents that have the word
ellis inside author fields, that do not contain words like
muon, 'muonic' etc in any field, that contain the phrase
(or the substring, to be more precise) 'dense quark matter' inside
abstract fields, and that were published in year starting by digits
'200', type:
Note that the default "any field" global index does contain only the metadata terms,
not the citation nor fulltext terms. You have to explicitely mention fulltext
or reference
index to search there. For example, to find the term Higgs
in either metadata, references or fulltext files, type:
This permits an interesting combination of metadata, fulltext and citation search in
the same query. For example, to get all documents written by
Lin whose fulltext files contain the words
Schwarzschild and AdS, and who cite journal
Adv. Theor. Math. Phys., type:
" "1" "
Currently, fulltext files and references are not fully searchable on the CERN site.
Assumed operational time: Q1 2007.
|
">
All the syntax mentioned above can be combined together in one
query. For example, to find documents that have the word
ellis inside author fields, that do not contain words like
muon, 'muonic' etc in any field, that contain the phrase
(or the substring, to be more precise) 'dense quark matter' inside
abstract fields, and that were published in year starting by digits
'200', type:
Note that the default "any field" global index does contain only the metadata terms,
not the citation nor fulltext terms. You have to explicitely mention fulltext
or reference
index to search there. For example, to find the term Higgs
in either metadata, references or fulltext files, type:
This permits an interesting combination of metadata, fulltext and citation search in
the same query. For example, to get all documents written by
Lin whose fulltext files contain the words
Schwarzschild and AdS, and who cite journal
Adv. Theor. Math. Phys., type:
" "1" "
Currently, fulltext files and references are not fully searchable on the CERN site.
Assumed operational time: Q1 2007.
|
">
All the syntax mentioned above can be combined together in one
query. For example, to find documents that have the word
ellis inside author fields, that do not contain words like
muon, 'muonic' etc in any field, that contain the phrase
(or the substring, to be more precise) 'dense quark matter' inside
abstract fields, and that were published in year starting by digits
'200', type:
Note that the default "any field" global index does contain only the metadata terms,
not the citation nor fulltext terms. You have to explicitely mention fulltext
or reference
index to search there. For example, to find the term Higgs
in either metadata, references or fulltext files, type:
This permits an interesting combination of metadata, fulltext and citation search in
the same query. For example, to get all documents written by
Lin whose fulltext files contain the words
Schwarzschild and AdS, and who cite journal
Adv. Theor. Math. Phys., type:
" "1" "
Currently, fulltext files and references are not fully searchable on the CERN site.
Assumed operational time: Q1 2007.
|
">
All the syntax mentioned above can be combined together in one
query. For example, to find documents that have the word
ellis inside author fields, that do not contain words like
muon, 'muonic' etc in any field, that contain the phrase
(or the substring, to be more precise) 'dense quark matter' inside
abstract fields, and that were published in year starting by digits
'200', type:
Note that the default "any field" global index does contain only the metadata terms,
not the citation nor fulltext terms. You have to explicitely mention fulltext
or reference
index to search there. For example, to find the term Higgs
in either metadata, references or fulltext files, type:
This permits an interesting combination of metadata, fulltext and citation search in
the same query. For example, to get all documents written by
Lin whose fulltext files contain the words
Schwarzschild and AdS, and who cite journal
Adv. Theor. Math. Phys., type:
" "1" "
Currently, fulltext files and references are not fully searchable on the CERN site.
Assumed operational time: Q1 2007.
|
">
Toda la sintaxis mencionada anteriormente se puede combinar en una
misma consulta. Por ejemplo, para recuperar documentos que contienen
la palabra ellis dentro del campo autor, y que no contienen
palabras como muon, 'muonic', etc., en ningún otro
campo, y que contienen (o subcadena de palabras, para ser más
precisos) ‘dense quark matter’ dentro del campo de resumen, y que han sido
publicados dentro de los años que comienzan por los dígitos '200',
debe escribirse:
Obsérvese que la opción de índice global “cualquier campo” por defecto
contiene únicamente términos de metadatos, no del texto completo ni de
las citas bibliográficass. Es necesario especificar explícitamente
las opciones de buscar en el índice texto completo
o de
cita bibliográfica
si se desea buscar en estos campos.
Por ejemplo, para recuperar el término Higgs tanto dentro de
los metadatos, las citas o el texto completo, debe escribirse:
Ello permite una interesante combinación de metadatos, texto completo
y citas dentro de una misma búsqueda. Por ejemplo, para recuperar
todos los documentos escritos por Lin que en el texto
completo contengan las palabras Schwarzschild y AdS,
que citen la revista Adv. Theor. Math. Phys., debe
escribirse:
" ""1" ""1""
Actualmente, los registros con archivos a texto completo y citas no se pueden recuperar en el web de CERN. Assumed operational time: Q1 2007.
|
">
Tota la sintaxi mencionada anteriorment es pot combinar en una
mateixa consulta. Per exemple, per recuperar documents que contenen
la paraula ellis dins el camp d’autor, i que no contenen
paraules com muon, 'muonic', etc., a cap altre
camp, i que contenen la frase (o subcadena de paraules, per ser més
precisos) ‘dense quark matter’ dins el camp de resum, i que han estat
publicats dins els anys que comencen pels dígits '200', cal escriure:
Observis que l’opció d’índex global “qualsevol camp” per defecte conté
només els termes de metadades, no del text complet ni de les
referències bibliogràfiques. Cal especificar explícitament les
opcions de cercar a l’índex text complet
o de
referència bibliogràfica
si volem cercar per aquests
camps. Per exemple, per recuperar el terme Higgs tant dins
les metadades, les referències o el text complet, cal escriure:
Això permet una interessant combinació de metadades, text complet i
referències dins una mateixe cerca. Per exemple, per recuperar
tots els documents escrits per Lin que en el text complet
continguin les paraules Schwarzschild and AdS,
que citi la revista Adv. Theor. Math. Phys., cal escriure:
" ""1" ""1""
Actualment, els registres amb arxius a text complet i referències no es poden recuperar al web de CERN. Assumed operational time: Q1 2007.
|
">
- Whenever possible, prefer word searches instead of phrase searches.
Search rather for
black hole
than for "black hole"
.
- Avoid common terms such as
and
, of
, or CERN
.
- If you are searching for a specific metadata information, such
as a report number, choose corresponding index.
- If you are looking for a specific document collection, such
as Theses, choose the
Theses collection first, and start your search from there.
- Whenever possible, prefer word searches instead of phrase searches.
Search rather for
black hole
than for "black hole"
.
- Avoid common terms such as
and
, of
, or CERN
.
- If you are searching for a specific metadata information, such
as a report number, choose corresponding index.
- If you are looking for a specific document collection, such
as Theses, choose the
Theses collection first, and start your search from there.
- Whenever possible, prefer word searches instead of phrase searches.
Search rather for
black hole
than for "black hole"
.
- Avoid common terms such as
and
, of
, or CERN
.
- If you are searching for a specific metadata information, such
as a report number, choose corresponding index.
- If you are looking for a specific document collection, such
as Theses, choose the
Theses collection first, and start your search from there.
- Whenever possible, prefer word searches instead of phrase searches.
Search rather for
black hole
than for "black hole"
.
- Avoid common terms such as
and
, of
, or CERN
.
- If you are searching for a specific metadata information, such
as a report number, choose corresponding index.
- If you are looking for a specific document collection, such
as Theses, choose the
Theses collection first, and start your search from there.
- Whenever possible, prefer word searches instead of phrase searches.
Search rather for
black hole
than for "black hole"
.
- Avoid common terms such as
and
, of
, or CERN
.
- If you are searching for a specific metadata information, such
as a report number, choose corresponding index.
- If you are looking for a specific document collection, such
as Theses, choose the
Theses collection first, and start your search from there.
- Whenever possible, prefer word searches instead of phrase searches.
Search rather for
black hole
than for "black hole"
.
- Avoid common terms such as
and
, of
, or CERN
.
- If you are searching for a specific metadata information, such
as a report number, choose corresponding index.
- If you are looking for a specific document collection, such
as Theses, choose the
Theses collection first, and start your search from there.
- Whenever possible, prefer word searches instead of phrase searches.
Search rather for
black hole
than for "black hole"
.
- Avoid common terms such as
and
, of
, or CERN
.
- If you are searching for a specific metadata information, such
as a report number, choose corresponding index.
- If you are looking for a specific document collection, such
as Theses, choose the
Theses collection first, and start your search from there.
- Whenever possible, prefer word searches instead of phrase searches.
Search rather for
black hole
than for "black hole"
.
- Avoid common terms such as
and
, of
, or CERN
.
- If you are searching for a specific metadata information, such
as a report number, choose corresponding index.
- If you are looking for a specific document collection, such
as Theses, choose the
Theses collection first, and start your search from there.
- Whenever possible, prefer word searches instead of phrase searches.
Search rather for
black hole
than for "black hole"
.
- Avoid common terms such as
and
, of
, or CERN
.
- If you are searching for a specific metadata information, such
as a report number, choose corresponding index.
- If you are looking for a specific document collection, such
as Theses, choose the
Theses collection first, and start your search from there.
- Whenever possible, prefer word searches instead of phrase searches.
Search rather for
black hole
than for "black hole"
.
- Avoid common terms such as
and
, of
, or CERN
.
- If you are searching for a specific metadata information, such
as a report number, choose corresponding index.
- If you are looking for a specific document collection, such
as Theses, choose the
Theses collection first, and start your search from there.
- Whenever possible, prefer word searches instead of phrase searches.
Search rather for
black hole
than for "black hole"
.
- Avoid common terms such as
and
, of
, or CERN
.
- If you are searching for a specific metadata information, such
as a report number, choose corresponding index.
- If you are looking for a specific document collection, such
as Theses, choose the
Theses collection first, and start your search from there.
- Whenever possible, prefer word searches instead of phrase searches.
Search rather for
black hole
than for "black hole"
.
- Avoid common terms such as
and
, of
, or CERN
.
- If you are searching for a specific metadata information, such
as a report number, choose corresponding index.
- If you are looking for a specific document collection, such
as Theses, choose the
Theses collection first, and start your search from there.
- Whenever possible, prefer word searches instead of phrase searches.
Search rather for
black hole
than for "black hole"
.
- Avoid common terms such as
and
, of
, or CERN
.
- If you are searching for a specific metadata information, such
as a report number, choose corresponding index.
- If you are looking for a specific document collection, such
as Theses, choose the
Theses collection first, and start your search from there.
- Whenever possible, prefer word searches instead of phrase searches.
Search rather for
black hole
than for "black hole"
.
- Avoid common terms such as
and
, of
, or CERN
.
- If you are searching for a specific metadata information, such
as a report number, choose corresponding index.
- If you are looking for a specific document collection, such
as Theses, choose the
Theses collection first, and start your search from there.
- Whenever possible, prefer word searches instead of phrase searches.
Search rather for
black hole
than for "black hole"
.
- Avoid common terms such as
and
, of
, or CERN
.
- If you are searching for a specific metadata information, such
as a report number, choose corresponding index.
- If you are looking for a specific document collection, such
as Theses, choose the
Theses collection first, and start your search from there.
- Whenever possible, prefer word searches instead of phrase searches.
Search rather for
black hole
than for "black hole"
.
- Avoid common terms such as
and
, of
, or CERN
.
- If you are searching for a specific metadata information, such
as a report number, choose corresponding index.
- If you are looking for a specific document collection, such
as Theses, choose the
Theses collection first, and start your search from there.
- Whenever possible, prefer word searches instead of phrase searches.
Search rather for
black hole
than for "black hole"
.
- Avoid common terms such as
and
, of
, or CERN
.
- If you are searching for a specific metadata information, such
as a report number, choose corresponding index.
- If you are looking for a specific document collection, such
as Theses, choose the
Theses collection first, and start your search from there.
- Whenever possible, prefer word searches instead of phrase searches.
Search rather for
black hole
than for "black hole"
.
- Avoid common terms such as
and
, of
, or CERN
.
- If you are searching for a specific metadata information, such
as a report number, choose corresponding index.
- If you are looking for a specific document collection, such
as Theses, choose the
Theses collection first, and start your search from there.
- Siempre que sea posible, es preferible realizar búsquedas por
palabra antes que por frase. Es preferible buscar por
agujero
negro
que por "agujero negro"
.
- Se aconseja evitar vocablos comunes tales como
y
,
de
, o siglas como CERN
.
- Si la búsqueda versa sobre información específica en los
metadatos, como por ejemplo, número de registro, seleccionar
el índice correspondiente.
- Si la búsqueda versa sobre una colección específica de documentos,
como por ejemplo, Tesis, elegir en primer lugar la colección
Tesis, e iniciar la búsqueda a partir
de aquí.
- Sempre que sigui possible, es preferible realitzar cerques per
paraula abans que per frase. Es preferible una cerca per
forat
negre
que per "forat negre"
.
- S’aconsella evitar mots comuns tals com les
preposicions
i
, de
, o sigles com
CERN
.
- Si la cerca versa sobre informació específica a les metadades, com
per exemple, número de registre, cal seleccionar l’índex
corresponent.
- Si la cerca versa sobre una col•lecció específica de documents,
com per exemple, Tesis, cal escollir en primer lloc la
col•lecció Tesis, e iniciar la cerca
a partir de aquí.
You can search for an author in many ways, each having its own
advantages and disadvantages.
- First of all, note that searching for words isn't usually what you
would want here. If you choose to search for the words
Ellis
J
within the author index, it means that two queries (for the
words Ellis
and J
) are effected first and a
boolean AND is performed next:
Such a query would match also a document whose first author is
Ellis, R and the second author Finch, A J, which is
probably not what you wanted. While the search is very fast and you
would have found the results for the author you were looking for, such
a technique could have returned you many false positives, as the one
cited above. Instead of searching for words, a more suitable
technique to apply in this case is to search for phrases which will
permit you to achieve higher search precisions.
- The author names are usually stored in a form containing initials
only, such as Ellis, J. To get the list of publications of
an author whose name is spelled exactly that way, type:
You can search for an author in many ways, each having its own
advantages and disadvantages.
- First of all, note that searching for words isn't usually what you
would want here. If you choose to search for the words
Ellis
J
within the author index, it means that two queries (for the
words Ellis
and J
) are effected first and a
boolean AND is performed next:
Such a query would match also a document whose first author is
Ellis, R and the second author Finch, A J, which is
probably not what you wanted. While the search is very fast and you
would have found the results for the author you were looking for, such
a technique could have returned you many false positives, as the one
cited above. Instead of searching for words, a more suitable
technique to apply in this case is to search for phrases which will
permit you to achieve higher search precisions.
- The author names are usually stored in a form containing initials
only, such as Ellis, J. To get the list of publications of
an author whose name is spelled exactly that way, type:
You can search for an author in many ways, each having its own
advantages and disadvantages.
- First of all, note that searching for words isn't usually what you
would want here. If you choose to search for the words
Ellis
J
within the author index, it means that two queries (for the
words Ellis
and J
) are effected first and a
boolean AND is performed next:
Such a query would match also a document whose first author is
Ellis, R and the second author Finch, A J, which is
probably not what you wanted. While the search is very fast and you
would have found the results for the author you were looking for, such
a technique could have returned you many false positives, as the one
cited above. Instead of searching for words, a more suitable
technique to apply in this case is to search for phrases which will
permit you to achieve higher search precisions.
- The author names are usually stored in a form containing initials
only, such as Ellis, J. To get the list of publications of
an author whose name is spelled exactly that way, type:
You can search for an author in many ways, each having its own
advantages and disadvantages.
- First of all, note that searching for words isn't usually what you
would want here. If you choose to search for the words
Ellis
J
within the author index, it means that two queries (for the
words Ellis
and J
) are effected first and a
boolean AND is performed next:
Such a query would match also a document whose first author is
Ellis, R and the second author Finch, A J, which is
probably not what you wanted. While the search is very fast and you
would have found the results for the author you were looking for, such
a technique could have returned you many false positives, as the one
cited above. Instead of searching for words, a more suitable
technique to apply in this case is to search for phrases which will
permit you to achieve higher search precisions.
- The author names are usually stored in a form containing initials
only, such as Ellis, J. To get the list of publications of
an author whose name is spelled exactly that way, type:
You can search for an author in many ways, each having its own
advantages and disadvantages.
- First of all, note that searching for words isn't usually what you
would want here. If you choose to search for the words
Ellis
J
within the author index, it means that two queries (for the
words Ellis
and J
) are effected first and a
boolean AND is performed next:
Such a query would match also a document whose first author is
Ellis, R and the second author Finch, A J, which is
probably not what you wanted. While the search is very fast and you
would have found the results for the author you were looking for, such
a technique could have returned you many false positives, as the one
cited above. Instead of searching for words, a more suitable
technique to apply in this case is to search for phrases which will
permit you to achieve higher search precisions.
- The author names are usually stored in a form containing initials
only, such as Ellis, J. To get the list of publications of
an author whose name is spelled exactly that way, type:
You can search for an author in many ways, each having its own
advantages and disadvantages.
- First of all, note that searching for words isn't usually what you
would want here. If you choose to search for the words
Ellis
J
within the author index, it means that two queries (for the
words Ellis
and J
) are effected first and a
boolean AND is performed next:
Such a query would match also a document whose first author is
Ellis, R and the second author Finch, A J, which is
probably not what you wanted. While the search is very fast and you
would have found the results for the author you were looking for, such
a technique could have returned you many false positives, as the one
cited above. Instead of searching for words, a more suitable
technique to apply in this case is to search for phrases which will
permit you to achieve higher search precisions.
- The author names are usually stored in a form containing initials
only, such as Ellis, J. To get the list of publications of
an author whose name is spelled exactly that way, type:
You can search for an author in many ways, each having its own
advantages and disadvantages.
- First of all, note that searching for words isn't usually what you
would want here. If you choose to search for the words
Ellis
J
within the author index, it means that two queries (for the
words Ellis
and J
) are effected first and a
boolean AND is performed next:
Such a query would match also a document whose first author is
Ellis, R and the second author Finch, A J, which is
probably not what you wanted. While the search is very fast and you
would have found the results for the author you were looking for, such
a technique could have returned you many false positives, as the one
cited above. Instead of searching for words, a more suitable
technique to apply in this case is to search for phrases which will
permit you to achieve higher search precisions.
- The author names are usually stored in a form containing initials
only, such as Ellis, J. To get the list of publications of
an author whose name is spelled exactly that way, type:
You can search for an author in many ways, each having its own
advantages and disadvantages.
- First of all, note that searching for words isn't usually what you
would want here. If you choose to search for the words
Ellis
J
within the author index, it means that two queries (for the
words Ellis
and J
) are effected first and a
boolean AND is performed next:
Such a query would match also a document whose first author is
Ellis, R and the second author Finch, A J, which is
probably not what you wanted. While the search is very fast and you
would have found the results for the author you were looking for, such
a technique could have returned you many false positives, as the one
cited above. Instead of searching for words, a more suitable
technique to apply in this case is to search for phrases which will
permit you to achieve higher search precisions.
- The author names are usually stored in a form containing initials
only, such as Ellis, J. To get the list of publications of
an author whose name is spelled exactly that way, type:
You can search for an author in many ways, each having its own
advantages and disadvantages.
- First of all, note that searching for words isn't usually what you
would want here. If you choose to search for the words
Ellis
J
within the author index, it means that two queries (for the
words Ellis
and J
) are effected first and a
boolean AND is performed next:
Such a query would match also a document whose first author is
Ellis, R and the second author Finch, A J, which is
probably not what you wanted. While the search is very fast and you
would have found the results for the author you were looking for, such
a technique could have returned you many false positives, as the one
cited above. Instead of searching for words, a more suitable
technique to apply in this case is to search for phrases which will
permit you to achieve higher search precisions.
- The author names are usually stored in a form containing initials
only, such as Ellis, J. To get the list of publications of
an author whose name is spelled exactly that way, type:
You can search for an author in many ways, each having its own
advantages and disadvantages.
- First of all, note that searching for words isn't usually what you
would want here. If you choose to search for the words
Ellis
J
within the author index, it means that two queries (for the
words Ellis
and J
) are effected first and a
boolean AND is performed next:
Such a query would match also a document whose first author is
Ellis, R and the second author Finch, A J, which is
probably not what you wanted. While the search is very fast and you
would have found the results for the author you were looking for, such
a technique could have returned you many false positives, as the one
cited above. Instead of searching for words, a more suitable
technique to apply in this case is to search for phrases which will
permit you to achieve higher search precisions.
- The author names are usually stored in a form containing initials
only, such as Ellis, J. To get the list of publications of
an author whose name is spelled exactly that way, type:
You can search for an author in many ways, each having its own
advantages and disadvantages.
- First of all, note that searching for words isn't usually what you
would want here. If you choose to search for the words
Ellis
J
within the author index, it means that two queries (for the
words Ellis
and J
) are effected first and a
boolean AND is performed next:
Such a query would match also a document whose first author is
Ellis, R and the second author Finch, A J, which is
probably not what you wanted. While the search is very fast and you
would have found the results for the author you were looking for, such
a technique could have returned you many false positives, as the one
cited above. Instead of searching for words, a more suitable
technique to apply in this case is to search for phrases which will
permit you to achieve higher search precisions.
- The author names are usually stored in a form containing initials
only, such as Ellis, J. To get the list of publications of
an author whose name is spelled exactly that way, type:
You can search for an author in many ways, each having its own
advantages and disadvantages.
- First of all, note that searching for words isn't usually what you
would want here. If you choose to search for the words
Ellis
J
within the author index, it means that two queries (for the
words Ellis
and J
) are effected first and a
boolean AND is performed next:
Such a query would match also a document whose first author is
Ellis, R and the second author Finch, A J, which is
probably not what you wanted. While the search is very fast and you
would have found the results for the author you were looking for, such
a technique could have returned you many false positives, as the one
cited above. Instead of searching for words, a more suitable
technique to apply in this case is to search for phrases which will
permit you to achieve higher search precisions.
- The author names are usually stored in a form containing initials
only, such as Ellis, J. To get the list of publications of
an author whose name is spelled exactly that way, type:
You can search for an author in many ways, each having its own
advantages and disadvantages.
- First of all, note that searching for words isn't usually what you
would want here. If you choose to search for the words
Ellis
J
within the author index, it means that two queries (for the
words Ellis
and J
) are effected first and a
boolean AND is performed next:
Such a query would match also a document whose first author is
Ellis, R and the second author Finch, A J, which is
probably not what you wanted. While the search is very fast and you
would have found the results for the author you were looking for, such
a technique could have returned you many false positives, as the one
cited above. Instead of searching for words, a more suitable
technique to apply in this case is to search for phrases which will
permit you to achieve higher search precisions.
- The author names are usually stored in a form containing initials
only, such as Ellis, J. To get the list of publications of
an author whose name is spelled exactly that way, type:
You can search for an author in many ways, each having its own
advantages and disadvantages.
- First of all, note that searching for words isn't usually what you
would want here. If you choose to search for the words
Ellis
J
within the author index, it means that two queries (for the
words Ellis
and J
) are effected first and a
boolean AND is performed next:
Such a query would match also a document whose first author is
Ellis, R and the second author Finch, A J, which is
probably not what you wanted. While the search is very fast and you
would have found the results for the author you were looking for, such
a technique could have returned you many false positives, as the one
cited above. Instead of searching for words, a more suitable
technique to apply in this case is to search for phrases which will
permit you to achieve higher search precisions.
- The author names are usually stored in a form containing initials
only, such as Ellis, J. To get the list of publications of
an author whose name is spelled exactly that way, type:
You can search for an author in many ways, each having its own
advantages and disadvantages.
- First of all, note that searching for words isn't usually what you
would want here. If you choose to search for the words
Ellis
J
within the author index, it means that two queries (for the
words Ellis
and J
) are effected first and a
boolean AND is performed next:
Such a query would match also a document whose first author is
Ellis, R and the second author Finch, A J, which is
probably not what you wanted. While the search is very fast and you
would have found the results for the author you were looking for, such
a technique could have returned you many false positives, as the one
cited above. Instead of searching for words, a more suitable
technique to apply in this case is to search for phrases which will
permit you to achieve higher search precisions.
- The author names are usually stored in a form containing initials
only, such as Ellis, J. To get the list of publications of
an author whose name is spelled exactly that way, type:
You can search for an author in many ways, each having its own
advantages and disadvantages.
- First of all, note that searching for words isn't usually what you
would want here. If you choose to search for the words
Ellis
J
within the author index, it means that two queries (for the
words Ellis
and J
) are effected first and a
boolean AND is performed next:
Such a query would match also a document whose first author is
Ellis, R and the second author Finch, A J, which is
probably not what you wanted. While the search is very fast and you
would have found the results for the author you were looking for, such
a technique could have returned you many false positives, as the one
cited above. Instead of searching for words, a more suitable
technique to apply in this case is to search for phrases which will
permit you to achieve higher search precisions.
- The author names are usually stored in a form containing initials
only, such as Ellis, J. To get the list of publications of
an author whose name is spelled exactly that way, type:
You can search for an author in many ways, each having its own
advantages and disadvantages.
- First of all, note that searching for words isn't usually what you
would want here. If you choose to search for the words
Ellis
J
within the author index, it means that two queries (for the
words Ellis
and J
) are effected first and a
boolean AND is performed next:
Such a query would match also a document whose first author is
Ellis, R and the second author Finch, A J, which is
probably not what you wanted. While the search is very fast and you
would have found the results for the author you were looking for, such
a technique could have returned you many false positives, as the one
cited above. Instead of searching for words, a more suitable
technique to apply in this case is to search for phrases which will
permit you to achieve higher search precisions.
- The author names are usually stored in a form containing initials
only, such as Ellis, J. To get the list of publications of
an author whose name is spelled exactly that way, type:
You can search for an author in many ways, each having its own
advantages and disadvantages.
- First of all, note that searching for words isn't usually what you
would want here. If you choose to search for the words
Ellis
J
within the author index, it means that two queries (for the
words Ellis
and J
) are effected first and a
boolean AND is performed next:
Such a query would match also a document whose first author is
Ellis, R and the second author Finch, A J, which is
probably not what you wanted. While the search is very fast and you
would have found the results for the author you were looking for, such
a technique could have returned you many false positives, as the one
cited above. Instead of searching for words, a more suitable
technique to apply in this case is to search for phrases which will
permit you to achieve higher search precisions.
- The author names are usually stored in a form containing initials
only, such as Ellis, J. To get the list of publications of
an author whose name is spelled exactly that way, type:
La búsqueda por autor puede realizarse de diversas formas, cada una
de las cuales presenta sus ventajas y desventajas.
- En primer lugar, es necesario anotar que el modo de búsqueda por
palabras no es el que más adecuado en este tipo de búsqueda. Si se
selecciona la búsqueda por palabras
Ellis J
dentro del
índice de autores, ello se interpretará como dos consultas (para las
palabras Ellis
y J
) que se efectuarán en
primer lugar, y una booleana Y que se realizará después.
La consulta realizada de este modo recuperará también un documento
que presenta como primer autor a Ellis, R y como segundo
autor Finch, A J, lo cual, probablemente, no es lo deseado.
La búsqueda se ha realizado muy rápidamente y se han recuperado
registros sobre el autor requerido, sin embargo, los resultados
recuperados siguiendo este método pueden no ser pertinentes, tal y
como ocurre en el ejemplo citado anteriormente. En lugar de buscar por
palabras, la técnica más conveniente que debe aplicarse en este caso
es la búsquda por frase, que permite conseguir mayor precisión.
- Es habitual que los nombres de autores que se introducen a través
de los formularios contengan únicamente la inicial del nombre, como
por ejemplo, Ellis, J. Para obtener un listado de las
publicaciones de dicho autor con el nombre escrito exactamente de ese
modo, debemos escribir:
La cerca per autor es pot realitzar de diverses formes, cadascuna
de les quals presenta els seus avantatges i les seves desavantatges.
- En primer lloc, cal notar que el mode de cerca per paraules no és
el més adient en aquests casos. Si es selecciona la cerca per paraules
Ellis J
dins l’índex d’autors, s’interpretarà como a dues
consultes (per a les paraules Ellis
i J
) que
es realitzaran en primer lloc, i una booleana I que es realitzarà
després.
La consulta realitzada d’aquesta forma recuperarà també un document
que tingui com a primer autor a Ellis, R i com a segon
autor a Finch, A J, fet que, probablement, no es el desitjat.
La cerca s’ha realitzat amb molta rapidesa i s’han recuperat registres
sobre l’autor requerit, ara bé, els resultats obtinguts seguint aquest
métode poden no ser pertinents, tal i com passa a l’exemple citat
anteriorment. En lloc de cercar per paraules, la tècnica més
convenient que s’ha d’aplicar en aquests casos és la cerca per frase,
que permet aconseguir major grau de precisió.
- Es habitual que els noms d’autors que s’introdueixen a través dels
formularis continguin únicament la inicial del nom, com per exemple,
Ellis, J. Per obtenir un llistat de les publicacions de tal
autor amb el nom escrit exactament d’aquesta manera, cal escriure:
This way of searching gives you the highest precision and no false
positives. (Assuming there are no other authors whose names are
spelled Ellis, J, an assumption that is often false*.) The search is very fast.
- Sometimes an author's first name may be spelled abbreviated on
some documents (such as Ellis, J) and sometimes full on
others (such as Ellis, John; eventually also with the middle
name: Ellis, John Rolfe). To get the list of publications
for all these forms at the same time, you could use a boolean OR
query:
This way of searching still keeps the highest precision and no
false positives. (Assuming there are no other authors whose names are
spelled Ellis, J or Ellis, John, an assumption that
is often false*.) The search is
fast.
- To match all of the above forms in a single search term, you can
try to use a wildcard query:
It would match all author names that start by the text
Ellis, J
, i.e. not only the wanted forms Ellis,
J and Ellis, John, but also Ellis, Jim, or
Ellis, John Rolfe, or Ellis, Jonathan Richard.
This way of searching returns you more results, which may be
suitable in case you don't know how the names are spelled in the
database. But you also risk the eventuality of getting false
positives. The search is relatively fast.
- Yet another, the most general alternative is to use a partial
phrase matching:
It would find not only all the authors mentioned above, but also
the ones whose names contain the expression Ellis, J
anywhere inside the name, such as De Lellis, Jim. It thus
gives you the largest possible number of hits at the largest risk of
false positives. The search is relatively slow.
(Note though that this way of searching may be very handy in case
of compound family names such Pepe-Altarelli, M or 't
Hooft, G where a casual user query for Hooft, G would
match the wanted author, unlike the methods mentioned above.)
- Finally, let us note that you can use the regular
expression syntax to construct any complex author query. A simple
example is to search for an author expressed in the database as either
Ellis, J or Ellis, John:
Please consult regular expression searching tips
to know more about regular expression search possibilities.
*NOTE:
If you produce your own list of publications and you notice that
sometimes your first name is spelled abbreviated and sometimes in
full, or if you want to identify your publications among several
authors with the same abbreviation, please contact the administrators of so that
they could work with you on inputting a consistently spelled and
properly formatted first name everywhere. Only the consistent
database content will ensure a proper author searching behaviour.
This way of searching gives you the highest precision and no false
positives. (Assuming there are no other authors whose names are
spelled Ellis, J, an assumption that is often false*.) The search is very fast.
- Sometimes an author's first name may be spelled abbreviated on
some documents (such as Ellis, J) and sometimes full on
others (such as Ellis, John; eventually also with the middle
name: Ellis, John Rolfe). To get the list of publications
for all these forms at the same time, you could use a boolean OR
query:
This way of searching still keeps the highest precision and no
false positives. (Assuming there are no other authors whose names are
spelled Ellis, J or Ellis, John, an assumption that
is often false*.) The search is
fast.
- To match all of the above forms in a single search term, you can
try to use a wildcard query:
It would match all author names that start by the text
Ellis, J
, i.e. not only the wanted forms Ellis,
J and Ellis, John, but also Ellis, Jim, or
Ellis, John Rolfe, or Ellis, Jonathan Richard.
This way of searching returns you more results, which may be
suitable in case you don't know how the names are spelled in the
database. But you also risk the eventuality of getting false
positives. The search is relatively fast.
- Yet another, the most general alternative is to use a partial
phrase matching:
It would find not only all the authors mentioned above, but also
the ones whose names contain the expression Ellis, J
anywhere inside the name, such as De Lellis, Jim. It thus
gives you the largest possible number of hits at the largest risk of
false positives. The search is relatively slow.
(Note though that this way of searching may be very handy in case
of compound family names such Pepe-Altarelli, M or 't
Hooft, G where a casual user query for Hooft, G would
match the wanted author, unlike the methods mentioned above.)
- Finally, let us note that you can use the regular
expression syntax to construct any complex author query. A simple
example is to search for an author expressed in the database as either
Ellis, J or Ellis, John:
Please consult regular expression searching tips
to know more about regular expression search possibilities.
*NOTE:
If you produce your own list of publications and you notice that
sometimes your first name is spelled abbreviated and sometimes in
full, or if you want to identify your publications among several
authors with the same abbreviation, please contact the administrators of so that
they could work with you on inputting a consistently spelled and
properly formatted first name everywhere. Only the consistent
database content will ensure a proper author searching behaviour.
This way of searching gives you the highest precision and no false
positives. (Assuming there are no other authors whose names are
spelled Ellis, J, an assumption that is often false*.) The search is very fast.
- Sometimes an author's first name may be spelled abbreviated on
some documents (such as Ellis, J) and sometimes full on
others (such as Ellis, John; eventually also with the middle
name: Ellis, John Rolfe). To get the list of publications
for all these forms at the same time, you could use a boolean OR
query:
This way of searching still keeps the highest precision and no
false positives. (Assuming there are no other authors whose names are
spelled Ellis, J or Ellis, John, an assumption that
is often false*.) The search is
fast.
- To match all of the above forms in a single search term, you can
try to use a wildcard query:
It would match all author names that start by the text
Ellis, J
, i.e. not only the wanted forms Ellis,
J and Ellis, John, but also Ellis, Jim, or
Ellis, John Rolfe, or Ellis, Jonathan Richard.
This way of searching returns you more results, which may be
suitable in case you don't know how the names are spelled in the
database. But you also risk the eventuality of getting false
positives. The search is relatively fast.
- Yet another, the most general alternative is to use a partial
phrase matching:
It would find not only all the authors mentioned above, but also
the ones whose names contain the expression Ellis, J
anywhere inside the name, such as De Lellis, Jim. It thus
gives you the largest possible number of hits at the largest risk of
false positives. The search is relatively slow.
(Note though that this way of searching may be very handy in case
of compound family names such Pepe-Altarelli, M or 't
Hooft, G where a casual user query for Hooft, G would
match the wanted author, unlike the methods mentioned above.)
- Finally, let us note that you can use the regular
expression syntax to construct any complex author query. A simple
example is to search for an author expressed in the database as either
Ellis, J or Ellis, John:
Please consult regular expression searching tips
to know more about regular expression search possibilities.
*NOTE:
If you produce your own list of publications and you notice that
sometimes your first name is spelled abbreviated and sometimes in
full, or if you want to identify your publications among several
authors with the same abbreviation, please contact the administrators of so that
they could work with you on inputting a consistently spelled and
properly formatted first name everywhere. Only the consistent
database content will ensure a proper author searching behaviour.
This way of searching gives you the highest precision and no false
positives. (Assuming there are no other authors whose names are
spelled Ellis, J, an assumption that is often false*.) The search is very fast.
- Sometimes an author's first name may be spelled abbreviated on
some documents (such as Ellis, J) and sometimes full on
others (such as Ellis, John; eventually also with the middle
name: Ellis, John Rolfe). To get the list of publications
for all these forms at the same time, you could use a boolean OR
query:
This way of searching still keeps the highest precision and no
false positives. (Assuming there are no other authors whose names are
spelled Ellis, J or Ellis, John, an assumption that
is often false*.) The search is
fast.
- To match all of the above forms in a single search term, you can
try to use a wildcard query:
It would match all author names that start by the text
Ellis, J
, i.e. not only the wanted forms Ellis,
J and Ellis, John, but also Ellis, Jim, or
Ellis, John Rolfe, or Ellis, Jonathan Richard.
This way of searching returns you more results, which may be
suitable in case you don't know how the names are spelled in the
database. But you also risk the eventuality of getting false
positives. The search is relatively fast.
- Yet another, the most general alternative is to use a partial
phrase matching:
It would find not only all the authors mentioned above, but also
the ones whose names contain the expression Ellis, J
anywhere inside the name, such as De Lellis, Jim. It thus
gives you the largest possible number of hits at the largest risk of
false positives. The search is relatively slow.
(Note though that this way of searching may be very handy in case
of compound family names such Pepe-Altarelli, M or 't
Hooft, G where a casual user query for Hooft, G would
match the wanted author, unlike the methods mentioned above.)
- Finally, let us note that you can use the regular
expression syntax to construct any complex author query. A simple
example is to search for an author expressed in the database as either
Ellis, J or Ellis, John:
Please consult regular expression searching tips
to know more about regular expression search possibilities.
*NOTE:
If you produce your own list of publications and you notice that
sometimes your first name is spelled abbreviated and sometimes in
full, or if you want to identify your publications among several
authors with the same abbreviation, please contact the administrators of so that
they could work with you on inputting a consistently spelled and
properly formatted first name everywhere. Only the consistent
database content will ensure a proper author searching behaviour.
This way of searching gives you the highest precision and no false
positives. (Assuming there are no other authors whose names are
spelled Ellis, J, an assumption that is often false*.) The search is very fast.
- Sometimes an author's first name may be spelled abbreviated on
some documents (such as Ellis, J) and sometimes full on
others (such as Ellis, John; eventually also with the middle
name: Ellis, John Rolfe). To get the list of publications
for all these forms at the same time, you could use a boolean OR
query:
This way of searching still keeps the highest precision and no
false positives. (Assuming there are no other authors whose names are
spelled Ellis, J or Ellis, John, an assumption that
is often false*.) The search is
fast.
- To match all of the above forms in a single search term, you can
try to use a wildcard query:
It would match all author names that start by the text
Ellis, J
, i.e. not only the wanted forms Ellis,
J and Ellis, John, but also Ellis, Jim, or
Ellis, John Rolfe, or Ellis, Jonathan Richard.
This way of searching returns you more results, which may be
suitable in case you don't know how the names are spelled in the
database. But you also risk the eventuality of getting false
positives. The search is relatively fast.
- Yet another, the most general alternative is to use a partial
phrase matching:
It would find not only all the authors mentioned above, but also
the ones whose names contain the expression Ellis, J
anywhere inside the name, such as De Lellis, Jim. It thus
gives you the largest possible number of hits at the largest risk of
false positives. The search is relatively slow.
(Note though that this way of searching may be very handy in case
of compound family names such Pepe-Altarelli, M or 't
Hooft, G where a casual user query for Hooft, G would
match the wanted author, unlike the methods mentioned above.)
- Finally, let us note that you can use the regular
expression syntax to construct any complex author query. A simple
example is to search for an author expressed in the database as either
Ellis, J or Ellis, John:
Please consult regular expression searching tips
to know more about regular expression search possibilities.
*NOTE:
If you produce your own list of publications and you notice that
sometimes your first name is spelled abbreviated and sometimes in
full, or if you want to identify your publications among several
authors with the same abbreviation, please contact the administrators of so that
they could work with you on inputting a consistently spelled and
properly formatted first name everywhere. Only the consistent
database content will ensure a proper author searching behaviour.
This way of searching gives you the highest precision and no false
positives. (Assuming there are no other authors whose names are
spelled Ellis, J, an assumption that is often false*.) The search is very fast.
- Sometimes an author's first name may be spelled abbreviated on
some documents (such as Ellis, J) and sometimes full on
others (such as Ellis, John; eventually also with the middle
name: Ellis, John Rolfe). To get the list of publications
for all these forms at the same time, you could use a boolean OR
query:
This way of searching still keeps the highest precision and no
false positives. (Assuming there are no other authors whose names are
spelled Ellis, J or Ellis, John, an assumption that
is often false*.) The search is
fast.
- To match all of the above forms in a single search term, you can
try to use a wildcard query:
It would match all author names that start by the text
Ellis, J
, i.e. not only the wanted forms Ellis,
J and Ellis, John, but also Ellis, Jim, or
Ellis, John Rolfe, or Ellis, Jonathan Richard.
This way of searching returns you more results, which may be
suitable in case you don't know how the names are spelled in the
database. But you also risk the eventuality of getting false
positives. The search is relatively fast.
- Yet another, the most general alternative is to use a partial
phrase matching:
It would find not only all the authors mentioned above, but also
the ones whose names contain the expression Ellis, J
anywhere inside the name, such as De Lellis, Jim. It thus
gives you the largest possible number of hits at the largest risk of
false positives. The search is relatively slow.
(Note though that this way of searching may be very handy in case
of compound family names such Pepe-Altarelli, M or 't
Hooft, G where a casual user query for Hooft, G would
match the wanted author, unlike the methods mentioned above.)
- Finally, let us note that you can use the regular
expression syntax to construct any complex author query. A simple
example is to search for an author expressed in the database as either
Ellis, J or Ellis, John:
Please consult regular expression searching tips
to know more about regular expression search possibilities.
*NOTE:
If you produce your own list of publications and you notice that
sometimes your first name is spelled abbreviated and sometimes in
full, or if you want to identify your publications among several
authors with the same abbreviation, please contact the administrators of so that
they could work with you on inputting a consistently spelled and
properly formatted first name everywhere. Only the consistent
database content will ensure a proper author searching behaviour.
This way of searching gives you the highest precision and no false
positives. (Assuming there are no other authors whose names are
spelled Ellis, J, an assumption that is often false*.) The search is very fast.
- Sometimes an author's first name may be spelled abbreviated on
some documents (such as Ellis, J) and sometimes full on
others (such as Ellis, John; eventually also with the middle
name: Ellis, John Rolfe). To get the list of publications
for all these forms at the same time, you could use a boolean OR
query:
This way of searching still keeps the highest precision and no
false positives. (Assuming there are no other authors whose names are
spelled Ellis, J or Ellis, John, an assumption that
is often false*.) The search is
fast.
- To match all of the above forms in a single search term, you can
try to use a wildcard query:
It would match all author names that start by the text
Ellis, J
, i.e. not only the wanted forms Ellis,
J and Ellis, John, but also Ellis, Jim, or
Ellis, John Rolfe, or Ellis, Jonathan Richard.
This way of searching returns you more results, which may be
suitable in case you don't know how the names are spelled in the
database. But you also risk the eventuality of getting false
positives. The search is relatively fast.
- Yet another, the most general alternative is to use a partial
phrase matching:
It would find not only all the authors mentioned above, but also
the ones whose names contain the expression Ellis, J
anywhere inside the name, such as De Lellis, Jim. It thus
gives you the largest possible number of hits at the largest risk of
false positives. The search is relatively slow.
(Note though that this way of searching may be very handy in case
of compound family names such Pepe-Altarelli, M or 't
Hooft, G where a casual user query for Hooft, G would
match the wanted author, unlike the methods mentioned above.)
- Finally, let us note that you can use the regular
expression syntax to construct any complex author query. A simple
example is to search for an author expressed in the database as either
Ellis, J or Ellis, John:
Please consult regular expression searching tips
to know more about regular expression search possibilities.
*NOTE:
If you produce your own list of publications and you notice that
sometimes your first name is spelled abbreviated and sometimes in
full, or if you want to identify your publications among several
authors with the same abbreviation, please contact the administrators of so that
they could work with you on inputting a consistently spelled and
properly formatted first name everywhere. Only the consistent
database content will ensure a proper author searching behaviour.
This way of searching gives you the highest precision and no false
positives. (Assuming there are no other authors whose names are
spelled Ellis, J, an assumption that is often false*.) The search is very fast.
- Sometimes an author's first name may be spelled abbreviated on
some documents (such as Ellis, J) and sometimes full on
others (such as Ellis, John; eventually also with the middle
name: Ellis, John Rolfe). To get the list of publications
for all these forms at the same time, you could use a boolean OR
query:
This way of searching still keeps the highest precision and no
false positives. (Assuming there are no other authors whose names are
spelled Ellis, J or Ellis, John, an assumption that
is often false*.) The search is
fast.
- To match all of the above forms in a single search term, you can
try to use a wildcard query:
It would match all author names that start by the text
Ellis, J
, i.e. not only the wanted forms Ellis,
J and Ellis, John, but also Ellis, Jim, or
Ellis, John Rolfe, or Ellis, Jonathan Richard.
This way of searching returns you more results, which may be
suitable in case you don't know how the names are spelled in the
database. But you also risk the eventuality of getting false
positives. The search is relatively fast.
- Yet another, the most general alternative is to use a partial
phrase matching:
It would find not only all the authors mentioned above, but also
the ones whose names contain the expression Ellis, J
anywhere inside the name, such as De Lellis, Jim. It thus
gives you the largest possible number of hits at the largest risk of
false positives. The search is relatively slow.
(Note though that this way of searching may be very handy in case
of compound family names such Pepe-Altarelli, M or 't
Hooft, G where a casual user query for Hooft, G would
match the wanted author, unlike the methods mentioned above.)
- Finally, let us note that you can use the regular
expression syntax to construct any complex author query. A simple
example is to search for an author expressed in the database as either
Ellis, J or Ellis, John:
Please consult regular expression searching tips
to know more about regular expression search possibilities.
*NOTE:
If you produce your own list of publications and you notice that
sometimes your first name is spelled abbreviated and sometimes in
full, or if you want to identify your publications among several
authors with the same abbreviation, please contact the administrators of so that
they could work with you on inputting a consistently spelled and
properly formatted first name everywhere. Only the consistent
database content will ensure a proper author searching behaviour.
This way of searching gives you the highest precision and no false
positives. (Assuming there are no other authors whose names are
spelled Ellis, J, an assumption that is often false*.) The search is very fast.
- Sometimes an author's first name may be spelled abbreviated on
some documents (such as Ellis, J) and sometimes full on
others (such as Ellis, John; eventually also with the middle
name: Ellis, John Rolfe). To get the list of publications
for all these forms at the same time, you could use a boolean OR
query:
This way of searching still keeps the highest precision and no
false positives. (Assuming there are no other authors whose names are
spelled Ellis, J or Ellis, John, an assumption that
is often false*.) The search is
fast.
- To match all of the above forms in a single search term, you can
try to use a wildcard query:
It would match all author names that start by the text
Ellis, J
, i.e. not only the wanted forms Ellis,
J and Ellis, John, but also Ellis, Jim, or
Ellis, John Rolfe, or Ellis, Jonathan Richard.
This way of searching returns you more results, which may be
suitable in case you don't know how the names are spelled in the
database. But you also risk the eventuality of getting false
positives. The search is relatively fast.
- Yet another, the most general alternative is to use a partial
phrase matching:
It would find not only all the authors mentioned above, but also
the ones whose names contain the expression Ellis, J
anywhere inside the name, such as De Lellis, Jim. It thus
gives you the largest possible number of hits at the largest risk of
false positives. The search is relatively slow.
(Note though that this way of searching may be very handy in case
of compound family names such Pepe-Altarelli, M or 't
Hooft, G where a casual user query for Hooft, G would
match the wanted author, unlike the methods mentioned above.)
- Finally, let us note that you can use the regular
expression syntax to construct any complex author query. A simple
example is to search for an author expressed in the database as either
Ellis, J or Ellis, John:
Please consult regular expression searching tips
to know more about regular expression search possibilities.
*NOTE:
If you produce your own list of publications and you notice that
sometimes your first name is spelled abbreviated and sometimes in
full, or if you want to identify your publications among several
authors with the same abbreviation, please contact the administrators of so that
they could work with you on inputting a consistently spelled and
properly formatted first name everywhere. Only the consistent
database content will ensure a proper author searching behaviour.
This way of searching gives you the highest precision and no false
positives. (Assuming there are no other authors whose names are
spelled Ellis, J, an assumption that is often false*.) The search is very fast.
- Sometimes an author's first name may be spelled abbreviated on
some documents (such as Ellis, J) and sometimes full on
others (such as Ellis, John; eventually also with the middle
name: Ellis, John Rolfe). To get the list of publications
for all these forms at the same time, you could use a boolean OR
query:
This way of searching still keeps the highest precision and no
false positives. (Assuming there are no other authors whose names are
spelled Ellis, J or Ellis, John, an assumption that
is often false*.) The search is
fast.
- To match all of the above forms in a single search term, you can
try to use a wildcard query:
It would match all author names that start by the text
Ellis, J
, i.e. not only the wanted forms Ellis,
J and Ellis, John, but also Ellis, Jim, or
Ellis, John Rolfe, or Ellis, Jonathan Richard.
This way of searching returns you more results, which may be
suitable in case you don't know how the names are spelled in the
database. But you also risk the eventuality of getting false
positives. The search is relatively fast.
- Yet another, the most general alternative is to use a partial
phrase matching:
It would find not only all the authors mentioned above, but also
the ones whose names contain the expression Ellis, J
anywhere inside the name, such as De Lellis, Jim. It thus
gives you the largest possible number of hits at the largest risk of
false positives. The search is relatively slow.
(Note though that this way of searching may be very handy in case
of compound family names such Pepe-Altarelli, M or 't
Hooft, G where a casual user query for Hooft, G would
match the wanted author, unlike the methods mentioned above.)
- Finally, let us note that you can use the regular
expression syntax to construct any complex author query. A simple
example is to search for an author expressed in the database as either
Ellis, J or Ellis, John:
Please consult regular expression searching tips
to know more about regular expression search possibilities.
*NOTE:
If you produce your own list of publications and you notice that
sometimes your first name is spelled abbreviated and sometimes in
full, or if you want to identify your publications among several
authors with the same abbreviation, please contact the administrators of so that
they could work with you on inputting a consistently spelled and
properly formatted first name everywhere. Only the consistent
database content will ensure a proper author searching behaviour.
This way of searching gives you the highest precision and no false
positives. (Assuming there are no other authors whose names are
spelled Ellis, J, an assumption that is often false*.) The search is very fast.
- Sometimes an author's first name may be spelled abbreviated on
some documents (such as Ellis, J) and sometimes full on
others (such as Ellis, John; eventually also with the middle
name: Ellis, John Rolfe). To get the list of publications
for all these forms at the same time, you could use a boolean OR
query:
This way of searching still keeps the highest precision and no
false positives. (Assuming there are no other authors whose names are
spelled Ellis, J or Ellis, John, an assumption that
is often false*.) The search is
fast.
- To match all of the above forms in a single search term, you can
try to use a wildcard query:
It would match all author names that start by the text
Ellis, J
, i.e. not only the wanted forms Ellis,
J and Ellis, John, but also Ellis, Jim, or
Ellis, John Rolfe, or Ellis, Jonathan Richard.
This way of searching returns you more results, which may be
suitable in case you don't know how the names are spelled in the
database. But you also risk the eventuality of getting false
positives. The search is relatively fast.
- Yet another, the most general alternative is to use a partial
phrase matching:
It would find not only all the authors mentioned above, but also
the ones whose names contain the expression Ellis, J
anywhere inside the name, such as De Lellis, Jim. It thus
gives you the largest possible number of hits at the largest risk of
false positives. The search is relatively slow.
(Note though that this way of searching may be very handy in case
of compound family names such Pepe-Altarelli, M or 't
Hooft, G where a casual user query for Hooft, G would
match the wanted author, unlike the methods mentioned above.)
- Finally, let us note that you can use the regular
expression syntax to construct any complex author query. A simple
example is to search for an author expressed in the database as either
Ellis, J or Ellis, John:
Please consult regular expression searching tips
to know more about regular expression search possibilities.
*NOTE:
If you produce your own list of publications and you notice that
sometimes your first name is spelled abbreviated and sometimes in
full, or if you want to identify your publications among several
authors with the same abbreviation, please contact the administrators of so that
they could work with you on inputting a consistently spelled and
properly formatted first name everywhere. Only the consistent
database content will ensure a proper author searching behaviour.
This way of searching gives you the highest precision and no false
positives. (Assuming there are no other authors whose names are
spelled Ellis, J, an assumption that is often false*.) The search is very fast.
- Sometimes an author's first name may be spelled abbreviated on
some documents (such as Ellis, J) and sometimes full on
others (such as Ellis, John; eventually also with the middle
name: Ellis, John Rolfe). To get the list of publications
for all these forms at the same time, you could use a boolean OR
query:
This way of searching still keeps the highest precision and no
false positives. (Assuming there are no other authors whose names are
spelled Ellis, J or Ellis, John, an assumption that
is often false*.) The search is
fast.
- To match all of the above forms in a single search term, you can
try to use a wildcard query:
It would match all author names that start by the text
Ellis, J
, i.e. not only the wanted forms Ellis,
J and Ellis, John, but also Ellis, Jim, or
Ellis, John Rolfe, or Ellis, Jonathan Richard.
This way of searching returns you more results, which may be
suitable in case you don't know how the names are spelled in the
database. But you also risk the eventuality of getting false
positives. The search is relatively fast.
- Yet another, the most general alternative is to use a partial
phrase matching:
It would find not only all the authors mentioned above, but also
the ones whose names contain the expression Ellis, J
anywhere inside the name, such as De Lellis, Jim. It thus
gives you the largest possible number of hits at the largest risk of
false positives. The search is relatively slow.
(Note though that this way of searching may be very handy in case
of compound family names such Pepe-Altarelli, M or 't
Hooft, G where a casual user query for Hooft, G would
match the wanted author, unlike the methods mentioned above.)
- Finally, let us note that you can use the regular
expression syntax to construct any complex author query. A simple
example is to search for an author expressed in the database as either
Ellis, J or Ellis, John:
Please consult regular expression searching tips
to know more about regular expression search possibilities.
*NOTE:
If you produce your own list of publications and you notice that
sometimes your first name is spelled abbreviated and sometimes in
full, or if you want to identify your publications among several
authors with the same abbreviation, please contact the administrators of so that
they could work with you on inputting a consistently spelled and
properly formatted first name everywhere. Only the consistent
database content will ensure a proper author searching behaviour.
This way of searching gives you the highest precision and no false
positives. (Assuming there are no other authors whose names are
spelled Ellis, J, an assumption that is often false*.) The search is very fast.
- Sometimes an author's first name may be spelled abbreviated on
some documents (such as Ellis, J) and sometimes full on
others (such as Ellis, John; eventually also with the middle
name: Ellis, John Rolfe). To get the list of publications
for all these forms at the same time, you could use a boolean OR
query:
This way of searching still keeps the highest precision and no
false positives. (Assuming there are no other authors whose names are
spelled Ellis, J or Ellis, John, an assumption that
is often false*.) The search is
fast.
- To match all of the above forms in a single search term, you can
try to use a wildcard query:
It would match all author names that start by the text
Ellis, J
, i.e. not only the wanted forms Ellis,
J and Ellis, John, but also Ellis, Jim, or
Ellis, John Rolfe, or Ellis, Jonathan Richard.
This way of searching returns you more results, which may be
suitable in case you don't know how the names are spelled in the
database. But you also risk the eventuality of getting false
positives. The search is relatively fast.
- Yet another, the most general alternative is to use a partial
phrase matching:
It would find not only all the authors mentioned above, but also
the ones whose names contain the expression Ellis, J
anywhere inside the name, such as De Lellis, Jim. It thus
gives you the largest possible number of hits at the largest risk of
false positives. The search is relatively slow.
(Note though that this way of searching may be very handy in case
of compound family names such Pepe-Altarelli, M or 't
Hooft, G where a casual user query for Hooft, G would
match the wanted author, unlike the methods mentioned above.)
- Finally, let us note that you can use the regular
expression syntax to construct any complex author query. A simple
example is to search for an author expressed in the database as either
Ellis, J or Ellis, John:
Please consult regular expression searching tips
to know more about regular expression search possibilities.
*NOTE:
If you produce your own list of publications and you notice that
sometimes your first name is spelled abbreviated and sometimes in
full, or if you want to identify your publications among several
authors with the same abbreviation, please contact the administrators of so that
they could work with you on inputting a consistently spelled and
properly formatted first name everywhere. Only the consistent
database content will ensure a proper author searching behaviour.
This way of searching gives you the highest precision and no false
positives. (Assuming there are no other authors whose names are
spelled Ellis, J, an assumption that is often false*.) The search is very fast.
- Sometimes an author's first name may be spelled abbreviated on
some documents (such as Ellis, J) and sometimes full on
others (such as Ellis, John; eventually also with the middle
name: Ellis, John Rolfe). To get the list of publications
for all these forms at the same time, you could use a boolean OR
query:
This way of searching still keeps the highest precision and no
false positives. (Assuming there are no other authors whose names are
spelled Ellis, J or Ellis, John, an assumption that
is often false*.) The search is
fast.
- To match all of the above forms in a single search term, you can
try to use a wildcard query:
It would match all author names that start by the text
Ellis, J
, i.e. not only the wanted forms Ellis,
J and Ellis, John, but also Ellis, Jim, or
Ellis, John Rolfe, or Ellis, Jonathan Richard.
This way of searching returns you more results, which may be
suitable in case you don't know how the names are spelled in the
database. But you also risk the eventuality of getting false
positives. The search is relatively fast.
- Yet another, the most general alternative is to use a partial
phrase matching:
It would find not only all the authors mentioned above, but also
the ones whose names contain the expression Ellis, J
anywhere inside the name, such as De Lellis, Jim. It thus
gives you the largest possible number of hits at the largest risk of
false positives. The search is relatively slow.
(Note though that this way of searching may be very handy in case
of compound family names such Pepe-Altarelli, M or 't
Hooft, G where a casual user query for Hooft, G would
match the wanted author, unlike the methods mentioned above.)
- Finally, let us note that you can use the regular
expression syntax to construct any complex author query. A simple
example is to search for an author expressed in the database as either
Ellis, J or Ellis, John:
Please consult regular expression searching tips
to know more about regular expression search possibilities.
*NOTE:
If you produce your own list of publications and you notice that
sometimes your first name is spelled abbreviated and sometimes in
full, or if you want to identify your publications among several
authors with the same abbreviation, please contact the administrators of so that
they could work with you on inputting a consistently spelled and
properly formatted first name everywhere. Only the consistent
database content will ensure a proper author searching behaviour.
This way of searching gives you the highest precision and no false
positives. (Assuming there are no other authors whose names are
spelled Ellis, J, an assumption that is often false*.) The search is very fast.
- Sometimes an author's first name may be spelled abbreviated on
some documents (such as Ellis, J) and sometimes full on
others (such as Ellis, John; eventually also with the middle
name: Ellis, John Rolfe). To get the list of publications
for all these forms at the same time, you could use a boolean OR
query:
This way of searching still keeps the highest precision and no
false positives. (Assuming there are no other authors whose names are
spelled Ellis, J or Ellis, John, an assumption that
is often false*.) The search is
fast.
- To match all of the above forms in a single search term, you can
try to use a wildcard query:
It would match all author names that start by the text
Ellis, J
, i.e. not only the wanted forms Ellis,
J and Ellis, John, but also Ellis, Jim, or
Ellis, John Rolfe, or Ellis, Jonathan Richard.
This way of searching returns you more results, which may be
suitable in case you don't know how the names are spelled in the
database. But you also risk the eventuality of getting false
positives. The search is relatively fast.
- Yet another, the most general alternative is to use a partial
phrase matching:
It would find not only all the authors mentioned above, but also
the ones whose names contain the expression Ellis, J
anywhere inside the name, such as De Lellis, Jim. It thus
gives you the largest possible number of hits at the largest risk of
false positives. The search is relatively slow.
(Note though that this way of searching may be very handy in case
of compound family names such Pepe-Altarelli, M or 't
Hooft, G where a casual user query for Hooft, G would
match the wanted author, unlike the methods mentioned above.)
- Finally, let us note that you can use the regular
expression syntax to construct any complex author query. A simple
example is to search for an author expressed in the database as either
Ellis, J or Ellis, John:
Please consult regular expression searching tips
to know more about regular expression search possibilities.
*NOTE:
If you produce your own list of publications and you notice that
sometimes your first name is spelled abbreviated and sometimes in
full, or if you want to identify your publications among several
authors with the same abbreviation, please contact the administrators of so that
they could work with you on inputting a consistently spelled and
properly formatted first name everywhere. Only the consistent
database content will ensure a proper author searching behaviour.
This way of searching gives you the highest precision and no false
positives. (Assuming there are no other authors whose names are
spelled Ellis, J, an assumption that is often false*.) The search is very fast.
- Sometimes an author's first name may be spelled abbreviated on
some documents (such as Ellis, J) and sometimes full on
others (such as Ellis, John; eventually also with the middle
name: Ellis, John Rolfe). To get the list of publications
for all these forms at the same time, you could use a boolean OR
query:
This way of searching still keeps the highest precision and no
false positives. (Assuming there are no other authors whose names are
spelled Ellis, J or Ellis, John, an assumption that
is often false*.) The search is
fast.
- To match all of the above forms in a single search term, you can
try to use a wildcard query:
It would match all author names that start by the text
Ellis, J
, i.e. not only the wanted forms Ellis,
J and Ellis, John, but also Ellis, Jim, or
Ellis, John Rolfe, or Ellis, Jonathan Richard.
This way of searching returns you more results, which may be
suitable in case you don't know how the names are spelled in the
database. But you also risk the eventuality of getting false
positives. The search is relatively fast.
- Yet another, the most general alternative is to use a partial
phrase matching:
It would find not only all the authors mentioned above, but also
the ones whose names contain the expression Ellis, J
anywhere inside the name, such as De Lellis, Jim. It thus
gives you the largest possible number of hits at the largest risk of
false positives. The search is relatively slow.
(Note though that this way of searching may be very handy in case
of compound family names such Pepe-Altarelli, M or 't
Hooft, G where a casual user query for Hooft, G would
match the wanted author, unlike the methods mentioned above.)
- Finally, let us note that you can use the regular
expression syntax to construct any complex author query. A simple
example is to search for an author expressed in the database as either
Ellis, J or Ellis, John:
Please consult regular expression searching tips
to know more about regular expression search possibilities.
*NOTE:
If you produce your own list of publications and you notice that
sometimes your first name is spelled abbreviated and sometimes in
full, or if you want to identify your publications among several
authors with the same abbreviation, please contact the administrators of so that
they could work with you on inputting a consistently spelled and
properly formatted first name everywhere. Only the consistent
database content will ensure a proper author searching behaviour.
This way of searching gives you the highest precision and no false
positives. (Assuming there are no other authors whose names are
spelled Ellis, J, an assumption that is often false*.) The search is very fast.
- Sometimes an author's first name may be spelled abbreviated on
some documents (such as Ellis, J) and sometimes full on
others (such as Ellis, John; eventually also with the middle
name: Ellis, John Rolfe). To get the list of publications
for all these forms at the same time, you could use a boolean OR
query:
This way of searching still keeps the highest precision and no
false positives. (Assuming there are no other authors whose names are
spelled Ellis, J or Ellis, John, an assumption that
is often false*.) The search is
fast.
- To match all of the above forms in a single search term, you can
try to use a wildcard query:
It would match all author names that start by the text
Ellis, J
, i.e. not only the wanted forms Ellis,
J and Ellis, John, but also Ellis, Jim, or
Ellis, John Rolfe, or Ellis, Jonathan Richard.
This way of searching returns you more results, which may be
suitable in case you don't know how the names are spelled in the
database. But you also risk the eventuality of getting false
positives. The search is relatively fast.
- Yet another, the most general alternative is to use a partial
phrase matching:
It would find not only all the authors mentioned above, but also
the ones whose names contain the expression Ellis, J
anywhere inside the name, such as De Lellis, Jim. It thus
gives you the largest possible number of hits at the largest risk of
false positives. The search is relatively slow.
(Note though that this way of searching may be very handy in case
of compound family names such Pepe-Altarelli, M or 't
Hooft, G where a casual user query for Hooft, G would
match the wanted author, unlike the methods mentioned above.)
- Finally, let us note that you can use the regular
expression syntax to construct any complex author query. A simple
example is to search for an author expressed in the database as either
Ellis, J or Ellis, John:
Please consult regular expression searching tips
to know more about regular expression search possibilities.
*NOTE:
If you produce your own list of publications and you notice that
sometimes your first name is spelled abbreviated and sometimes in
full, or if you want to identify your publications among several
authors with the same abbreviation, please contact the administrators of so that
they could work with you on inputting a consistently spelled and
properly formatted first name everywhere. Only the consistent
database content will ensure a proper author searching behaviour.
This way of searching gives you the highest precision and no false
positives. (Assuming there are no other authors whose names are
spelled Ellis, J, an assumption that is often false*.) The search is very fast.
- Sometimes an author's first name may be spelled abbreviated on
some documents (such as Ellis, J) and sometimes full on
others (such as Ellis, John; eventually also with the middle
name: Ellis, John Rolfe). To get the list of publications
for all these forms at the same time, you could use a boolean OR
query:
This way of searching still keeps the highest precision and no
false positives. (Assuming there are no other authors whose names are
spelled Ellis, J or Ellis, John, an assumption that
is often false*.) The search is
fast.
- To match all of the above forms in a single search term, you can
try to use a wildcard query:
It would match all author names that start by the text
Ellis, J
, i.e. not only the wanted forms Ellis,
J and Ellis, John, but also Ellis, Jim, or
Ellis, John Rolfe, or Ellis, Jonathan Richard.
This way of searching returns you more results, which may be
suitable in case you don't know how the names are spelled in the
database. But you also risk the eventuality of getting false
positives. The search is relatively fast.
- Yet another, the most general alternative is to use a partial
phrase matching:
It would find not only all the authors mentioned above, but also
the ones whose names contain the expression Ellis, J
anywhere inside the name, such as De Lellis, Jim. It thus
gives you the largest possible number of hits at the largest risk of
false positives. The search is relatively slow.
(Note though that this way of searching may be very handy in case
of compound family names such Pepe-Altarelli, M or 't
Hooft, G where a casual user query for Hooft, G would
match the wanted author, unlike the methods mentioned above.)
- Finally, let us note that you can use the regular
expression syntax to construct any complex author query. A simple
example is to search for an author expressed in the database as either
Ellis, J or Ellis, John:
Please consult regular expression searching tips
to know more about regular expression search possibilities.
*NOTE:
If you produce your own list of publications and you notice that
sometimes your first name is spelled abbreviated and sometimes in
full, or if you want to identify your publications among several
authors with the same abbreviation, please contact the administrators of so that
they could work with you on inputting a consistently spelled and
properly formatted first name everywhere. Only the consistent
database content will ensure a proper author searching behaviour.
Esta técnica de búsqueda confiere mayor precisión y evita falsos
resultados aparentemente positivos. (La presunción de que no existen
otros autores cuyo nombre se escriba como Ellis, J, en
ocasiones puede no ser cierta*.) La búsqueda se realizará
con mucha rapidez.
- Algunas veces, en algunos documentos, el nombre propio de un
autor se escribe de forma abreviada, (como Ellis, J) y otras
de forma completa (como Ellis, John; y en algunas ocasiones
también con el nombre compuesto:Ellis, John Rolfe). Para
obtener una lista de publicaciones del autor con todas sus formas en
una misma búsqueda, se puede utilizar el operador booleano O:
Este modo de búsqueda nos ofrece aún mayor precisión y evita falsos
resultados positivos (o no pertinentes). (La presunción de que no hay
más autores que se escriban como Ellis, J O Ellis,
John, en ocasiones puede no ser cierta *.) La búsqueda es muy
rápida.
- Para localizar todas las formas introducidas en el ejemplo
anterior con un único término de búsqueda, podemos probar de utilizar
una búsqueda con comodín:
Ello recuperará todos los nombres de autor que comienzan con el
texto Ellis, J
, no sólo con las formas requeridas en el
ejemplo Ellis, J y Ellis, John, sino también
Ellis, Jim, o Ellis, John Rolfe, o Ellis,
Jonathan Richard.
Esta búsqueda retornará muchos más resultados, pero puede resultar
conveniente en el caso en que se desconozca la forma de introducción
de los nombres en la base de datos. Sin embargo, aumenta el riesgo de
obtener resultados poco pertinentes. La búsqueda es relativamente rápida.
- Aparte de esta última, la alternativa general más utilizada es el
uso de una búsqueda por parte de la frase:
Esta búsqueda recupera no sólo todos los autores mencionados, sino
también todos aquellos cuyos nombres contengan la expresión
Ellis, J
en cualquier parte de su nombre, como por
ejemplo De Lellis, Jim. Ello aumenta enormemente las
posibilidades de obtener registros con un alto riesgo de ser poco
pertinentes. La búsqueda es relativamente lenta.
(Obsérvese que este modo de búsqueda puede resultar muy práctico
para apellidos compuestos tales como Pepe-Altarelli, M o
't Hooft, G en la que una consulta puntual de usuario por
Hooft, G recuperará el autor requerido, a diferencia de los
métodos mencionados anteriormente.)
- Finalmente, anotar que es posible utilizar la sintaxis de expresión regular para construir
consultas complejas para buscar por autor. Un ejemplo sencillo es la
búsqueda de un autor introducido en la base de datos tanto como
Ellis, J como Ellis, John:
Se recomienda la consulta de búsqueda por
expresiones regulares para conocer más acerca de las posibilidades
de este modo de búsqueda.
*NOTA:
Si es autor de su propia lista de publicaciones y detecta que algunas
veces su nombre se escribe de forma abreviada y a veces completo, o si
desea identificar sus publicaciones entre diversos autores con la
misma forma abreviada, por favor contacte con losadministradores de que
trataran de trabajar conjuntamente para implementar una forma
consistente y normalizada de introducción de su nombre en toda la base
de datos. Sólo una base de datos con contenido consistente puede
garantizar una búqueda por autores exitosa.
Aquesta tècnica de cerca confereix major grau de precisió i evita falsos
resultats aparentement positius. (La presumpció de que no existeixen
altres autores els noms dels quals s’escrigui com Ellis, J, en
ocasions pot no ser certa*.) La cerca es realitzarà
con amb molta rapidesa.
- Algunes vegadess, en alguns documents, el nom propi d’un
autor s’escriu de forma abreujada, (com Ellis, J) i altres
de forma completa (com Ellis, John; i en altres ocasions
també amb el nom compost:Ellis, John Rolfe). Per
obtenir una llista de publicacions de l’autor amb totes les seves formes en
una mateixa cerca, es pot utilitzar l’operador booleà O:
Aquest mode de cerca ens ofereix encara major grau de precisió i
evita falsos resultats positius (o no pertinents). (La presumpció de
que no hi ha més autors que s’escriguin com Ellis, J O
Ellis, John, en ocasions pot no ser certa *.) La cerca és molt ràpida.
- Per localitzar totes les formes introduïdes a l’exemple anterior
amb un únic terme de cerca, podem provar d’emprar una cerca amb
comodí:
Això recuperarà tots els noms d’autor que comencen amb el text
Ellis, J
, no només amb les formes requerides a l’exemple
Ellis, J i Ellis, John, sinó també Ellis,
Jim, o Ellis, John Rolfe, o Ellis,Jonathan
Richard.
Aquesta cerca retornarà molts més resultats, però pot resultar
convenient en el cas que es desconegui la forma d’introducció dels
noms a la base de dades. Ara bé, augmenta el risc d’obtenir resultats
poc pertinents. La cerca és relativament ràpida.
- Apart d’aquesta darrera, l’alternativa general més emprada és la
cerca per part de la frase:
Aquesta cerca recupera no només tots els autors mencionats, sinó
també tots aquells els noms dels quals continguin l’expresió
Ellis, J
a qualsevol part del seu nom, com per exemple
De Lellis, Jim. Això augmenta enormement les possibilitats
d’obtenir registres amb un alt risc de ser poc pertinents. La cerca
és relativament lenta.
(Observis que aquest mode de cerca pot resultar molt pràctic per a
cognoms compostos, tals com Pepe-Altarelli, M o 't Hooft,
G en els que una consulta d’una consulta puntual de usuario por
Hooft, G recuperarà l’autor requerit, a diferència dels
mètodes mencionats anteriorment.)
- Finalment, anotar que es possible emprar la sintaxi de expressió regular per construir
consultes complexes per fer cerques per autor. Un exemple senzill és
la cerca d’un autor introduït a la base de dades tant per Ellis,
J com per Ellis, John:
Es recomana la consulta de cerca per expressions
regulars per conèixer més sobre les possibilitats d’aquest mode de
cerca.
*NOTA:
Si es autor de la seva pròpia llista de publicacions i detecta que
algunes vegades el seu nom s’escriu de forma abreujada i de vegades
complet, o si desitja identificar les seves publicacions entre
diversos autors amb la mateixa forma abreujada, sis plau, contacti amb
els administradors de
que tractaran de treballar-hi conjuntament per implementar una forma
consistent i normalitzada d’introducció del seu nom a tota la base de
dades. Només una base de dades amb contingut consistent pot garantir
una cerca per autors exitosa.
You may select a certain field according to which sort the search
results, for example to sort the results by main title. However,
sometimes you may want to sort by a report number and it happens
that your documents have several of them. For example, the report
numbers hep-ph/0204140, CERN-TH-2002-069 and
RM3-TH-02-4 all denote the
same document. Now if you sort your search results set
containing this document, the system will take into consideration
the first report number, that may be either of these three.
Sometimes you may want to classify this document under its
hep-ph number, sometimes under its CERN number,
depending on whether you produce a list of CERN or hep-ph
publications. How can you influence the search engine to prefer
one report number rather than the other?
In other words, the search engine by default answers a query
like "sort by first author" or "sort by first report number", but
sometimes you may want to ask the search engine to "sort by first
report number that starts by the text CERN-". The latter
possibility is available via a "silent" sort parameter called
sp
(for "sort pattern") that sorts preferentially
according to the given textual pattern if they can be found. The
parameter is "silent" in a way that it is not present in the search
interface, you have to add it manually to your search URL.
For example, to get all CERN-TH publications of the year 2001
sorted by their CERN-TH numbers, you would search for
CERN-TH-2001*
within reportnumber
index,
and on the search results page, being satisfied with the results,
you would add &sp=CERN-TH
to the URL to sort the
results preferentially by CERN-TH report numbers, to get a nicely
sorted list of all CERN-TH 2001 publications.
You may select a certain field according to which sort the search
results, for example to sort the results by main title. However,
sometimes you may want to sort by a report number and it happens
that your documents have several of them. For example, the report
numbers hep-ph/0204140, CERN-TH-2002-069 and
RM3-TH-02-4 all denote the
same document. Now if you sort your search results set
containing this document, the system will take into consideration
the first report number, that may be either of these three.
Sometimes you may want to classify this document under its
hep-ph number, sometimes under its CERN number,
depending on whether you produce a list of CERN or hep-ph
publications. How can you influence the search engine to prefer
one report number rather than the other?
In other words, the search engine by default answers a query
like "sort by first author" or "sort by first report number", but
sometimes you may want to ask the search engine to "sort by first
report number that starts by the text CERN-". The latter
possibility is available via a "silent" sort parameter called
sp
(for "sort pattern") that sorts preferentially
according to the given textual pattern if they can be found. The
parameter is "silent" in a way that it is not present in the search
interface, you have to add it manually to your search URL.
For example, to get all CERN-TH publications of the year 2001
sorted by their CERN-TH numbers, you would search for
CERN-TH-2001*
within reportnumber
index,
and on the search results page, being satisfied with the results,
you would add &sp=CERN-TH
to the URL to sort the
results preferentially by CERN-TH report numbers, to get a nicely
sorted list of all CERN-TH 2001 publications.
You may select a certain field according to which sort the search
results, for example to sort the results by main title. However,
sometimes you may want to sort by a report number and it happens
that your documents have several of them. For example, the report
numbers hep-ph/0204140, CERN-TH-2002-069 and
RM3-TH-02-4 all denote the
same document. Now if you sort your search results set
containing this document, the system will take into consideration
the first report number, that may be either of these three.
Sometimes you may want to classify this document under its
hep-ph number, sometimes under its CERN number,
depending on whether you produce a list of CERN or hep-ph
publications. How can you influence the search engine to prefer
one report number rather than the other?
In other words, the search engine by default answers a query
like "sort by first author" or "sort by first report number", but
sometimes you may want to ask the search engine to "sort by first
report number that starts by the text CERN-". The latter
possibility is available via a "silent" sort parameter called
sp
(for "sort pattern") that sorts preferentially
according to the given textual pattern if they can be found. The
parameter is "silent" in a way that it is not present in the search
interface, you have to add it manually to your search URL.
For example, to get all CERN-TH publications of the year 2001
sorted by their CERN-TH numbers, you would search for
CERN-TH-2001*
within reportnumber
index,
and on the search results page, being satisfied with the results,
you would add &sp=CERN-TH
to the URL to sort the
results preferentially by CERN-TH report numbers, to get a nicely
sorted list of all CERN-TH 2001 publications.
You may select a certain field according to which sort the search
results, for example to sort the results by main title. However,
sometimes you may want to sort by a report number and it happens
that your documents have several of them. For example, the report
numbers hep-ph/0204140, CERN-TH-2002-069 and
RM3-TH-02-4 all denote the
same document. Now if you sort your search results set
containing this document, the system will take into consideration
the first report number, that may be either of these three.
Sometimes you may want to classify this document under its
hep-ph number, sometimes under its CERN number,
depending on whether you produce a list of CERN or hep-ph
publications. How can you influence the search engine to prefer
one report number rather than the other?
In other words, the search engine by default answers a query
like "sort by first author" or "sort by first report number", but
sometimes you may want to ask the search engine to "sort by first
report number that starts by the text CERN-". The latter
possibility is available via a "silent" sort parameter called
sp
(for "sort pattern") that sorts preferentially
according to the given textual pattern if they can be found. The
parameter is "silent" in a way that it is not present in the search
interface, you have to add it manually to your search URL.
For example, to get all CERN-TH publications of the year 2001
sorted by their CERN-TH numbers, you would search for
CERN-TH-2001*
within reportnumber
index,
and on the search results page, being satisfied with the results,
you would add &sp=CERN-TH
to the URL to sort the
results preferentially by CERN-TH report numbers, to get a nicely
sorted list of all CERN-TH 2001 publications.
You may select a certain field according to which sort the search
results, for example to sort the results by main title. However,
sometimes you may want to sort by a report number and it happens
that your documents have several of them. For example, the report
numbers hep-ph/0204140, CERN-TH-2002-069 and
RM3-TH-02-4 all denote the
same document. Now if you sort your search results set
containing this document, the system will take into consideration
the first report number, that may be either of these three.
Sometimes you may want to classify this document under its
hep-ph number, sometimes under its CERN number,
depending on whether you produce a list of CERN or hep-ph
publications. How can you influence the search engine to prefer
one report number rather than the other?
In other words, the search engine by default answers a query
like "sort by first author" or "sort by first report number", but
sometimes you may want to ask the search engine to "sort by first
report number that starts by the text CERN-". The latter
possibility is available via a "silent" sort parameter called
sp
(for "sort pattern") that sorts preferentially
according to the given textual pattern if they can be found. The
parameter is "silent" in a way that it is not present in the search
interface, you have to add it manually to your search URL.
For example, to get all CERN-TH publications of the year 2001
sorted by their CERN-TH numbers, you would search for
CERN-TH-2001*
within reportnumber
index,
and on the search results page, being satisfied with the results,
you would add &sp=CERN-TH
to the URL to sort the
results preferentially by CERN-TH report numbers, to get a nicely
sorted list of all CERN-TH 2001 publications.
You may select a certain field according to which sort the search
results, for example to sort the results by main title. However,
sometimes you may want to sort by a report number and it happens
that your documents have several of them. For example, the report
numbers hep-ph/0204140, CERN-TH-2002-069 and
RM3-TH-02-4 all denote the
same document. Now if you sort your search results set
containing this document, the system will take into consideration
the first report number, that may be either of these three.
Sometimes you may want to classify this document under its
hep-ph number, sometimes under its CERN number,
depending on whether you produce a list of CERN or hep-ph
publications. How can you influence the search engine to prefer
one report number rather than the other?
In other words, the search engine by default answers a query
like "sort by first author" or "sort by first report number", but
sometimes you may want to ask the search engine to "sort by first
report number that starts by the text CERN-". The latter
possibility is available via a "silent" sort parameter called
sp
(for "sort pattern") that sorts preferentially
according to the given textual pattern if they can be found. The
parameter is "silent" in a way that it is not present in the search
interface, you have to add it manually to your search URL.
For example, to get all CERN-TH publications of the year 2001
sorted by their CERN-TH numbers, you would search for
CERN-TH-2001*
within reportnumber
index,
and on the search results page, being satisfied with the results,
you would add &sp=CERN-TH
to the URL to sort the
results preferentially by CERN-TH report numbers, to get a nicely
sorted list of all CERN-TH 2001 publications.
You may select a certain field according to which sort the search
results, for example to sort the results by main title. However,
sometimes you may want to sort by a report number and it happens
that your documents have several of them. For example, the report
numbers hep-ph/0204140, CERN-TH-2002-069 and
RM3-TH-02-4 all denote the
same document. Now if you sort your search results set
containing this document, the system will take into consideration
the first report number, that may be either of these three.
Sometimes you may want to classify this document under its
hep-ph number, sometimes under its CERN number,
depending on whether you produce a list of CERN or hep-ph
publications. How can you influence the search engine to prefer
one report number rather than the other?
In other words, the search engine by default answers a query
like "sort by first author" or "sort by first report number", but
sometimes you may want to ask the search engine to "sort by first
report number that starts by the text CERN-". The latter
possibility is available via a "silent" sort parameter called
sp
(for "sort pattern") that sorts preferentially
according to the given textual pattern if they can be found. The
parameter is "silent" in a way that it is not present in the search
interface, you have to add it manually to your search URL.
For example, to get all CERN-TH publications of the year 2001
sorted by their CERN-TH numbers, you would search for
CERN-TH-2001*
within reportnumber
index,
and on the search results page, being satisfied with the results,
you would add &sp=CERN-TH
to the URL to sort the
results preferentially by CERN-TH report numbers, to get a nicely
sorted list of all CERN-TH 2001 publications.
You may select a certain field according to which sort the search
results, for example to sort the results by main title. However,
sometimes you may want to sort by a report number and it happens
that your documents have several of them. For example, the report
numbers hep-ph/0204140, CERN-TH-2002-069 and
RM3-TH-02-4 all denote the
same document. Now if you sort your search results set
containing this document, the system will take into consideration
the first report number, that may be either of these three.
Sometimes you may want to classify this document under its
hep-ph number, sometimes under its CERN number,
depending on whether you produce a list of CERN or hep-ph
publications. How can you influence the search engine to prefer
one report number rather than the other?
In other words, the search engine by default answers a query
like "sort by first author" or "sort by first report number", but
sometimes you may want to ask the search engine to "sort by first
report number that starts by the text CERN-". The latter
possibility is available via a "silent" sort parameter called
sp
(for "sort pattern") that sorts preferentially
according to the given textual pattern if they can be found. The
parameter is "silent" in a way that it is not present in the search
interface, you have to add it manually to your search URL.
For example, to get all CERN-TH publications of the year 2001
sorted by their CERN-TH numbers, you would search for
CERN-TH-2001*
within reportnumber
index,
and on the search results page, being satisfied with the results,
you would add &sp=CERN-TH
to the URL to sort the
results preferentially by CERN-TH report numbers, to get a nicely
sorted list of all CERN-TH 2001 publications.
You may select a certain field according to which sort the search
results, for example to sort the results by main title. However,
sometimes you may want to sort by a report number and it happens
that your documents have several of them. For example, the report
numbers hep-ph/0204140, CERN-TH-2002-069 and
RM3-TH-02-4 all denote the
same document. Now if you sort your search results set
containing this document, the system will take into consideration
the first report number, that may be either of these three.
Sometimes you may want to classify this document under its
hep-ph number, sometimes under its CERN number,
depending on whether you produce a list of CERN or hep-ph
publications. How can you influence the search engine to prefer
one report number rather than the other?
In other words, the search engine by default answers a query
like "sort by first author" or "sort by first report number", but
sometimes you may want to ask the search engine to "sort by first
report number that starts by the text CERN-". The latter
possibility is available via a "silent" sort parameter called
sp
(for "sort pattern") that sorts preferentially
according to the given textual pattern if they can be found. The
parameter is "silent" in a way that it is not present in the search
interface, you have to add it manually to your search URL.
For example, to get all CERN-TH publications of the year 2001
sorted by their CERN-TH numbers, you would search for
CERN-TH-2001*
within reportnumber
index,
and on the search results page, being satisfied with the results,
you would add &sp=CERN-TH
to the URL to sort the
results preferentially by CERN-TH report numbers, to get a nicely
sorted list of all CERN-TH 2001 publications.
You may select a certain field according to which sort the search
results, for example to sort the results by main title. However,
sometimes you may want to sort by a report number and it happens
that your documents have several of them. For example, the report
numbers hep-ph/0204140, CERN-TH-2002-069 and
RM3-TH-02-4 all denote the
same document. Now if you sort your search results set
containing this document, the system will take into consideration
the first report number, that may be either of these three.
Sometimes you may want to classify this document under its
hep-ph number, sometimes under its CERN number,
depending on whether you produce a list of CERN or hep-ph
publications. How can you influence the search engine to prefer
one report number rather than the other?
In other words, the search engine by default answers a query
like "sort by first author" or "sort by first report number", but
sometimes you may want to ask the search engine to "sort by first
report number that starts by the text CERN-". The latter
possibility is available via a "silent" sort parameter called
sp
(for "sort pattern") that sorts preferentially
according to the given textual pattern if they can be found. The
parameter is "silent" in a way that it is not present in the search
interface, you have to add it manually to your search URL.
For example, to get all CERN-TH publications of the year 2001
sorted by their CERN-TH numbers, you would search for
CERN-TH-2001*
within reportnumber
index,
and on the search results page, being satisfied with the results,
you would add &sp=CERN-TH
to the URL to sort the
results preferentially by CERN-TH report numbers, to get a nicely
sorted list of all CERN-TH 2001 publications.
You may select a certain field according to which sort the search
results, for example to sort the results by main title. However,
sometimes you may want to sort by a report number and it happens
that your documents have several of them. For example, the report
numbers hep-ph/0204140, CERN-TH-2002-069 and
RM3-TH-02-4 all denote the
same document. Now if you sort your search results set
containing this document, the system will take into consideration
the first report number, that may be either of these three.
Sometimes you may want to classify this document under its
hep-ph number, sometimes under its CERN number,
depending on whether you produce a list of CERN or hep-ph
publications. How can you influence the search engine to prefer
one report number rather than the other?
In other words, the search engine by default answers a query
like "sort by first author" or "sort by first report number", but
sometimes you may want to ask the search engine to "sort by first
report number that starts by the text CERN-". The latter
possibility is available via a "silent" sort parameter called
sp
(for "sort pattern") that sorts preferentially
according to the given textual pattern if they can be found. The
parameter is "silent" in a way that it is not present in the search
interface, you have to add it manually to your search URL.
For example, to get all CERN-TH publications of the year 2001
sorted by their CERN-TH numbers, you would search for
CERN-TH-2001*
within reportnumber
index,
and on the search results page, being satisfied with the results,
you would add &sp=CERN-TH
to the URL to sort the
results preferentially by CERN-TH report numbers, to get a nicely
sorted list of all CERN-TH 2001 publications.
You may select a certain field according to which sort the search
results, for example to sort the results by main title. However,
sometimes you may want to sort by a report number and it happens
that your documents have several of them. For example, the report
numbers hep-ph/0204140, CERN-TH-2002-069 and
RM3-TH-02-4 all denote the
same document. Now if you sort your search results set
containing this document, the system will take into consideration
the first report number, that may be either of these three.
Sometimes you may want to classify this document under its
hep-ph number, sometimes under its CERN number,
depending on whether you produce a list of CERN or hep-ph
publications. How can you influence the search engine to prefer
one report number rather than the other?
In other words, the search engine by default answers a query
like "sort by first author" or "sort by first report number", but
sometimes you may want to ask the search engine to "sort by first
report number that starts by the text CERN-". The latter
possibility is available via a "silent" sort parameter called
sp
(for "sort pattern") that sorts preferentially
according to the given textual pattern if they can be found. The
parameter is "silent" in a way that it is not present in the search
interface, you have to add it manually to your search URL.
For example, to get all CERN-TH publications of the year 2001
sorted by their CERN-TH numbers, you would search for
CERN-TH-2001*
within reportnumber
index,
and on the search results page, being satisfied with the results,
you would add &sp=CERN-TH
to the URL to sort the
results preferentially by CERN-TH report numbers, to get a nicely
sorted list of all CERN-TH 2001 publications.
You may select a certain field according to which sort the search
results, for example to sort the results by main title. However,
sometimes you may want to sort by a report number and it happens
that your documents have several of them. For example, the report
numbers hep-ph/0204140, CERN-TH-2002-069 and
RM3-TH-02-4 all denote the
same document. Now if you sort your search results set
containing this document, the system will take into consideration
the first report number, that may be either of these three.
Sometimes you may want to classify this document under its
hep-ph number, sometimes under its CERN number,
depending on whether you produce a list of CERN or hep-ph
publications. How can you influence the search engine to prefer
one report number rather than the other?
In other words, the search engine by default answers a query
like "sort by first author" or "sort by first report number", but
sometimes you may want to ask the search engine to "sort by first
report number that starts by the text CERN-". The latter
possibility is available via a "silent" sort parameter called
sp
(for "sort pattern") that sorts preferentially
according to the given textual pattern if they can be found. The
parameter is "silent" in a way that it is not present in the search
interface, you have to add it manually to your search URL.
For example, to get all CERN-TH publications of the year 2001
sorted by their CERN-TH numbers, you would search for
CERN-TH-2001*
within reportnumber
index,
and on the search results page, being satisfied with the results,
you would add &sp=CERN-TH
to the URL to sort the
results preferentially by CERN-TH report numbers, to get a nicely
sorted list of all CERN-TH 2001 publications.
You may select a certain field according to which sort the search
results, for example to sort the results by main title. However,
sometimes you may want to sort by a report number and it happens
that your documents have several of them. For example, the report
numbers hep-ph/0204140, CERN-TH-2002-069 and
RM3-TH-02-4 all denote the
same document. Now if you sort your search results set
containing this document, the system will take into consideration
the first report number, that may be either of these three.
Sometimes you may want to classify this document under its
hep-ph number, sometimes under its CERN number,
depending on whether you produce a list of CERN or hep-ph
publications. How can you influence the search engine to prefer
one report number rather than the other?
In other words, the search engine by default answers a query
like "sort by first author" or "sort by first report number", but
sometimes you may want to ask the search engine to "sort by first
report number that starts by the text CERN-". The latter
possibility is available via a "silent" sort parameter called
sp
(for "sort pattern") that sorts preferentially
according to the given textual pattern if they can be found. The
parameter is "silent" in a way that it is not present in the search
interface, you have to add it manually to your search URL.
For example, to get all CERN-TH publications of the year 2001
sorted by their CERN-TH numbers, you would search for
CERN-TH-2001*
within reportnumber
index,
and on the search results page, being satisfied with the results,
you would add &sp=CERN-TH
to the URL to sort the
results preferentially by CERN-TH report numbers, to get a nicely
sorted list of all CERN-TH 2001 publications.
You may select a certain field according to which sort the search
results, for example to sort the results by main title. However,
sometimes you may want to sort by a report number and it happens
that your documents have several of them. For example, the report
numbers hep-ph/0204140, CERN-TH-2002-069 and
RM3-TH-02-4 all denote the
same document. Now if you sort your search results set
containing this document, the system will take into consideration
the first report number, that may be either of these three.
Sometimes you may want to classify this document under its
hep-ph number, sometimes under its CERN number,
depending on whether you produce a list of CERN or hep-ph
publications. How can you influence the search engine to prefer
one report number rather than the other?
In other words, the search engine by default answers a query
like "sort by first author" or "sort by first report number", but
sometimes you may want to ask the search engine to "sort by first
report number that starts by the text CERN-". The latter
possibility is available via a "silent" sort parameter called
sp
(for "sort pattern") that sorts preferentially
according to the given textual pattern if they can be found. The
parameter is "silent" in a way that it is not present in the search
interface, you have to add it manually to your search URL.
For example, to get all CERN-TH publications of the year 2001
sorted by their CERN-TH numbers, you would search for
CERN-TH-2001*
within reportnumber
index,
and on the search results page, being satisfied with the results,
you would add &sp=CERN-TH
to the URL to sort the
results preferentially by CERN-TH report numbers, to get a nicely
sorted list of all CERN-TH 2001 publications.
You may select a certain field according to which sort the search
results, for example to sort the results by main title. However,
sometimes you may want to sort by a report number and it happens
that your documents have several of them. For example, the report
numbers hep-ph/0204140, CERN-TH-2002-069 and
RM3-TH-02-4 all denote the
same document. Now if you sort your search results set
containing this document, the system will take into consideration
the first report number, that may be either of these three.
Sometimes you may want to classify this document under its
hep-ph number, sometimes under its CERN number,
depending on whether you produce a list of CERN or hep-ph
publications. How can you influence the search engine to prefer
one report number rather than the other?
In other words, the search engine by default answers a query
like "sort by first author" or "sort by first report number", but
sometimes you may want to ask the search engine to "sort by first
report number that starts by the text CERN-". The latter
possibility is available via a "silent" sort parameter called
sp
(for "sort pattern") that sorts preferentially
according to the given textual pattern if they can be found. The
parameter is "silent" in a way that it is not present in the search
interface, you have to add it manually to your search URL.
For example, to get all CERN-TH publications of the year 2001
sorted by their CERN-TH numbers, you would search for
CERN-TH-2001*
within reportnumber
index,
and on the search results page, being satisfied with the results,
you would add &sp=CERN-TH
to the URL to sort the
results preferentially by CERN-TH report numbers, to get a nicely
sorted list of all CERN-TH 2001 publications.
You may select a certain field according to which sort the search
results, for example to sort the results by main title. However,
sometimes you may want to sort by a report number and it happens
that your documents have several of them. For example, the report
numbers hep-ph/0204140, CERN-TH-2002-069 and
RM3-TH-02-4 all denote the
same document. Now if you sort your search results set
containing this document, the system will take into consideration
the first report number, that may be either of these three.
Sometimes you may want to classify this document under its
hep-ph number, sometimes under its CERN number,
depending on whether you produce a list of CERN or hep-ph
publications. How can you influence the search engine to prefer
one report number rather than the other?
In other words, the search engine by default answers a query
like "sort by first author" or "sort by first report number", but
sometimes you may want to ask the search engine to "sort by first
report number that starts by the text CERN-". The latter
possibility is available via a "silent" sort parameter called
sp
(for "sort pattern") that sorts preferentially
according to the given textual pattern if they can be found. The
parameter is "silent" in a way that it is not present in the search
interface, you have to add it manually to your search URL.
For example, to get all CERN-TH publications of the year 2001
sorted by their CERN-TH numbers, you would search for
CERN-TH-2001*
within reportnumber
index,
and on the search results page, being satisfied with the results,
you would add &sp=CERN-TH
to the URL to sort the
results preferentially by CERN-TH report numbers, to get a nicely
sorted list of all CERN-TH 2001 publications.
You may select a certain field according to which sort the search
results, for example to sort the results by main title. However,
sometimes you may want to sort by a report number and it happens
that your documents have several of them. For example, the report
numbers hep-ph/0204140, CERN-TH-2002-069 and
RM3-TH-02-4 all denote the
same document. Now if you sort your search results set
containing this document, the system will take into consideration
the first report number, that may be either of these three.
Sometimes you may want to classify this document under its
hep-ph number, sometimes under its CERN number,
depending on whether you produce a list of CERN or hep-ph
publications. How can you influence the search engine to prefer
one report number rather than the other?
In other words, the search engine by default answers a query
like "sort by first author" or "sort by first report number", but
sometimes you may want to ask the search engine to "sort by first
report number that starts by the text CERN-". The latter
possibility is available via a "silent" sort parameter called
sp
(for "sort pattern") that sorts preferentially
according to the given textual pattern if they can be found. The
parameter is "silent" in a way that it is not present in the search
interface, you have to add it manually to your search URL.
For example, to get all CERN-TH publications of the year 2001
sorted by their CERN-TH numbers, you would search for
CERN-TH-2001*
within reportnumber
index,
and on the search results page, being satisfied with the results,
you would add &sp=CERN-TH
to the URL to sort the
results preferentially by CERN-TH report numbers, to get a nicely
sorted list of all CERN-TH 2001 publications.
Es posible seleccionar un campo determinado en función del tipo de
ordenación de los resultados de búsqueda, por ejemplo para
ordenarse los resultados por el título principal. De este modo, en
ocasiones puede ocurrir que se desee ordenar los documentos por el
código de referencia y que un mismo documento tenga más de uno.
Por ejemplo, los códigos hep-ph/0204140,
CERN-TH-2002-069 y RM3-TH-02-4 apuntan todos al
mismo documento. Si se ordena el conjunto de resultados de
búsqueda contenidos en el documento, el sistema tendrá en cuenta el
primer número de informe, que puede ser cualquiera de los tres. En
ocasiones se puede desear clasificar un documento según un
determinado código de referencia hep-ph , u otro
CERN> según si se ha publicado en una colección de
publicaciones de CERN o hep-ph. ¿Como se puede influir en el motor
de búsqueda para priorizar un código antes que otro?
En otras palabras, el motor de búsqueda responde por defecto a
una pregunta similar a “ordena por el primer autor” u “ordena por
el primer código de informe”, pero en ocasiones se desea instar al
buscador para que ordene por el “primer código de informe que
comience por el texto CERN-". Esta opción es posible a
través del uso de un paràmetre de ordenación “invisible” denominado
sp
(para a "ordenar según un patrón") que permite
ordenar siguiendo un patron de preferencia dado. Este parámetro es
“invisible” desde el punto de vista de que no está presente en el
interfaz de búsqueda, sino que debe ser añadido manualmente en el
URL de la búsqueda.
Por ejemplo, para recuperar todas las publicaciones del CERN-TH del
año 2001 ordenados por su código, debe buscarse por
CERN-TH-2001*
dentro del índice código de
informe
, y en la página de resultados de búsqueda, cuando esté
satisfecho con los resultados obtenidos, añadir
&sp=CERN-TH
en el URL a fin de ordenar los resultados
sgún los códigos de informe CERN-TH, y conseguir una correcta
ordenación del listado de todas las publicaciones CERN-TH del
2001.
Es possible seleccionar un camp determinat en funció del tipus
d’ordenació dels resultats de la cerca, per exemple per ordenar els
resultats pel títol principal. D’aquesta forma, en ocasions pot
passar que es desitgi ordenar els documents pel codi de referència
i que un mateix document en tingui més d’un. Per exemple, els
codis hep-ph/0204140, CERN-TH-2002-069 i
RM3-TH-02-4 apunten tots al
mateix document. Si s’ordena el conjunt de resultats de cerca
que conté el document, el sistema tindrà en consideració el primer
número d’informe, que pot ser qualsevol dels tres. En ocasions es
desitja classificar un document segons un determinat codi de
referència hep-ph , o altre CERN> segons si ha
estat publicat a una col•lecció de publicacions CERN o hep-ph. Com
es pot influir en el motor de cerca per prioritzar un codi abans de
l’altre?
En altres paraules, el motor de cerca respon per defecte a una
pregunta semblant a “ordena pel primer autor” o “ordena pel primer
codi d’informe”, però en ocasions es pot desitjar instar al
cercador per tal que ordeni pel “primer codi d’informe que comenci
pel text CERN-". Aquesta darrera opció és possible a
través d’un paràmetre d’ordenació “invisible” denominat
sp
(per a "ordenar segons un patró") que permet
ordenar segons un patró de preferència donat. Aquest paràmetre és
“invisible” des del punt de vista que no és present a l’interfície
de cerca, sinó que ha d’afegir-se manualment a la URL de cerca.
Per exemple, per recuperar totes les publicacions del CERN-TH de l’any
2001 ordenats pel seu codi, cal cercar per CERN-TH-2001*
dins l’índex de códi d’informe
, i a la pàgina de
resultats de cerca, quan s’estigui satisfet amb els resultats
obtinguts, afegir &sp=CERN-TH
a la URL per tal d’ordenar
els resultats segons els codis d’informe CERN-TH, i aconseguir una
correcta
ordenació de la llista de totes les publicacions CERN-TH del
2001.
On the search results page, links to other servers like Google, SPIRES or KEK are
automatically proposed in a box entitled "Try your search on". You
can simply click on the proposed links to run your query on these
search engines.
Note that the links aren't printed if the search engine doesn't
support it. For example, SPIRES or KEK cannot search for terms within
"any field", so we don't link to them in these cases.
" "1" "
Note also that KEK has scanned a lot of old CERN reports. If
you find that we don't have fulltext to some old CERN report, it
may be worthy to look there. For example, search for CERN
ISR-MA/73-17 in our system:
and you will see that CDS contains the document in the archives only, i.e. not in a electronic format.
However, if you follow the proposed KEK search link,
you will see that KEK proposes "scanned images" that you can download.
">
On the search results page, links to other servers like Google, SPIRES or KEK are
automatically proposed in a box entitled "Try your search on". You
can simply click on the proposed links to run your query on these
search engines.
Note that the links aren't printed if the search engine doesn't
support it. For example, SPIRES or KEK cannot search for terms within
"any field", so we don't link to them in these cases.
" "1" "
Note also that KEK has scanned a lot of old CERN reports. If
you find that we don't have fulltext to some old CERN report, it
may be worthy to look there. For example, search for CERN
ISR-MA/73-17 in our system:
and you will see that CDS contains the document in the archives only, i.e. not in a electronic format.
However, if you follow the proposed KEK search link,
you will see that KEK proposes "scanned images" that you can download.
">
On the search results page, links to other servers like Google, SPIRES or KEK are
automatically proposed in a box entitled "Try your search on". You
can simply click on the proposed links to run your query on these
search engines.
Note that the links aren't printed if the search engine doesn't
support it. For example, SPIRES or KEK cannot search for terms within
"any field", so we don't link to them in these cases.
" "1" "
Note also that KEK has scanned a lot of old CERN reports. If
you find that we don't have fulltext to some old CERN report, it
may be worthy to look there. For example, search for CERN
ISR-MA/73-17 in our system:
and you will see that CDS contains the document in the archives only, i.e. not in a electronic format.
However, if you follow the proposed KEK search link,
you will see that KEK proposes "scanned images" that you can download.
">
On the search results page, links to other servers like Google, SPIRES or KEK are
automatically proposed in a box entitled "Try your search on". You
can simply click on the proposed links to run your query on these
search engines.
Note that the links aren't printed if the search engine doesn't
support it. For example, SPIRES or KEK cannot search for terms within
"any field", so we don't link to them in these cases.
" "1" "
Note also that KEK has scanned a lot of old CERN reports. If
you find that we don't have fulltext to some old CERN report, it
may be worthy to look there. For example, search for CERN
ISR-MA/73-17 in our system:
and you will see that CDS contains the document in the archives only, i.e. not in a electronic format.
However, if you follow the proposed KEK search link,
you will see that KEK proposes "scanned images" that you can download.
">
On the search results page, links to other servers like Google, SPIRES or KEK are
automatically proposed in a box entitled "Try your search on". You
can simply click on the proposed links to run your query on these
search engines.
Note that the links aren't printed if the search engine doesn't
support it. For example, SPIRES or KEK cannot search for terms within
"any field", so we don't link to them in these cases.
" "1" "
Note also that KEK has scanned a lot of old CERN reports. If
you find that we don't have fulltext to some old CERN report, it
may be worthy to look there. For example, search for CERN
ISR-MA/73-17 in our system:
and you will see that CDS contains the document in the archives only, i.e. not in a electronic format.
However, if you follow the proposed KEK search link,
you will see that KEK proposes "scanned images" that you can download.
">
On the search results page, links to other servers like Google, SPIRES or KEK are
automatically proposed in a box entitled "Try your search on". You
can simply click on the proposed links to run your query on these
search engines.
Note that the links aren't printed if the search engine doesn't
support it. For example, SPIRES or KEK cannot search for terms within
"any field", so we don't link to them in these cases.
" "1" "
Note also that KEK has scanned a lot of old CERN reports. If
you find that we don't have fulltext to some old CERN report, it
may be worthy to look there. For example, search for CERN
ISR-MA/73-17 in our system:
and you will see that CDS contains the document in the archives only, i.e. not in a electronic format.
However, if you follow the proposed KEK search link,
you will see that KEK proposes "scanned images" that you can download.
">
On the search results page, links to other servers like Google, SPIRES or KEK are
automatically proposed in a box entitled "Try your search on". You
can simply click on the proposed links to run your query on these
search engines.
Note that the links aren't printed if the search engine doesn't
support it. For example, SPIRES or KEK cannot search for terms within
"any field", so we don't link to them in these cases.
" "1" "
Note also that KEK has scanned a lot of old CERN reports. If
you find that we don't have fulltext to some old CERN report, it
may be worthy to look there. For example, search for CERN
ISR-MA/73-17 in our system:
and you will see that CDS contains the document in the archives only, i.e. not in a electronic format.
However, if you follow the proposed KEK search link,
you will see that KEK proposes "scanned images" that you can download.
">
On the search results page, links to other servers like Google, SPIRES or KEK are
automatically proposed in a box entitled "Try your search on". You
can simply click on the proposed links to run your query on these
search engines.
Note that the links aren't printed if the search engine doesn't
support it. For example, SPIRES or KEK cannot search for terms within
"any field", so we don't link to them in these cases.
" "1" "
Note also that KEK has scanned a lot of old CERN reports. If
you find that we don't have fulltext to some old CERN report, it
may be worthy to look there. For example, search for CERN
ISR-MA/73-17 in our system:
and you will see that CDS contains the document in the archives only, i.e. not in a electronic format.
However, if you follow the proposed KEK search link,
you will see that KEK proposes "scanned images" that you can download.
">
On the search results page, links to other servers like Google, SPIRES or KEK are
automatically proposed in a box entitled "Try your search on". You
can simply click on the proposed links to run your query on these
search engines.
Note that the links aren't printed if the search engine doesn't
support it. For example, SPIRES or KEK cannot search for terms within
"any field", so we don't link to them in these cases.
" "1" "
Note also that KEK has scanned a lot of old CERN reports. If
you find that we don't have fulltext to some old CERN report, it
may be worthy to look there. For example, search for CERN
ISR-MA/73-17 in our system:
and you will see that CDS contains the document in the archives only, i.e. not in a electronic format.
However, if you follow the proposed KEK search link,
you will see that KEK proposes "scanned images" that you can download.
">
On the search results page, links to other servers like Google, SPIRES or KEK are
automatically proposed in a box entitled "Try your search on". You
can simply click on the proposed links to run your query on these
search engines.
Note that the links aren't printed if the search engine doesn't
support it. For example, SPIRES or KEK cannot search for terms within
"any field", so we don't link to them in these cases.
" "1" "
Note also that KEK has scanned a lot of old CERN reports. If
you find that we don't have fulltext to some old CERN report, it
may be worthy to look there. For example, search for CERN
ISR-MA/73-17 in our system:
and you will see that CDS contains the document in the archives only, i.e. not in a electronic format.
However, if you follow the proposed KEK search link,
you will see that KEK proposes "scanned images" that you can download.
">
On the search results page, links to other servers like Google, SPIRES or KEK are
automatically proposed in a box entitled "Try your search on". You
can simply click on the proposed links to run your query on these
search engines.
Note that the links aren't printed if the search engine doesn't
support it. For example, SPIRES or KEK cannot search for terms within
"any field", so we don't link to them in these cases.
" "1" "
Note also that KEK has scanned a lot of old CERN reports. If
you find that we don't have fulltext to some old CERN report, it
may be worthy to look there. For example, search for CERN
ISR-MA/73-17 in our system:
and you will see that CDS contains the document in the archives only, i.e. not in a electronic format.
However, if you follow the proposed KEK search link,
you will see that KEK proposes "scanned images" that you can download.
">
On the search results page, links to other servers like Google, SPIRES or KEK are
automatically proposed in a box entitled "Try your search on". You
can simply click on the proposed links to run your query on these
search engines.
Note that the links aren't printed if the search engine doesn't
support it. For example, SPIRES or KEK cannot search for terms within
"any field", so we don't link to them in these cases.
" "1" "
Note also that KEK has scanned a lot of old CERN reports. If
you find that we don't have fulltext to some old CERN report, it
may be worthy to look there. For example, search for CERN
ISR-MA/73-17 in our system:
and you will see that CDS contains the document in the archives only, i.e. not in a electronic format.
However, if you follow the proposed KEK search link,
you will see that KEK proposes "scanned images" that you can download.
">
On the search results page, links to other servers like Google, SPIRES or KEK are
automatically proposed in a box entitled "Try your search on". You
can simply click on the proposed links to run your query on these
search engines.
Note that the links aren't printed if the search engine doesn't
support it. For example, SPIRES or KEK cannot search for terms within
"any field", so we don't link to them in these cases.
" "1" "
Note also that KEK has scanned a lot of old CERN reports. If
you find that we don't have fulltext to some old CERN report, it
may be worthy to look there. For example, search for CERN
ISR-MA/73-17 in our system:
and you will see that CDS contains the document in the archives only, i.e. not in a electronic format.
However, if you follow the proposed KEK search link,
you will see that KEK proposes "scanned images" that you can download.
">
On the search results page, links to other servers like Google, SPIRES or KEK are
automatically proposed in a box entitled "Try your search on". You
can simply click on the proposed links to run your query on these
search engines.
Note that the links aren't printed if the search engine doesn't
support it. For example, SPIRES or KEK cannot search for terms within
"any field", so we don't link to them in these cases.
" "1" "
Note also that KEK has scanned a lot of old CERN reports. If
you find that we don't have fulltext to some old CERN report, it
may be worthy to look there. For example, search for CERN
ISR-MA/73-17 in our system:
and you will see that CDS contains the document in the archives only, i.e. not in a electronic format.
However, if you follow the proposed KEK search link,
you will see that KEK proposes "scanned images" that you can download.
">
On the search results page, links to other servers like Google, SPIRES or KEK are
automatically proposed in a box entitled "Try your search on". You
can simply click on the proposed links to run your query on these
search engines.
Note that the links aren't printed if the search engine doesn't
support it. For example, SPIRES or KEK cannot search for terms within
"any field", so we don't link to them in these cases.
" "1" "
Note also that KEK has scanned a lot of old CERN reports. If
you find that we don't have fulltext to some old CERN report, it
may be worthy to look there. For example, search for CERN
ISR-MA/73-17 in our system:
and you will see that CDS contains the document in the archives only, i.e. not in a electronic format.
However, if you follow the proposed KEK search link,
you will see that KEK proposes "scanned images" that you can download.
">
On the search results page, links to other servers like Google, SPIRES or KEK are
automatically proposed in a box entitled "Try your search on". You
can simply click on the proposed links to run your query on these
search engines.
Note that the links aren't printed if the search engine doesn't
support it. For example, SPIRES or KEK cannot search for terms within
"any field", so we don't link to them in these cases.
" "1" "
Note also that KEK has scanned a lot of old CERN reports. If
you find that we don't have fulltext to some old CERN report, it
may be worthy to look there. For example, search for CERN
ISR-MA/73-17 in our system:
and you will see that CDS contains the document in the archives only, i.e. not in a electronic format.
However, if you follow the proposed KEK search link,
you will see that KEK proposes "scanned images" that you can download.
">
On the search results page, links to other servers like Google, SPIRES or KEK are
automatically proposed in a box entitled "Try your search on". You
can simply click on the proposed links to run your query on these
search engines.
Note that the links aren't printed if the search engine doesn't
support it. For example, SPIRES or KEK cannot search for terms within
"any field", so we don't link to them in these cases.
" "1" "
Note also that KEK has scanned a lot of old CERN reports. If
you find that we don't have fulltext to some old CERN report, it
may be worthy to look there. For example, search for CERN
ISR-MA/73-17 in our system:
and you will see that CDS contains the document in the archives only, i.e. not in a electronic format.
However, if you follow the proposed KEK search link,
you will see that KEK proposes "scanned images" that you can download.
">
On the search results page, links to other servers like Google, SPIRES or KEK are
automatically proposed in a box entitled "Try your search on". You
can simply click on the proposed links to run your query on these
search engines.
Note that the links aren't printed if the search engine doesn't
support it. For example, SPIRES or KEK cannot search for terms within
"any field", so we don't link to them in these cases.
" "1" "
Note also that KEK has scanned a lot of old CERN reports. If
you find that we don't have fulltext to some old CERN report, it
may be worthy to look there. For example, search for CERN
ISR-MA/73-17 in our system:
and you will see that CDS contains the document in the archives only, i.e. not in a electronic format.
However, if you follow the proposed KEK search link,
you will see that KEK proposes "scanned images" that you can download.
">
A la pàgina de resultats de cerca, s'ofereixen automàticament
enllaços a altres servidors com Google, SPIRES o KEK sota el nom
de "Proveu la vostra cerca a...". Amb un simple clic sobre els
enllaços proposats es pot enviar la cerca realitzada en aquests
cercadors.
Observis que els enllaços a altres cercadors no es mostren si el cercador no suporta la cerca. Per exemple, SPIRES o KEK no poden cercar termes dintre del camp "qualsevol camp", de forma que en aquests casos, el sistema no els enllaçarà.
" "1" "
Observis també que KEK ha escanejat molts informes antics del CERN. Si es comprova que no es disposa del text complet d'un informe antic del CERN, pot ser interessant cercar aquí. Per exemple, si es cerca per CERN
ISR-MA/73-17 dins el sistema:
es pot comprovar que CDS conté el document únicament als arxius, i.e. no en format electrònic. Ara bé, si seguim l'enllaç a KEKproposat, podem observar que ens ofereix "imatges escanejades" que podem descarregar.
">
En la página de resultadoss de búsqueda, se oferecen automáticament
enlaces a otros servidores tales como Google, SPIRES o KEK bajo el
nombre de "Intentar la búsqueda en...". Con un simple cic sobre los
enlaces propuestos se puede enviar la búsqueda realizada en dichos
buscadores.
Obsérvese que los enlaces a otros cercadores no se muestran si el
buscador no soporta el tipo de búsqueda. Por ejemplo, SPIRES o KEK no
pueden buscar términos dentro del campo "cualquier campo", de forma
que en estos casos, el sistema no los enlazará.
" "1" "
Obsérvese también que KEK ha escaneado un gran número de informes
antiguos del CERN. Si se comprueba que no se dispone del texto
completo de un informe antiguo del CERN, puede ser interesante
buscar allí. Por ejemplo, si se busca por CERN
ISR-MA/73-17 dentro del sistema:
se puede comprobar que CDS contiene el documento únicamente en los
archivos, i.e. no en formato electrónico. Sin embargo, si seguimos el
enlace a KEKpropuesto, podemos observar que nos ofrece
"imágenes escaneadas" que podemos descargar. ">
If a metadata record contains some associated fulltext files,
tries to extract the textual information from the files and index it into a separate fulltext
index.
To search for all records that contain the term e- in their fulltext files,
type:
Recall that fulltext words aren't included in the default global ``any field'' index,
but that you may freely combine a fulltext and metadata search. For example, to find all
articles written by Ellis that contain the word muon either in the
metadata or in the fulltext, type:
" "1" "
Currently, the fulltext indexes aren't available on the CERN site.
Assumed operational time: Q1 2007.
Please use the
old fulltext interface
instead in the meantime.
|
">
If a metadata record contains some associated fulltext files,
tries to extract the textual information from the files and index it into a separate fulltext
index.
To search for all records that contain the term e- in their fulltext files,
type:
Recall that fulltext words aren't included in the default global ``any field'' index,
but that you may freely combine a fulltext and metadata search. For example, to find all
articles written by Ellis that contain the word muon either in the
metadata or in the fulltext, type:
" "1" "
Currently, the fulltext indexes aren't available on the CERN site.
Assumed operational time: Q1 2007.
Please use the
old fulltext interface
instead in the meantime.
|
">
If a metadata record contains some associated fulltext files,
tries to extract the textual information from the files and index it into a separate fulltext
index.
To search for all records that contain the term e- in their fulltext files,
type:
Recall that fulltext words aren't included in the default global ``any field'' index,
but that you may freely combine a fulltext and metadata search. For example, to find all
articles written by Ellis that contain the word muon either in the
metadata or in the fulltext, type:
" "1" "
Currently, the fulltext indexes aren't available on the CERN site.
Assumed operational time: Q1 2007.
Please use the
old fulltext interface
instead in the meantime.
|
">
If a metadata record contains some associated fulltext files,
tries to extract the textual information from the files and index it into a separate fulltext
index.
To search for all records that contain the term e- in their fulltext files,
type:
Recall that fulltext words aren't included in the default global ``any field'' index,
but that you may freely combine a fulltext and metadata search. For example, to find all
articles written by Ellis that contain the word muon either in the
metadata or in the fulltext, type:
" "1" "
Currently, the fulltext indexes aren't available on the CERN site.
Assumed operational time: Q1 2007.
Please use the
old fulltext interface
instead in the meantime.
|
">
If a metadata record contains some associated fulltext files,
tries to extract the textual information from the files and index it into a separate fulltext
index.
To search for all records that contain the term e- in their fulltext files,
type:
Recall that fulltext words aren't included in the default global ``any field'' index,
but that you may freely combine a fulltext and metadata search. For example, to find all
articles written by Ellis that contain the word muon either in the
metadata or in the fulltext, type:
" "1" "
Currently, the fulltext indexes aren't available on the CERN site.
Assumed operational time: Q1 2007.
Please use the
old fulltext interface
instead in the meantime.
|
">
If a metadata record contains some associated fulltext files,
tries to extract the textual information from the files and index it into a separate fulltext
index.
To search for all records that contain the term e- in their fulltext files,
type:
Recall that fulltext words aren't included in the default global ``any field'' index,
but that you may freely combine a fulltext and metadata search. For example, to find all
articles written by Ellis that contain the word muon either in the
metadata or in the fulltext, type:
" "1" "
Currently, the fulltext indexes aren't available on the CERN site.
Assumed operational time: Q1 2007.
Please use the
old fulltext interface
instead in the meantime.
|
">
If a metadata record contains some associated fulltext files,
tries to extract the textual information from the files and index it into a separate fulltext
index.
To search for all records that contain the term e- in their fulltext files,
type:
Recall that fulltext words aren't included in the default global ``any field'' index,
but that you may freely combine a fulltext and metadata search. For example, to find all
articles written by Ellis that contain the word muon either in the
metadata or in the fulltext, type:
" "1" "
Currently, the fulltext indexes aren't available on the CERN site.
Assumed operational time: Q1 2007.
Please use the
old fulltext interface
instead in the meantime.
|
">
If a metadata record contains some associated fulltext files,
tries to extract the textual information from the files and index it into a separate fulltext
index.
To search for all records that contain the term e- in their fulltext files,
type:
Recall that fulltext words aren't included in the default global ``any field'' index,
but that you may freely combine a fulltext and metadata search. For example, to find all
articles written by Ellis that contain the word muon either in the
metadata or in the fulltext, type:
" "1" "
Currently, the fulltext indexes aren't available on the CERN site.
Assumed operational time: Q1 2007.
Please use the
old fulltext interface
instead in the meantime.
|
">
If a metadata record contains some associated fulltext files,
tries to extract the textual information from the files and index it into a separate fulltext
index.
To search for all records that contain the term e- in their fulltext files,
type:
Recall that fulltext words aren't included in the default global ``any field'' index,
but that you may freely combine a fulltext and metadata search. For example, to find all
articles written by Ellis that contain the word muon either in the
metadata or in the fulltext, type:
" "1" "
Currently, the fulltext indexes aren't available on the CERN site.
Assumed operational time: Q1 2007.
Please use the
old fulltext interface
instead in the meantime.
|
">
If a metadata record contains some associated fulltext files,
tries to extract the textual information from the files and index it into a separate fulltext
index.
To search for all records that contain the term e- in their fulltext files,
type:
Recall that fulltext words aren't included in the default global ``any field'' index,
but that you may freely combine a fulltext and metadata search. For example, to find all
articles written by Ellis that contain the word muon either in the
metadata or in the fulltext, type:
" "1" "
Currently, the fulltext indexes aren't available on the CERN site.
Assumed operational time: Q1 2007.
Please use the
old fulltext interface
instead in the meantime.
|
">
If a metadata record contains some associated fulltext files,
tries to extract the textual information from the files and index it into a separate fulltext
index.
To search for all records that contain the term e- in their fulltext files,
type:
Recall that fulltext words aren't included in the default global ``any field'' index,
but that you may freely combine a fulltext and metadata search. For example, to find all
articles written by Ellis that contain the word muon either in the
metadata or in the fulltext, type:
" "1" "
Currently, the fulltext indexes aren't available on the CERN site.
Assumed operational time: Q1 2007.
Please use the
old fulltext interface
instead in the meantime.
|
">
If a metadata record contains some associated fulltext files,
tries to extract the textual information from the files and index it into a separate fulltext
index.
To search for all records that contain the term e- in their fulltext files,
type:
Recall that fulltext words aren't included in the default global ``any field'' index,
but that you may freely combine a fulltext and metadata search. For example, to find all
articles written by Ellis that contain the word muon either in the
metadata or in the fulltext, type:
" "1" "
Currently, the fulltext indexes aren't available on the CERN site.
Assumed operational time: Q1 2007.
Please use the
old fulltext interface
instead in the meantime.
|
">
If a metadata record contains some associated fulltext files,
tries to extract the textual information from the files and index it into a separate fulltext
index.
To search for all records that contain the term e- in their fulltext files,
type:
Recall that fulltext words aren't included in the default global ``any field'' index,
but that you may freely combine a fulltext and metadata search. For example, to find all
articles written by Ellis that contain the word muon either in the
metadata or in the fulltext, type:
" "1" "
Currently, the fulltext indexes aren't available on the CERN site.
Assumed operational time: Q1 2007.
Please use the
old fulltext interface
instead in the meantime.
|
">
If a metadata record contains some associated fulltext files,
tries to extract the textual information from the files and index it into a separate fulltext
index.
To search for all records that contain the term e- in their fulltext files,
type:
Recall that fulltext words aren't included in the default global ``any field'' index,
but that you may freely combine a fulltext and metadata search. For example, to find all
articles written by Ellis that contain the word muon either in the
metadata or in the fulltext, type:
" "1" "
Currently, the fulltext indexes aren't available on the CERN site.
Assumed operational time: Q1 2007.
Please use the
old fulltext interface
instead in the meantime.
|
">
If a metadata record contains some associated fulltext files,
tries to extract the textual information from the files and index it into a separate fulltext
index.
To search for all records that contain the term e- in their fulltext files,
type:
Recall that fulltext words aren't included in the default global ``any field'' index,
but that you may freely combine a fulltext and metadata search. For example, to find all
articles written by Ellis that contain the word muon either in the
metadata or in the fulltext, type:
" "1" "
Currently, the fulltext indexes aren't available on the CERN site.
Assumed operational time: Q1 2007.
Please use the
old fulltext interface
instead in the meantime.
|
">
If a metadata record contains some associated fulltext files,
tries to extract the textual information from the files and index it into a separate fulltext
index.
To search for all records that contain the term e- in their fulltext files,
type:
Recall that fulltext words aren't included in the default global ``any field'' index,
but that you may freely combine a fulltext and metadata search. For example, to find all
articles written by Ellis that contain the word muon either in the
metadata or in the fulltext, type:
" "1" "
Currently, the fulltext indexes aren't available on the CERN site.
Assumed operational time: Q1 2007.
Please use the
old fulltext interface
instead in the meantime.
|
">
If a metadata record contains some associated fulltext files,
tries to extract the textual information from the files and index it into a separate fulltext
index.
To search for all records that contain the term e- in their fulltext files,
type:
Recall that fulltext words aren't included in the default global ``any field'' index,
but that you may freely combine a fulltext and metadata search. For example, to find all
articles written by Ellis that contain the word muon either in the
metadata or in the fulltext, type:
" "1" "
Currently, the fulltext indexes aren't available on the CERN site.
Assumed operational time: Q1 2007.
Please use the
old fulltext interface
instead in the meantime.
|
">
If a metadata record contains some associated fulltext files,
tries to extract the textual information from the files and index it into a separate fulltext
index.
To search for all records that contain the term e- in their fulltext files,
type:
Recall that fulltext words aren't included in the default global ``any field'' index,
but that you may freely combine a fulltext and metadata search. For example, to find all
articles written by Ellis that contain the word muon either in the
metadata or in the fulltext, type:
" "1" "
Currently, the fulltext indexes aren't available on the CERN site.
Assumed operational time: Q1 2007.
Please use the
old fulltext interface
instead in the meantime.
|
">
Si un registre de metadades té arxius a text complet associats
tractarà de extraure la informació textual dels arxius e
indexar-la a un índex de text complet
separat. Per
recuperar tots els documents que contenen el terme e-al text
complet dels seus documents associats, cal escriure:
Recordem que les paraules del text complet no s'inclouen a l'índex
global 'qualsevol camp' predeterminat, però és possible realitzar una
combinació lliure de text complet i metadades dins una mateixa cerca.
Per exemple, per recuperar tots els articles escrits per
Ellis que continguin la paraula muon tant a les
metadades como all text complet, cal escriure:
" "1" "
En aquests moments, els índexs de text complet no estan disponibles al web del CERN. Assumed operational time: Q1 2007.
Sius plau, emprar mentrestant l'antiga
interfície de text complet.
|
">
Si un registro de metadatos contiene archivos a texto completo
asociados, tratará de extraer la información textual de
los archivos e indexarla en un índice de texto
completo
separado. Para recuperar todos los documentos que
contienen el término e- en el texto completo de sus
documentos asociados, debemos escribir:
Recordamos que las palabras del texto completo no se incluyen en el
índice global 'cualquier campo' predeterminado, pero es posible
realizar una combinación libre de texto completo y metadatos en una
misma búsqueda. Por ejemplo, para recuperar todos los artículos
escritos por Ellis que contengan la palabra muon
tanto en los metadatos como en el texto completo, debemos escribir:
" "1" "
En estos momentos, los índices de texto completo no están disponibles en el web del CERN.
Assumed operational time: Q1 2007.
Por favor, utilicen mientras tanto el
antiguo interfaz de texto completo.
|
">
If a metadata record contains an associated fulltext file,
tries to extract references automatically from that file and index
them into a separate reference
index. To search for
all records that cite Ellis in their reference lists,
type:
To search for all records that cite preprint hep-ph/0103062
in their reference lists, type:
To search for all records that cite an article from Giddings and Ross published in
Physical Review D in volume 61 in year 2000, type:
Recall that citation terms aren't included in the default global "any field" index,
but that you may freely combine a citation search with a metadata search.
For example, to find all articles on standard model that aren't written by
Ellis but that do cite him, type:
" "1" "
Currently, the reference indexes aren't available on the CERN site.
The citation search is therefore impossible at the moment.
Assumed operational time: Q1 2007.
|
">
If a metadata record contains an associated fulltext file,
tries to extract references automatically from that file and index
them into a separate reference
index. To search for
all records that cite Ellis in their reference lists,
type:
To search for all records that cite preprint hep-ph/0103062
in their reference lists, type:
To search for all records that cite an article from Giddings and Ross published in
Physical Review D in volume 61 in year 2000, type:
Recall that citation terms aren't included in the default global "any field" index,
but that you may freely combine a citation search with a metadata search.
For example, to find all articles on standard model that aren't written by
Ellis but that do cite him, type:
" "1" "
Currently, the reference indexes aren't available on the CERN site.
The citation search is therefore impossible at the moment.
Assumed operational time: Q1 2007.
|
">
If a metadata record contains an associated fulltext file,
tries to extract references automatically from that file and index
them into a separate reference
index. To search for
all records that cite Ellis in their reference lists,
type:
To search for all records that cite preprint hep-ph/0103062
in their reference lists, type:
To search for all records that cite an article from Giddings and Ross published in
Physical Review D in volume 61 in year 2000, type:
Recall that citation terms aren't included in the default global "any field" index,
but that you may freely combine a citation search with a metadata search.
For example, to find all articles on standard model that aren't written by
Ellis but that do cite him, type:
" "1" "
Currently, the reference indexes aren't available on the CERN site.
The citation search is therefore impossible at the moment.
Assumed operational time: Q1 2007.
|
">
If a metadata record contains an associated fulltext file,
tries to extract references automatically from that file and index
them into a separate reference
index. To search for
all records that cite Ellis in their reference lists,
type:
To search for all records that cite preprint hep-ph/0103062
in their reference lists, type:
To search for all records that cite an article from Giddings and Ross published in
Physical Review D in volume 61 in year 2000, type:
Recall that citation terms aren't included in the default global "any field" index,
but that you may freely combine a citation search with a metadata search.
For example, to find all articles on standard model that aren't written by
Ellis but that do cite him, type:
" "1" "
Currently, the reference indexes aren't available on the CERN site.
The citation search is therefore impossible at the moment.
Assumed operational time: Q1 2007.
|
">
If a metadata record contains an associated fulltext file,
tries to extract references automatically from that file and index
them into a separate reference
index. To search for
all records that cite Ellis in their reference lists,
type:
To search for all records that cite preprint hep-ph/0103062
in their reference lists, type:
To search for all records that cite an article from Giddings and Ross published in
Physical Review D in volume 61 in year 2000, type:
Recall that citation terms aren't included in the default global "any field" index,
but that you may freely combine a citation search with a metadata search.
For example, to find all articles on standard model that aren't written by
Ellis but that do cite him, type:
" "1" "
Currently, the reference indexes aren't available on the CERN site.
The citation search is therefore impossible at the moment.
Assumed operational time: Q1 2007.
|
">
If a metadata record contains an associated fulltext file,
tries to extract references automatically from that file and index
them into a separate reference
index. To search for
all records that cite Ellis in their reference lists,
type:
To search for all records that cite preprint hep-ph/0103062
in their reference lists, type:
To search for all records that cite an article from Giddings and Ross published in
Physical Review D in volume 61 in year 2000, type:
Recall that citation terms aren't included in the default global "any field" index,
but that you may freely combine a citation search with a metadata search.
For example, to find all articles on standard model that aren't written by
Ellis but that do cite him, type:
" "1" "
Currently, the reference indexes aren't available on the CERN site.
The citation search is therefore impossible at the moment.
Assumed operational time: Q1 2007.
|
">
If a metadata record contains an associated fulltext file,
tries to extract references automatically from that file and index
them into a separate reference
index. To search for
all records that cite Ellis in their reference lists,
type:
To search for all records that cite preprint hep-ph/0103062
in their reference lists, type:
To search for all records that cite an article from Giddings and Ross published in
Physical Review D in volume 61 in year 2000, type:
Recall that citation terms aren't included in the default global "any field" index,
but that you may freely combine a citation search with a metadata search.
For example, to find all articles on standard model that aren't written by
Ellis but that do cite him, type:
" "1" "
Currently, the reference indexes aren't available on the CERN site.
The citation search is therefore impossible at the moment.
Assumed operational time: Q1 2007.
|
">
If a metadata record contains an associated fulltext file,
tries to extract references automatically from that file and index
them into a separate reference
index. To search for
all records that cite Ellis in their reference lists,
type:
To search for all records that cite preprint hep-ph/0103062
in their reference lists, type:
To search for all records that cite an article from Giddings and Ross published in
Physical Review D in volume 61 in year 2000, type:
Recall that citation terms aren't included in the default global "any field" index,
but that you may freely combine a citation search with a metadata search.
For example, to find all articles on standard model that aren't written by
Ellis but that do cite him, type:
" "1" "
Currently, the reference indexes aren't available on the CERN site.
The citation search is therefore impossible at the moment.
Assumed operational time: Q1 2007.
|
">
If a metadata record contains an associated fulltext file,
tries to extract references automatically from that file and index
them into a separate reference
index. To search for
all records that cite Ellis in their reference lists,
type:
To search for all records that cite preprint hep-ph/0103062
in their reference lists, type:
To search for all records that cite an article from Giddings and Ross published in
Physical Review D in volume 61 in year 2000, type:
Recall that citation terms aren't included in the default global "any field" index,
but that you may freely combine a citation search with a metadata search.
For example, to find all articles on standard model that aren't written by
Ellis but that do cite him, type:
" "1" "
Currently, the reference indexes aren't available on the CERN site.
The citation search is therefore impossible at the moment.
Assumed operational time: Q1 2007.
|
">
If a metadata record contains an associated fulltext file,
tries to extract references automatically from that file and index
them into a separate reference
index. To search for
all records that cite Ellis in their reference lists,
type:
To search for all records that cite preprint hep-ph/0103062
in their reference lists, type:
To search for all records that cite an article from Giddings and Ross published in
Physical Review D in volume 61 in year 2000, type:
Recall that citation terms aren't included in the default global "any field" index,
but that you may freely combine a citation search with a metadata search.
For example, to find all articles on standard model that aren't written by
Ellis but that do cite him, type:
" "1" "
Currently, the reference indexes aren't available on the CERN site.
The citation search is therefore impossible at the moment.
Assumed operational time: Q1 2007.
|
">
If a metadata record contains an associated fulltext file,
tries to extract references automatically from that file and index
them into a separate reference
index. To search for
all records that cite Ellis in their reference lists,
type:
To search for all records that cite preprint hep-ph/0103062
in their reference lists, type:
To search for all records that cite an article from Giddings and Ross published in
Physical Review D in volume 61 in year 2000, type:
Recall that citation terms aren't included in the default global "any field" index,
but that you may freely combine a citation search with a metadata search.
For example, to find all articles on standard model that aren't written by
Ellis but that do cite him, type:
" "1" "
Currently, the reference indexes aren't available on the CERN site.
The citation search is therefore impossible at the moment.
Assumed operational time: Q1 2007.
|
">
If a metadata record contains an associated fulltext file,
tries to extract references automatically from that file and index
them into a separate reference
index. To search for
all records that cite Ellis in their reference lists,
type:
To search for all records that cite preprint hep-ph/0103062
in their reference lists, type:
To search for all records that cite an article from Giddings and Ross published in
Physical Review D in volume 61 in year 2000, type:
Recall that citation terms aren't included in the default global "any field" index,
but that you may freely combine a citation search with a metadata search.
For example, to find all articles on standard model that aren't written by
Ellis but that do cite him, type:
" "1" "
Currently, the reference indexes aren't available on the CERN site.
The citation search is therefore impossible at the moment.
Assumed operational time: Q1 2007.
|
">
If a metadata record contains an associated fulltext file,
tries to extract references automatically from that file and index
them into a separate reference
index. To search for
all records that cite Ellis in their reference lists,
type:
To search for all records that cite preprint hep-ph/0103062
in their reference lists, type:
To search for all records that cite an article from Giddings and Ross published in
Physical Review D in volume 61 in year 2000, type:
Recall that citation terms aren't included in the default global "any field" index,
but that you may freely combine a citation search with a metadata search.
For example, to find all articles on standard model that aren't written by
Ellis but that do cite him, type:
" "1" "
Currently, the reference indexes aren't available on the CERN site.
The citation search is therefore impossible at the moment.
Assumed operational time: Q1 2007.
|
">
If a metadata record contains an associated fulltext file,
tries to extract references automatically from that file and index
them into a separate reference
index. To search for
all records that cite Ellis in their reference lists,
type:
To search for all records that cite preprint hep-ph/0103062
in their reference lists, type:
To search for all records that cite an article from Giddings and Ross published in
Physical Review D in volume 61 in year 2000, type:
Recall that citation terms aren't included in the default global "any field" index,
but that you may freely combine a citation search with a metadata search.
For example, to find all articles on standard model that aren't written by
Ellis but that do cite him, type:
" "1" "
Currently, the reference indexes aren't available on the CERN site.
The citation search is therefore impossible at the moment.
Assumed operational time: Q1 2007.
|
">
If a metadata record contains an associated fulltext file,
tries to extract references automatically from that file and index
them into a separate reference
index. To search for
all records that cite Ellis in their reference lists,
type:
To search for all records that cite preprint hep-ph/0103062
in their reference lists, type:
To search for all records that cite an article from Giddings and Ross published in
Physical Review D in volume 61 in year 2000, type:
Recall that citation terms aren't included in the default global "any field" index,
but that you may freely combine a citation search with a metadata search.
For example, to find all articles on standard model that aren't written by
Ellis but that do cite him, type:
" "1" "
Currently, the reference indexes aren't available on the CERN site.
The citation search is therefore impossible at the moment.
Assumed operational time: Q1 2007.
|
">
If a metadata record contains an associated fulltext file,
tries to extract references automatically from that file and index
them into a separate reference
index. To search for
all records that cite Ellis in their reference lists,
type:
To search for all records that cite preprint hep-ph/0103062
in their reference lists, type:
To search for all records that cite an article from Giddings and Ross published in
Physical Review D in volume 61 in year 2000, type:
Recall that citation terms aren't included in the default global "any field" index,
but that you may freely combine a citation search with a metadata search.
For example, to find all articles on standard model that aren't written by
Ellis but that do cite him, type:
" "1" "
Currently, the reference indexes aren't available on the CERN site.
The citation search is therefore impossible at the moment.
Assumed operational time: Q1 2007.
|
">
If a metadata record contains an associated fulltext file,
tries to extract references automatically from that file and index
them into a separate reference
index. To search for
all records that cite Ellis in their reference lists,
type:
To search for all records that cite preprint hep-ph/0103062
in their reference lists, type:
To search for all records that cite an article from Giddings and Ross published in
Physical Review D in volume 61 in year 2000, type:
Recall that citation terms aren't included in the default global "any field" index,
but that you may freely combine a citation search with a metadata search.
For example, to find all articles on standard model that aren't written by
Ellis but that do cite him, type:
" "1" "
Currently, the reference indexes aren't available on the CERN site.
The citation search is therefore impossible at the moment.
Assumed operational time: Q1 2007.
|
">
If a metadata record contains an associated fulltext file,
tries to extract references automatically from that file and index
them into a separate reference
index. To search for
all records that cite Ellis in their reference lists,
type:
To search for all records that cite preprint hep-ph/0103062
in their reference lists, type:
To search for all records that cite an article from Giddings and Ross published in
Physical Review D in volume 61 in year 2000, type:
Recall that citation terms aren't included in the default global "any field" index,
but that you may freely combine a citation search with a metadata search.
For example, to find all articles on standard model that aren't written by
Ellis but that do cite him, type:
" "1" "
Currently, the reference indexes aren't available on the CERN site.
The citation search is therefore impossible at the moment.
Assumed operational time: Q1 2007.
|
">
Si un registro de metadatos contiene un fichero de texto asociado,
trata de extraer las citas automaticamente del fichero e
indexarlas en un índice separado de citas
. Para
recuperar todos los registros que citan a Ellis en sus
listados de citas bibliogáficas, escribiremos:
Para recuperar todos los registros que citan el pre-print
hep-ph/0103062en sus listados de citas bibliográficas,
escribiremos:
Para recuperar todos los documentos que citan un artículo de
Giddings y Rosspublicado en Physical Review
D volumen 61 y en el año 2000, escribiremos:
Recuerde que los términos de las citaciones no estan incluidos dentro
del índice “cualquier campo” en la búsqueda global predeterminada,
pero puede realizar una combinación libre entre búsqueda por cita
bibliogràfica y por metadatos. Por ejemplo, para recuperar todos los
artículos sobre modelo estándar que no han sido escritos por
Ellis pero lo citan, escribiremos:
" "1" "
Actualmente, los índices de citas bibliográficas no estan disponibles en la pàgina web. La búsqueda por cita bibliográfica es imposible en este momento.
Assumed operational time: Q1 2007.
|
">
Si un registre de metadades conté un fitxer de text associat,
tracta de extraure les referències automàticament del
fitxer e indexar-les a un índex separat de referències
.
Para recuperar tots els registres que citen a Ellis en els
seus llistats de referències bibliogràfiques, escriurem:
Per recuperar tots els registres que citen el pre-print
hep-ph/0103062en els seus llistats de referències
bibliogràfiques, escriurem:
Per recuperar tots els documents que citen un article de
Giddings i Rosspublicat a Physical Review D
volum 61 i a l’any 2000, escriurem:
Recordi que els termes de les referències no estan inclosos dins
l’índex “qualsevol camp” a la cerca global predeterminada, però pot
realitzar una combinació lliure entre cerca por referència i per
metadades.
Per exemple, per recuperar tots els articles sobre model
estàndar que no han estat escrits per Ellis però el
citen, escriurem:
" "1" "
Actualment, els índexs de referències bibliogràfiques no estan
disponibles a la pàgina web. La cerca per cita bibliogràfica no
és possible en aquest moment. Assumed operational time: Q1
2007.
|
">
\ No newline at end of file
diff --git a/modules/websearch/doc/search-help.webdoc b/modules/websearch/doc/search-help.webdoc
index 3c82dcba7..f5582cc17 100644
--- a/modules/websearch/doc/search-help.webdoc
+++ b/modules/websearch/doc/search-help.webdoc
@@ -1,187 +1,187 @@
## -*- mode: html; coding: utf-8; -*-
## $Id$
## This file is part of CDS Invenio.
## Copyright (C) 2002, 2003, 2004, 2005, 2006, 2007 CERN.
##
## CDS Invenio is free software; you can redistribute it and/or
## modify it under the terms of the GNU General Public License as
## published by the Free Software Foundation; either version 2 of the
## License, or (at your option) any later version.
##
## CDS Invenio is distributed in the hope that it will be useful, but
## WITHOUT ANY WARRANTY; without even the implied warranty of
## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
## General Public License for more details.
##
## You should have received a copy of the GNU General Public License
## along with CDS Invenio; if not, write to the Free Software Foundation, Inc.,
## 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.
-
+
Find out all about searching
Trouvez tout sur la recherche de
Lernen Sie alles über den Suchemöglichkeiten beim
Find out all about searching
Trobeu tota l'ajuda sobre la cerca
Find out all about searching
Descubra tudo sobre buscas no
Tutto quanto vi serve per poter ricercare in
Find out all about searching
Tu nájdete všetko čo sa týka hľadania na serveri
Zde naleznete vše co se týče vyhledávání na serveru
Finn ut alt om søking i
Finn ut allt om sökning av
Find out all about searching
Find out all about searching
Find out all about searching
Find out all about searching
Find out all about searching
Find out all about searching
Find out all about searching
-- _(Search Tips)_
+- _(Search Tips)_
-
This page presents you with useful tips and techniques in order to
help you use the site to the full.
Cette page vous présente des suggestions et des techniques qui puissent vous être utiles
afin d'utiliser au mieux .
Diese Seite zeigt Ihnen alle nützliche Tipps und Techniken die
beim zur Verfügung stehen.
This page presents you with useful tips and techniques in order to
help you use the site to the full.
Aquesta pàgina us presenta suggeriments i tècniques que us poden
resultar útils per usar en totes les seves possibilitats.
This page presents you with useful tips and techniques in order to
help you use the site to the full.
Esta página oferece dicas úteis e técnicas para ajuda-lo a usar o sítio do
em toda sua potencialidade.
Questa pagina vi fornisce utili consigli per servirvi al meglio
.
This page presents you with useful tips and techniques in order to
help you use the site to the full.
Táto stránka Vám ponúka užitočné tipy a triky ktoré Vám umožnia
plne využívať možností .
Tato stránka Vám nabízí užitečné tipy a triky které Vám umožní
plně využívat možností .
Denne siden presenter nyttige tips og teknikker slik at du lettere kan få
fullt utbytte av sine sider.
Denna sida ger dig användbara tips och tekniker för att hjälpa dig att
till fullo använda denna webbplats som erbjuder dig.
This page presents you with useful tips and techniques in order to
help you use the site to the full.
This page presents you with useful tips and techniques in order to
help you use the site to the full.
This page presents you with useful tips and techniques in order to
help you use the site to the full.
This page presents you with useful tips and techniques in order to
help you use the site to the full.
This page presents you with useful tips and techniques in order to
help you use the site to the full.
This page presents you with useful tips and techniques in order to
help you use the site to the full.
This page presents you with useful tips and techniques in order to
help you use the site to the full.
--
+
-
Search Guide
Guide de Recherche
Search Guide
Search Guide
Guia de Cerca
Search Guide
Guia de buscas
Search Guide
Search Guide
Search Guide
Search Guide
Search Guide
Search Guide
Search Guide
Search Guide
Search Guide
Search Guide
Search Guide
Search Guide
Search Guide
-
Full guide on how to search
Le guide complet sur comment rechercher sur
Full guide on how to search
Full guide on how to search
Guia completa de com cercar a l'
Full guide on how to search
Guia completo de como realizar buscas no
Full guide on how to search
Full guide on how to search
Full guide on how to search
Full guide on how to search
Full guide on how to search
Full guide on how to search
Full guide on how to search
Full guide on how to search
Full guide on how to search
Full guide on how to search
Full guide on how to search
Full guide on how to search
Full guide on how to search
.
diff --git a/modules/websearch/doc/search-tips.webdoc b/modules/websearch/doc/search-tips.webdoc
index 72d8d7d5b..84a8fcca3 100644
--- a/modules/websearch/doc/search-tips.webdoc
+++ b/modules/websearch/doc/search-tips.webdoc
@@ -1,305 +1,305 @@
## -*- mode: html; coding: utf-8; -*-
## $Id$
## This file is part of CDS Invenio.
## Copyright (C) 2002, 2003, 2004, 2005, 2006, 2007 CERN.
##
## CDS Invenio is free software; you can redistribute it and/or
## modify it under the terms of the GNU General Public License as
## published by the Free Software Foundation; either version 2 of the
## License, or (at your option) any later version.
##
## CDS Invenio is distributed in the hope that it will be useful, but
## WITHOUT ANY WARRANTY; without even the implied warranty of
## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
## General Public License for more details.
##
## You should have received a copy of the GNU General Public License
## along with CDS Invenio; if not, write to the Free Software Foundation, Inc.,
## 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.
-
+
How to find any value in any field:
|
Empty search box returns all records in the database.
|
How to find documents in a particular collection:
|
Click on a link below the search box to see and select subcollections
such as Preprints or Theses, or select/deselect the tick boxes next to a
particular collection before doing the search.
|
|
If you want documents from a 'collection' not proposed by default,
such as NA60 documents, then enter it as a search term.
|
-
+
How to search for words/phrases (within titles, abstracts, etc):
|
Returns records containing words higgs and boson.
|
|
Returns records containing phrase 'higgs boson' in title.
|
|
Returns records entitled exactly "Higgs boson" but not records such as
"Overview of Higgs boson production".
|
-
+
How to use truncation:
|
Returns records containing words muon, muons, muonic, etc.
|
-
+
How to use boolean operators:
or:
|
Returns records containing both muon and kaon.
|
|
Returns records containing either muon or kaon.
|
|
Returns records containing muon but not kaon.
|
-
+
How to find documents from a certain period:
|
Type 2003 and select the year field.
|
|
Alternatively, type field name colon value.
|
|
You can enter specific year range.
|
-
+
How to search for authors:
|
Some authors have unique names and
their publications can be retrieved by searching for
the surname in any field.
|
|
For better results, type surname comma initial(s) and select the author field.
|
|
Sometimes authors are indexed with their full name.
|
|
Find papers by J.Ellis written from 1990 until 1993, using truncation
to match all first names beginning with J.
|
-
+
More information:
Special characters, regular expressions, fulltext searching, citation
searching, and other capabilities are fully explained in the complete
-Search Guide.
+Search Guide.