...
Attendees
Goals
- Second meeting: recruiting, procedure hardening, proposal to register shoulders, Slack integration
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
announcements |
- from primary contact vs service provider contact
- to primary contact vs, if primary contact is a service provider, institutional contact
Proposed: expand the role of NAAN registry to record not only per-institutional NAANs, but also shoulders under one of the four non-institutional NAANs
The question of registering shoulders (outside of EZID) has come up before, and with INCIPIT is a bit more pressing. As with NAANs, the purpose is to prevent name assignment collisions between institutions. One alternative is to create a new special-purpose NAAN (eg, 99998, 99997, ...) for each institution that wants to do test ARKs, but that would dilute the recognizability of test ARKs (recipients would have to memorize an ever growing list of NAANs) and it would clutter the NAAN namespace. An advantage of beginning to register shoulders just for these 4 special-case NAANs is that it would formalize existing practice and make it more transparent. It would also provide a framework for addressing a couple anomalies in EZID (for 99152 and 99166). There are other existing practices for assigning shoulders under non-shared NAANs (eg, BnF and EZID practices) that would not be affected by this change. | BC: BnF has some plans and interest in this topid General agreement that a clearer understanding of the different options would be good, including the technical, admin, and user impact of each option ACTION: jak will write up options | ||
Slack integration? |