2022-12-07 Meeting notes

Wind:  

Jen: Tentative DS programming with possible implications for open research/scholarship; if moves forward, I would want to try for Spring 2023 starts: DS incubator. Going forward to LAT: DS affinity group,

Yuan:   

Ofira: Attended a Data Science for the Humanities and Social Sciences networking event organized by gradFUTURE. 

Neggin:  

Willow:   

Ameet:   

Meghan:  There is now a #text-analysis slack channel 

• LibGuide: https://libguides.princeton.edu/open 
  
  • Calendar: display open research events (Neggin) - done
    
    • Shows 5 listings by default (can change if desired).
    • When creating an event, select category "open research" to show up on calendar
  • Open Licensing section is hidden until complete
  • Open Access + Publishing - Princeton Resources section is hidden until complete
  • Marketing/Sharing
    • PUL Newsletter (PUL Comms)
    • Link on PRDS website (Neggin)
    • Share with GradFutures via their listserv (Ofira)
    • Link to Protocols.ai page (Meghan)
    • Link to Stokes Viz Hub page (Ofira)
• LibCal: Tag your events 
  • Please tag your open-related events with the 'open research' tag in LibCal to have your events appear on the calendar.

Discussion points

• Any follow-ups?
  • Text-analysis Slack channel came out of this meeting (Meghan)
  • First Slack channel with PUL / CDH joint membership
  • Facilitates cross dept. communication
  • Next step involves defining scope of support for text analysis.
  • Penn folks would like to continue collaborative discussion about open publishing and related topics.
  • Common interests between Yuan and Dorothy at Penn (institutional repository manager). Opportunity for future follow-up.
  • Opportunity for deeper dive / focused conversation about research data. (Neggin)
  • Interpretation and scope of "digital scholarship" at Penn and Princeton.
    • Digital Scholarship organization at Penn: https://www.library.upenn.edu/page/research-data-and-digital-scholarship-staff
    • Biggest difference between Princeton and Penn DS, they have digital humanities librarian and a dept-dedicated programmer.
    • Question about how data visualization services are offered at Penn.
  • Status of ORCid adoption at Penn? Opportunity to share practices.
• Themes
  • Challenges across institutions including: Outreach, workshop participation
  • Questions if / how engagement with users is working via liaison librarians?
    • Pipeline problem of getting people to the resources we have.
    • Led to a discussion about efficacy of email ticketing system to align user need with right resource (triaging requests).
    • Some CRM system to organize contacts with users (e.g. Salesforce), may be valuable in tracing users' engagement with resources and people. May prevent users being "bounced around."
    • Open Research Steering Committee group could be a CRM pilot?
    • Text analysis Slack channel is a step in the right direction; allows crowd-sourcing library support based on user needs.
    • Trello may be another option for ticketing system (PRDS using this tool).
      • Looking into who is using Trello across PUL.
      • "Introduction to Project Management using Trello"
    • Better understanding when gaps occur when engaging with users.
    • CDH uses Asana ticketing system (Penn does not use a ticketing system).
• User-groups
  • User groups based on tool (Python, R).
  • Is there a complementary group to PUL's "Social Sciences Librarian Affinity Group" at Penn?
• Partnering opportunities
  • ORSC / Digital Scholarship trip to Penn (Jen will follow up)
  • Include Penn folks on a Slack channel for ease of communications? Possibly the IPSC Slack?
  • Google workspace could be a possibility for facilitating communications.
  • Regular follow-up via in-person and virtual meetings.
  • Offering guest workshops on relevant tools, services.
  • Examining Penn / Princeton co-authored publications to understand how they do (or do not) engage with our respective digital scholarship resources.

10min

Planning for training modules and service mapping 

• Did last summer's co-working sessions work?
• Nice to have the time allocated to working on tasks and asking questions (also nice to hang out with colleagues!).
• Putting together calendars, workshops that saves the time of the user by reducing barriers to knowledge and participation (recordings, for example).
• Training modules and service mapping centers researchers.
• Next step: think about what pieces do we need to assemble to create service maps.  Univ of Central Florida open research service map is an exemplar (process involved creating faculty committees). - Meghan will find and circulate.
• Gather a collection of resources via GDrive.
  • Anu may have knowledge about previous efforts.