Skip to main content
Stanford
NetDB Help

Full Search

Full Search is more powerful and complete than Quick Search. Users can search using every field of each record type.

Expressions

Below is a list of wildcards, separators, boolean operators, etc that are supported in search values:

  1. All fields are case insensitive except regular expressions.
  2. Wildcards
    • * and % are multi-character wildcards
    • ? and _ are single character wildcards
  3. Regular Expressions
    • Strings enclosed in forward slashes are treated as regular expressions. Regular expressions are case sensitive; adding 'i' after the closing slash makes them case insensitive. Details of the regular expression syntax used in NetDB can be found here.
  4. Separators
    • separators are spaces and carriage returns
    • trailing and leading spaces are stripped off unless quoted
  5. Quotes
    • String fields with spaces must be enclosed in double quotes. First double quote must be preceded by separator or beginning of line. Double quotes, which are part of the field itself must be escaped with backslashes (\). Backslashes must be escaped with another backslash, i.e. \\.
  6. Boolean Operators - listed in order of precedence
    • NOT operators: "NOT" , "not".
    • AND operators: "AND", "and"
    • OR operators: "OR", "or".
    • grouping operators, i.e. parenthesis : "(" and ")".

Table of Search Fields

Below is a table showing the fields on the full search pages. The first column lists the field name. The second column, field type, describes how to search for the information. The field types are described in detail below. The subsequent columns are checked if that field is in the respective full search. To see explanations of what each field means, please see the help pages linked in the headings of each column.

Field Name Field Type Node User Network Group Admin Team Domain
Active radio   X        
Address Space string     X      
Administrator string X         X
Assign Names in string           X
Code string X          
Comments string X X X X X X
Created By string X X X X X X
Created When date X X X X X X
Custom Field label X          
Default Address Space string   X        
Default Domain string   X        
Default Group string   X        
Delegated Domain radio           X
Department string X       X  
DHCP radio X          
DHCP Options label X   X      
DHCP Service string     X      
Email string   X     X  
Expiration Date date X          
Group string X X X   X X
Hardware Address hardware address X          
IP Address IP address X   X      
PTR Preference radio X          
IP Address Status radio X   X      
Field Name Field Type Node User Network Group Admin Team Domain
Last Login date   X        
Limited Domain radio           X
LNA Department string   X        
Location string X   X      
Make/Model string X          
Member string         X  
Modified By string X X X X X X
Modified When date X X X X X X
MX string X          
Name string X X X X X X
Name Type checkbox X          
Nameserver string           X
Networking Consultant string   X        
Node Type checkbox X          
Node User string X          
OAuth ID string   X        
OS string X          
Phone string   X     X  
Record Type Access checkbox   X        
Roaming radio X          
Room string X          
Site string X          
State string X          
Use as Name string           X
VLAN Area string     X      
VLAN Number string     X      

Field Types

Radio button

With radio buttons, one and only one selection must be made. Radio buttons are used for simple fields where one and only one choice must be made (DHCP, Roaming, Active, etc).

Checkbox

Checkboxes are used when a field can be none, one or more values from a short list.

String fields

The string input field allows all the search expressions listed above. Note that Name fields (Node Name, Alias, MX) assume that the search is across all domains unless explicitly indicated.

It should be noted that due to the nature of HTML, multiple spaces may not be shown. For example, two Nodes may have comments "foo<space>bar" and "foo<space> <space>bar". If you take a look at the info for each Node, they may appear to have the same comment. However, performing a search for Nodes with the comment "foo<space>bar" will only find one Node.

Date fields

Dates must be entered in the following allowed formats. For 2 digit years, the rollover year is 50. In other words, years '00 to '49 actually mean years 2000 to 2049. Years '40 to '99 are assumed to mean years 1940 to 1999.

  • m/d/yyyy, m/dd/yyyy, mm/d/yyyy, mm/dd/yyyy
  • m-d-yyyy, m-dd-yyyy, mm-d-yyyy, mm-dd-yyyy
  • m/d/yy, m/dd/yy, mm/d/yy, mm/dd/yy
  • m-d-yy, m-dd-yy, mm-d-yy, mm-dd-yy
Wildcards are not allowed.

IP Address fields

IP Addresses can be searched for as strings or IP address ranges.

  • IP Address String Format
    • Wildcards are supported, but regular expressions are not.
  • IP Address Range Formats
    • w.x.y.z/n - address range expressed as a prefix (171.64.60.0/24)
    • w.x.y/n - address range expressed as a prefix without trailing zeroes (171.64.60/24)
    • w.x.y.z - smallest meaningful range, a single IP address (171.64.60.10)
    • w.x.y.z-a - address range expressed with a dash (171.64.60.42-46)
    • Wildcards and regular expressions are not supported.

Hardware Address fields

Punctuation and case are ignored in hardware address searches. The search engine will take the entire contents of the field and match it to a hardware address format. For example, hardware addresses may be shown as ABCD.1234.5678 or abcd12:345678. Either format is fine. Unlike searching for hardware addresses in Quck Search, Full Search allows the use of wildcards.

Label Fields

The two label fields are DHCP Options and Custom Fields. With exceptions noted is below, they are just like string fields. Searches should be in the following format:

  • <label or option>=<value> For example, if the DHCP option is "filename" and the value is "boot.txt", enter filename=boot.txt or "filename=boot.txt".
  • All the search expressions are supported.
  • If there is an equal sign in the label tag or label value, the equal sign must be escaped with "\".
  • If either label or value has a space in it, quote the entire expression. For example, if the custom tag is "monitor type" and the value is "viewsonic 15", search by quoting the entire string "monitor type=viewsonic 15"

Display Options

The default column order is the order of the fields on the Search page. The remaining column positions can be customized by selecting a value from the dropdown menu to the right of the fields. Selecting a column number always takes precedence over "Yes".

"-" do not display this column
"Yes" display this column in the default location.
"1" display this column first.
"2" display this column second.
"3" display this column third.

CSV (Comma Separated Value) Format

For easy import into a spreadsheet, search results can be displayed in CSV format by selecting "Generate result in CSV form" at the bottom of the search results page. Unlike the regular search results, where each record may have multiple lines if fields have multiple values, the CSV format has only one line per record with each field separated by commas. Multiple values for a field are separated by the pipe symbol (|). Save the CSV results as text into a file - then open the file with a spreadsheet. Excel will automatically recognize the file as CSV format if the filename has ".csv" as the extension.

Gotchas

Search for dhcp options or custom fields containing spaces in either name or value will fail, even if it is enclosed in double quotes. The workaround is to use asterisks (*) in place of spaces, e.g. for custom field "faculty=visiting*scholar"