Skip to content
Snippets Groups Projects
Select Git revision
  • 153a48e68e9f0c240f51d05d60de571b45d9af18
  • master default
2 results

DisseminationCommunityBuilding.tex

Blame
  • DisseminationCommunityBuilding.tex 13.46 KiB
    \begin{workpackage}[id=dissem,wphases=1-36!.5, short={Dissemination and Community Organization},
      title={Community Building, Dissemination, and Outreach},
      lead=EMS,
        FAURM=10,PSRM=3,EMSRM=8,ULRM=8,CAERM=3,FIZRM=9,CHARM=3]
      % T5.1 FAU=6, *=1
      % T5.2 UL=6, *=1
      % T5.3 EMS=6, *=1
      % T5.4 FIZ=6, FAU=2
    \begin{wpobjectives}
      The objective of this work package is to
      \begin{inparaenum}[\em i\rm)]
      \item further develop the community generating, curating, and utilizing mathematical data at the European scale,
      \item foster cross-team collaboration, spread the expertise, and engage the greater community to participate in the definition and refinement of the requirements,
      \item leverage the communities' vast investment in existing open databases by exploiting their visibility in a uniform standard and platform.
      \end{inparaenum}
      This includes:
      \begin{compactitem}
      \item ensuring awareness of the results in the user community
      \item engaging cross communities discussions to foster scientific collaboration and conjoint development,
      \item spreading the expertise through workshops and training sessions,
      \item providing training for dataset developers how to make their datasets more visible.
    %  \item managing existing and new intellectual property.
      \end{compactitem}
    \end{wpobjectives}
    
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    \begin{wpdescription}
    The activities in this work package are split into four tasks depending on the style of communication and the role of the task leader:
    \begin{compactitem}
     \item \localtaskref{outreachfau} comprises all direct, periodic, and mostly unidirectional dissemination and public communication
     activities that are organized through the coordinating site.
     \item \localtaskref{outreachul} conducts major workshops targeted at specific communities of researchers.
     These have the goal of popularizing and EOSC in general and \TheProject in particular and of training researchers in the \TheProject standard.
     \item \localtaskref{outreachems} conducts general outreach activities towards the broader community, including mathematicians as a whole, researchers from other disciplines, and industry.
     \item \localtaskref{outreachwikidata} conducts outreach activities towards the general public.
    \end{compactitem}
    
    This work package does not include the formal publication of our respective scientific findings, which all members organize in the usual way in the open scientific literature and announced at scientific meetings and conferences.
    Similarly, it goes without saying that we will publish all data, software, source code, scientific papers, and documents openly. Open access to all publications resulting from the project will be ensured.
    
    Moreover, we will also participate in the concertation activities, consultations, and related and events of related European E-Infrastructure projects, in particular those for the EOSC.
    
    The work package is nominally led by \site{EMS}, but the primary responsibility is with the respective task leaders.
    \end{wpdescription}
    
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    \begin{tasklist}
    \begin{task}[id=outreachfau,title=Central Dissemination Activities,
    lead=FAU,partners={CAE,CHA,EMS,FIZ,UL,PS},
    PM=12, wphases=0-36!.15]
    Central activities include press releases at major project milestones, maintenance of the project web-site (including visitor analysis and monitoring tools),
    project-wide scientific and technical publications, outreach activities (seminars, keynote talks,
    media interviews), promotion through social media (e.g. Twitter,
    Facebook, LinkedIn), the creation of advertisement materials such as flyers, posters, and
    electronic feeds as well as their distribution.
    We will use standard community building technology such as mailing lists, Wikis and Forums, to ensure dissemination and
    engagement of the community to support this.
    
    This task will be led by the coordinating site. All other sites will contribute, e.g., in the form of articles for the website, specific press releases, or social media posts.
    \end{task}
    
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    \begin{task}[id=outreachul,title=Community Building: Training Workshops,
    lead=UL,partners={CAE,CHA,EMS,FAU,FIZ,PS},
    PM=12,wphases={8-10!.2,10-14!.6,14-22!.2,22-26!.6,26-32!.2,32-34!.6}]
    We will organize a number of community building workshops throughout the project.
    This includes in particular
    \begin{compactitem}
     \item announcement-style workshops open to all researchers at major conferences, in particular the European Congress of Mathematicians in 2020 and the International Congress of Mathematicians in 2022,
     \item Data Carpentry~\cite{datacarpentry:on} training sessions on a Open Scientific Data,
     \item two major events, which we tentatively call ``Summer of Math Data'' and which will be the flagship meetings centered on \TheProject.
    \end{compactitem}
    
    The European Congress of Mathematicians is the biggest European meeting of mathematicians and is co-organized in 2020 by the \site{EMS} and \site{UL} sites.
    In the summer of 2022, we will organize a major workshop at the $4$-annual International Congress of Mathematicians, where we will officially release the final results of \TheProject.
     
    The Summer of Math Data events will take place in 2020 and 2021 (hosted by \site{UL}) and will bring together
     \begin{inparaenum}[\em i\rm)]
     	\item providers of mathematical datasets,
     	\item service developers, and
     	\item existing and potential users of these services
     \end{inparaenum}
     in order to popularize \TheProject and Open Data.
    
    They will be organized as multi-week retreats (organized by \site{UL}) on the Slovenian coast.
    They will feature a series of partially overlapping research visits, 
    anchored by short workshops open to all mathematicians and subsume consecutive meetings of multiple kinds:
    \begin{compactitem}
     \item invitation-only parts that bring together a core group of people for coding and research sprints,
     \item public multi-day workshops on FAIR mathematics organized by the \TheProject members,
     \item existing conferences, for which we will submit hosting bids, in particular the Conference on Intelligent Computer Mathematics (CICM; where \site{FAU} PIs are in the steering committee), the International Congress on Mathematical Software (ICMS; the \pn coordinator is in the steering committee), and the International Congress of Mathematicians (ICM; together with the IMKT)
     \item the annual internal project meeting of all \TheProject sites.
    \end{compactitem}
    
    They will also implement and evaluate key aspects of \TheProject, including the user interface and other heavily user-oriented components.
    They provide an efficient way to communicate with experts outside of the \TheProject.
    In particular, several external researchers will be invited to attend the workshops, with expenses partially covered by \TheProject, especially the dataset providers with whom we need to collaborate in Task \taskref{cases}{recorddata}).
    A typical collaboration would consist in inviting a few dataset providers, teach them how to make their datasets available in the \TheProject data standard, and gather feedback from them on the \TheProject services.
    
    This task will be led by \site{UL} and will tie in particularly with \taskref{cases}{recorddata}.
    All other sites contribute.
    \end{task}
    
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    \begin{task}[id=outreachems,title=Outreach to Researchers and Industry,
    lead=EMS,wphases=6-36!.3,
    PM=12,partners={CAE,CHA,FAU,FIZ,UL,PS}]
    In this task, we conduct general outreach activities targeted at researchers and industry practitioners.
    These will take the form of official communications, workshops at major mathematical meetings, and targeted communications to  specific communities.
    This includes transdisciplinary outreach to related fields that involve mathematical data, in particular computer science, physics, life sciences, and engineering.
    We will build on existing research communities connected with the partners, such as the more than 2,000 individual EMS members or more than 7,000 zbMATH reviewers. APIs designed for specific community needs will propel the adaptation of the services further. As a model serves, e.g., the open zbMATH API for the MathOverflow community site \cite{MO:on}, which is currently the largest online community in mathematics ($\approx 90 K$ registered users). A lean API facilitates the integration of references into the discussed questions there, and allows vice versa for the seamless interlinking of the literature with ongoing research. Similar advantages can be expected from availability of research data. Beyond mathematics, this task will be synergistically supported by the system APIs to RADAR research data hosting service provided by \site{FIZ}: researchers from other domains can host their research data on RADAR and integrate mathematical aspects into the \pn framework. 
    
    This task will be led by \site{EMS}, which has the institutional support and recognition to conduct formal outreach activities.
    All other sites will contribute.
    \end{task}
    
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    \begin{task}[id=outreachwikidata,title=Public Outreach via Wikipedia,
    lead=FIZ,partners=FAU,PM=8,wphases=24-30]
    Wikipedia is a major way that non-mathematicians learn about and interact with mathematical knowledge.
    Therefore, in order to make the public aware of scientific data collections and their benefits, we develop an integration of our datasets with Wikipedia.
    
    Concretely, this will take the form of a Wikidata interface for the \TheProject services.
    We compute an abstraction of all the data of \TheProject that can be represented as linked data.
    Using the same alignments as developed in \taskref{cases}{wikidata} (but this time in the opposite direction), we will export this linked data into Wikidata and thus Wikipedia. Simultaneously, we can take advantage of the existing Wikidata infrastructure and community to provide feedback and enhancements. A specific advantage of our approach is that the semantic tool and alignments developed within the project allow to address the language barrier which often prohibits the dissemination of mathematical information beyond the field. This will yield an impact of \TheProject much beyond the mathematical, and even the research community into the public discourse.
    
    This task will be led by \site{FIZ}, which already leads the corresponding task \taskref{cases}{wikidata}.
    \end{task}
    
    \end{tasklist}
    
    The first three tasks are continuous activities and do not have natural due dates for deliverables.
    Therefore, we will provide two reports each at Month 18 resp. 36 that summarize the activities and their impacts; in each case, the second report will be an update to the first one.
    
    \begin{wpdelivs}
      \begin{wpdeliv}[due=18,miles=startup,id=devil:outreachfau:1,dissem=PU,nature=R,lead=FAU]{Central Dissemination (intermediate report)}
      	The first report about the activities of \localtaskref{outreachfau}.
      \end{wpdeliv}
      \begin{wpdeliv}[due=36,miles=startup,id=devil:outreachfau:2,dissem=PU,nature=R,lead=FAU]{Central Dissemination final report}
      	The final report about the activities of \localtaskref{outreachfau}.
      \end{wpdeliv}
      \begin{wpdeliv}[due=18,miles=startup,id=devil:outreachul:1,dissem=PU,nature=R,lead=UL]{Community Building (intermediate report)}
      	The first report about the activities of \localtaskref{outreachul}.
      \end{wpdeliv}
      \begin{wpdeliv}[due=36,miles=startup,id=devil:outreachul:2,dissem=PU,nature=R,lead=UL]{Community Building (final report)}
      	The final report about the activities of \localtaskref{outreachul}.
      \end{wpdeliv}
      \begin{wpdeliv}[due=18,miles=startup,id=devil:outreachems:1,dissem=PU,nature=R,lead=EMS]{General Outreach (intermediate report)}
      	The first report about the activities of \localtaskref{outreachems}.
      \end{wpdeliv}
      \begin{wpdeliv}[due=36,miles=startup,id=devil:outreachems:2,dissem=PU,nature=R,lead=EMS]{General Outreach: final report}
      	The final report about the activities of \localtaskref{outreachems}.
      \end{wpdeliv}
      \begin{wpdeliv}[due=24,miles=startup,id=devil:outreachwikidata,dissem=PU,nature=R,lead=FIZ]{Public Outreach via Wikipedia}
      	A report about the Wikipedia integration developed in \localtaskref{outreachwikidata}.
      \end{wpdeliv}
    \end{wpdelivs}
    \end{workpackage}
    
    %%% Local Variables:
    %%% mode: latex
    %%% mode: visual-line
    %%% fill-column: 5000
    %%% TeX-master: "../proposal"
    %%% End:
    
    %  LocalWords:  workpackage dissem wphases wpobjectives wpdescription tasklist WPref nmag dissem,wphases inparaenum utilizing compactitem compactenum organized project-intro,lead 20,partners 6,miles startup,id press-release-1,dissem PU,nature R,lead proto1,id ils-tool,dissem 36,id eval,nature PS,issue oldpart ednote 12,partners 6,miles 36,id outreachfau,title outreachul,title outreachemstitle Teachers,lead 12,partners 6,miles 36,id wrapup,nature UL,partners 10,wphases outreachems,title 12,partners wikidata,title 6,wphases synchronizes 6,miles 30,id wikidata,dissem 36,id outreachfau outreachul popularizing outreachems outreachwikidata 12,wphases datacarpentry:on 12,partners outreachwikidata,title 8,wphases summarize devil:outreachwikidata,dissem 12,wphases 12,partners 8,wphases
    %  LocalWords:  delivref linkedin organisation finalpressrelease organise wpdelivs github
    %  LocalWords:  wpdeliv dissemination-of-oommf-nb-virtual-environment OOMMFNB taskref
    %  LocalWords:  oommf-python-interface oommf-tutorial-and-documentation mumag magpar
    %  LocalWords:  mumax micromagnum micromagnetic oommf-py-ipython-attributes summarising
    %  LocalWords:  dissemination-of-oommf-nb-workshops localtaskref MMM-Intermag Fangohr
    %  LocalWords:  maximise sagecell structdocs Algèbre Calcul formel eparatoires Annexe
    %  LocalWords:  Jeroen