Re: [boinc_dev] [boinc_projects] keywords

2017-07-17 Thread David Anderson 

Richard:
Thanks for the comments.
In the current framework, keywords have "symbols" as well as integer IDs:
https://boinc.berkeley.edu/keywords.php?header=c
https://boinc.berkeley.edu/keywords.php?header=python
This makes it easy to specify them e.g. in job-submission programs.

I think it's better not to encode hierarchy into the symbols,
because we may want to change the hierarchy over time:
e.g. to move Cosmology from Astronomy to Physics,
or create new levels.

This doesn't preclude hierarchical search;
it would be based on the actual hierarchy as encoded, e.g., in
https://boinc.berkeley.edu/keywords.php
rather than on symbols.

-- David

On 7/17/2017 3:40 AM, Richard Haselgrove wrote:

That intervention has prompted me to look more closely at the 'Job and Project 
Keywords' design document.
It reminds me very much of a project I was involved in between 1990 and about 
2005. I was the sole coder on the team, but the philosophy and design were led 
by a project leader above me.
Our project was called 'FunderFinder', and was intended to help UK community 
groups raise funds from UK charitable trusts, some of which had trust deeds 
dating back to the seventeenth century - so the terminology was arcane, to say 
the least. Our matching had to be more precise, so we did develop a 'complete 
taxonomy of charity funding' (with the help of a cataloguing expert from the 
British Library), but in general terms our solution was very similar to yours.
I would identify two differences - the first trivial, the second perhaps 
significant.
We used a three-way classification: People, Subjects, Places - that enabled us 
to distinguish between, for example, medical research into cancer (a subject), 
and the care of patients with cancer (people).
More importantly, instead of your integer to represent a keyword, we used an 
alphanumeric code: to keep the structure clear in our own minds, we used lower 
case letters for people, upper case letters for subjects, and numerals for 
places.
I can't match your examples exactly, but we had
HMedicine and HealthHM  Diseases and disordersHMWTumours 
(including cancer)HMWC  CancerHMWL  LeukaemiaHMWM  Melanoma
and for the patients,
jdgwc  Cancer
We found that seven-character codes were sufficient to cover the worst case, 
from 2 (UK) / 5 (rest of the world) down to a single historic parish council 
via the modern local government administrative structure.
The advantage of using a hierarchical coding was that I could use sub-string 
pattern matching to include and exclude higher or lower level matches. That's 
probably overkill for the current proposal, but it seems to be a shame to 
design out the possibility of a hierarchical search at this stage.

 On Monday, 17 July 2017, 9:04, Christian Beer  
wrote:
  


  I just want to voice my disagreement with the process in which this
proposal was handled. There was barely time to comment and so far no one
did but implementation into the master branch has already started for
what seems to be a major change to Client and Server code.

As a volunteer contributor and committer to BOINC and as a BOINC PMC
member this proposal and the process in which it is done does not have
my approval.

Regards
Christian

P.S.: Although this mail is sent from my AEI email the opinion expressed
above is my personal one.

On 14.07.2017 01:04, David Anderson wrote:

I propose adding a mechanism for associating keyword attributes
(such as science area) with jobs and projects.
https://boinc.berkeley.edu/trac/wiki/DesignKeywords
Comments welcome.
-- David
___
boinc_projects mailing list
boinc_proje...@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_projects
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.



___

boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] [boinc_projects] BOINC 2017 Workshop - Paris - Sept 6-8

2017-07-17 Thread David Wallom 
Hello Jord,

When planning the BPINC 2017 workshop we originally included as possible dates 
to start from the day after the end of BOINC fast to allow people to combine 
trips. Unfortunately and as may have been noticed from the current agenda,  the 
workshop is intended to have significant discussion about the formation of the 
BOINC community and ongoing support for the software, documentation and 
management of the project overall going forward. A message went out on the list 
to allow all interested parties to suggest their dates and in the end of those 
that replied the dates chosen we amongst the best which also had 
representatives from major BOINC based projects able to attend. The events are 
now a week apart and so from that pov are separate and so if they were any 
greater time than this apart would have the same effect.

Re link with BOINC Fast with material etc then I for one had originally planned 
on submitting a paper but personal circumstance got in the way, I don't know 
about others.

Regards

