Versions Compared

Old Version 27

changes.mady.by.user Lisa Spagnolo

Saved on

compared with

New Version 28

changes.mady.by.user Lisa Spagnolo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • A dedicated Slack channel for emerging issues to include designated campus and CDL electronic resources staff, as well as AEFG members. UPDATE NOTE: This Slack channel has been established as a communication mechanism for the Electronic Resources Subgroup, described below.

  • Weekly office hours for review of specific cases, record infrastructure issues, and any electronic resource related topic, hosted by AEFG, to continue during the immediate post-go-live period (reviewed at 30-60-90 days for any modification). UPDATE NOTE: These sessions are not yet established, but will be proposed as part of the AEFG Electronic Resources Subgroup Launch Session on 7/21. Weekly Workshop sessions have been scheduled for the Outbound Linking update project.

UPDATED FOR GO-LIVE: An AEFG Electronic Resources Project/Consultation Subgroup has been created to include those who work on electronic resources troubleshooting, manage administrative credentials and settings, and manage electronic inventory records. This subgroup will be consulting as needed on local campus Institution Zone (IZ)-level and CDL Network Zone (NZ)-level issues related to electronic resources.

...

Action/Point Person

Expected Completion Date

Discussion Notes

Status

AEFG starting discussion of this item week of May 10.

  • How to identify CDL vs IZ

    • = 6530

  • Wiki pages for recurring problems

  • Available for settings may not be as granular as needed

  • CDL e-resources tracking page: https://cdlib.org/services/collections/scp/tracking/e-resources-tracking-cdl-licensed-electronic-resources/

  • Need additional testing on “Available for” and Tier 2s

  • NZ CDL collections will not have package 793s

  • UC elinks – Report a problem

    • Fullfillment/Public services/Discovery should configure Primo Journal/Article page with help/ILL options

  • CZ collection issues should be submitted straight to ExL

  • IZs have access to Override URL fields in their electronic collections

    • Can IZs override NZ links?

    • Best practice: matter of urgency or consistency of NZ data?

  • Who reports CDI problems to ExL?

    • IZ issues

    • NZ issues

    • all IZ Salesforce worktickets should be CC’d to “someone TBD” at CDL

  • Policy questions:

    • EResources governance group

    • Start a page first – governance later

  • 11 am meeting slot

  • How detailed do we want to be re recommendations for troubleshooting?

Done

AEFG Coordination with CDL (Lisa S. discussing at PPC-NZ-CDL subgroup meetings and on Slack channel)

6/7/2021

  • First recurring migration/display issue: CDL needs to resolve 360 migration to fix “available for” groups (possibly through E-Resource governance group)

  • Is there an API or a cloud app to fix in batch?

  • CDL needs to make specific recommendations on submitting Alma and Primo issues on Helpline - Alison indicates if assessed to be NZ resource that is CDL, appropriate to submit via Helpline.

Done

Collaboration with Discovery FG, possibly End User Outreach Group

  •  Lisa Spagnolo will create separate decision page for configuring Primo VE options
  •  recurring/known issues needs to be communicated to UCs (CDL to do?)

  • Discovery and Fulfillment could provide input to Acq/ERM representatives in helping to configure general electronic services, ILL, and workticket submission options

    • NEEDS A SEPARATE MVP/GO LIVE DECISION PAGE: MVP 14

  • Fulfillment should determine which campus users can submit ILL forms and worktickets

  • Public services and technical services should coordinate on workflows to submit errors to technical services staff specializing in errors in linking, access, and/or cataloging

    • i.e., recommending internal coordination before submitting a ticket to CDL Helpline OR Salesforce

  • Campuses without existing error ticketing/databases are encouraged to organize their Primo and Alma error reports in a sustainable manner: some examples of free applications include:

    • Trello

    • Teams

    • Asana

    • Springshare

    • Or create a a homegrown system

    • Consider creating tags or other ways of categorizing worktickets to maximize later data-gathering about errors

Done - note open action item to be developed.

AEFG Recommendation Approval

6/9/2021

Approved! 5s with 4s indicate wanting to review for any gaps

Done

Final Approval by PPC

6/11/2021

Approved

Done

Distribution and Communication Follow-up (including any End-User Outreach Group or other training/documentation).

6/14/2021

Done

Revision to reflect updates after Decision Page approval. / Lisa Spagnolo

7/20/2021

  • Reflects creation of E-Resources Subgroup for consultation and coordination. Added notes to recommendations to indicate creation of Slack channel and getting input for an hourly e-res troubleshooting “office hour.”

  • Links to Known Issues Page for Alma/Primo VE.

  • Clarifies use of SalesForce in context of How to Report a Problem guidelines.

  • Links to CDL’s Report a Problem webpage.

In progress (drafted, to review/refine)