2023-10-26 Outreach WG Agenda and Notes

Welcome Jack OMalley. Jack is does programming and metadata schema development at the Frick Collection. 
jm: I did a lightning talk yesterday for ARLIS mini-conference in NYC (https://www.arlisny.org/event-5442603); ARKs seemed like a very new concept to this very general audience of art historians, many of whom were probably 5-10 years out of MLIS programs
rf: we are re-engaging with DPLA to explore their goals wrt wikimedia and wikidata
jm: wikidata is one of my core areas, and I'd would be willing to help advise
rf: SI has a wikipedian-in-residence, Andrew Lih (I can ask for an intro), who has done stuff for  the NY Met
jm: I have an ARK use case that I could describe

There is a conference in Prague, JK will be doing a remote ARK tutorial. An in-person tutorial in St. Louis is coming up. Data Documentation Initiative (DDI) is coming up in Slovenia. Web Archiving Conference is coming up in Paris in April.

rf: I wonder if Jack's use case for ARKs and Wikidata might be an interesting blog topic? Jack agrees that it might. Have we ever thought of trying to get a slot at SXSW? It's in March, 2024. Ricc will look into this one.

jm: leaving St Louis on morning of 15th, our digi pres people will be htere
rf: is a good blog topic could be ARKs and wikidata; for conferences, what about SXSW (https://www.sxsw.com/) for cultural applications? next meeting is in March

The Frick has a working server/minter for ARKs that is built on arklet and was completed over the summer. With this demo, the Frick is looking for feedback, potentially leading to a blog post the project. Codebase: https://github.com/squidgetx/arklet-frick/tree/master

The Frick has a working server/minter for ARKs that is build on arklet and was completed over the summer. With this demo, the Frick is looking for feedback, potentially leading to a blog post abbout the project. Codebase: https://github.com/squidgetx/arklet-frick/tree/master (Jack O'Malley)

Jack shares a screen to github repo. The previous metadata librarian identified ARKs as a solution, during a db migration to a new LMS- that accidentally severed the relationship between the catalog and the digital collections. Jack put out an RFP for a developer to build on arklet (from IA) and to add features for their use cases. They have a small IT department, just 2 people, none of them are backend or web server experts- so they couldn't support hosting a resolver. They went with digital ocean and their droplet, along with a digital ocean db. Digital ocean is very cost-effective for them. They get $2K in credit for a nonprofit. Using a docker container for now and thinking about a consortial arrangement with MOMA and Brooklyn Museum or Metropolitan Digital Library folks (who have a robust team).

The shoulders concept really appealed to groups at Frick for autonomous operation (shoulders give control, each with defined content and metadata conventions). Supports bulk minting- staff can use spreadsheets, CSVs of up to 100 ARKs at a time. Supports suffix passthrough, separable minter and resolver, shoulder rules, extensive metadata. schema is based on dcterms- url, title, type, commitment, identifier, format, relation, source. When he mints a shoulder, he writes a constant standard for people to fill out. ?info and ?json endpoints. Jupyter notebook use case will be to enrich wikidata.org Frick presence; the Frick has a really strong digital art history dept, with LinkedData and AI. Aiming for 1-2 million ARKs.