David 
--
===
Professor David Wallom
Associate Professor
Oxford eResearch Centre
University of Oxford
7 Keble Road
Oxford
OX1 3QG
UK

Tel: 01865 610601
===


On 16/07/2017, 20:54, "boinc_projects on behalf of Jord van der Elst" 
 wrote:

A good question by boboviz on the BOINC forums: was some kind of
"interaction" (participant, papers, lines of code) planned with Boinc FAST,
happening from August 28th to 1 September?

I'm wondering, was BOINC FAST (http://boincfast.ru/index.php/main/) taken
into account when planning the dates for the BOINC Workshop?
Is it possible that people who wanted to visit both are now not able to, as
they happen quite close together?


-- Jord van der Elst.

On Tue, Jul 11, 2017 at 11:55 PM, Marius Millea  wrote:

> Hi everyone,
>
> On behalf of the organizing committee, I want to extend a warm invitation
> to all members of the BOINC community to join us at the 2017 edition of the
> BOINC Workshop, taking place in Paris at the Institut d'Astrophysique de
> Paris this Sept 6-8. The workshop will be an opportunity to reflect on
> lessons learned from existing projects, to discuss the status of BOINC and
> the community, and to plan ahead for the future. For many of us, it will
> also be a great chance to meet in person and get to know our fellow
> collaborators and interested parties of this open source project.
>
> There is no fee to attend, but you do need to register on the website
> below. Please do so at your earliest convenience if you would like to come.
> If you need an invitation to obtain travel documents to France, please
> don't hesitate to contact us.
>
> Also feel free to circulate the following flyer around, or point others to
> the workshop page https://cern.ch/bw17
>
> [image: Inline image 1]
>
> Hope to see many of you there!
>
> Marius (Cosmology@Home admin)
>
> ___
> boinc_dev mailing list
> boinc_dev@ssl.berkeley.edu
> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.
>
___
boinc_projects mailing list
boinc_proje...@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_projects
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] [boinc_projects] keywords

2017-07-17 Thread Richard Haselgrove 
Details of the project I described are no longer available on the web, but they 
can be explored here:

https://web.archive.org/web/19961221214555/http://www.funderfinder.org.uk/
 

On Monday, 17 July 2017, 11:44, Richard Haselgrove 
 wrote:
 

 That intervention has prompted me to look more closely at the 'Job and Project 
Keywords' design document.
It reminds me very much of a project I was involved in between 1990 and about 
2005. I was the sole coder on the team, but the philosophy and design were led 
by a project leader above me.
Our project was called 'FunderFinder', and was intended to help UK community 
groups raise funds from UK charitable trusts, some of which had trust deeds 
dating back to the seventeenth century - so the terminology was arcane, to say 
the least. Our matching had to be more precise, so we did develop a 'complete 
taxonomy of charity funding' (with the help of a cataloguing expert from the 
British Library), but in general terms our solution was very similar to yours.
I would identify two differences - the first trivial, the second perhaps 
significant.
We used a three-way classification: People, Subjects, Places - that enabled us 
to distinguish between, for example, medical research into cancer (a subject), 
and the care of patients with cancer (people).
More importantly, instead of your integer to represent a keyword, we used an 
alphanumeric code: to keep the structure clear in our own minds, we used lower 
case letters for people, upper case letters for subjects, and numerals for 
places.
I can't match your examples exactly, but we had
H        Medicine and HealthHM      Diseases and disordersHMW    Tumours 
(including cancer)HMWC  CancerHMWL  LeukaemiaHMWM  Melanoma
and for the patients,
jdgwc  Cancer
We found that seven-character codes were sufficient to cover the worst case, 
from 2 (UK) / 5 (rest of the world) down to a single historic parish council 
via the modern local government administrative structure.
The advantage of using a hierarchical coding was that I could use sub-string 
pattern matching to include and exclude higher or lower level matches. That's 
probably overkill for the current proposal, but it seems to be a shame to 
design out the possibility of a hierarchical search at this stage. 

    On Monday, 17 July 2017, 9:04, Christian Beer  
wrote:
 

 I just want to voice my disagreement with the process in which this
proposal was handled. There was barely time to comment and so far no one
did but implementation into the master branch has already started for
what seems to be a major change to Client and Server code.

