Management of content in EBSCOhost is not quite the same as managing content in EDS.
Also See
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 Text | Performs 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-Author | Performs a keyword search for any authors of an article. |
| TI-Title | Searches keywords in a record's English and non-English title field. |
| JN-Journal Title | Searches keywords in a record's Journal Title title field. |
| SU-Subject Terms | Performs a keyword search of the subject headings listed in the records. |
| DE-Exact Subject heading | Performs a search for exact subject headings within the Subject Fields section of a citation. |
| SO-Source | Performs a keyword search for the journal name of the article. |
| AB-Abstract | Performs a keyword search of the abstract summaries. |
| IS-ISSN | Performs an exact search for a publication's International Standard Serial Number. |
| IB-ISBN | Performs an exact search for an article's identification number in the ISBN and EISBN fields. |
| FT Y | Use in conjunction with a Boolean Operator to find all Full Text for a Search Term |
| FM T | Use in conjunction with a Boolean Operator to find all HTML Full Text for a Search Term |
| FM P | Use in conjunction with a Boolean Operator to find all PDF Full Text for a Search Term |
| FM C | Use 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 # |
| NU | Performs 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.
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.
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.
A separate version of the Full Text Finder customlink exists for the EBSCOHost resources. [UMAAH SERVICE] FTF - EHOST Full Text Finder is configured to show Always and does not use the local collection backed by HLM as a limiter. This is so records with no full text (and with no corresponding subscription accessible via FTF) can have a way to be requested via ILL. Patrons will be able to click the FTF button and submit an ILL request using the HLM link as opposed to the ILL CustomLink. The ILL CustomLink should not be used in EHOST because the EHOST profiles have no way of setting only 1 link to show - so ILL and FTF links will appear together on the same record. This change was made in August 2022 based on feedback from the science librarians.
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.
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 be 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.