...
The Outreach Working Group (WG) oversees development of the ARK Alliance (ARKA) community, as well as the promotion of awareness, understanding, and adoption of ARKs, the only major persistent identifier scheme that is open, decentralized, non-siloed, and non-paywalled.
Objectives
- Campaign strategy. Develop a process to gather
- Develop strategies for gathering requirements, priorities, and models for shared community and infrastructure management (eg, consider using the
- . Examples include ARK community survey draft created by the BnF ).Communications and Marketing.
- , organizing events such as the 2018 ARK summit, spreading the word in international conferences, supporting the world map of ARK assigning organizations updated via geo-locations in the NAAN registry, etc.
- Clearly articulate what ARKs are, how they can be used, and why they are essential (the “value proposition”) and implement a plan for promoting
- promote their adoption and use. Examples include creating an “ARKs brochure” website using the arks.org domain name, keeping a world map of ARK assigning organizations updated automatically via geo-locations in the NAAN registry, organizing events such as the 2018 ARK summit, spreading the word in international conferences, etc. Counting ARKs.People want to know how many ARKs there are in the world (as ARKs can be assigned without permission from a central assigning authority), and some organizations may opt to let us harvest stats from them about how many ARKs they have assigned. Work with the Technical WG to (a) draft requirements for simple summary counts that ARK assigning organizations can voluntarily post and maintain, (b) specify how those counts, once harvested, should be publicized, and (c) recruit organizations to opt in.
Deliverables
- Maintain and update the ARK Alliance website at arks.org and documentation at the n2t.net ARK resolver.
- Support the calendar of events and list of ARKA-related email groups.
- Develop ways to characterize ARK usage, such as surveys or an API permitting ARK organizations to self-report via a harvestable API endpoint.
- Develop training materials and videos.
- Oversee the information used to support ARKA working groups (currently Confluence wiki).
Deliverables
- public website maintenance and published blog posts
- newsletter and wikipedia page (ongoing)
- social media (such as Mastodon, Twitter, Discord, Zulip, Youtube)
- action plan to represent ARK-identified resources and Name Assigning Authorities in Wikidata
- maintain material (on arks.org) associated with
website and blog
newsletter and wikipedia page
- tie in with wikidata guide to
- getting started with ARKs
- plan for community to transition from v18 to the v34 specification
- v37 specification
- confluence wiki oversight to support working group activities
- creating canned presentations, slide shows, webinars
- recruiting translations of existing documents (e.g., https://francearchives.gouv.fr/fr/article/339695117)
- assembling tool resource guides to promote ARK software (eg, OJS plugin)
- representing ARKA representation on NDSA and IIIF working groups
- move wiki and wordpress site to github pages
Resources
arks.org domain name
- list of email groups for outreach
- calendar of events
n2t.net ARK resolver
- Notes from ARK "Experts" meetings in 2018, with discussions of surveys, ARK spec changes, counting ARKs, sustainability, etc
- Technical WG
- General WG features common across ARKA
- common across ARKA working groups
Working Group Members
- Bertrand Caron BnF BnF (National Library of France)
- Carlos Authier National Scientific and Technical Research Council, Argentina
- Donny Winston Polyneme LLC
- Jack OMalley Frick Collection
- John Jung co-chair, University of Chicago
- John Kunze chair, Ronin Institute
- Julien Antoine Raemy vice-chair, Data and Service Center for the Humanities (DaSCH)
- Maria Gould California Digital Library Peter Sachs Collopy Caltech
- Lesley Frew Old Dominion University
- Omo Oaiya WACREN
- Riccardo Ferrante (AG Liaison) Smithsonian Institution Libraries and Archives
- Sergio Santamarina, University of José C Paz, Argentina
Meeting Times
Teleconferences are generally held once a month, held every other month, 16:00-17:00 UTC, on the fourth Thursday. Connection details included in calendar invitations.
...
| Create from template | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...