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:51] cknapp [L/P Linking Parameters and Flag Values] |
sfx_routine_maintenance [2016/09/21 16:21] cknapp [Target Service Edit] |
||
|---|---|---|---|
| Line 88: | Line 88: | ||
| ==== 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. |
| Line 113: | Line 115: | ||
| ==== Target Service Edit ==== | ==== Target Service Edit ==== | ||
| - | **AutoUpdate**: If AutoUpdate is checked, local target service parser and parse param, as well as local object portfolio parser and parse params, will be removed. AutoUpdate should usually be checked but not in cases where we want our local information to remain intact (e.g. ILLIAD). We may want to retain a broken symbolic link because we have made changes to the parser (e.g. ProQuest Dissertations and Theses) either long term or temporarily. | + | **AutoUpdate**: If AutoUpdate is checked, local target service parser and parse param, as well as local object portfolio parser and parse params, can be removed by ExLibris during an update. AutoUpdate should be checked if we receive all items in a target and want ExLibris to update the target. We do not want AutoUpdate checked if we partially activate a target, 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. |
| ==== UMLinks Button, Images and Logos ==== | ==== UMLinks Button, Images and Logos ==== | ||
