2015-16 Deliverable Ideas

Nov. 2, 2015: Latest version of deliverable summary.

SFX Data From/And/In/To Other Systems.  
 

The committee will look at and document ways information gets into SFX and how SFX data are used by other systems. People are using SFX data in a number of different systems including PubMed/ NCBI, Worldcat (and/or other OCLC products), EBSCO Discovery Service, Google Scholar, Serials Solutions,  RefWorks, Illiad (& other ILL tools), CrossRef, EZ Proxy and e-magazine tools such as BrowZine.

We will focus on creating best practices and/or technical guides for how to manage these processes, and share these with the CARLI SFX community via the CARLI website

_____________________________________________________________________________________________________________________

1. Multiple KBs and link resolver tools

Many CARLI libraries use more than one knowledge base (KB) and link resolver tool. The committee will research how and why libraries manage multiple KBs/link resolvers.We will report on our findings in a document (potentially) discussing why multiple tools are used and how to reduce library staff doing similar tasks multiple times.  For example, SFX administrators could use the Export Tool, Dataloader and other SFX admin features to facilitate easier maintenance of other KBs/link resolvers such as Serial Solutions or OCLC Knowledge Base. (As related to Discovery products too.)

2. Local documentation writers' toolkit

What does the current SFX administrator need to have at her fingertips? What will the next SFX administrator wish the current administrator had written down? The committee could put together a local documentation writers' toolkit for SFX administrators. It might be comparable to (but more polished than) what the CARLI Office once put together for I-Share library liaisons. It might include places to record:

• SFX base URL and, if deployed, ejournal A-Z URL, ebook A-Z URL, CitationLinker URL
• Logon credentials for
  
  • SFX
  • SalesForce
  • Local ERM
  • Source systems' administrative interfaces
  • Sources or targets from which the SFX administrator would download usage statistics, to complement SFX usage data
• EZProxy or other proxy server information (Who administers? Where's documentation? Logon credentials, if relevant)
• Contact information for individuals in the library who know about eresource subscriptions, or, if the new SFX administrator must become this person and there is no ERM, contact info for account reps for all eresource subscriptions and packages.
• Archive of former years' usage stat reports
• Checklist of actions to take after each weekly update (the local, here's-how-we-do-it version of Andrea's video lesson)
• Printout of the troubletree, annotated with info about recurring or not-yet-resolved problems
• Where does LOCAL_FEEDBACK mail go?
• Local guidelines on how to select the right target to represent local holdings
• Local decision on whether to record print holdings in SFX, and how often to refresh them
• Local decision on free and OA targets
• Local decision on use of CARLI shared instance
• Local decision on "report a problem" options
• Local decision on related titles
• Discursive description of SFX Display Logic rules: what were you trying to accomplish?
• Local CrossRef information
• Originals of any graphics (banners, buttons) uploaded to SFX

As a complementary document, we could develop a checklist for new administrators: things you'll want to find out, if you haven't already (that is, if your predecessor failed to use our local documentation writers' toolkit!), about your library's SFX instance. This would be comparable to the Post-Training Checklist we developed years ago, when libraries were first bringing up SFX, but would be geared towards the new administrator who's taking over responsibility for an established instance, a kind of where-are-we-and-where-do-we-go-from-here? document, yet something that doesn't just replicate our "Beyond the Basics" pathfinder.

• Get a list of your library's eresources and compare it to your list of active targets. Are the raw counts about the same order of magnitude? Any glaring omissions?
• Is there a list of ejournals maintained outside of SFX that you can compare to an export or a count of ejournals activated in SFX?
• What are your most active sources, based on usage data? Has the library implemented GoogleScholar or PubMed yet?
• What are your most active targets, based on usage data? Does this surprise your eresources/serials person? Any glaring omissions?
• Where does LOCAL_FEEDBACK email go?
• How much enhanced linking has your library implemented? Related Books? CrossRef? DirectLink?
• How much look-and-feel customization has your library done? Simplified template? SFX button?
• Which public interfaces to SFX does your library deploy? Menu of services? A-Z? Citation Linker?
• What does the Localization Manager tell you about local thresholds or where the proxy box is checked?

3. SFX data from/and/in/to other systems.

The committee could look at ways information gets into SFX and how SFX data is used by other systems. I think we could focus on creating best practices and/or technical guides for how to manage these processes. People are using SFX data in a number of different systems including PubMed/ NCBI, Worldcat (and/or other OCLC products), EBSCO Discovery Service, Google Scholar, Serials Solutions,  RefWorks, Illiad (& other ILL tools), CrossRef, EZ Proxy and e-magazine tools such as BrowZine.

4. SFX workflow and intra library practices.

5. How are different libraries using SFX? (more of strategy than product?) ex. some libraries not use A to Z list. (dropped from consideration)