Versions Compared

Old Version 6

changes.mady.by.user Jessica Kruppa

Saved on

compared with

New Version 7

changes.mady.by.user Jessica Kruppa

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
See Best Practices for Decision Pages and Tags for groups
Legend:
Status
titlenot started
Status
colourYellow
titleIN PROGRESS
Status
colourRed
titleSTALLED
Status
colourGreen
titledecided
Page Properties

Status

Status
colourYellow
titleIN PROGRESSnot started

Description

Investigate how limit by availability is impacting UX; also assess/consider ILL impact

Impact

Priority

High

Dependencies with other groups

lots of input needed from local groups

Optional: recommendations on which group(s) might be assigned the work

Notes and links to reference documents

Getting reports of problems with records that we have no services available, no recourse for users to pursue. LibGuides have been a common complaint.

Existing Salesforce tickets

Band-aid

Target decision date

Date decided

Recommendation

Describe the final recommendation/decision.

Impact

...

Stakeholder group

...

Impact

...

Who does this decision affect? [name of the group]

...

Explain the significance of the decision to EACH stakeholder group. How will this decision impact this particular group? What will change? Do they need to take any action? If so, when?

...

Decision summary

Owning group

DISC

Approver

Final decider; group with the authority to approve the decision. Unless multiple groups are affected or additional staffing or finances are required, your group can approve its own decisions.

Consulted

eResources, Fulfillment

Informed

Groups/individuals who need to know about this decision.

For broad-reaching decisions, SILS has a cohort-wide email list (SILS-Cohort-L@ucop.edu) and slack channel for all SILS members #all-cohort. SILS News email list reaches ~500 self-subscribed UC staff (SILS-News-L@ucop.edu)

Decision-making process

Describe the process your group will use to make the decision.

Priority

High

Target decision date

[type // to add Date]

The date your group aims to make the decision. Allow time for consulting.

Date decided

[type // to add Date] You must add a date field for it to sort properly. It will not sort if you simply type the date.

The date the Approver approves the decision.

Background

Prior to the migration to a consortium, campuses were able to curate their CDI collections. While this required them to turn on access to individual collections, it also allowed them to weed out collections with poor metadata.

...

We are revisiting this issue in order to provide guidance and examples of the pros and cons of limiting by availability or not.

Options Considered

...

Option 2:

Option 1:

Option 2

Description

Limit CDI by Availability

CDI displays all results, regardless of availability

Description

Pros

Cons

Dependencies

Questions to consider

  • There was no good option with easy active vs fully flexible. There were pros and cons on both sides. Easy active was less work on the catalog side of things.

  • How does the EasyActive Exception List work? Is it theoretically possible to manually shut stuff off?

  • Consider that the whole point of this shared catalog thing was to get everything accessible by the UCs into one bucket for people to discover, even if it’s not currently on the shelf or subscribed to. An increased ILL Workload is definitely going to be a part of that.

    • What options do we have on the Discovery side to reduce the number of “bad” requests coming from inaccurate metadata records?

Action Log

Action/Point Person

Expected Completion Date

Notes

Status