Miscellaneous information about SFX. Some SFX-related files may be found in R/S:\Acquisitions\SFX. Help with SFX terms is available at this SFX glossary.

SFX Object types: DATABASE will not display on the A-Z list. JOURNAL will.

Currently (2013) this is only available for Miscellaneous targets. Make local changes in Object Portfolio Edit screen and submit. “Contribute” button should then show in the OP View screen.

SFX provides a tool for composing local thresholds in the object portfolio edit screen.

Reporting incorrect date thresholds:

• For ejournal packages and databases, report incorrect date thresholds to the publisher/vendor if the corrected date threshold will apply to all ExLibris customers. ExLibris has automated its loading of title lists. Even if ExLibris complies with our request, publisher/vendor title lists may remain unchanged so our fix would be temporary.
• For individual subscriptions, report incorrect date thresholds to ExLibris if the corrected date threshold will apply to all ExLibris customers.
• Only NERL can submit date threshold change requests to ExLibris for their package targets.
• Create a local threshold if the dates are per our licensed agreement with the publisher/vendor.
• Add a General Note in the object portfolio edit screen if it will be helpful to users. Example: “ Content may not yet be available.”
• Add an internal note if appropriate.

Embargoes and moving walls: Use the composer tool to set up an embargo. For a 1 year embargo use the text below. NOTE: do not use “==” which does not display an embargo on the menu.

• In the edit screen, click “Add Local” beside Threshold (Global), click “Compose”, fill in First Publication (year at least), click down arrow beside “Embargo/Moving wall”. For a 1 year embargo choose “greater than or equal to”, choose time (“1 year” ago). For other time increments, choose one from the drop down and edit afterward.
• Resulting date threshold should look something like this:
  • $obj→parsedDate('>=','2007',undef,undef) && $obj→timediff('>=','1y')

Split date thresholds: Use “||” to separate the runs. For example, holdings from 1999-2002 and 2008 would use the text below. This displays as “Available from 1999 until 2002, Available in 2008”.

• $obj→parsedDate('>=','1999',undef,undef) && $obj→parsedDate('⇐','2002',undef,undef) || $obj→parsedDate('==','2008',undef,undef)

SFX images are located at R:\Content&Discovery\Information_Resources_Management\DRMS\SFX\SFX_Project\Images. Images are also available on the CMS for those who have access.

Contact Josh in systems for customizations.

For customizations of full screen and mobile menu headers, UMLinks buttons, multi-object menus and more, see the SFX users guides.

Some targets require flag values to enable the functioning of open URLs. For information about specific target L/P codes see the SFX Target and Alma E-Collection Configuration. L/P values should be added to CORAL Access notes (if there are many databases see main resource, such as EBSCOHost Academic Search Premier).

Past problems have been:

• L/P edit boxes may mysteriously disappear. Go to the target service edit screen, open a local parse param, put in a blank space, submit, go back in and clear local parse param, and the L/P edit box should return.
• L/P flags may appear to be in place but may need to be re-entered after an update to the target.

Internal Note fields. Use these notes:

• PA to (dates)
• Prev title (to…title optional)
• Accessible (dates)
• Free for (dates)
• OA
• Continues (title)

General Note fields. Use these notes:

• Current issues may not be available.
• Content may not yet be available.
• Some full text content may not be available.
• Some years are not available.
• Additional content may be available.
• We are working on restoring access.

MARCIt records are no longer being used but this list of object types is still useful. The following object types are considered serials (and generated MARCIt records).

• Journal
• Conference
• Newspaper
• Series
• Transcript
• Wire
• Database (as object)

The following object types are not considered serials (and did not generate MARCIt records).

• Book
• CD
• Dissertation
• Document
• Manuscript
• Proceeding
• Report

Lists all files for which symbolic links to global SFX files have been broken. SFX UNIX side.

• da; ./server_admin_util; 2=Filesystem maintenance; 8=Check for broken symbolic links; Save output in file=N; Recreate symbolic links?=N
• NEVER recreate symbolic links here!!! UMass custom files are included.

Lists targets which lack activations at the target, target service, or object portfolio level. SFX UNIX side. Report is saved in the dbs/scratch directory.

