[ 
https://issues.apache.org/jira/browse/BEAM-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900652#comment-15900652
 ] 

Milinda Kasun commented on BEAM-1439:
-------------------------------------

Hi, I'm Milinda Kasun, I am a Final year undergraduate from the Department of 
Computer Science and Engineering (University of Moratuwa, Sri Lanka). I have 
experience on development with Java and Python. I would like do this project 
for GSoC 2017. It would be greatly appreciated if you could help me get started.

Thank You


> Beam Example(s) exploring public document datasets
> --------------------------------------------------
>
>                 Key: BEAM-1439
>                 URL: https://issues.apache.org/jira/browse/BEAM-1439
>             Project: Beam
>          Issue Type: Wish
>          Components: examples-java
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>            Priority: Minor
>              Labels: gsoc2017, java, mentor, python
>
> In Beam, we have examples illustrating counting the occurrences of words and 
> performing a basic TF-IDF analysis on the works of Shakespeare (or whatever 
> you point it at). It would be even cooler to do these analyses, and more, on 
> a much larger data set that is really the subject of current investigations.
> In chatting with professors at the University of Washington, I've learned 
> that scholars of many fields would really like to explore new and highly 
> customized ways of processing the growing body of publicly-available 
> scholarly documents, such as PubMed Central. Queries like "show me documents 
> where chemical compounds X and Y were both used in the 'method' section"
> So I propose a Google Summer of Code project wherein a student writes some 
> large-scale Beam pipelines to perform analyses such as term frequency, bigram 
> frequency, etc.
> Skills required:
>  - Java or Python
>  - (nice to have) Working through the Beam getting started materials



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to