Search options available in STN databases - FIZ Karlsruhe
Search options available in STN databases - FIZ Karlsruhe
Search options available in STN databases - FIZ Karlsruhe
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Search</strong> examples<br />
28.1.3 L<strong>in</strong>k<strong>in</strong>g classification and text search<br />
Classification codes were found for all aspects of the search question. As a pla<strong>in</strong> classification search may lead to a<br />
large number of hits (<strong>in</strong> particular <strong>in</strong> <strong>in</strong>ternational <strong>databases</strong>) the search by classification should be l<strong>in</strong>ked to the<br />
search by keywords. The various comb<strong>in</strong>ations of classification codes (IPC) and keywords should be considered, e.g.:<br />
1. IPC (brakes for skates) AND Keywords (<strong>in</strong>-l<strong>in</strong>e skates)<br />
2. IPC (<strong>in</strong>-l<strong>in</strong>e skates) AND Keywords (brakes)<br />
3. IPC (brakes for skates) AND IPC (<strong>in</strong>-l<strong>in</strong>e skates)<br />
4. Keywords (<strong>in</strong>-l<strong>in</strong>e skates) AND Keywords (brakes)<br />
At last the <strong>in</strong>dividual results are comb<strong>in</strong>ed by OR to form the overall result.<br />
Comb<strong>in</strong>ation (3) improves the overall result <strong>in</strong> particular for documents lack<strong>in</strong>g text fields (e.g. utility models <strong>in</strong><br />
PATDPA, where there is neither an abstract nor a claim) while comb<strong>in</strong>ation (4) yields an improved result with <strong>in</strong>complete<br />
or unfavourable classification.<br />
28.1.4 <strong>Search</strong> with IPC: DWPI, alternative 1<br />
(Bibliographic file <strong>in</strong> English, IPC8 with re-classification, us<strong>in</strong>g the field IPC for IPC1 8, for IPC1 7 the ICI and ICA<br />
fields are <strong>in</strong>cluded, attributes are not used <strong>in</strong> this example, range search<strong>in</strong>g)<br />
28.1.4.1 Command file for search<strong>in</strong>g with <strong>STN</strong> Express<br />
Monitor<strong>in</strong>g patents<br />
\* SEARCH "BRAKES FOR INLINE-SKATES" IN THE WPINDEX FILE<br />
=> fil wp<strong>in</strong>dex<br />
\* IPC: ASPECT -<br />
=> s (a63c0017-04-a63c0017-08)/ipc\> _IPC<strong>in</strong>lsk<br />
\<br />
=> s (a63c0017-14 or b60t)/ipc\> _IPCbrake<br />
\* KEYWORDS: ASPECT "IN-LINE SKATES"<br />
=> s ?skat?\> _kw1<br />
=> s ?rollerblad? or ?roller?(1a)?blad?\> _kw2<br />
=> s ?roller?(1a)?shoe?\> _kw3<br />
=> s _kw1-_kw3\> _kw4<br />
=> s <strong>in</strong>l<strong>in</strong>e or <strong>in</strong>-l<strong>in</strong>e\> _kw5<br />
=> s align##\> _sw6<br />
=> s (s<strong>in</strong>gle or one)(1a)(row# or track#)\> _kw7<br />
=> s _kw5-_kw7\> _kw8<br />
=> s _kw4(3a)_kw8\> _KW<strong>in</strong>lsk<br />
\* KEYWORDS: ASPECT "BRAKES"<br />
=> s ?brake? or ?brak<strong>in</strong>g or stop####\> _KWbrake<br />
\* LINKING<br />
=> s _IPC<strong>in</strong>lsk and _KWbrake\> _res1<br />
=> s _IPCbrake and _KW<strong>in</strong>lsk\> _res2<br />
=> s _KW<strong>in</strong>lsk and _KWbrake \> _res3<br />
=> s _IPC<strong>in</strong>lsk and _IPCbrake\> _res4<br />
=> s _res1-_res4\> _res<br />
28.1.4.2 <strong>Search</strong><br />
=> FIL WPINDEX<br />
FILE 'WPINDEX' ENTERED<br />
CCOPYRIGHT (C) 2011 THOMSON REUTERS<br />
-<br />
=> S (A63C0017-04-A63C0017-08)/IPC<br />
L1 2242 (A63C0017-04-A63C0017-08)/IPC (3 TERMS)<br />
(A63C0017-04+NEXT2/IPC)<br />
223