This is an old revision of the document!

EBSCOhost Database Maintenance

Management of content in EBSCOhost is not quite the same as managing content in EDS.

Also See

Field Code Searching

Field codes allow for searching individual metadata fields in EDS and EBSCOhost. There is no centralized place on EBSCOConnect where this lives. Below are some of the most important.

TX-All TextPerforms a keyword search of all the database's searchable fields. Using the TX field code will cause the search to look for the keyword in the full text as well as the citation record.
AU-AuthorPerforms a keyword search for any authors of an article.
TI-TitleSearches keywords in a record's English and non-English title field.
JN-Journal TitleSearches keywords in a record's Journal Title title field.
SU-Subject TermsPerforms a keyword search of the subject headings listed in the records.
DE-Exact Subject headingPerforms a search for exact subject headings within the Subject Fields section of a citation.
SO-SourcePerforms a keyword search for the journal name of the article.
AB-AbstractPerforms a keyword search of the abstract summaries.
IS-ISSNPerforms an exact search for a publication's International Standard Serial Number.
IB-ISBNPerforms an exact search for an article's identification number in the ISBN and EISBN fields.
FT YUse in conjunction with a Boolean Operator to find all Full Text for a Search Term
FM TUse in conjunction with a Boolean Operator to find all HTML Full Text for a Search Term
FM PUse in conjunction with a Boolean Operator to find all PDF Full Text for a Search Term
FM CUse in conjunction with a Boolean Operator to find all HTML Full Text with Graphics for a Search Term
OC Unclear: Using this field code in a KW Search with the space and then the lowercase prefix (ocn, etc) and the # will perform an index of Aleph records by OCLC #
NUPerforms a basic call number browse, but requires truncation. Example search for Call No. PA4020.P18 R984 2019 would be “NU PA4020*”

Additional field codes for date and time ranges can be found here.

Finding Indexed and Full Text Content

EBSCOhost indexes a wide variety of content, but not all records in EBSCOhost databases will link to full text. The journal Podiatry Review for instance has full text from 9/1/2009 to present, but has metadata indexed from 1/1/2008 to present. This can be found in the publication page in EBSCOhost. Click on the pub. title in the advanced record to find full holdings information. What is indexed versus what has full text is based on marketing and sales decisions by EBSCO. Title lists for ehost databases can be found here.

Native Linking

Primary linking for EBSCOhost databases is through direct links to PDF/HTML (Smart Links) and Linked Full Text (Smart Links Plus). Anything else is powered by CustomLinks (which we have chosen not to enable in EBSCOhost) and the link resolver CustomLink.


Many profiles exist in the Main User Group. We have several profiles for ehost databases. The most important is “EBSCOhost Web (ehost) - ehost” which covers all our EBSCOhost databases. A cleanup was performed in Spring 2020 to remove deprecated profiles. Those that remain are in use in the Database A-Z. All profiles (in all sites) were migrated to HTTPs as of May 2020. Settings can be reviewed in the Auth. menu under HTTPS.

  • EDS API, EIT: Webservice, and Z39.50 Client perform similar file transfer functions.
  • Search for Images remains. Collab. with RS to see if it is necessary.
  • New profiles should be created for FTF & PFUI once we go live.
  • Unclear if Flipster Mobile App is being used or if patrons are directed to Flipster but in a browser.
  • is non-configurable

The other three Groups have varying types of profiles. It is unclear what Remote was created for. UMAAH FTF Test should be removed after FTF and PFUI Go-Live and new test profiles should b created in Test. At that time, all profiles except for JGM1019 should be deleted, and new profiles should be created to reflect all live profiles.

SFX Linking

The main method of linking after native linking is through the SFX UMLinks. The CustomLink “SFX Link Resolver (Main User Group) EHOST” is attached to the “EBSCOhost Web (ehost) - ehost” profile in the Admin. It is joined by a specific CustomLink (SFX Link Resolver (GeoRef Only) UMAAH) for SFX linking through GeoRef. Bob has stated that he sees no need for this CL to exist. Apparently it only searches GeoRef, but it doesn't display because of the rankings in ehost and the main SFX CL is working fine.

These CLs cascade down to all EBSCOhost databases contained within a profile. The local collection “EDRS Exclude (umaah.edex)” is selected for the eHOST version, but is being ignored since the CL is set to always show if there is no other full text. Bob is unsure why the local collection would have ever been selected.

Primary contact: Jack Mulvaney

ebscohost_maintenance.1605707781.txt.gz · Last modified: 2020/11/18 08:56 by jmulvaney Creative Commons License Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0