2024-06-19 NAAN Registry WG Agenda and Notes

ARK tutorial at Open Repositories 2024 conference resulted in several test NAAN requests
Large number of new NAANs from Canada probably from a group of libraries JK spoke with several months ago
Resolver upgrade now scheduled for Monday 24 June
No announcement yet on the francophone list

Next tutorial will be at DLF in Michigan July 29

no progress on naan processing, pending resolver upgrade

46 Requests : 39 New NAAN, 4 updates, 3 Tests. 1 request remaining : #471 (2 NAANs for one organization?)

rm, jk: It was a huge number of NAAN requests, with many email exchanges as well. Curator hero award goes to Chloé!
jk: how do we protect the primary curator from overwork while maintaining a turnaround of 2 business days?
rm: should be add more curators or make the duty period shorter?
jk: CDL's new NAAN processing should streamline some of this; also we could explore bulk assignment, which has been proposed by Lautaro Matas for LA Referencia organizations
all: both approaches seem promising

cp: who do we forward resolver technical problems to, eg, delays in resolver seeing registry updates?
jk: and what do we do with general ARK support questions that often, inevitably, follow on NAAN requests? we want to be helpful but don't necessarily have the time, eg, requests on how to mint ids under new NAAN

jk: there's a push to register personal scientific collections https://scientific-collections.gbif.org/ ; can this inform how we respond to NAAN requests for things that look more personal (eg, "my uncle's collection") than we're usually comfortable with? some personal collections can be very important, especially for requests from under-resourced, under-represented regions; if we act on them, where would we draw a line? I'd like to think about this and perhaps propose some guidelines
all: fine

Curator changeover as of today (standing schedule always found on group home page)