...
Attendees
Goals
- Revise first contact with AITO: NAAN Request form
- Review presentation materials for a general introduction to ARKs
- Review stale top-level wiki content pages – revise? toss?
...
| Time | Item | Who | Notes |
|---|---|---|---|
Announcements:
| |||
The NAAN Request form is one of the first contacts people have with ARKs and ARKsInTheOpen.org. With that in mind, before the meeting, please
The registry working group Github repo contains documentation on procedures for actually incorporating the data entered on this form into the registry. For EZID, Maria is generally filling out the form on behalf of the client. The Geneva approach will also be to centrally administer NAAN registration for several universities. | Some people act as service providers, eg, Maria for EZID JR will be acting in that role wrt Swiss Universities | ||
Good time for us to think about the ARK/AITO message, as next month there will be 3 presos on ARKs:
| |||
Before the meeting, please review these stale top-level wiki pages, which seem to be in scope for Outreach, and consider what changes you would make: Volunteers needed: are you willing to make some revisions? Feel free to suggest anything, including retitling a page, deleting it, changing it's theme, etc. A page that served AITO during project infancy may not serve it well now. | Roadmap: John and Kurt will revise and shorten, with links out to WG pages, and share for feedback. Resources and Value statement: This doesn't seem stale, but does raise the question of which metrics we know and how we can track them. The audience might be internal to ARKs in the Open rather than external. Parts of the document describe ARKs rather than ARKs in the Open. Tracy will review. Project Communications: John and Kurt will revise and share for feedback. Events: Maintaining the events list would be the most challenging; others could be reviewed quarterly or biannually. In the IIIF community, events sponsored by IIIF are on their website, but third parties can enter events into a Google doc, then another person can validate them, and a script then publishes them on a website. Should we have a list of past events? Not on an events page, but perhaps elsewhere. If we don't host regular events, we can drop this page. We don't know how much traffic these pages get. John Kunze will look into it when requesting credentials for Julien RAntoine Raemy. | ||
Volunteers still needed:
| Short history: Peter will write, citing longer account by John, which John and Kurt will find a venue for. (Additional idea: https://blogs.loc.gov/thesignal/) Translation: A few links to take a look at: https://marketplace.atlassian.com/apps/28648/language-macros-for-confluence?hosting=server&tab=overview, https://marketplace.atlassian.com/apps/1215126/language-manager?hosting=server&tab=overview. An alternative approach: Would it be simpler to just keep each version in a Google doc? | ||
WG introspection: given recent cancellations, change meeting frequency? | We'll change the frequency to monthly, on either the second or fourth Thursday of each month. What is the state of ARK support built into digital asset management systems? There seem to be vendors doing this, but not the open source systems yet. Developing support within open source repositories could be a grant proposal. John Kunze will meet with Julien Antoine Raemy and Tracy Seneca to talk about ARKs, repos, IIIF, and grants |
Action items
- Everyone: Provide feedback on commenting version of NAAN request form by March 5
- John: Ask Lyrasis for traffic analytics on top-level wiki pages, schedule future meetings, decide whether to publish FAQ translations on Confluence or Google Docs
- John and Kurt: Review roadmap and communications page and share with outreach working group for feedback, find venue for John’s account of ARK development
- Tracy: Review resources and values statement, assess whether it needs revisions and what information we have on the listed metrics, and raise questions for revision
- Peter: Write a brief ARK history for Wikipedia
...