2020-05-06 DSpace Marketing Working Group Agenda/Notes

Review of April communications

• Beta 2 announcement and planning sprint
• Thank you announcement about fundraising goal
• Member communications: conversation with Bronze and Copper members, messaging about renewals
• Repositories in a Time of Crisis webinar series

• 2 meetings: one for east coast of Europe and one for Australia–Australian meeting was cancelled.
• 20 or 30 people attended the European meeting.
• First one of these meetings; not a lot of Q & A; call to action ending
• Structure was good–governance and members came together; online event is more inclusive
• event was purposefully not recorded; good decision to allow people to feel at ease asking questions
• gave broad look at DSpace activities; presentations were useful
• Notes from the meeting https://docs.google.com/document/d/1hmjaA_LCAcRkggZntU429coo27VZJH5aHkQFoKodHXg/edit
• Sli.do Curate questions for Q & A? https://www.sli.do/
• Follow-up: Survey focused on why people did not attend?
• Need to do something for members in Australia and West Coast of US

• Next Beta likely to be June, pending outcome of the planning sprint

Repos in Time of Crisis

• Advance planning for DSpace 7 final release
• 21 national user groups are starting to be active in sharing ideas with each other and act as a resource for DSpace. 
• Meeting yesterday of Spanish-speaking organizers was very active and engaged. 
• Since July 2019, over 20 webinars in 5 languages and 16 countries reaching over 3,000 people
• Best process to create a global announcement/presentation of DSPace 7 coordinated with all the national user groups, in different languages, more or less at the same time. Prepare slides and translations, have the same kind of presentations, which can have translated scripts, at the same time. Zoom has an option to designate a translator in a meeting, which could be an option for webinars at times that are convenient in multiple languages. 
• How to get UG up to speed enough to give a presentation, get prepared for the process. June s not a good time for Tim. Best way to do this might be to re-do videos with scripts. Bram's demo videos used the demo site, but took some time to select correct examples for the videos. It was one take after deciding on examples. Bram could share the raw video of just the point and click that can have subtitles added. Because Bram used Mac tools (iMovie) he could do a quick introduction to how to do the videos step by step. 
• Spanish-speaking group is identifying materials to start translating (wiki, videos, most important DSpace 7 materials). Also want a shared calendar of events happening in their countries to better schedule, identify topics. 
• https://www.deepl.com/translatorSoftware that is considers pretty good for structured documents. Very promising.
• Bram is active in the French-speaking DSpace community and Mic wants to create a user group there to support translations and events. 
• Developers are deep in work on development and it isn't clear who is going to be leading documentation. No reason this can't start. Need to have English versions of documentation in order to do translations. SP language will potentially open an ES wiki page that replicates existing documentation. Will remain on the wiki.
• Once we get to a public release, notion of simultaneous release of the same information everywhere will be difficult if we can't pre-load that, get the material we want to disseminate translated before the date of release. Is there utility in coming up with a less technical presentation than what the devs would create but that would introduce features and be focused on repo managers. Could we do that enough in advance to distribute and have translated?
• We should certainly try, and it would need to be well in advance. Might need to put in place a workflow. Translators and coordinators need 1-2 weeks? to translate and get prepared for a presentation. If we can have a process in place. Or, we do whatever we would like and they translate after. But having something released and translated at the same time would be preferred. It might mean delaying a presentation. FOr technical presentations, might need an internal to the user groups presentations and those representatives can then present to their audience. 
• Take on as a task of this group to plan a workflow. For DS 3-6 there was a feature freeze at some point, could be different for 7, but a certain amount of time for testing could still be a good idea. Can use this time to prep and create materials and translate them. Need to ask the working group if this will happen. Also ties into a testathon. Using this community to reach everyone in a way other repositories cannot. Using the community to push DSpace 7 forward. 
• Next step: workflow and timing for how much time we need for each step and run it past the leadership group. Ask them: do we want to have a testathon? if so we will have time, if not, good to know this now. We are assuming this will happen, must confirm with working group.