Floe Planning
Jonathan Hung
jhung at ocadu.ca
Fri Mar 7 15:57:58 EST 2014
Hi Michelle,
Sorry I had missed the meeting in which these topics were discussed, and
I've attempted to catch up by talking to Justin, Dana, and Joanna. Here is
what I have understood based on these discussions and would like to know if
it matches what you were thinking.
1. Build a new demo that shows the following:
- Metadata authoring of an existing learning resource
- Metadata authoring of a new / blank resource (much like the current demo)
- Upon saving, the user can see some effect of the metadata on the content
authored (i.e. a caption track shows along with a video). In this context,
it would also be nice to show some of the other Floe tools (i.e. Learner
Options and Exploration Tool).
- The NOAA demo is a possible example for framing this new demo, although
it doesn't necessarily have to be the NOAA demo with Metadata editing built
in.
2. Show content finding, delivery, and consumption
- in the short term there may not be an implementation of this. Instead,
we will create some material which supports or illustrates how content is
created, saved, delivered, and filtered.
- this is where we can make connections to video player, saving of learner
options, and searching and filtering learner content
Does this fit with what was discussed? Please add / correct where needed.
- Jon.
On Tue, Mar 4, 2014 at 5:10 PM, Michelle D'Souza <michelled33 at gmail.com>wrote:
> Hi everyone,
>
> The Floe team met today to talk though the work that we will be doing over
> the next couple of months. We are planning to spend most of our effort in
> improving our metadata authoring infrastructure and components, and our
> content delivery. Some of the tasks that came out of the meeting are below.
>
> *Metadata Authoring:
> http://metadata.floeproject.org/demos/html/metadata.html
> <http://metadata.floeproject.org/demos/html/metadata.html>*
> 1. Design an interface that explores simple management of multiple
> resources. It should allow a user to select a resource that has been
> partially developed and create new resources.
> 2. Complete the metadata infrastructure work to split the metadata tools
> and components from the demo authoring environment.
> 3. Implement a view mode of the resource being authored.
> 4. Ensure the demo authoring environment can handle a complex resource
> like the NOAA demo.
>
> *Content Finding*
> 1. Consider designs for simple content finding based on preferences and
> metadata.
>
> *Delivering and Using Content *
> 1. Show the delivery of content within the context of authoring.
> * do preferences framework integration (this might not be done in the
> first sprint)
> * do video player integration (this might not be done in the first sprint)
> * explore saving content (this is unlikely to be done in the first sprint)
> 2. Connect existing demos (Exploration Tool, NOAA, Mammals) to the
> preferences server (this is unlikely to be done in the first sprint)
>
> We'll be updating the iteration plan page with our work as usual:
> http://wiki.fluidproject.org/display/fluid/Floe+Iteration+Plan
>
> Michelle
>
>
>
>
>
>
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
>
--
*JONATHAN HUNG*
INCLUSIVE DESIGNER, IDRC
*T:* 416 977 6000 x3951
*F:* 416 977 9844
*E:* jhung at ocadu.ca
*OCAD UNIVERSITY*
Inclusive Design Research Centre
205 Richmond Street W, Toronto, ON, M5V 1V3
www.ocadu.ca
www.idrc.ocad.ca
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20140307/64410662/attachment.html>
More information about the fluid-work
mailing list