Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Status

IN PROGRESS

Description

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 would like us to think about how to frame informative documentation to make the decision tree "mean something” and articulate why a campus might make a specific decision (or why not) so that campuses can decide the best way to represent their individual collections to researchers.

Impact

Priority

Dependencies with other groups

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

Notes and links to reference documents

Digital Collections Project Team Overview: https://uc-sils.atlassian.net/wiki/spaces/DCPT
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

Sandbox Testing Collections: https://docs.google.com/spreadsheets/d/1BMNSa6MEZYIwf-cUZGehaYwbTblz47CXMpLhxoLLbeY/edit#gid=0

Existing Salesforce tickets

Band-aid

Target decision date

Date decided

Discussion

Question:

  1. Why might a campus want to share item level records from a collection in Primo?

  2. Why might a campus want to share a collection level record in Primo (instead of item level)?

  3. Are there other options in Primo to improve collection visibility?

    1. Adding a link to Calisphere into the Available Online section of the Collection Record

    2. Collection Discovery?

Example 1:

Catherine Clark Papers. Harvested from Calisphere

https://uclibraries-psb.primo.exlibrisgroup.com/discovery/search?query=any,contains,catherine clark&tab=DiscoveryNetwork&search_scope=DiscoveryNetwork&vid=01UCS_NETWORK:UCS_UNION&offset=0

Harry Mayo Surfing Photography (Individual photographs, no real context)

https://uclibraries-psb.primo.exlibrisgroup.com/discovery/search?query=any,contains,harry%20mayo&tab=DiscoveryNetwork&search_scope=DiscoveryNetwork&vid=01UCS_NETWORK:UCS_UNION&offset=0

Recommendation

Describe the final recommendation/decision.

[Trashy notes]

[] Question 1: Why might a campus want to share item level records from a collection in Primo?

Item level could create greater visibility
item level doesn't provide context, but it does let them

[] Question 2: Why might a campus want to share a collection level record in Primo (instead of item level)?

collection level def needs to have the link moved up into get it, but terminology needs to be updated. RM has discussed the tech aspects of moving the link. So double check with them.

Undergrad needs to understand that the link takes them to the collection. Could we recommend phrasing? Why not?

We see the scenarios, then come up with recommended phrasing.

not every student is coming at it from this from a collection level.

How are the students accessing this?
I want outfits from the Persian dynasty.
How do we let our students get to the individual items?
But it also has to work for upper grad.

labels this group can apply at the disc level
and also the metadata
do we need a joint meeting to hash it all out?

in order for this to be usable we need x, y, z, then it has to go to the RM groups to make it happen.

Ultimately we need to test it against the users looking for primary sources.

[] Question 3: Are there other options in Primo to improve collection visibility?

qualify that we're giving our recommendation based on limited information.
Then there's testing if each campus is doing things differently, so there is a local component to teh UX.

ACTION: I'll draft up a recommendation, we can look at it, make tweaks and then I'll submit it.

  • No labels