Date
Attendees
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
announcements LYRASIS / DuraSpace merger Laurie Arp joining AG calls | Merger https://twitter.com/duraspace/status/1148594779279810564 DuraStaff are now LYRASIS staff - we are functionally and operationally working as one team. We had the first DuraSpace division team meeting in Atlanta this week. We had training on ITAV and we are going to begin using a common vocabulary. Laurie can begin attending the Advisory meetings going forward to leverage her ITAV expertise and also prep for Erin's parental leave this fall. | ||
WG progress updates
| FAQ is published. It's mature enough that it had public airing via the ARKS mailing list. We have a Gdoc version too and hopefully, that will avoid needing a login to provide edits. David - Confluence has a commenting feature - but you need an account to use it. If you're logged into the wiki you can add in-line comments. Not as low a barrier for editing as GDoc. Wiki is configured to require a login because it gets spammed if we change it to allowing people to create their own account. JohnK - we have a license to a product that could help us manage this. It's called UserSnap and it uses JavaScript to make access more secure and allow editing. ACTION - David will check if there's integration with that tool. Sustainability (see the section below) Technical - we have approval for all spec changes suggested in the ARKS summit. Will submit the spec next. One late-breaking change is holding this up. | ||
initial survey results (22 respondents out of 32): | Everyone opens the Report PDF - Kurt walking us through it. We had one respondent said they had 200 ppl using ARKS in their organization. But that person didn't share contact info! So we can't know if this is real or if they misunderstood the question. This brings into question our decision to not make contact information required for participants in the survey. I'm finding the inability to follow up not very useful. Especially for where we're asking for financial contribution - we want to follow up with them and get on their budgets for next year. David - if they're not useful then let's strongly encourage providing contact info or make it mandatory. John - In this case, contact info is really important. Kurt - we sent out 32 invitations - 22 responses and 14 included their contact info. So half included their contact information on a small sample size. We will send it out to 540 NAAN registered organizations. If we got 250 responses that would be amazing and it would be representative. Erin - I would expect less than 100 responses. Brian - yeah I think we should ask for the info and expect fewer responses. Kurt - half are running their own infrastructure. Some people we're sure on Q7. We modified the membership question so we can differentiate the responses better for next round. Q9 - ranking (the priority heat map on the analysis document is easiest to interpret). "Effort to promote ARK understanding and usage" is a high priority and everything else is a distant second. But much of the list was acknowledged as important. Surprises? Kurt - I expected more self-serving responses, e.g. let's create someone I or my org can use. but we saw much more of a 'public good' response here. Our community is full of a bunch of do-gooders John - it was surprising to see a focus on outreach and promotion. I hope it means or leads to engagement. There were people who shared the survey link with their friends. That might have skewed things. 3 people from Argentina filled it out and they're not using but will put a push to get them. Kurt - the number one vote-getter was the first option on the list. We don't need to go there. Did they chose that because it was Erin - Survey monkey can allow you to randomize the order of the list. John - we put the options in this order because we thought it would make it easier to understand. Kurt - we'll need to think about this and decide on an approach. Go back to the report and scroll to the end - it's a catch-all question for additional comments. Some contradiction there. John - some of the ppl who didn't respond was interesting. Some ppl who are sitting on working groups didn't fill it out. They were part of the review of the survey. We could have improved our communications. Kurt - contribute effort or funding - the analysis document shows this better. Seeing that people are more likely to contribute effort but there was support for the 2 open source development pieces. David - the responses around effort - those might be from people who don't have budget control. Kurt - 75% of respondents are managers so we think they have funding control. Erin - should we include what contributing effort looks like from a time commitment? I hope they would actually show up. Kurt - we can think about including time commitment in the next phase or in another future survey. Already some lessons learned from this process. We made some revisions to the survey. I am wondering how this small sample will compare to the larger group that has actually registered with ARKs (because 50% of the current respondents aren't using ARKs). John - still feels like there's a big vaccum in our sustainability planning. If the survey shows us that promotion is what's important then at least we'll need what we'll be asking for money for. Kurt - it could fund website, animations, travel to conferences if the results hold true. And hopefully the promotion piece could lead to more interest in running community infrastructure. John - another question that's front and center is to understand what our organizational home will be. The merger impacts that. It ties into Roger Schofield's concerns. There weren't many people who indicated they are already members in LYR or DuraSpace. Erin - some respondents may think they are Fedora members, not DuraSpace members. Kurt - I'm not too worried about that. We might be creating something new. Next steps - meeting wth outreach group and in next 3 wks sending out this survey to every org registered for a NAAN. We will keep it open a few weeks and we will see what we get. No red flags from Mark and Brian. |
.