MemberFullList

Version 7 (Mike Gunderloy, 05/21/2009 08:05 pm)

1 1
h1. Members Full List
2 1
3 1
We're going to try to scrape this data at some point, so it's important to keep the format consistent.
4 1
5 1
Do something like this (figure we can make it look like "YAML":http://www.yaml.org and just parse it):
6 1
<pre>
7 1
<pre>
8 1
unique_id:
9 1
  key: value
10 1
</pre>
11 1
</pre>
12 1
13 1
Where key is one of the following fields (feel free to add to this list, but we need to keep consistent)
14 1
<pre>
15 1
 name, email, blog, www, irc, aim, msn, gtalk, yahoo, twitter, friendfeed, company, projects
16 1
</pre>
17 1
18 1
Here's a base template to get you started:
19 1
<pre>
20 1
your_identifier:
21 1
  name: 
22 1
  email: 
23 1
  blog: 
24 1
  twitter: 
25 1
  company: 
26 1
  projects:
27 1
   - project 1
28 1
   - project 2
29 1
</pre>
30 1
31 7 Mike Gunderloy
Let's keep entries alphabetized by last name to make it easier to find people manually.
32 5 Jeff Schoolcraft
33 3 Jeff Schoolcraft
[[Full List|FullList]]
34 4 Jeff Schoolcraft
35 5 Jeff Schoolcraft
36 5 Jeff Schoolcraft
37 4 Jeff Schoolcraft
Then, all we have to do to scrape it is:
38 5 Jeff Schoolcraft
39 4 Jeff Schoolcraft
40 6 Jeff Schoolcraft
<pre><code class="ruby">
41 4 Jeff Schoolcraft
require 'rubygems'
42 4 Jeff Schoolcraft
require 'open-uri'
43 4 Jeff Schoolcraft
require 'pp'
44 4 Jeff Schoolcraft
45 4 Jeff Schoolcraft
pp YAML::load(open('http://wiki.railsbridge.org/projects/railsbridge/wiki/Full_List?format=txt'))
46 4 Jeff Schoolcraft
</code></pre>