Date
Attendees
Harvard: Michelle Durocher, Amy Armitage, Chew Chiat Naun
Brown: Boaz Nadav-Manes, Ann Caldwell, Rebecca, Jeanette Norris
Chicago: Larisa Walsh
Colorado: Paul Moeller,
Columbia: Amber Billey, Kate Harcourt, Robert Rendall, Melanie Wacker, Brian Lucero
Cornell: Jim LeBlanc, Sarah Ross
Michigan State: Joshua Barton, Lucas Mak, Lisa Robinson
Stanford: Nancy Lorimer, Phil Schreur, Joanna Dyla
Texas A&M: Tatyana Chubaryan, Jeannette Ho
UC Davis: Xiaoli Li
UCLA: John Riemer, Paul Priebe
Wisconsin-Madison: Michael Cohen, Jamie Woods, Tom Lundstrom, Denis Brunke, Victor Gorodinsky, Betsy Robbins
PCC: Matthew Beacom (PCC Chair), SCA-Ben Abrahamse, SCS-Chew Chiat Naun, co-chair; SCT-George Prager, co-chair
PCC TG on Identity Management in NACO: Michelle Durocher, Violeta Ilik, Amber Billey, John Riemer
Agenda
1.Welcome & confirm agenda; volunteer to take notes?
2. Introductions
3. Review PCC ISNI Pilot goals, including
- participant responsibilities
- anticipated project timeline & deliverables
- 1st quarter activities (July 15-Oct 15) – status update for PoCo’s Nov. 1-3 meeting
- roles of the PCC Standing Committees and how they might work with pilot participants
ISNI Membership details:
4. Review ISNI membership responsibilities
5. Review/solicit input on the PCC's data privacy/openness matrix for ISNI membership set-up; this will establish how data elements contributed by PCC can be viewed in the ISNI public database
PCC ISNI Pilot— Working together
6. Collaboration tools for consideration:
- Common wiki space w/ documentation
- Supplemented by Google Docs for shared work?
- Email group for practitioners to help each other?
- Other?
7. Frequency and type of meetings: whole pilot group vs. subgroups?
8. Next steps for Pilot participants: getting started!
Meeting notes
1. Welcome
2. Introductions & welcome:
Matthew kicked off the meeting by thanking the pilot participants for their involvement with this important initiative.
3. Review pilot goals
Early adopter assumptions (see initial email invitation)
- Expect a lot of experimentation, trial & error, iterative process, working to make the future smoother for future participants
- Engagement with a lot of ISNI tools, for practitioners; some batch processes and usage of OCLC Leiden Office’s API’s. Different institutions will vary in technical and operational priorities.
Hope to have 90 days of experience (ending Oct 15) to report on by November PCC Policy Committee meeting.
- The policy lead from each place is expected to help report on progress.
Deliverables:
- PoCo report in mid-October.
- The pilot will pave the way to put into place all the information, documentation and guidelines that would be necessary for future PCC institutions to participate in ISNI with clarity and support. If PCC NACO were starting today, what would the needs be in terms of training, applications?
- Engagement with OCLC on the technical tools: development of enhancements/wish list. A wish list that emerges from the pilot experience will need prioritizing so that our collective experience can inform OCLC on which things would have the greatest impact.
PCC Standing Committees participation: all three have a logical role.
4. ISNI Membership details:
- Look for “Use of the Public and Confidential Data for the ISNI Database” to come to us after the meeting. Policy leads need to review sections 2-4 carefully.
- Tension between open data and locally confidential data. Some data useful for matching might be confidential (and could be stored in ISNI). SCS will also be asked to review.
“PCC ISNI Member Rights and Responsibilities” (nothing will be surprising). Look for copy of the document after our meeting today.
6. PCC ISNI Pilot—Working together
- Collaboration tools for consideration:
- Common wiki space w/ documentation
- Supplemented by Google Docs for shared work?
- Email group for practitioners to help each other? (and to communicate with each other)
https://wiki.duraspace.org/display/PCCISNI/PCC+ISNI+Pilot+Home
- Note the link to the ISNI Documentation page.
- Magenta font for the pages expected to be of high value to us.
- Expect a request for list of your people you want to have access to the wiki page and to identify who should be added to a dedicated email list for detailed practitioner questions.
- OCLC asks that we ask each other our questions, so that we learn from each other and judiciously ask for outside help when it is truly needed.
Question: Will we have a public facing info/documentation page?
Answer: Duraspace can accommodate our having a public site that has non-public content, so we will make sure the wiki is set up to support both public and restricted content.
7. Frequency and type of meetings: whole pilot group vs. subgroups?
- Hold another meeting about 2 weeks after we have gotten our logons? (For practitioners)
- Don’t feel pressured to attend every meeting, when the calls go out.
- Harvard staff who have been working in ISNI previously will be sharing their experience to be supportive of new arrivals, since Harvard has been an ISNI member for a while.
- BnF and BL, and members of the ISNI Quality Team, will also be great resources for us as well.
The 5 Subgroups will be convened soon. Please think about whether you can play a role as a subgroup lead.
- API review/testing
- Batch processing template/workflow
- Documentation & training
- Workflow & tools best practices
- ISNI maintenance best practices
8. Next steps for Pilot participants.
Read attachments that come to us after the meeting:
- Member Rights and Responsibilities
- Data Privacy document
Identify pilot participants/email addresses for access to the Pilot wiki.
Identify pilot participants/email addresses for a pilot email address list for participation questioners distributed internally to share expertise among the group members
Gathering discrete IP ranges for ISNI client access. We will need to provide IP address ranges from our institutions. The ISNI client can be downloaded. While we will begin working in the ISNI web interface, the ISNI client (called WinIBW) will allow us to perform more complex maintenance and ISNI assignment activities.
