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 [2019/02/13 21:19] cknapp |
sfx_routine_maintenance [2019/02/13 21:24] cknapp [Support Cases] |
||
---|---|---|---|
Line 93: | Line 93: | ||
==== Notes for Public View on SFX Menu ==== | ==== Notes for Public View on SFX Menu ==== | ||
- | Notes can be added to the target service or object portfolio general notes field for public view. Format like this (see in wiki edit mode): | + | Notes can be added to the target service or object portfolio general notes field for public view. For direct linking to publisher sites as a workaround to target problems, format like this (view in wiki edit mode): |
Reach an error message? Try searching <A HREF="https://www.sciencedirect.com/browse/journals-and-books?contentType=JL">Science Direct ejournals.</A> | Reach an error message? Try searching <A HREF="https://www.sciencedirect.com/browse/journals-and-books?contentType=JL">Science Direct ejournals.</A> | ||
==== Object Portfolio Edit Notes ==== | ==== Object Portfolio Edit Notes ==== | ||
- | 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. | + | 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. Here are formats used. |
* General Note fields. Use these notes: | * General Note fields. Use these notes: | ||
* Current issues may not be available. | * Current issues may not be available. | ||
Line 161: | Line 161: | ||
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 (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 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 association targets like Highwire. 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. | + | * Report to publisher/vendor: Important metadata problems (not single article, supplement, or issue), problems with web sites or title lists, etc. |