Clariying what a "vignette" is...

[Peter Knoop]

On the UX call today the confusion over what "vignette" means in this specific context was raised.  I've added some text (see below) to the Potential Vignette Use Case page to try and help clarify the situation:

http://confluence.sakaiproject.org/confluence/x/nQvWAg

If anyone else on the call today has some other clarifying thoughts to add, please do so.

-peter



What does "vignette" mean in the context of this discussion?  Vignette here is roughly equivalent to other words like widget, gadget, entity, etc. used in other Sakai contexts.  It is being used to refer to a chunk or snippet or piece of Sakai's capabilities that can be incorporated into a page; you can have multiple vignettes per page if desired as well.  

A simple example to envision would be a page you might compose for students to read before a class session.  You author text on it, embedd files in the text that are pictures and graphs, include a link to a self-test at the bottom that they can take when they've completed the reading, and a discussion area to discuss the reading before/after the face-to-face class session.  So in this example the vignettes are offering the capabilities for:
* files vignette - As an instructor you need the vignette to support finding or uploading the files you want to place in the reading.  For the student, the vignette simply displays the content in the right place in the page.
* self-test vignette - As the instructor you need the vignette to support creating a short quiz or selecting an existing one that you've created beforehand.  You also need to be able to choose to include the self-test questions directly in the page, rather than just a link to them.  You probably also want the vignette to provide summary stats on how students have done, once they start taking the self-test.  As the student you need the vignette to display the questions, accept your answers, and probably provide feedback on your responses.
* discussion vignette - As an instructor the vignette provides a way to create a discussion topic or thread, or pick from an existing list, to configure options like who can respond and how responses are handled, and to view posts once the discussion starts. As a student you need to be able to view the topic and existing posts and add your own input.

Vignette is not being used here as another word for use-case or usage-scenario.  Rather, this page is a place to post examples of the latter, so that they can inform the design of and capabilities needed in vignettes/widgets/gadgets/entities, and how those vignettes should be able to be put together with each other and/or other page content.
----------------------
This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org//portal) from the DG: User Experience site.
You can modify how you receive notifications at My Workspace > Preferences.

[Josh Baron]

Peter,

I just want to check in with you on my understanding of what you want
folks to be contributing to the confluence page you reference below.

It sounds like you do still want this page to be a place where folks post
"use cases" for the vignettes (I find the word "widget" to be a bit
clearer but maybe that is just me) that have been listed, correct?  From
the call we had last week I thought that the real need in the UX and
Developer groups were for teaching and learning folks to provide examples
of how "vignettes" or widget would be used and not how the widgets should
work or be designed.

Am I on the right track here?

Josh

-----------------------------
Joshua Baron
Director, Academic Technology and eLearning
Marist College
Poughkeepsie, New York  12601
[phone] (work)



From:
"Knoop, Peter" <knoop@...>
To:
Sakai UX <sakai-ux@...>, sakai-user
<sakai-user@...>
Date:
02/02/2009 02:07 PM
Subject:
Clariying what a "vignette" is...




On the UX call today the confusion over what "vignette" means in this
specific context was raised.  I've added some text (see below) to the
Potential Vignette Use Case page to try and help clarify the situation:

http://confluence.sakaiproject.org/confluence/x/nQvWAg

If anyone else on the call today has some other clarifying thoughts to
add, please do so.

-peter



What does "vignette" mean in the context of this discussion?  Vignette
here is roughly equivalent to other words like widget, gadget, entity,
etc. used in other Sakai contexts.  It is being used to refer to a chunk
or snippet or piece of Sakai's capabilities that can be incorporated into
a page; you can have multiple vignettes per page if desired as well.

A simple example to envision would be a page you might compose for
students to read before a class session.  You author text on it, embedd
files in the text that are pictures and graphs, include a link to a
self-test at the bottom that they can take when they've completed the
reading, and a discussion area to discuss the reading before/after the
face-to-face class session.  So in this example the vignettes are offering
the capabilities for:
* files vignette - As an instructor you need the vignette to support
finding or uploading the files you want to place in the reading.  For the
student, the vignette simply displays the content in the right place in
the page.
* self-test vignette - As the instructor you need the vignette to support
creating a short quiz or selecting an existing one that you've created
beforehand.  You also need to be able to choose to include the self-test
questions directly in the page, rather than just a link to them.  You
probably also want the vignette to provide summary stats on how students
have done, once they start taking the self-test.  As the student you need
the vignette to display the questions, accept your answers, and probably
provide feedback on your responses.
* discussion vignette - As an instructor the vignette provides a way to
create a discussion topic or thread, or pick from an existing list, to
configure options like who can respond and how responses are handled, and
to view posts once the discussion starts. As a student you need to be able
to view the topic and existing posts and add your own input.

