...

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 truly open, decentralized, non-siloed, and non-paywalled.

Objectives

Campaign strategy. Develop a process to gather
1. Develop strategies for gathering requirements, priorities, and models for shared community and infrastructure management
(eg, consider using the
2. . Examples include ARK community survey draft created by the BnF
).Communications and Marketing.
3. , 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.
4. Clearly articulate what ARKs are, how they can be used, and why they are essential (the “value proposition”) and
implement a plan for promoting
5. promote their adoption and use.
 Examples include creating an “ARKs brochure” website using the arks.org domain name (similar to doi.org), 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

• Kickoff: clarify objectives and assign roles for the three objectives

• Month 1: share draft campaign and awareness strategies with the AG for early feedback and share it with sustainability WG for review

• Month 2: draft requirements (and share with the Technical WG) and a vision for publicizing ARK counts; after feedback, begin implementing the campaign and awareness strategies

• Months 3-5: several rounds of review, feedback, and revision, including public review via the arks-forum list; expect also interaction with the Technical WG when they share designs and prototypes

• Month 6: work with the Technical WG to test the counting ARKs prototype; propose plan for ARKs brochure site; analysis from the results of the survey and share early basic results with the Technical WG for the needs for the standardization process

• Months 7-12: reach out to recruit more organizations with ARKs to be counted

• Month 11: production-ready brochure site, including publicity about the survey; production-ready ARK counting is in place

• Month 12: updated WG objectives and deliverables for the coming year

Resources

...

arks.org domain name

...

2. Maintain and update the ARK Alliance website at arks.org and documentation at the n2t.net ARK resolver.
3. Support the calendar of events and list of ARKA-related email groups.
4. Develop ways to characterize ARK usage, such as surveys or an API permitting ARK organizations to self-report via a harvestable API endpoint. 
5. Develop training materials and videos.
6. 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  getting started with ARKs
• plan for community to transition from v18 to the v37 specification
• canned presentations, slide shows, webinars
• translations of existing documents (e.g.,  https://francearchives.gouv.fr/fr/article/339695117)
• tool resource guides to promote ARK software (eg, OJS plugin)
• ARKA representation on NDSA and IIIF working groups
• move wiki and wordpress site to github pages

Resources

...

• Notes from ARK "Experts" meetings in 2018, with discussions of surveys, ARK spec changes, counting ARKs, sustainability, etc
  • Latest draft survey
• Technical WG
• General WG features
 common across ARKA
• common across ARKA working groups

Working Group Members

• Bertrand Caron (AG Liaison), BnF 

• Peter Sachs Collopy Caltech

• Kurt Ewoldsen CDL

• Maria Gould CDL

• John B Howard (AG Liaison), University College Dublin
• 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 InstituteJohn Kunze CDL
• Julien Antoine Raemy Data and Service Center for the Humanities (DaSCH)

• Tracy Seneca University of Illinois at Chicago

• Carlos Authier National Scientific and Technical Research Council, Argentina
• Lesley Frew Old Dominion University
• Omo Oaiya WACREN
• Riccardo Ferrante (AG Liaison) Smithsonian Institution Libraries and Archives
• Sergio Santamarina, University of José C Paz, ArgentinaRoxana Maurer National Library of Luxembourg

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.

...

...