Versions Compared

Version Old Version 6 New Version Current
Changes made by

lm15@cornell.edu

Sharon Markus

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Item

Who

Notes

AttendanceSharon

Today's Attendance Taker: Linda Miller

Today's notetaker:  Scott Perry

Last week's notetaker: Angela Zoss

Updates from Various Reporting Related Groups and EffortsVarious

The Reporting SIG is using small work groups to address priorities and complete our work. Each week, we will provide updates to the Reporting SIG from these various reporting-related groups and efforts:

  • Community and coordination: did not meet
  • LDP Data Privacy Working Group: no update
  • LDP SysOps Working Group: didn't meet
  • Software development:  
  • Other efforts?


Updates from WolfCon 2020All

The Reporting SIG hosted 4 sessions at the WolfCon 2020 Conference. Let's discuss what happened in each session.

  • General impressions from remote and in-person attendees
  • LDP 101 
    • KW: Good questions.  SB: Good for an FAQ to answer basic questions about LDP:  How fresh is the data, why use the LDP, Anonymization)
  • LDP 102 AZ: MM is going to come back with case studies for the various reports discussed in the meeting
  • LDP 103 SB: RM many questions about ERM and usage data
  • LDP 104 SB: RA updates to the clusters.

KW: Feedback from the other SIGS was very helpful.

SB:  Questions about bringing external data into the LDP (ILL, etc.).  Will need to collaborate more with the SIGS.

AZ: Different ways to store eresources (inventory vs knowledge base).

LM: Was there any discussion of standardizing use of FOLIO.  AZ: There were groups of people planning using different models (especially around eresources).

AZ: Attended meeting with developers discussing documentation.  Little documentation of FOLIO from the user perspective.  Most documentation is for developers.  Material types driven by RDA also part of the loan rules.  Being used differently for different types of inventory.  Item status

SB: Questions about multi-school tenants

LM: Community broadly needs to work on remote participation so everyone can hear all.

EP: Tagging has potential. 


Organizing work in the Reporting SIG

Let's discuss some ideas for dividing our work into functional area report development teams:

  • divide into RA/UM Team, RM/ERM Team, and MM Team
  • 2 team leads for each functional area stay on top of JIRA tickets/report development and communicate about progress
  • use Reporting SIG home page to describe role for each Reporting SIG member in doing this work

RM/ERM: Sharon and Scott, MM: Kevin.  Looking for RA/UM leads and also interested in others interested in any of the functional areas.  More useful to be up to date with functional areas.  Not important to be SQL expert.

SB: Ask people to update the column work team to express interest in specific areas. Reporting SIG Home

Additional Topics?All 
Topics for Future MeetingsAll

Review and update Topics for Future Reporting SIG Meetings 



Action items

  •   Community and Coordination group to discuss how to maintain GDPR compliance for REP 147 and REP 148
  •  Angela Zoss (Old) work with Nassib Nassar to go over names list, create final proposal
  •  Angela Zoss (Old)  (?) to share proposed list with POs of SIGs to make sure changed names still make sense

...