Hi John,
John Callahan wrote:
> I had started to migrate the examples from the old wiki and elsewhere
> on the web over to the new wiki. While doing so, it made sense to me
> to include other resources, like blog posts or third-party apps that
> make use of SIMILE widgets. It also made sense to include information
> from all SIMILE projects. So, I created an Exhibit (powered by a
> Google Spreadsheet) of all the resources I found and linked them from
> the new wiki home:
>
>
> http://www.simile-widgets.org/wiki/ (up to 153 resources!)
>
That looks really great! It must have taken you a lot of time! Some of
these I've forgotten about or don't even remember running across before.
>
> A few thoughts...
>
> 1. It would be nice if this Exhibit was not on my server (geo42.com)
> but rather directly on simile-widgets.org. (and styled a bit nicer as
> well!) I've tried a few things to add the necessary javascript
> components to the wiki but I do not believe I have permission to do
> so. Is this something worthwhile to add to the main s-w.org site?
>
We can definitely do that. In the past, we've done something similar,
but for all the projects we had when we were really prolific...
http://simile.mit.edu/projects.html
>
> 2. Using a Google spreadsheet is the best way I know for community
> maintenance of this data. It's easy to turn into a JSON feed as input
> to Exhibit. My first thought was to create a new wiki page for each
> resource, tag it sufficiently, then somehow generate a JSON feed with
> all the appropriate tags as attributes. I can do this in Drupal but
> couldn't figure it out with Mediawiki. (that method is probably
> overkill anyway.) If necessary, does anyone have another idea
> besides a Google spreadsheet? (of course, a custom PHP/MySQL app
> would work if anyone wants to code it up.)
>
I think Google Spreadsheets is the easiest UI around to handle data sets
of this size.
>
> 3. The attributes in the spreadsheet are very limited: title,
> description, SIMILE project, type of resource, In The Wild or
> homegrown, does it include a map, does it include a graph, and URL.
> Of course, it'd be nice to have things like a screenshot image, the
> software version, features used, date published, person/org, etc...
> However, IMO, this information would be difficult to maintain. As
> well, I don't know how to find that information easily for many of the
> entries. Although some info *may* be better than none. Any
> thoughts here?
>
The fields you have seem to be easy to maintain. Let's just keep using
it (e.g., to help newcomers) and see what else we feel missing.
>
> (Wouldn't it be nice to have a script that went through the URLs of
> each resource, tested the URL to make sure it's alive, and parsed the
> HTML/javascript code to determine which SIMILE product it's using and
> what features are enabled? :-) )
>
We have sorta tried something like that for just exhibits, but then the
automated cron job somehow got broken. It's really hard to automate this
sort of thing for dynamic web pages.
David
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"SIMILE Widgets" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/simile-widgets?hl=en
-~----------~----~----~----~------~----~------~--~---