Vignette is not being used here as another word for use-case or
usage-scenario.  Rather, this page is a place to post examples of the
latter, so that they can inform the design of and capabilities needed in
vignettes/widgets/gadgets/entities, and how those vignettes should be able
to be put together with each other and/or other page content.
----------------------
This automatic notification message was sent by Sakai Collab (
https://collab.sakaiproject.org//portal) from the DG: User (Using Sakai)
site.
You can modify how you receive notifications at My Workspace >
Preferences.



----------------------
This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org//portal) from the DG: User Experience site.
You can modify how you receive notifications at My Workspace > Preferences.

[Peter Knoop]

Well, I hope I'm not muddying things further then :)

The "use cases" need to be detailed enough to explain what various users are trying to achieve, so that the necessary capabilities can be designed in a way for them to achieve it.  So the use cases don't need to worry about prescribing how capabilities for vignettes are presented in their little "boxes" on the page, but should instead focus on explaining what capabilities are needed for a page and why.

-peter


From: Josh Baron [mailto:Josh.Baron@...]
Sent: Monday, February 02, 2009 2:18 PM
To: Knoop, Peter
Cc: sakai-user; Sakai UX
Subject: Re: Clariying what a "vignette" is...


Peter,

I just want to check in with you on my understanding of what you want folks to be contributing to the confluence page you reference below.

It sounds like you do still want this page to be a place where folks post "use cases" for the vignettes (I find the word "widget" to be a bit clearer but maybe that is just me) that have been listed, correct?  From the call we had last week I thought that the real need in the UX and Developer groups were for teaching and learning folks to provide examples of how "vignettes" or widget would be used and not how the widgets should work or be designed.

Am I on the right track here?

Josh

-----------------------------
Joshua Baron
Director, Academic Technology and eLearning
Marist College
Poughkeepsie, New York  12601
[phone] (work)

From:

"Knoop, Peter" <knoop@...>

To:

Sakai UX <sakai-ux@...>, sakai-user <sakai-user@...>

Date:

02/02/2009 02:07 PM

Subject:

Clariying what a "vignette" is...


________________________________




On the UX call today the confusion over what "vignette" means in this specific context was raised.  I've added some text (see below) to the Potential Vignette Use Case page to try and help clarify the situation:

http://confluence.sakaiproject.org/confluence/x/nQvWAg

If anyone else on the call today has some other clarifying thoughts to add, please do so.

-peter



What does "vignette" mean in the context of this discussion?  Vignette here is roughly equivalent to other words like widget, gadget, entity, etc. used in other Sakai contexts.  It is being used to refer to a chunk or snippet or piece of Sakai's capabilities that can be incorporated into a page; you can have multiple vignettes per page if desired as well.

A simple example to envision would be a page you might compose for students to read before a class session.  You author text on it, embedd files in the text that are pictures and graphs, include a link to a self-test at the bottom that they can take when they've completed the reading, and a discussion area to discuss the reading before/after the face-to-face class session.  So in this example the vignettes are offering the capabilities for:
* files vignette - As an instructor you need the vignette to support finding or uploading the files you want to place in the reading.  For the student, the vignette simply displays the content in the right place in the page.
* self-test vignette - As the instructor you need the vignette to support creating a short quiz or selecting an existing one that you've created beforehand.  You also need to be able to choose to include the self-test questions directly in the page, rather than just a link to them.  You probably also want the vignette to provide summary stats on how students have done, once they start taking the self-test.  As the student you need the vignette to display the questions, accept your answers, and probably provide feedback on your responses.
* discussion vignette - As an instructor the vignette provides a way to create a discussion topic or thread, or pick from an existing list, to configure options like who can respond and how responses are handled, and to view posts once the discussion starts. As a student you need to be able to view the topic and existing posts and add your own input.

Vignette is not being used here as another word for use-case or usage-scenario.  Rather, this page is a place to post examples of the latter, so that they can inform the design of and capabilities needed in vignettes/widgets/gadgets/entities, and how those vignettes should be able to be put together with each other and/or other page content.
----------------------
This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org//portal<https://collab.sakaiproject.org/portal>) from the DG: User (Using Sakai) site.
You can modify how you receive notifications at My Workspace > Preferences.


----------------------
This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org//portal) from the DG: User Experience site.
You can modify how you receive notifications at My Workspace > Preferences.

[Nathan Pearson-2]

I'd like to add some additional clarity to defining what a "vignette" is --
even though it's only a subtext to the current discussion.

For starters, I still think the term "widget" (or "gadget") remains relevant
to our vocabulary.  In fact, a vignette is a type of widget.

Here's the break down:

A widget refers to a portable technology that can exist on a page, on one's
desktop, etc.  But there are two main flavors of widgets; those that pull
data from an external source (like a slide-show widget pulling from some
file browser) and those that do not (like a clock).

So to be clear about the type of widget we mean as we talk about this stuff,
I introduced this highfalutin vignette terminology, which refers to the
former.

As a side note...

Why wouldn't the word entity do the trick?  Well, these things that we're
placing on pages (widgets... some of which are vignettes) can be though of
as entities, but so too can the page itself.  So exclusively using the word
entity makes things confusing.  Nevertheless, it too remains relevant to our
vocabulary.

My suggestion is to use whatever word you like if you're causally talking
about this stuff, but to be clear technically, it helps to use the
appropriate term.




On Mon, Feb 2, 2009 at 12:39 PM, Knoop, Peter <knoop@...> wrote:

>   Well, I hope I'm not muddying things further then J
>
>
>
> The "use cases" need to be detailed enough to explain what various users
> are trying to achieve, so that the necessary capabilities can be designed in
> a way for them to achieve it.  So the use cases don't need to worry about
> prescribing how capabilities for vignettes are presented in their little
> "boxes" on the page, but should instead focus on explaining what
> capabilities are needed for a page and why.
>
>
>
> -peter
>
>
>
>
>
> *From:* Josh Baron [mailto:Josh.Baron@...]
> *Sent:* Monday, February 02, 2009 2:18 PM
> *To:* Knoop, Peter
> *Cc:* sakai-user; Sakai UX
> *Subject:* Re: Clariying what a "vignette" is...
>
>
>
>
> Peter,
>
> I just want to check in with you on my understanding of what you want folks
> to be contributing to the confluence page you reference below.
>
> It sounds like you do still want this page to be a place where folks post
> "use cases" for the vignettes (I find the word "widget" to be a bit clearer
> but maybe that is just me) that have been listed, correct?  From the call we
> had last week I thought that the real need in the UX and Developer groups
> were for teaching and learning folks to provide examples of how "vignettes"
> or widget would be used and not how the widgets should work or be designed.
>
> Am I on the right track here?
>
> Josh
>
> -----------------------------
> Joshua Baron
> Director, Academic Technology and eLearning
> Marist College
> Poughkeepsie, New York  12601
> [phone] (work)
>
>   From:
>
> "Knoop, Peter" <knoop@...>
>
> To:
>
> Sakai UX <sakai-ux@...>, sakai-user <
> sakai-user@...>
>
> Date:
>
> 02/02/2009 02:07 PM
>
> Subject:
>
> Clariying what a "vignette" is...
>
>
>  ------------------------------
>
>
>
>
>
> On the UX call today the confusion over what "vignette" means in this
> specific context was raised.  I've added some text (see below) to the
> Potential Vignette Use Case page to try and help clarify the situation:
>
> http://confluence.sakaiproject.org/confluence/x/nQvWAg
>
> If anyone else on the call today has some other clarifying thoughts to add,
> please do so.
>
> -peter
>
>
>
> What does "vignette" mean in the context of this discussion?  Vignette here
> is roughly equivalent to other words like widget, gadget, entity, etc. used
> in other Sakai contexts.  It is being used to refer to a chunk or snippet or
> piece of Sakai's capabilities that can be incorporated into a page; you can
> have multiple vignettes per page if desired as well.
>
> A simple example to envision would be a page you might compose for students
> to read before a class session.  You author text on it, embedd files in the
> text that are pictures and graphs, include a link to a self-test at the
> bottom that they can take when they've completed the reading, and a
> discussion area to discuss the reading before/after the face-to-face class
> session.  So in this example the vignettes are offering the capabilities
> for:
> * files vignette - As an instructor you need the vignette to support
> finding or uploading the files you want to place in the reading.  For the
> student, the vignette simply displays the content in the right place in the
> page.
> * self-test vignette - As the instructor you need the vignette to support
> creating a short quiz or selecting an existing one that you've created
> beforehand.  You also need to be able to choose to include the self-test
> questions directly in the page, rather than just a link to them.  You
> probably also want the vignette to provide summary stats on how students
> have done, once they start taking the self-test.  As the student you need
> the vignette to display the questions, accept your answers, and probably
> provide feedback on your responses.
> * discussion vignette - As an instructor the vignette provides a way to
> create a discussion topic or thread, or pick from an existing list, to
> configure options like who can respond and how responses are handled, and to
> view posts once the discussion starts. As a student you need to be able to
> view the topic and existing posts and add your own input.
>
> Vignette is not being used here as another word for use-case or
> usage-scenario.  Rather, this page is a place to post examples of the
> latter, so that they can inform the design of and capabilities needed in
> vignettes/widgets/gadgets/entities, and how those vignettes should be able
> to be put together with each other and/or other page content.
> ----------------------
> This automatic notification message was sent by Sakai Collab (
> https://collab.sakaiproject.org//portal<https://collab.sakaiproject.org/portal>)
> from the DG: User (Using Sakai) site.
> You can modify how you receive notifications at My Workspace > Preferences.
>
>
> ------------------------------
>
> This automatic notification message was sent by Sakai Collab (
> https://collab.sakaiproject.org//portal) from the DG: User Experience
> site.
> You can modify how you receive notifications at My Workspace > Preferences.
>

--
Nathan Pearson | UX Lead | Sakai Foundation

E. me@...
M. 602.418.5092
Y. npearson99 (Yahoo)
S. npearson99 (Skype)

http://www.google.com/calendar/embed?src=kfqdgv5itkg1kl08050cu45pb8%40group.calendar.google.com&ctz=America/Phoenix

----------------------
This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org//portal) from the DG: User Experience site.
You can modify how you receive notifications at My Workspace > Preferences.