DataONE:Tips and reflections on OWW

From OpenWetWare

(Difference between revisions)
Jump to: navigation, search
(My experience)
(incorporated Sarah's comments and gave it all more of a "we" feeling)
Line 1: Line 1:
-
I've been asked to write down some tips and reflections about my experience, to date, with OpenWetWare.  Here they are.
+
We've been asked to write down some tips and reflections about our experience, to date, with OpenWetWare.  Here they are.
== Tips for getting started ==
== Tips for getting started ==
Line 52: Line 52:
* notebooks, protocols, etc where a useful framework for thinking about things
* notebooks, protocols, etc where a useful framework for thinking about things
* a "well-known name" in the open notebook field, respected and understood as a hosting choice
* a "well-known name" in the open notebook field, respected and understood as a hosting choice
-
*'''[[User:Sarah Judson|Sarah Judson]] 16:23, 16 August 2010 (EDT)''': calendar pages for logging notes and making task lists  
+
* calendar pages for logging notes and making task lists  
-
*'''[[User:Sarah Judson|Sarah Judson]] 16:23, 16 August 2010 (EDT)''':collaborative ability through comments (though I feel it was under-utilized and non-standardized)
+
* collaborative ability through comments (though it was under-utilized and non-standardized)
-
*'''[[User:Sarah Judson|Sarah Judson]] 16:23, 16 August 2010 (EDT)''':archive of text communication (easy reference, kept us accountable, absent members able to view later)
+
* archive of text communication (easy reference, kept us accountable, absent members able to view later)
 +
 
===What hasn't worked well for us===
===What hasn't worked well for us===
* can't view or update offline
* can't view or update offline
Line 63: Line 64:
* hard to browse
* hard to browse
* RSS diffs hard to read
* RSS diffs hard to read
-
**'''[[User:Sarah Judson|Sarah Judson]] 16:23, 16 August 2010 (EDT)''':Though it was difficult to read the RSS, it was easier than tracking changes through OWW itself and allowed me to easily keep tabs on other people's discoveries and to tag or star relevant posts in my reader for future reference
+
** though it was easier than tracking changes through OWW itself and allowed us to easily keep tabs on other people's discoveries and to tag or star relevant posts in my reader for future reference
* knowing what to put in user vs lab space was not clear
* knowing what to put in user vs lab space was not clear
* wasn't clear how to separate notebook vs static page content
* wasn't clear how to separate notebook vs static page content
* no way to automate posts, use local tools
* no way to automate posts, use local tools
* "talk" pages made it hard to see comments and content at the same time
* "talk" pages made it hard to see comments and content at the same time
-
*'''[[User:Sarah Judson|Sarah Judson]] 16:23, 16 August 2010 (EDT)''':didn't attract as much community or mentor input as we originally hoped
+
* didn't attract as much community or mentor input as we originally hoped
-
* not a good fit for my workflow ('''[[User:Sarah Judson|Sarah Judson]] 16:23, 16 August 2010 (EDT)''':nor mine, I often forgot to post)
+
* not a good fit for workflow ('''[[User:Heather A Piwowar|Heather A Piwowar]] 15:08, 18 August 2010 (EDT)''':well, not a good for mine anyway '''[[User:Sarah Judson|Sarah Judson]] 16:23, 16 August 2010 (EDT)''':nor mine, I often forgot to post)
-
*'''[[User:Sarah Judson|Sarah Judson]] 16:23, 16 August 2010 (EDT)''':not easy (or possible?) to archive to desktop (if someone nows how and I'm just oblivious, please let me know as I have files and such to backup!)
+
* not easy (or possible?) to archive to desktop
 +
** if someone nows how and we're just oblivious, please let us know.  We have files and such to backup!)
==Sustainability==
==Sustainability==

Revision as of 14:08, 18 August 2010

We've been asked to write down some tips and reflections about our experience, to date, with OpenWetWare. Here they are.

Contents

Tips for getting started

Look around

Look around other people's pages to see how others use OWW and what is possible. Some places to start:

Request a login

http://openwetware.org/wiki/OpenWetWare:How_to_join

Read a bit

http://openwetware.org/wiki/OpenWetWare:Getting_started

Edit your user page

http://openwetware.org/wiki/OpenWetWare:Getting_started_2

Choose a "lab" name, or join one that already exists.

Could be PI last name or a project like "DataONE." You'll want to keep it short, because it will be in every URL! http://openwetware.org/wiki/Help:Starting_a_lab_wiki

Set up a lab notebook

We learned that it is easiest if you create a "Lab" notebook rather than a user one: http://openwetware.org/wiki/Lab_Notebook

Establish some standard ways to annotate each other's records

Will you comment on "talk" pages, or inline, or in comment boxes, or ??

Test and publicize your RSS feed

It will be this, where DataONE is substituted with your lab name:

Tips

What OWW says about its strengths

Our experience

What we really liked

  • it worked
  • embedding (google docs, Mendeley, gists, FriendFeed, Evernote shares, pubmed ids, etc)
  • notebooks, protocols, etc where a useful framework for thinking about things
  • a "well-known name" in the open notebook field, respected and understood as a hosting choice
  • calendar pages for logging notes and making task lists
  • collaborative ability through comments (though it was under-utilized and non-standardized)
  • archive of text communication (easy reference, kept us accountable, absent members able to view later)

What hasn't worked well for us

  • can't view or update offline
  • can't to some private, some public
  • awkward to post images (Sarah Judson 16:23, 16 August 2010 (EDT): and files)
  • can't save drafts or bundle mini updates
  • OWW tools, syntax not generalizable to other things
  • hard to browse
  • RSS diffs hard to read
    • though it was easier than tracking changes through OWW itself and allowed us to easily keep tabs on other people's discoveries and to tag or star relevant posts in my reader for future reference
  • knowing what to put in user vs lab space was not clear
  • wasn't clear how to separate notebook vs static page content
  • no way to automate posts, use local tools
  • "talk" pages made it hard to see comments and content at the same time
  • didn't attract as much community or mentor input as we originally hoped
  • not a good fit for workflow (Heather A Piwowar 15:08, 18 August 2010 (EDT):well, not a good for mine anyway Sarah Judson 16:23, 16 August 2010 (EDT):nor mine, I often forgot to post)
  • not easy (or possible?) to archive to desktop
    • if someone nows how and we're just oblivious, please let us know. We have files and such to backup!)

Sustainability

Stats

So it is still being used, but growth in number of users and notebooks is linear not exponential

  • DataONE accounted for 8% of the activity in July

Long term future

  • worrying
  • very few recent blog posts, community group posts, comments from leadership, funding plans
  • not innovating at this point
Personal tools