Reorderer for Sakai

Daphne Ogle daphne at media.berkeley.edu
Thu Sep 11 22:07:42 UTC 2008


Righteo Peter!  We are talking about integrating it into the current  
Sakai.

And I soooo agree about really understanding the problem the user is  
trying to solve in a way that meets their needs.  3.0 gives us the  
opportunity to do just this.

-Daphne

On Sep 11, 2008, at 6:33 AM, Knoop, Peter wrote:

> Seeing Sakai 3 and Announcements put together, I just want to check  
> that
> I understand at what work this thread is targeted.  The re-order in
> Announcements makes sense to me in helping improve the existing  
> Sakai 2
> experience, even if it is mostly to help with work-arounds to get  
> Sakai
> to do what you want it to do overall.  For Sakai 3, however, I hope we
> can start by thinking more about what the users are really trying to  
> do
> with Announcements, Messages, Mailtool, and Email Archive, and in the
> contexts of those tools' full and synoptic/recent activity/what's new
> views, before we assume Announcements is still needed in Sakai 3 and
> needs re-ordering.
>
> -peter
>
>> -----Original Message-----
>> From: fluid-work-bounces at fluidproject.org [mailto:fluid-work-
>> bounces at fluidproject.org] On Behalf Of John Norman
>> Sent: Thursday, September 11, 2008 7:13 AM
>> To: Daphne Ogle
>> Cc: fluid-work
>> Subject: Re: Reorderer for Sakai
>>
>> Posed this way we can include the Tool Reorder tool in the use-cases.
>> (Found in SiteInfo if you are an admin on a site)
>>
>> A related example would be in our model of site page organisation for
>> Sakai 3, would be reordering the list of pages in the site nav bar.
>>
>> John
>>
>> On 11 Sep 2008, at 02:22, Daphne Ogle wrote:
>>
>>> I've captured the scenarios discussed (titles at least) on the
>>> wiki:  http://wiki.fluidproject.org/display/fluid/Scenarios+-
>> +List+Reorderer
>>>
>>> Its parent page, List Reorderer Design Overview, is also in its
>>> infancy:
>>
> http://wiki.fluidproject.org/display/fluid/List+Reorderer+Design 
> +Overvi
>> ew
>>>
>>> John, should we pose a question to the Sakai lists to capture more
>>> use cases/scenarios?
>>>
>>> Thanks, Daphne
>>>
>>> On Sep 10, 2008, at 11:48 AM, Jess Mitchell wrote:
>>>
>>>> Excellent.
>>>>
>>>> I know we've already begun a use case for this John L. -- Look for
>>>> more from us soon.
>>>>
>>>> Best,
>>>> Jess
>>>>
>>>> ~~~~~~~~~~~~~~~~~~~~~~
>>>> Jess Mitchell
>>>> Boston, MA, USA
>>>> Project Manager / Fluid Project
>>>> jess at jessmitchell.com
>>>> / w / 617.326.7753  / c / 919.599.5378
>>>> jabber: jessmitchell at gmail.com
>>>> http://www.fluidproject.org
>>>> ~~~~~~~~~~~~~~~~~~~~~~
>>>>
>>>>
>>>>
>>>>
>>>> On Sep 10, 2008, at 2:34 PM, John Leasia wrote:
>>>>
>>>>> Some here use Announcements along with other tools to present week
>>>>> by week info, in order of week.  They can put them in originally
>>>>> in the right order, but if they have to go back and edit it gets
>>>>> out of order. Or if they later want to add something somewhere in
>>>>> the middle, etc. Others have said they want one announcement
>>>>> always at the top - maybe class meeting times/hours or class
>>>>> policies or class honor code info or whatever.  Those are from
>>>>> here - reorder in Annc has also been requested by other
>>>>> institutions.
>>>>>
>>>>> John L
>>>>>
>>>>> Jess Mitchell wrote:
>>>>>> John,
>>>>>>
>>>>>> I wondered the same thing and then in a meeting with Gonzalo I
>>>>>> blurted out the following:
>>>>>> I can imagine the case where you have announcements listed in
>>>>>> order of entry, but you want to prioritize one announcement out
>>>>>> of its chronological entry.  Rather than having to enter the
>>>>>> announcement again, you can just drag it to the top of the list.
>>>>>>
>>>>>> Think of the "to-dos" in iCal (if you happen to use iCal).  I can
>>>>>> drag them into a "priority" of listing from top to bottom in
>>>>>> addition to assigning them a priority.  I imagine the same top to
>>>>>> bottom priority would be useful in announcements?
>>>>>>
>>>>>> I've no idea if this is what John L. had in mind and quite
>>>>>> frankly, if it is a use case, then it's my first!
>>>>>>
>>>>>> Best,
>>>>>> Jess
>>>>>>
>>>>>> ~~~~~~~~~~~~~~~~~~~~~~
>>>>>> Jess Mitchell
>>>>>> Boston, MA, USA
>>>>>> Project Manager / Fluid Project
>>>>>> jess at jessmitchell.com
>>>>>> / w / 617.326.7753  / c / 919.599.5378
>>>>>> jabber: jessmitchell at gmail.com
>>>>>> http://www.fluidproject.org
>>>>>> ~~~~~~~~~~~~~~~~~~~~~~
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sep 10, 2008, at 1:21 PM, John Norman wrote:
>>>>>>
>>>>>>> Is there a use case or usage scenario for this work? John Leasia
>>>>>>> mentioned it in passing the other day and I was a bit mystified
>>>>>>> as to
>>>>>>> why one might want to reorder announcements. I guessed you might
>>>>>>> be
>>>>>>> using the grid layout to create an experience similar to pinning
>> a
>>>>>>> notice to a notice board, but it seems not. The only other thing
>>>>>>> I can
>>>>>>> think of is if you have a fixed size list (say 5 announcements)
>>>>>>> and
>>>>>>> there are 7 recent announcements, you might want to juggle the
>>>>>>> list so
>>>>>>> the most important ones appear.
>>>>>>>
>>>>>>> Have I missed something?
>>>>>>>
>>>>>>> "Curious from Cambridge"
>>>>>>>
>>>>>>> On 10 Sep 2008, at 01:26, Daphne Ogle wrote:
>>>>>>>
>>>>>>>> Hi there,
>>>>>>>>
>>>>>>>> As I start design for the reorderer in the context of Sakai's
>>>>>>>> announcements tool, I realize I'm not sure where the work
>>>>>>>> should live
>>>>>>>> in the wiki which leads me to where does it fall in the "family
>>>>>>>> of
>>>>>>>> components" for the reorderer.   I think our naming convention
>>>>>>>> could
>>>>>>>> use some work and since I need a place to put design work
>>>>>>>> around this
>>>>>>>> new context it's forcing the issue.
>>>>>>>>
>>>>>>>> The reorderer itself doesn't have an interface and thus there
>>>>>>>> isn't
>>>>>>>> any UX design in it's space on the wiki.  So then we have the
>>>>>>>> lightbox
>>>>>>>> and the layout customizer which use the reorderer.  This new
>>>>>>>> context
>>>>>>>> seems to be at the same level as the lightbox and the layout
>>>>>>>> customizer -- offsprings of the reorderer.  So what to call
>>>>>>>> this new
>>>>>>>> offspring or is it really the same as one of the existing?
>>>>>>>> Although
>>>>>>>> the lightbox and the reordering of announcements both use the
>>>>>>>> "Drag
>>>>>>>> and Drop - list ordering design pattern" they are different
> user
>>>>>>>> experiences with one moving thumbnails and the other more like
>>>>>>>> rows in
>>>>>>>> a table or a list.  So, I believe this new context it's own
>>>>>>>> child.
>>>>>>>> And with the 3rd on the way, I think it's time for some clearer
>>>>>>>> naming
>>>>>>>> of our family.
>>>>>>>>
>>>>>>>> Here's a suggestion that is more closely aligned with our
>>>>>>>> naming for
>>>>>>>> the inline edit family but I would love to hear other thoughts
>>>>>>>> (my
>>>>>>>> suggestion is quite boring!).
>>>>>>>>
>>>>>>>> Family name:  Reorderers
>>>>>>>> Children:
>>>>>>>> Thumbnail reorderer (formerly known as the lightbox)
>>>>>>>> List reorderer
>>>>>>>> Layout reorderer ( or we could stick with "layout customizer"
>>>>>>>> as it
>>>>>>>> sounds better and is clearer but then it wouldn't match it's
>>>>>>>> siblings
>>>>>>>> names :))
>>>>>>>>
>>>>>>>> What do you all think?
>>>>>>>>
>>>>>>>> Daphne Ogle
>>>>>>>> Senior Interaction Designer
>>>>>>>> University of California, Berkeley
>>>>>>>> Educational Technology Services
>>>>>>>> daphne at media.berkeley.edu
>>>>>>>> cell (510)847-0308
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> fluid-work mailing list
>>>>>>>> fluid-work at fluidproject.org
>>>>>>>> http://fluidproject.org/mailman/listinfo/fluid-work
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> fluid-work mailing list
>>>>>>> fluid-work at fluidproject.org
>>>>>>> http://fluidproject.org/mailman/listinfo/fluid-work
>>>>>>
>>>>>> _______________________________________________
>>>>>> fluid-work mailing list
>>>>>> fluid-work at fluidproject.org
>>>>>> http://fluidproject.org/mailman/listinfo/fluid-work
>>>>>>
>>>>
>>>> _______________________________________________
>>>> fluid-work mailing list
>>>> fluid-work at fluidproject.org
>>>> http://fluidproject.org/mailman/listinfo/fluid-work
>>>
>>> Daphne Ogle
>>> Senior Interaction Designer
>>> University of California, Berkeley
>>> Educational Technology Services
>>> daphne at media.berkeley.edu
>>> cell (510)847-0308
>>>
>>>
>>>
>>> _______________________________________________
>>> fluid-work mailing list
>>> fluid-work at fluidproject.org
>>> http://fluidproject.org/mailman/listinfo/fluid-work
>>
>> _______________________________________________
>> fluid-work mailing list
>> fluid-work at fluidproject.org
>> http://fluidproject.org/mailman/listinfo/fluid-work

Daphne Ogle
Senior Interaction Designer
University of California, Berkeley
Educational Technology Services
daphne at media.berkeley.edu
cell (510)847-0308






More information about the fluid-work mailing list