• da; ./server_admin_util; 6=Diagnostics; 6=Report Incomplete Activations.

See SFX users guides.

When target precedence on SFX menus needs a general update, use the sort_services.config file and activate by wizard.

• Export active targets.
• Check active targets against SFX Admin/UNIX File Manager/config/sort_services.config. This config file is organized by most reliable publishers, lesser reliable publishers, aggregators and databases, newspapers, ebooks, open access and free, and target and menu services other than getFullTxt. Do not include bX.
• Go to SFX Admin > Menu Configuration > Menu Design > Simplified Template and Mobile Configuration > Service Precedence – take a snip copy of “Chosen service types” (do not include bX or use getRecommendation for bX), which should be: getFullTxt, getSelectedFullTxt, getMessageNoFullTxt, getHolding, getDocumentDelivery. Make sure these remain when process is finished.
• SFX Admin > Menu Configuration > Menu Design > Simplified Template and Mobile Configuration > Target Precedence. Run Import Precedence Wizard.
  • Select Basic services config.
  • Uncheck all but sort_services_config_ AND basic_grouping.config_ (may need to click through intro screen first)
  • SAVE
• Check sample changes on SFX menus.

Send support cases to Salesforce.

Add cknapp@library.umass.edu to support case “Additional emails” section if you would like Catherine to track the case. As of 2016, dbhelpers are focusing on getting articles to patrons, not reporting metadata problems unless it is worth the time. General guidelines (with plenty of exceptions):

• Report to SFX: Problems with linking (not metadata), SFX functionality, requests to update a target, questions about platform changes and targets, etc. ExLibris is often not interested in metadata problems because they are relying on publisher/vendor data to inform targets. The exception is individual subscriptions, especially in the MISCELLANEOUS EJOURNALS or Highwire targets. Do not report metadata problems for databases or NERL targets (contact publisher or NERL to request they send updated files to ExLibris). For journal packages, use best judgement.
• Report to publisher/vendor: Important metadata problems, problems with web sites or title lists, etc.

If we have installed any patched parsers, which are now supplied by the update, you will need to reconnect the symbolic link so we get future updates to the file:

• Login to SFX instance UNIX-side as instance user.
• Go to the appropriate directory for the file you wish to relink (e.g. “tp”) for target parsers and move to the appropriate subdirectory (e.g. “cd filename”)
• Copy the current file for backup (e.g. “mv filename filename.bak” creates backup)
• Reconnect the link using the appropriate path (e.g. for SFX ver.4.1 “ln -s /exlibris/sfx_ver/sfx4_1/sfxglb41/lib/Parsers/TargetParser/Directoryname/filename”)
• To check if symbolic link is restored, “vi filename”, “N” when asked if you want to break symbolic link, “:q!” to quit without saving.
• Restart Apache. Type apachectl restart OR go to the ./server_admin_util menu and restart the Apache instance.
• Example if JSTOR is filename.
  • tp
  • cd JSTOR
  • mv JSTOR.pm JSTOR.pm.bak
  • ln -s /exlibris/sfx_ver/sfx4_1/sfxglb41/lib/Parsers/TargetParser/JSTOR/JSTOR.pm
  • Restart: da, ./server_admin_util, 1=Start Stop Services, 8=Instance Apache Restart, q=quit, exit.
• See p.19 of the SFX System Administration Guide for instructions on restoring symlinks.

AutoUpdate: Usually we want AutoUpdate checked so that ExLibris maintains the target. If AutoUpdate is checked, local target service parser and parse param, as well as local object portfolio parser and parse params, can be changed by ExLibris during an update. Do not check AutoUpdate when we want our local information to remain intact (e.g. ILLIAD), or because we have made changes to the parser (e.g. ProQuest Dissertations and Theses) either long term or temporarily.

AutoActive should be checked if we have access to all items in a target and want ExLibris to manage activation. We do not want AutoUpdate checked if we partially activate a target.

Proxy should be checked if we want to run linking through EZProxy. We do not proxy open access or ebrary.

— Primary contact: Catherine Knapp