<html>
<body>
<br><br>
Eric / Ed -<br>
Eric, is it fair to assume you have read both of Ed's posts on the
subject? It sounds, from the way I read the second, which was a
clarification to Wim, like he is suggesting a very specific 'trial'
topic, to see just how the process would work. I wonder, in
fact, what the harvesting, and digestion process would entail, but I'm
foolish enough to be interested. You wouldn't want to leave it up to the
individual search skills of the volunteer, right? You'd need to have some
method.<br><br>
Ed - as you go along, I would like to see you refine / clarify the focus
distinctions between the Journal, CAUT site, pianopedia, and refinements
in list functioning. I'm not sure the initiative can or should be
targeted equally. You want to harvest the list and create a
definitive document, but, in theory, you need to know whether that
definitiveness reflects all that was found on CAUT, or whether additional
information would be added, if the CAUT data was found wanting. And
again, would this ignore information available on pianotech?<br><br>
Just some idle thoughts.<br><br>
Regards <br><br>
David Skolnik<br><br>
I'm having more trouble lately deciding what to quote and what to
cut.<br><br>
<br><br>
<br>
At 02:55 PM 7/21/2008, Eric wrote:<br>
<blockquote type=cite class=cite cite="">Hi Ed,<br>
<br>
This seems like a great idea to me and I will run it by the committee to
find a volunteer to coordinate such an effort. Perhaps it could be
compiled and edited into topics which could be formatted and posted on
the CAUT website as well. In this form it could be the beginnings of a
pianopaedia forum with relevant technical info from identified authors
which could grow…<br>
<br>
Eric<br>
<br>
Eric Wolfley, RPT<br>
Director of Piano Services<br>
College-Conservatory of Music<br>
University of Cincinnati<br>
<b>From:</b> caut-bounces@ptg.org
[<a href="mailto:caut-bounces@ptg.org" eudora="autourl">
mailto:caut-bounces@ptg.org</a>] <b>On Behalf Of </b>Ed Sutton<br>
<b>Sent:</b> Sunday, July 20, 2008 2:27 PM<br>
<b>To:</b> College and University Technicians<br>
<b>Subject:</b> [CAUT] A Project that might Work<br>
<br>
Dear CAUT List Folks-<br>
<br>
Over the past year the <i>Journal</i> has used gracious contributions of
the CAUT Committee to expand our technical coverage.<br>
In particular, Fred Sturm has given us the use of his posts (edited by
him, and a then little more by us) to show some methods of efficient
institutional maintenance. Kent Swafford is currently compiling some
earlier posts about sostenuto regulation (real tech posts about real
regulation problems!), which we will soon publish. It would be wonderful
if the Journal were to receive similar contributions on technical topics
for an extended period.<br>
<br>
A general range of topics could be: Institutional piano maintenance,
Tuning, voicing, regulating the high performance piano.<br>
<br>
I am suggesting the most productive effort would be focused on the
practical daily work of the college technician. Other topics might
eventually be covered under a different sponsor.<br>
<br>
Articles should mostly be about generally accepted technical practice
which can be replicated and tested, and any unusual opinions should
clearly be identified as such.<br>
<br>
The CAUT Committee would have authority to review/plan/make topic
assignments for the project.<br>
<br>
The CAUT Committee and Journal editors will create a "template"
for the articles, which should facilitate production.<br>
<br>
The <i>Journal</i> editors will contribute editing, spelling and photo
shop skills to the project.<br>
<br>
If we can agree on this model, or some modification of it, and get
approval from the CAUT Committee, we can proceed to the next levels of
development, such as listing possible topics, discussing how to extract
the material, assigning writers, etc.<br>
<br>
I would like to hear responses to this idea.<br>
<br>
[Please don't use clever names and cute phrases. I can't understand
them.]<br>
<br>
Thank you!<br>
<br>
Ed Sutton<br>
writing now as editor of <i>PTJournal<br>
</i> <br>
<br>
No virus found in this incoming message.<br>
Checked by AVG. <br>
Version: 7.5.524 / Virus Database: 270.5.3/1563 - Release Date: 7/20/2008
12:59 PM</blockquote></body>
<br>
</html>