Date
Attendees
- Karen Hanson
- Dave Vieglais
- John Kunze
- Donny Winston
- Mark Phillips
- Curtis Mirci
- Tom Creighton
- Greg Janée
- Roxana Maurer
Goals
Spec updates, draft CoC, persistence statements, IIIF and ARKs
Discussion items
Item | Who | Notes |
---|---|---|
Announcements | jk: experimenting with beta ARKA stickers – anyone know of a business that accept sticker orders from users and mail directly to them? I've heard of shopify.com but didn't see the right fit. | |
Calls for papers, submission deadlines, upcoming meetings: Calendar of events 2023 Code4Lib pre-conference From Hardy Pottinger We are now accepting pre-conference proposals for the 2023 Code4Lib conference at Princeton University in Princeton, New Jersey. These pre-conferences can either be a 1-day (six hour) or a 1/2-day session (three hour) and will occur on Tuesday, March 14th. These workshops are required to be In-Person ONLY. Code4Lib 2023 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4Lib community, please visit https://code4lib.org/about/. The pre-conference sessions give folks a space to share and build knowledge, as well as to teach attendees new skills relevant to library technology. Pre-conference sessions can range from workshops to working sessions. To propose a session, please go to the 2023 submission form. If you're looking for inspiration, there are many great examples of pre-conferences from recent years: https://2022.code4lib.org/workshops/, We are taking proposals until November 30, 2022, 5 PM PST / 8 PM EST. After a period of public voting on workshops, we hope to confirm sessions with the facilitators shortly after. If you have any questions, please do not hesitate to email us - by responding to this email or by contacting Code4Lib.Workshops@gmail.com. Best, Code4Lib 2023 Pre-conference Committee | ARK panel turned down for CNI briefings, but it was suggested to resubmit as a CNI pre-recorded briefing dw: I would be interested in developing a half-day workshop; I've worked with the carpentries, and its not too much of a stretch for me dv: I have some open source ARK code that might be useful to present in a code4lib venue | |
blog posts? draft new ARKs-Service | blog post being prepared by U of Toronto Scarborough Library | |
New markdown format for ARK spec | dv: converted the ARK spec from XML to markdown | |
IIIF connection made While the spec recommends opacity in the base identifier, over time the spec has become more relaxed about semantics in extensions. In that vein, the IIIF API specifies certain characters (eg, ! and ^) in extensions in order to request variants of the base image object. OTOH, like the ARK spec, the IIIF spec uses characters that should be encoded in URIs. Interest in working with IIIF on this issue, or on PIDs in general? | mp: a nice thing about iiif is that there's another vendor that can do dw: it may be interesting to discuss tradeoffs of the use of slashes (/) to identify resource variants versus the ARK spec's discussion using periods (.) for variant delimiting vs having (/) be more geared to hierarchy. see e.g. the image API syntax: https://iiif.io/api/image/3.0/#21-image-request-uri-syntax (cf. what Mark is talking about) dv: chars that look like others can be a problem; I'm keen to participate in IIIF | |
Code of Conduct draft – please review by Nov 18 | cm: CoC looks good rm: CoC looks good kh: CoC looks good jk: will check with Advisory Group and other working groups | |
Persistence statements status subgroup: Rob Lyon (familysearch), Roxana Maurer, Kirsta Stapelfeldt (utsc) + who else | rm: very interested in persistence statements | |
docker-arknoid status | jk: not much progress, but bugs exist and will be deal with; minter state not persisting with anonymous volumes; would be nice to have minters not run out; would be nice to use arka dockerhub repo instead of personal repo | |
POSI alignment for ARKA/N2T.net? (https://openscholarlyinfrastructure.org/) | Donny | did not have time for this item jk: the ARK/N2T infrastructure planners began using this as a blueprint around 2016 (see timeline) |
Action items
- jk and dw to talk about possible C4L preconference 3-hour workshop
- jk add ARK spec conversion to markdown to community update blog post
- jk, dv, gj to meet with persistence statements subgroup
- jk fix bugs in docker-arknoid