Date
Attendees
Curtis Mirci, Dave Vieglais, Karen Hanson, Greg Janee, Roxana Maurer, Lautaro Mata, Bertrand Caron, John Kunze
Goals
transition off Wordpress and old N2T resolver
Discussion items
Item | Who | Notes | |||
---|---|---|---|---|---|
Announcements | got new 45 minute tutorial recording posted on youtube channel, from Czech memory institutions meeting | ||||
Any news items we should blog about? Any calls for papers, submission deadlines, upcoming meetings we should note? Please add to Calendar of events. | ARK tutorial accepted at No Time To Wait conference, 60 minutes, online or onsite, Nov 8 | ||||
ARK spec transition update reframe as resolver and best practices transition? eg, what to do with foreign NAANs? | cm: best practices reframing seem reasonable dv: maybe talk about minor vs major version changes; practices could include what an API should look like | ||||
update on arks.org transition off of Wordpress | Mark | Mark: (from email of Oct 10) Currently the arks.org website is backed by an instance of Wordpress that is hosted on a Dreamhost server. There are a few challenges with this setup. First it requires funding to pay for the hosting and administration to keep the Wordpress instance updated. While both of these are nominal amounts of funding and time, currently they are managed by just one person. Another challenge is the process of updating the website, the process is not always clear and there are some single or few points of failure in how things are managed. To put pieces in motion to help with these challenges, the UNT Libraries took on the work over the summer to create an instance of the arks.org website using the static site builder Jekyll. We made use of the GitHub Pages infrastructure to develop the site and the repository is available here - https://github.com/arks-org/arks.github.io with the online version (built automatically from the repository) available here https://arks-org.github.io/arks.github.io/ as a beta site. While this is still early in the stages of switching things over, the groundwork has been put down so that this transition could happen. There are benefits of using the GitHub repository for managing the website and content. The Outreach group is beginning to look at the publishing process and how that can be handled with standard Github mechanisms like Issues, Wiki pages, Merges and Approval processes. As we look at transitioning the arks.org website from DreamHost to the CDL where it will function as both the website and a resolver, the Jekyll version of the website should allow for easy deployments based on the final architecture of the service. I am happy to answer additional questions about the work that we've done on this if anyone has them. jk: Just an observation that the Wordpress site is open to anyone in the ARKA to edit, and a dozen people have established credentials. That few of them contribute to arks.org may still be an issue with the new site, but managing changes via github may be more palatable to potential contributors than Wordpress. | |||
n2t resolver code refactoring update | Dave | dv: big changes coming, but no user visible changes | |||
Missing properties for ARKs in Wikidata (Wkd): Upload the arks.org logo? CC license? | update on arks.org transition off of Wordpress | Mark | n2t resolver code refactoring update | Bertrand | bc: i've taken it on myself to make tweaks to Wkd call for others to contribute to review and refresh of Wkd pages ran out of time – to be taken up next time Dave |