Differences

This shows you the differences between two versions of the page.

--- ebscohost_maintenance [2019/10/10 12:17]
jmulvaney [SFX Linking]
+++ ebscohost_maintenance [2022/08/23 19:27] (current)
jmulvaney
@@ Line 5: / Line 5: @@
 **Also See**
   * [[hlm_admin_maintenance|HLM Admin Maintenance]]
-  * [[ebsco_regular_tasks|EDS & HLM Regular Tasks]]
   * [[eds_admin_management|EDS Admin Management]]
+==== 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 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 [[https://connect.ebsco.com/s/article/How-can-I-search-for-content-by-date-using-the-DT-field-code?language=en_US|found here.]]
 ==== Finding Indexed and Full Text Content ====
@@ Line 12: / Line 33: @@
 ==== 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.
+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.
+==== Full Text Finder ====
+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.
-==== SFX Linking ====
+==== Profiles ====
-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. **
+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.
+  * ConsumerReports.org	is non-configurable
-These CLs cascade down to all EBSCOhost databases, regardless of if they have a specific profile. For instance, CINAHL has a profile with no CustomLinks but still uses SFX linking. These CLs are set to "Always Show," with the secondary setting to suppress the CL based on the "Hide if Full Text" toggle. The local collection "EDRS Exclude (umaah.edex)" is selected, 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.**
+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.
+==== Branding ====
+  * The branding tab for the main and individual EHost profiles should match EDS wherever possible. We use the traditional rather than enhanced branding so some options are not configurable.
+  * Advanced branding is handled through the [UMAAH] EHOST bottom branding document. It currently only includes the Favicon Icon but could be expanded to include more of the customizations we have made to EDS.
  --- //[[jmulvaney@library.umass.edu|Primary contact: Jack Mulvaney]]//