Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
sfx_routine_maintenance [2016/09/21 15:41] cknapp |
sfx_routine_maintenance [2016/09/21 16:13] cknapp [Support Cases] |
||
|---|---|---|---|
| Line 17: | Line 17: | ||
| * Add an internal note if appropriate. | * Add an internal note if appropriate. | ||
| - | **Embargoes**: 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. | + | **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). | + | * 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') | + | * 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". | **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". | ||
| Line 29: | Line 30: | ||
| Contact Josh in systems for customizations. | Contact Josh in systems for customizations. | ||
| - | For customizations of full screen and mobile menu headers, UMLinks buttons, multi-object menus and more, see the [[http://knowledge.exlibrisgroup.com/SFX/Product_Documentation/01_Version_4.0 | SFX user's guides.]] | + | For customizations of full screen and mobile menu headers, UMLinks buttons, multi-object menus and more, see the [[http://knowledge.exlibrisgroup.com/SFX/Product_Documentation/01_Version_4.0 | SFX users guides.]] |
| ==== L/P Linking Parameters and Flag Values ==== | ==== L/P Linking Parameters and Flag Values ==== | ||
| - | Some targets require flag values to enable the functioning of open URLs. | + | Some targets require flag values to enable the functioning of open URLs. For information about specific target L/P codes see the [[ http://knowledge.exlibrisgroup.com/SFX/Product_Documentation/02_KnowledgeBase_Information|SFX Target and Alma E-Collection Configuration.]] |
| + | |||
| + | 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 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. | * L/P flags may appear to be in place but may need to be re-entered after an update to the target. | ||
| Line 82: | Line 85: | ||
| ==== SFX Documentation and User's Guides ==== | ==== SFX Documentation and User's Guides ==== | ||
| - | See [[http://knowledge.exlibrisgroup.com/SFX/Product_Documentation/01_Version_4.0 | SFX user's guides.]] | + | See [[http://knowledge.exlibrisgroup.com/SFX/Product_Documentation/01_Version_4.0 | SFX users guides.]] |
| ==== Support Cases ==== | ==== Support Cases ==== | ||
| + | Send support cases to [[https://exlidp.exlibrisgroup.com | Salesforce.]] | ||
| + | |||
| Add cknapp@library.umass.edu to support case "Additional emails" section if you would like Catherine to track the case. | 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): | 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, SFX functionality, requests to update a target, questions about platform changes and targets, etc. ExLibris is not interested in metadata problems because they are relying on 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 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 vendor: Important metadata problems, problems with web sites or title lists, etc. | + | * Report to publisher/vendor: Important metadata problems, problems with web sites or title lists, etc. |
