...
- “Sam” is the name of the prospective (or former) participant.
- You are a person with admin privileges on the online sites and services in question, as detailed in the Credentials section near the end of this document. If you don’t have admin privileges yet – often particular, separate privileges per site – someone else who has them on that site must be available to assign them to you.
- In most cases, you are a chair (or vice-chair) with “admin” (perhaps “owner”) status account on the site or service, meaning that, in addition to creating and modifying content, you have the ability to create and delete accounts for other members, and to promote some of them to “admin” status. Chairs can propagate these privileges to successor chairs. Applies to arks.org, google groups, google forms, the github organization account.
- Some service accounts cannot propagate privileges, so chairs have to share passwords and new chairs have to change them when previous chairs step down. Applies to mailchimp, twitter, and youtube.
Online sites and services that are for ARKA group support direct use by the ARKA Working Groups (WGs) and the Advisory Group (AG) include
- wiki.lyrasis.org – group support: agendas, meeting notes, working documents, …
- emailed meeting invites – using your own system; eg, Outlook, Google, Apple, …
- google group – email list for each group, public archives except for NAAN group
Online In the purview of the Outreach WG are oOnline sites and services for ARKA user support outreach and promotion. These include
- arks.org – official ARKA website, currently run as a Wordpress site
- email forum – arks-forum@googlegroups.com for general discussion in English
- email forum – arks-forum-fr@framalistes.org for general discussion in French
- google forms – NAAN requests, Expressions of Interest, …
- mailchimp.com – newsletter generated from arks.org/blog
- twitter.com – official @arks_org handle
- youtube.com – ARKA channel
- github.org/arks-org – ARKA organization; coming soon: NAAN registry, resolver code, github pages
...
Goal: enable Sam to create and edit pages on the Confluence wiki at lyrasis.org in support of the working group.
Privileges: use your own wiki account; each working group chair and vice-chair confers admin privileges to the next generation.
Process:
- If Sam doesn’t yet have credentials on this wiki, establish credentials (an account) by emailing wikihelp@lyrasis.org and CCing Sam.
- Sam should receive an email with instructions to create a wiki account.
- Once Sam completes them, you login to the wiki with your own credentials.
- In the space “ARKs in the Open”, go to the sidebar and select Space Tools > Permissions.
- Add the Sam’s account to the list of users and then check off the appropriate permissions similar to the others.
- Sam should now have privileges for all working groups in the space. For more advanced issues, email itsupport@lyrasis.zendesk.com.
- Edit the group homepage, https://wiki.lyrasis.org/display/ARKs/Advisory+Group, and add Sam and Sam’s affiliation to the list of group members.
...
International numbers available: [link: https://zoom.us/u/C9RwM]
Meeting ID: 987 654 748 973321
Google email group
Goal: add Sam to the google email group used to contact the entire group. Be aware that all group archives are publicly readable except for the NAAN group.
Privileges: use your own google account; each working group chair and vice-chair confers admin privileges to the next generation.
Process:
- Visit (for example) https://groups.google.com/g/arka-advisory-group
- From the sidebar, select People > Members, then “Add members”.
- Enter Sam’s email address, toggle “Directly add members” with no invitation message (they're expecting it, and you’re busy and don’t want to have to remind them to accept it if they didn’t see the invitation), and “Send invites”.
- Make sure you have invited Sam to the calendared meeting (above).
- Make sure you have added Sam to the working group home page.
...
Goal: enable Sam to edit content on the official ARKA website (arks.org).
Privileges: use your own account; each working group chair and vice-chair confers admin privileges to the next generation. Alternatively, login with info@arks.org.
This is currently a Wordpress site hosted by Dreamhost, although we hope to convert it to a github Pages site. Generally edit access isn't needed unless Sam is creating or editing a blog post or a document, so adding Sam can usually wait until the need arises.
...
Goal: connect Sam to the main ARKs forums in English and French. Consider asking another member with admin privileges to grant you admin privileges on one or both of these lists.
Privileges: use your own google or framalistes account; each working group chair and vice-chair confers admin privileges to the next generation.
Process:
- If not already subscribed, Sam should visit https://groups.google.com/g/arks-forum to subscribe to the main ARKs forum.
- (optional) Sam may wish to visit https://framalistes.org/sympa/info/arks-forum-fr to subscribe to the French ARKs forum.
...
Goal: allow the general public to submit a NAAN request that will be processed by the NAAN Registry working group.
Privileges: use your own google account; each working group chair and vice-chair confers admin privileges to the next generation.
The request form https://n2t.net/e/naan_request is a google form owned by arksalliance@gmail.com and is jointly managed by “editors”. Similarly there is also an Expression of Interest form at https://docs.google.com/forms/d/1ylEeI3hUVHcLl-wNtDI7-F7JReBtVbgx65y9Uiy78q8.
...
Privileges: login with your own github account; working group chairs confer admin privileges to the next generation.
The official ARKA github repo is https://github.com/arks-org. This is envisioned to be the home of the NAAN registry, the ARK specification, the resolver code, and possibly the arks.org content (replacing the Wordpress site). New users are invited by an existing user.
Credentials
Logins Shared logins and passwords are stored with keybase.io under the “ARKAadmin” team. Currently this is shared among a small number of group chairs. You will need to create a Keybase account and be invited onto that team by a current member in order to get access.