2024-09-13 Partner Call

Facilitator: @Heather Greer Klein

Note Taker: @Emily Lynema

Attendees

• @Jon Dunn

• @Stuart Kenny

• @Kirsten Leonard

• @Paul Walk

• @Karen Cariani

• @david.schober

• @Kate Lynch

• @Esmé Cowles

• @Alicia Morris

• @Nicholas Mark Homenda

• @Rob Kaufman

• @Emily Lynema

• @Jim Halliday

• @Glen Horton

• @Chris Awre

• @Robin Lindley Ruggaber

Agenda & Notes

1. Any other items for the agenda?
   
   

2. Discussion: Research data services for ingestion, identity management, and storage (Kate Lynch)

   1. see slides

   2. Research Data Services @ Princeton

      1. Princeton Data Commons (ingestion)

         1. submission and review of research data (https://datacommons.princeton.edu/describe). DOIs and DateCite integrations. Researchers make submissions and team of curators review submissions. Includes change history. https://github.com/pulibrary/pdc_describe

         2. PDC Discovery makes submissions available to public (https://datacommons.princeton.edu/discovery). Open source application based on Blacklight (https://github.com/pulibrary/pdc_discovery). Integration with Globus. Analytics collection with Plausible.io (focus on privacy). Presented at Open Repositories 2024.

      2. TigerData

         1. support for Research Data storage use and project creation; developed in collaboration with campus research computing. Learn more: https://tigerdata.princeton.edu

         2. Active development, soft launch with actual users soon

      3. ORCID@Princeton

         1. Encourage researchers to create link from Princeton ID to ORCID. https://orcid.princeton.edu. Open source: https://github.com/pulibrary/orcid_princeton

         2. Launched recently.

   3. How handling issues of scale? ex: instrumentation datasets, not tabular data

      1. Princeton: seeing more large data sets coming back to new system. Ex: millions of small files of instrumentation data. Use Globus to help orchestrate files into back-end storage. Starting to work with researchers to try to get them to restructure datasets in ways that actually make sense (paired down, tarball, etc). There is a human element to this problem, not just technical. Sometimes at really large scale, a different solution is needed (may not make sense to use this infrastructure).

      2. Data governance policy: https://datacommons.princeton.edu/discovery/policies

      3. Robin: having library be part of the visible conversation about how to recruit faculty and support research data can lead to funding for the library

   4. Tools for data packaging?

      1. Princeton: James Griffin has been looking into Hugging Face; interest in this but not lots of development yet

      2. David:

   5. Multiple ORCIDs? IU and Princeton are making researchers pick one ORCID.

   6. Licensed dataset discovery and access

      1. IU actively working on this; Northwestern being asked about it

      2. further out on the roadmap for Princeton - make these discoverable and accessible w/o duplicate purchases / content duplication

   7. What do others have in common with Princeton services?

      1. Northwestern: trying to tackle all these same problems currently.

   8. What areas for Research Data support is your institution focusing on?

      1. PALNI is trying to figure out how to move into research support. Health Sciences generating lots of research data; want to find researchers working in common

      2. IU: yes, collaborating with campus. University also interested in data purchased by univ for use and how to make it discoverable. Working on Hyrax for cataloging these data sets, but doesn’t connect with how data provisioned to users yet (ex: may be externally hosted). Have lots of storage available to researchers but lack good governance. Working on ORCID with Internet2 as part of COmanage to build better ORCID support into COmanage registry to connect your institution ID to ORCID and store in COmanage and be provisioned out to other authorized apps

   9. Are you collaborating outside the Libraries?
      
      

3. Hyku for Consortia Sustaining the Hyku Repository Platform IMLS grant

   1. As part of the Sustaining the Hyku Repository Platform IMLS grant, our team is researching previous practices in open source collaboration, and we'd love some community feedback! We are aware of It Takes a Village: Open Source Software Sustainability and Community Cultivation: A Field Guide. Are there other open-source community-building resources/tools? What are some successful models for open source collaboration to look at?

      1. funding in the grant for 2 consultants who may not be familiar with our corner of open source; may need to get them up to speed

      2. pass along any ideas to Kirsten or Heather

      3. Paul: Might be worth having a look at OSS Watch
         
         

4. Partner call annual check-up - quick Partner call survey

   1. Are we meeting at the right time and frequency?

      1. A number of people can’t attend at this time, or on Fridays. What we tried Thursdays at 12pm ET/9am PT/5pm GMT for 2025?

   2. What is most valuable and what doesn’t work well on this call; what would you like more of and/or less of

   3. Please complete by October 1, and share with your colleagues.
      
      

5. Community metrics

   1. Question that came up from COLMEX about how to provide data that will reflect community health over time

   2. For a community like Samvera with multiple platforms and tools, what metrics should we track to monitor community sustainability, growth, participation, etc?

   3. Will take this to the next Board meeting for continued discussion

   4. How do we know Samvera isn’t going away? Needs to be persuasive to organizational directors.

   5. Lots of different signs of health: annual budget, users, staying up to date on app maintenance, last commit, issue participation / closure rate

   6. What do we look for when looking for a system?

   7. narrative of how the community has evolved as needs and participants change
      
      

6. Hyrax/Hyku Community Sprints for critical dependencies and accessibility - please pledge hours

   1. September 30th - October 11th: critical Hyrax dependency discussions and upgrade work (Bootstrap 4 is EOL and has a security concern; Rails upgrade and dependancies are also a concern to get ahead of). This work will be important for the accessibility sprint as well.

   2. October 28-November 8: Accessibility

      Goal to address all reported WCAG 2.0 A and AA accessibility issues. We’re feeling ambitious and need your help!
      
      

7. Regional Meetings - updates and planning needs

   1. Midwest (9/25-9/26)

      1. 33 registrants - lots of Hyku repository managers and IU developers

   2. West Coast (10/9-10/10)

      1. looking at accessibility?

   3. Northeast (10/14-10/15)

   4. Europe (10/22)

   5. virtual zoom meeting wrap-up in December?
      
      

8. Other Updates: 

   1. Nominations opening soon for the fall Samvera Board elections

   2. Sign up to present or facilitate a topic (5 - 30 minutes) at a future Partner call

      1. Potential idea related to the challenge of campus v library IT

   3. Documentation Interest Group proposed charter and September 17th kick-off

   4. Nominations open for the Julie Allinson Award 2024 open through Monday!

   5. Hyrax and Hyku development updates

      1. Green on QA for Hyrax Fedora 6 as of this morning.
         
         

Anything for the Samvera Board? (Standing item) 

Date of next call: October 11th

Notetaker: Kate Lynch