Page Comparison

Sharing and Updates

Share any Discovery related information from other SILS groups

5

All

Update: Single OCLC symbol for consortia e-content.

Identify if the new information creates new concerns or if we’ll continue to wait for ILL’s decision.

all

This is in regards to using SCPER for all consortia e-content, not for using a single symbol for regular holdings.RM was asked:
How would the linking from WorldCat/FirstSearch to campus specific discovery instances work under this system? (How would OCLC know that I’m a UCR student with access to that item vs UCD student who doesn’t have access?)

How would information be identified and limited by material available for a specific campus?

RM’s response.
The ability to distinguish different campuses would not be possible within OCLC products for these records if they were set to a single symbol. The catalog links are taken from whatever is in the WC registry: http://www.worldcat.org/webservices/registry/xsl/search-advanced (I’m not sure who was tasked with updating the registry for the *er symbols, but I suspect it was me and I didn’t do it).
Each symbol can have only ONE catalog link.The CDLER symbol does not currently have any online catalog at all (http://www.worldcat.org/webservices/registry/Institutions/132451 ), meaning that (right now), no link to a campus would be provided. (I would guess the decision about what the link would be, if any, would fall to Discovery OST, should this decision go forward).(As this is only related to consortia e-content, not to individual campus content, does anyone think there would be any Discovery concerns?)Discussion Page: https://uc-sils.atlassian.net/wiki/spaces/DIS/pages/1889271842/Discovery+Impact+of+Resource+Management+s+OCLC+Streamlined+Worldcat+Holdings+Project+2022

•  Jessica will e-mail the Resource Management chair with DISC’s concerns and a request for examples to better understand how users will access e-Resources content under a single SCPER symbol.

Revisit: Shared Code Repository

Joshua Gomez Gem Stone-Logan

Mobile usability issues

Shared Repository Proposal: https://docs.google.com/document/d/1IEdjMzrhoLfOl6a5AmUCevhZywXuiM31jebHhJJ91Hs/edit#heading=h.36u2v11b1agr

Team approved GitHub proposal. Gem is sending it up the ladder.

Joshua, Sean, and Michael will meet to discuss how to best handle reviewing source code.

Review: excluding CDI ebooks

Identify pros/cons of including/excluding CDI eBooks from default Articles, books, and more.

all

Discussion Page: Exclude eBooks from CDI Results [Phase 4 delegated]

UCI Testing View for excluding CDI eBooks

Questions to consider:

• What are the potential risks of enabling “Exclude eBooks from CDI Results”?

• Are there any serious current problems that could be solved by enabling “Exclude eBooks from CDI Results”?

Team has not had ample opportunity for testing.

We will revisit this issue when we’ve had time to do actual testing.

•  Jessica will update the Discussion Page to include areas for the team to add questions, thoughts, and updates moving forward.

Review: How do the campuses utilize 930/973 fields?

Discussion Page: Discovery Impact: 930/973 fields - Practice for Continued Use

• Do your local campuses use a local MARC field like 973? Or do they use Alma’s built in tools?

• Does this use have any impact on the Discovery or is it only a back-end staff use field?

930/973 fields- practice for continued use

Description: These fields are used by CDL and campuses to pull together e-resource packages. There is a need to evaluate how effective these are and whether Alma has a better alternative, including relying on on e-resource Collection Names instead.

The Digital Collections Project Team is seeking Discovery's feedback on a project they inherited from phase 4.The "Digital Collections Decision Tree" is a tool to help campuses decide if they want to share their digital collections (typically archival, if I understood right) in UC Library Search and, if so, how to best represent those collections.They're looking for our initial "hot take" on this tree and the documentation, as well as any questions or concerns we may have.Further, they would like us to think about how to frame informative documentation to make the decision tree "mean something." For example, answering the question of WHY (and why not) a campus might want to share their digital collections in the first place, WHY they might not want to share the entire collection, etc.Below are some documents that they sent me. Try and give them a look and we can start discussions on Friday.Digital Collections Project Team Overview: https://uc-sils.atlassian.net/wiki/spaces/DCPT/overview
Decision Tree: https://drive.google.com/file/d/105NFzVUSLhho3FW_fiNEV30iXNj95Cej/view?usp=sharing
Decision Tree Companion Document: https://docs.google.com/document/d/19G-O5ZtrK9oMPK0o2U9sHl1sEcdUwb5ki2SItQY8VPQ/edit#
Decision Tree documents: https://drive.google.com/drive/folders/1CwJCyeNLox-J9cHaQMrXnpfvo0ies7Qg

It doesn’t seem like any campus uses the 973 locally to track e-collections anymore, but they do use it for legacy information.

•  Jessica will gather the documentation needed for campuses that may want to keep using the 973 locally going forward

Review: Digital Collections Decision Tree

Discussion Page: Digital Collections Decision Tree

•  Jessica will ask DCPT if there are sandbox examples of collections that we can look at so we can better understand the impact each branch of the tree has on discovery.

Standing Item: Review Issues Spreadsheet and Parking Lot.

Issue tracking decision still pending (Shared code repository may be involved)

Wrap up

Review actions and decisions

5

Parking Lot

Capture important topics for future discussion:

Discussion Parking Lot / Future Topics

Total

45