Schedule

From Organic Design wiki
Revision as of 13:05, 9 June 2010 by Infomaniac (talk | contribs) (typo)

Template:Project This article now represents the general concept of how we want to integrate the time/schedule/inbox/changes concept into our wiki-based organisational system.

The main thing is to be able to collaborate on media channels and book resources. This needs to be done using a schedule interface. The aspects of monthly and yearly are fine with SimpleCalendar, but for working at the level of individual days and finer granularity require a more dynamic interface done with JavaScript or Flash.

A schedule should be able to be created as an aspect of any article with a tag function or parser function. The dynamic interface would need to allow time-slots to be created and collected together within their page. The time-slots would be rectangles of a length proportional to their duration and they could be dragged and dropped into the timeline.

Alternatively outside the timeline where the "potential" items are collected and created or removed, properties could be set for selected items allowing them to appear at regular intervals in the time-line.

Example uses

  • Making resources bookable
  • Creating channels and playlists
  • Organic design schedule, eg friday meetings

Requirements

  • A JS or SWF interface which allows zooming in or out over scales from yearly to seconds/minutes
  • Schedules can be added to any article
  • Schedule interface allows overlaying of other schedules
  • An event is simply wikitext content (could be stored in parser function, or in db)
  • Can link directly to an event within an article

Automation

We need a way to make items in a schedule represent changes of state in different ways, for example:

  • Change the source url of content on a streaming channel (a schedule of urls)
  • Change the workflow state of a job or project
  • Change the access rights of a resource based on booking schedule

This aspect may be best handled with a bot that watches a category. This could also act as an in-wiki cron interface for handling distributed backups, caretaker etc.

Questions

  • Are days separate articles or do all events go into the one title?
  • How can one event such as a friday meeting be associated with many schedules?
  • Is there a good in-wiki way to specify that events change a template's parameter value?

Old notes

Dynamic

Like the old changes in the logo (logo.as), but a new one would work based on Livelets using AJAX/SWF for push-based updates.

Multiple Sources

Allow the changes to be a more generic list of events in which the local wiki's changes are just one source. Other good sources would be file-system events, logs, remote wiki's, web-scrapers and pop-boxes. Of course this also implies that the changes lists are specific to users.

Sound on change

Can we have a customisable sound to be triggered by a change? Could work really well in conjunction with filtering. Good for when doing a job, for instance Borgification and being in dynamic communication using the wiki.

Yip I'll do this one sometime soon - I was actually going to do that, but got side-tracked into the merged changes instead.

RSS

Currently we're using the generic URL-matching rules to extract RSS changes title's. This is not ideal though because the generic URL-matching is based on detecting the differences between items, so if a comment is added which has the same title as a previous one it won't show up. Also it would be good to extract the author and timestamp etc, so a specific RSS reader should be added some time which would be quite easy to implement.

At this website we see an RSS-reader dashboard widget described that just allows you to pull the changes off a Basecamp. There might be some ideas for ultra-changes layout (tabbed changes?) here. On the other hand, maybe it would be possible to borgify Basecamp-changes into the ultra-changes using a similar technique to what the coder of the widget uses. Basecamp is very email-push oriented, it would be nice to free up the inbox and also to be able to follow the changes on a Basecamp without having to deal with its confusing layout. Maybe this is impractical but it can't hurt to ask.
Here's one: http://ccguest:ccguest@cocreators.grouphub.com/feed/recent_items_rss
And here's the login to the Co-creators Basecamp, maybe that's helpful:
With the Co-creators guest login you will be able to access all Projects on the Cocreators Basecamp. Have a look around to see what is going on at http://ccguest:ccguest@cocreators.grouphub.com/clients

Changes added in OD's TransformChanges.php

<php>

  1. We're using these cols and ordering

$cols = array('time','diff','title','comment','user','info');

  1. this is added before the final row-assembling line of wfTransformChangesLI()

$talk = preg_replace('| \\|.+</a>|',,$talk); $diff = preg_replace('|curid=[0-9]+&(amp;)?action=history|','action=edit',$diff); $diff = preg_replace('|>hist<|','>edit<',$diff); $user .= " $talk"; </php>

See also

Retrieved from "https://organicdesign.nz/wiki/index.php?title=Schedule&oldid=96950"