Date

Attendees

Goals

Clear up old action items; discuss changes to revised NAAN request form

Discussion items

ItemWhoNotes
announcements

BC: As duty curator, Maria Gould facilitates next month

calls for papers, submission deadlines, upcoming meetings: Calendar of events

JK: Interview posted with origin story of ARKs: https://saaers.wordpress.com/2021/09/14/ark-alliance-an-interview-with-john-kunze/

AC: Chloe has some historical stuff in her thesis
BM: maybe we should consider doing some post for World Digital Preservation Day, Nov 4

status review of previous action items


  • John Kunze Bertrand Caron see if CCFr did indeed stop using their own NAANs
  • John Kunze draft a policy statement in response to "we would like a different NAAN"
  • John Kunze ask Outreach WG for feedback on institutional type field




BM: will share draft community update




BC: have not yet heard back from INIST


JK: type list received no comments from Outreach; assuming it will never be perfect and there's nothing depending on it yet, is it good enough for now?
BM: yes (seconded)

BC: we will try to set up a meeting with CCFr


JK: this is done, and curation checklist points to the policy document



Final feedback on proposed revised NAAN request form? Some new issues:

  • what about NP/FP/Other form ambiguity?
  • assignment policy: lower, upper, mixed case
  • resolution policy: map to: lower, upper
  • NAAN-local id in redirect rule

BC: NP/FP field gets an error when "other"; should we include a longer statement that goes into the registry? or leave it blank; it can feel
    uncomfortable for the curator to make the decision; or put "unknown"
JK: idea was that manual change by curator to "fix" is worth it given that we can use this to learn about people's notion of what their institution
AC: with the institutional types, we get more info in the registry
BC: yes
JK: should we change to the form processor so that "other" becomes a third value in the registry? eg, NP/FP/OTHER
BM: yes (seconded

JK: dormant ${nlid} (NAAN-local id) N2T feature surfaced in dev instance; allows OJS and Wordpress sites to come up without access to a webmaster that can install a rewrite rule (no matter how simple, it still needs a webmaster when there may be none available to do it)
JK: also propose adding a declaration of uppercase or lowercase (mixed case being the default) in ARKs; this declaration permits great usability enhancements for users who can't know what case conventions apply and who just assume one case or the other will work (and this declaration can make them work for specific NAANs without harming ARKs' ability to handle mixed case in general)
BC: I like the ${nlid} idea and the case norm convention declaration and mapping idea; are there other ARK components that might be candidates for mapping during resolution?
JK: yes, there are several more dormant components (isolated in the decomposed ARK but not surfaced)

Action items

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.