As a volunteer contributor and committer to BOINC and as a BOINC PMC
member this proposal and the process in which it is done does not have
my approval.

Regards
Christian

P.S.: Although this mail is sent from my AEI email the opinion expressed
above is my personal one.

On 14.07.2017 01:04, David Anderson wrote:
> I propose adding a mechanism for associating keyword attributes
> (such as science area) with jobs and projects.
> https://boinc.berkeley.edu/trac/wiki/DesignKeywords
> Comments welcome.
> -- David
> ___
> boinc_projects mailing list
> boinc_proje...@ssl.berkeley.edu
> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_projects
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.


___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


  
___
boinc_projects mailing list
boinc_proje...@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_projects
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

   
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] [boinc_projects] keywords

2017-07-17 Thread Richard Haselgrove 
That intervention has prompted me to look more closely at the 'Job and Project 
Keywords' design document.
It reminds me very much of a project I was involved in between 1990 and about 
2005. I was the sole coder on the team, but the philosophy and design were led 
by a project leader above me.
Our project was called 'FunderFinder', and was intended to help UK community 
groups raise funds from UK charitable trusts, some of which had trust deeds 
dating back to the seventeenth century - so the terminology was arcane, to say 
the least. Our matching had to be more precise, so we did develop a 'complete 
taxonomy of charity funding' (with the help of a cataloguing expert from the 
British Library), but in general terms our solution was very similar to yours.
I would identify two differences - the first trivial, the second perhaps 
significant.
We used a three-way classification: People, Subjects, Places - that enabled us 
to distinguish between, for example, medical research into cancer (a subject), 
and the care of patients with cancer (people).
More importantly, instead of your integer to represent a keyword, we used an 
alphanumeric code: to keep the structure clear in our own minds, we used lower 
case letters for people, upper case letters for subjects, and numerals for 
places.
I can't match your examples exactly, but we had
H        Medicine and HealthHM      Diseases and disordersHMW    Tumours 
(including cancer)HMWC  CancerHMWL  LeukaemiaHMWM  Melanoma
and for the patients,
jdgwc  Cancer
We found that seven-character codes were sufficient to cover the worst case, 
from 2 (UK) / 5 (rest of the world) down to a single historic parish council 
via the modern local government administrative structure.
The advantage of using a hierarchical coding was that I could use sub-string 
pattern matching to include and exclude higher or lower level matches. That's 
probably overkill for the current proposal, but it seems to be a shame to 
design out the possibility of a hierarchical search at this stage. 

On Monday, 17 July 2017, 9:04, Christian Beer  
wrote:
 

 I just want to voice my disagreement with the process in which this
proposal was handled. There was barely time to comment and so far no one
did but implementation into the master branch has already started for
what seems to be a major change to Client and Server code.

As a volunteer contributor and committer to BOINC and as a BOINC PMC
member this proposal and the process in which it is done does not have
my approval.

Regards
Christian

P.S.: Although this mail is sent from my AEI email the opinion expressed
above is my personal one.

On 14.07.2017 01:04, David Anderson wrote:
> I propose adding a mechanism for associating keyword attributes
> (such as science area) with jobs and projects.
> https://boinc.berkeley.edu/trac/wiki/DesignKeywords
> Comments welcome.
> -- David
> ___
> boinc_projects mailing list
> boinc_proje...@ssl.berkeley.edu
> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_projects
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.


___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


   
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] [boinc_projects] keywords

2017-07-17 Thread Christian Beer 
I just want to voice my disagreement with the process in which this
proposal was handled. There was barely time to comment and so far no one
did but implementation into the master branch has already started for
what seems to be a major change to Client and Server code.

As a volunteer contributor and committer to BOINC and as a BOINC PMC
member this proposal and the process in which it is done does not have
my approval.

Regards
Christian

P.S.: Although this mail is sent from my AEI email the opinion expressed
above is my personal one.

On 14.07.2017 01:04, David Anderson wrote:
> I propose adding a mechanism for associating keyword attributes
> (such as science area) with jobs and projects.
> https://boinc.berkeley.edu/trac/wiki/DesignKeywords
> Comments welcome.
> -- David
> ___
> boinc_projects mailing list
> boinc_proje...@ssl.berkeley.edu
> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_projects
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.


___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.