<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-7">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">For those of us relatively new to things, has there been any structured work dealing with the management of the website before? What has worked and not worked,
or do we not have any information on that?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I think the suggestion of having a page listing proposed development projects and all the associated info would be fabulous. Added to that, I’d love to have
on the same page, examples of proposals which were sent out to developers. <o:p>
</o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’m starting to think that I (personally) could help contribute somewhere in the Community Editor section.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Kate Butler<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Technology Librarian<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Rodgers Memorial Library (Hudson, NH)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><a href="http://www.rodgerslibrary.org/">http://www.rodgerslibrary.org/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a href="mailto:open-ils-general-bounces@list.georgialibraries.org">open-ils-general-bounces@list.georgialibraries.org</a> [<a href="mailto:open-ils-general-bounces@list.georgialibraries.org">mailto:open-ils-general-bounces@list.georgialibraries.org</a>]
<b>On Behalf Of </b>Rogan Hamby<br>
<b>Sent:</b> Sunday, November 03, 2013 9:05 AM<br>
<b>To:</b> Evergreen Discussion Group<br>
<b>Subject:</b> [OPEN-ILS-GENERAL] editor roles version 2.something<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">This is part of an ongoing discussion where there seems to be some consensus that we should have some defined roles on the web team. The original proposal was modeled after the traditional hierarchy of newspapers just to see where that
analogy took us. Interestingly, in that very first discussion we decided that the WIKI was too much to deal with but by the follow up meeting we had a volunteer for Wiki Wrangler and that is going very well.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">As of the last meeting there was consensus that the newspaper model had too many roles for the size of our labor pool. With that in mind this is flattened out. The two challenges in inherent in this is that some role need to be made broad
and able to to be duplicated so that if the labor pool grows we can accommodate that (presumably there may be more to do too). At the same time some roles if duplicated may have people stepping on each other's toes a lot. So, some of those considerations
are embedded in this. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Editor in Chief - This would be combined with the traditional role of the managing editor. So, this person would be a liaison with the Oversight Board and make sure the site reflects the community needs and that other roles properly coordinate
their activities and stay on track. This means that they are responsible for making sure that changes happen on schedule and that everyone is doing their jobs and assigning / soliciting for jobs to be done. Additionally, they have the task of recruiting
new blood as we need it, an inevitable task. They should also be capable of some basic technical tasks, e.g. updating plugins from within Wordpress, managing Wordpress structures, some basic CSS tweaks needed, checking the site for screen reader compatibility,
etc... They would also lead in making sure layout changes are done appropriately though it would be a team challenge to address those needs. The changes being down to the downloads page is an example of this. In a perfect world when we have more volunteers
we would have a separate layout editor who could focus on those usability issues a bit more. Additional tasks to watch are the updating of content that may not be a specific responsibility but needs to be reviewed (e.g. adding a new mailing list to the Get
Involved section) and other one off tasks. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Server Admin - This is a job being done by Ben Shum right now. Ideally this shouldn't be a large time investment. The rest of the web team should be able to handle most issues within Wordpress without involvement from him.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">News Editor - This could be a one or multiple people role. Because news tends to be a timely thing they will need to coordinate closely to make sure they don't step on each other's toes but I imagine it mostly being a single person. <o:p></o:p></p>
</div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Community Editor - This is the section that would have the advocacy function. Examples of content include FAQs, installation maps, and more. Elizabeth
has talked about the need for this in the Oversight Board meetings this last year. This could easily be multiple people. <o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Conference Contributor - I break this out separately because with the rising interest in regional conferences (I've heard from several) I think we may
have contributors who do nothing but editor a static page for their conferences and those may come and go. <o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Wiki Wrangler - I think the work being done now speaks for itself. I think a great job is being done now but I think there would be merit in more with
specialized knowledge sets. <o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">for example, when I have some time come open I may jump in and look at testing older submitted SQL against current versions to make sure its good (it
should be though there may be better ways now) and then creating an index page by versions. I think one thing the Wiki Wrangler(s) could also do is give feedback to the web group as to what skills they see needed. For example, I could easily see an old OpenSRF
page that is a mess and they need someone to review it and make recommendations. <o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Rogan Hamby, MLS, CCNP, MIA<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Managers Headquarters Library and Reference Services, <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">York County Library System<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Georgia","serif";color:#181818;background:white">“You can never get a cup of tea large enough or a book long enough to suit me.” </span><span style="font-size:10.5pt;font-family:"Georgia","serif";color:#181818"><br>
<span style="background:white">¯ </span></span><a href="http://www.goodreads.com/author/show/1069006.C_S_Lewis" target="_blank"><span style="font-size:10.5pt;font-family:"Georgia","serif";color:#666600;background:white">C.S. Lewis</span></a><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>