Hey all,<br><br>I think I agree with Jason that I don't necessarily see a reason for a separate homepage and user page.<br><br>Julius, what naming convention did you envision using for naming the homepage? i.e. what would my homepage be called?
<br><br>One motivation for having the pages all linked from the person's userpage is that it becomes quite easy to encourage good naming conventions...<br><br>[[Special:Mypage]] goes to the logged in user's page.<br>
[[Special:Mypage/Projects]] goes to a page off the logged in user's user page.<br><br>That way you're not relying on folks typing in a new name for a page by hand and thus generally end up with better page names. (You just say in the how-to ... edit this page: [[Special:Mypage]]).
<br><br>With regards to the issue of scientific content in the user namespace versus the main namespace ... I am not sure that that matters so much. <br><br>-Reshma<br><br>PS I agree with Julius that scientific content is not easily browsable or well-organized on OWW. That's why I played around with the page
<a href="http://openwetware.org/wiki/Escherichia_coli">http://openwetware.org/wiki/Escherichia_coli</a> last week. All the lists of pages are generated dynamically from the dynamic page list extension based on categories. But this is a topic for a different thread.
<br><br><div><span class="gmail_quote">On 4/23/07, <b class="gmail_sendername">Julius Lucks</b> <<a href="mailto:lucks@fas.harvard.edu">lucks@fas.harvard.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="">Hey Jason,<div><br></div><div>Well I guess it is a little subjective, but I would argue for a separate 'Homepage' and User page for the following reasons:</div><div><br></div><div>* The User page can be used for more personal info like other interests/hobbies, etc - some info on getting to know the oww member behind the science.
</div><div>* The Homepage can be used to focus on the science.</div><div>* The Homepage serves as a portal for individual project pages: the naming convention for the project pages would be [[Homepage/project_page]] - i.e
.,</div><div>the Homepage name would be the base for all the project pages. Having a separate Homepage in the main wiki namespace I think is more useful than having them all inside the User: namespace since the main name space is where we are having scientific content at the moment. (I guess we could make a namespace for all of these Homepage and project pages.) Also, having the project page fall under a user's Homepage lends some kind of 'ownership' or at least 'foundership' to the project content, even though anyone can contribute at any time. This can be put to good use in advertising to potential new users as a way for them to keep some of the attribution for their work, since I imagine many new users are afraid of losing attribution. Another way to put it is this structure is closer to normal authorship identification of work, and will be more familiar and thus less of a jump for new users to get used to. (Note that of course one could always look into the history logs to see who created a page, but these logs are a complication I don't want to have to introduce to a new potential user.)
</div><div>* If new users can follow the [[Homepage/project_page]] convention, then they automatically start to learn good page naming habits, which is non-trivial given that you can name pages almost anything. </div><div>
* This naming convention also promotes self-organization of a lot of scientific content on OWW which is something I think we need to work on. Just browsing through the site and only navigating through clicking on links (and not typing any URLs), it is non-trivial to get from the front page of oww to some scientific content - at least for me, and I imagine for a new user. Having all this info in one place (with this naming convention) allows users to go to where they are familiar with the structure to look for new content - given that they are used to the structure from their own [[Homepage/project_page]] pages. Having all the info in this structure makes it really easy for us to scrape content and create some navigation pages like: a page that lists all the user Home pages, a page that lists all the projects that are ongoing, etc.
</div><div>* This system is a little bit like the lab Homepage system, but on a user level. Labs can then just link their user Homepages to start to form the lab pages, and people are familiar with lab Homepages which will lessen the learning curve.
</div><div><br></div><div>Julius</div><div><br></div><div><span class="q"><br><div> <span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
<div>-----------------------------------------------------</div><div><a href="http://openwetware.org/wiki/User:Lucks" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://openwetware.org/wiki/User:Lucks
</a></div><div>-----------------------------------------------------</div><div><br></div><br></span> </div><br></span><div><span class="q"><div>On Apr 23, 2007, at 1:50 AM, Jason Kelly wrote:</div><br></span><blockquote type="cite">
<span class="q"><div style="margin: 0px;">Yeah, I like this idea a lot.<span> </span>Thanks for the good work, guys.</div><div style="margin: 0px;">Putting up some default info about the person, plus simple</div><div style="margin: 0px;">
instructions on how to edit that info will help to 'break the ice' on</div><div style="margin: 0px;">editing for sure.</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">I'm a little unclear on whether you'd want to have a separate UserPage
</div><div style="margin: 0px;">and 'Homepage', rather than just seeding the userpage with the things</div><div style="margin: 0px;">you described in the Homepage.</div><div style="margin: 0px; min-height: 14px;">
<br></div><div style="margin: 0px;">thanks,</div><div style="margin: 0px;">jason</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">On 4/20/07, Julius Lucks <<a href="mailto:lucks@fas.harvard.edu" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
lucks@fas.harvard.edu</a>> wrote:</div> </span><blockquote type="cite"><span class="q"><div style="margin: 0px;">Hi All,</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">Vincent and I have been thinking a lot about how to get oww members to
</div><div style="margin: 0px;">contribute more content so that we can grow the existing oww community, and</div><div style="margin: 0px;">attract new members by pointing to high quality examples of content on oww.</div><div style="margin: 0px;">
One of the things that struck us is that there doesn't seem to be an easy</div><div style="margin: 0px;">way for a complete wiki novice to get into editing.<span> </span>The existing welcome</div><div style="margin: 0px;">
email is very long and has many links for people to follow and I think it is</div><div style="margin: 0px;">confusing to a novice.<span> </span>Also I have spent some time browsing around OWW and</div><div style="margin: 0px;">
it seems hard for someone completely new to the site to find content by just</div><div style="margin: 0px;">surfing around.</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px; min-height: 14px;">
<br></div><div style="margin: 0px;">So Vincent and I want to propose a new welcome system that involves</div></span><div style="margin: 0px;">automatically creating a 'Home page' for new users when their account is
</div><span class="q"><div style="margin: 0px;">created.<span> </span>I'll give you all the reasons why we think this is a good idea,</div></span><div style="margin: 0px;">but to see for yourself, please look at our mock Home page at
</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;"><a href="http://www.openwetware.org/wiki/OpenWetWare:Steering_committee/Outreach_chairs/mock_" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.openwetware.org/wiki/OpenWetWare:Steering_committee/Outreach_chairs/mock_</a>Home_page</div><span class="q"><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">or the one I am playing around with for myself at
</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;"><a href="http://www.openwetware.org/wiki/Lucks" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.openwetware.org/wiki/Lucks
</a></div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">The idea is that every user has 3 pages made for them when their account is</div></span><div style="margin: 0px;">created: the typical User page, a Home page, and a sample project page (more
</div><span class="q"><div style="margin: 0px;">about this one below).<span> </span>The User page can be used to show more personal</div></span><div style="margin: 0px;">information, but the idea behind the Home page is to give people a hands-on
</div><span class="q"><div style="margin: 0px;">quick introduction to the wiki-way in terms of their own academic projects.</div></span><div style="margin: 0px;">The Home page is set up in such a way as to provide both an introduction,
</div><span class="q"><div style="margin: 0px;">and an example system for how people might think about posting their</div><div style="margin: 0px;">academic content.<span> </span>Being an experienced user, I often find that wiki's give
</div><div style="margin: 0px;">too much freedom in the choice of page and section names, formatting</div></span><div style="margin: 0px;">options, etc.<span> </span>The Home page would give users something to work off of
</div><span class="q"><div style="margin: 0px;">rather than having to come up with a system on their own.</div><div style="margin: 0px; min-height: 14px;"><br></div></span><div style="margin: 0px;">The Home page also has a section listing seperate project pages for
</div><div><span class="e" id="q_1121eb85265bd4dd_21"><div style="margin: 0px;">individual projects.<span> </span>The third page automatically created is a sample</div><div style="margin: 0px;">project page that gives a skeleton outline of what kind of info it would be
</div><div style="margin: 0px;">good to have in describing a project on the wiki.<span> </span>The idea is the same here</div><div style="margin: 0px;">- that people can just start to fill this out instead of having to come up
</div><div style="margin: 0px;">with some system on their own.</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">I'm not sure about the technical difficulties of creating these pages, but
</div><div style="margin: 0px;">this is something along the lines of Reshma's recent suggestion of filling</div><div style="margin: 0px;">in the User page.<span> </span>The benefits of this system we think are as follows:
</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">* hands on introduction to the wiki for a new users OWN content rather than</div><div style="margin: 0px;">a standard tutorial page that they would have to read and then apply to a
</div><div style="margin: 0px;">page they create</div><div style="margin: 0px;">* having tutorial info on the page gives the user an incentive to start</div><div style="margin: 0px;">editing and personalizing right away (to remove the tutorial info)
</div><div style="margin: 0px;">* having a scaffold of pages is much easier for someone to handle than</div><div style="margin: 0px;">having a blank slate - we can emphasize that they can customize at any time</div><div style="margin: 0px;">
* the scaffold promotes good naming conventions and structuring of content</div><div style="margin: 0px;">on the wiki - if everyone did this it could help people find information</div><div style="margin: 0px;">easier because they would be automatically familiar with how other people
</div><div style="margin: 0px;">structure their content from knowing how they do their own</div><div style="margin: 0px;">* this is more along the lines of what scientists need.<span> </span>Wikipedia works</div><div style="margin: 0px;">
well because ALL the articles are in theory collaborated on by everyone, and</div><div style="margin: 0px;">a simple User page suffices to identify someone.<span> </span>Scientists work on many</div><div style="margin: 0px;">
projects and so need a place to put specific information about these</div><div style="margin: 0px;">projects in a place where they have at least semi-ownership to acknowledge</div><div style="margin: 0px;">that they are the principle person on the project, even though others may
</div><div style="margin: 0px;">edit.<span> </span>I think having a project page system like this is more along the</div><div style="margin: 0px;">lines of what people think of now in their non-wiki science and how they</div>
<div style="margin: 0px;">might use a private wiki if they have one.<span> </span>This makes it an easier</div><div style="margin: 0px;">transition into opening up the data and might facilitate faster content</div><div style="margin: 0px;">
migration from the private wikis to the public one.</div><div style="margin: 0px;">* the system is flexible and we can think of a way for people to easily hook</div><div style="margin: 0px;">into lab websites and what not, but this allows someone not affiliated with
</div><div style="margin: 0px;">an OWW lab to get going easily</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">The mock page could use some work, but I hope you all can give some good</div>
<div style="margin: 0px;">feedback on the general concept.</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">Cheers,</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">
Julius and Vincent</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">-----------------------------------------------------</div><div style="margin: 0px;"><a href="http://openwetware.org/wiki/User:Lucks" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://openwetware.org/wiki/User:Lucks</a></div><div style="margin: 0px;">-----------------------------------------------------</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px; min-height: 14px;">
<br></div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">_______________________________________________</div><div style="margin: 0px;">
OpenWetWare Steering Committee Mailing List</div><div style="margin: 0px;"><a href="mailto:sc@openwetware.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">sc@openwetware.org</a></div><div style="margin: 0px;">
<a href="http://mailman.mit.edu/mailman/listinfo/oww-sc" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://mailman.mit.edu/mailman/listinfo/oww-sc</a></div><div style="margin: 0px; min-height: 14px;">
<br></div><div style="margin: 0px; min-height: 14px;"><br></div> </span></div></blockquote></blockquote></div><br></div></div><br>_______________________________________________<br>OpenWetWare Steering Committee Mailing List
<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sc@openwetware.org">sc@openwetware.org</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://mailman.mit.edu/mailman/listinfo/oww-sc" target="_blank">
http://mailman.mit.edu/mailman/listinfo/oww-sc</a><br><br></blockquote></div><br>