IxD for building a list

10 Jul 2006 - 7:55am
8 years ago
5 replies
758 reads
russwilson
2005

I'm looking for a mechanism to build a list through
user input. Basically, the user should be able to add
one item and stop, add multiple items in sequence, or
cancel.

What we are considering is user input fields followed by
buttons with:

Add | Add & New | Cancel

Does this seem like the best solution? Is there something else to
consider?

Thanks,
Russ

Russell Wilson | Director of Product Design
NetQoS, Inc. | 5001 Plaza on the Lake, Austin, TX 78746
512.334.3725 | russell.wilson at netqos.com

NetQoS: Performance Experts
www.netqos.com

Comments

10 Jul 2006 - 8:05am
Cecily Walker
2006

I like flickr's interpretation of this behavior. The interface has one
single text box, and users can simply add one item, or create a list
of items by separating entries with commas.

On 7/10/06, Wilson, Russell <Russell.Wilson at netqos.com> wrote:

> I'm looking for a mechanism to build a list through
> user input. Basically, the user should be able to add
> one item and stop, add multiple items in sequence, or
> cancel.
>
> What we are considering is user input fields followed by
> buttons with:
>
>
> Add | Add & New | Cancel
>
>
> Does this seem like the best solution? Is there something else to
> consider?

10 Jul 2006 - 8:12am
russwilson
2005

In our case, the user must enter several fields
(not just one); that is, several fields comprise
"one entry". So this wouldn't work.

For single item entry, I like this too...

Thanks,
Russ

-----Original Message-----
From: discuss-bounces at lists.interactiondesigners.com
[mailto:discuss-bounces at lists.interactiondesigners.com] On Behalf Of
Cecily Walker
Sent: Monday, July 10, 2006 9:06 AM
Cc: discuss at lists.interactiondesigners.com
Subject: Re: [IxDA Discuss] IxD for building a list

[Please voluntarily trim replies to include only relevant quoted
material.]

I like flickr's interpretation of this behavior. The interface has one
single text box, and users can simply add one item, or create a list of
items by separating entries with commas.

On 7/10/06, Wilson, Russell <Russell.Wilson at netqos.com> wrote:

> I'm looking for a mechanism to build a list through user input.
> Basically, the user should be able to add one item and stop, add
> multiple items in sequence, or cancel.
>
> What we are considering is user input fields followed by buttons with:
>
>
> Add | Add & New | Cancel
>
>
> Does this seem like the best solution? Is there something else to
> consider?
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... discuss at ixda.org
List Guidelines ............ http://listguide.ixda.org/
List Help .................. http://listhelp.ixda.org/
(Un)Subscription Options ... http://subscription-options.ixda.org/
Announcements List ......... http://subscribe-announce.ixda.org/
Questions .................. lists at ixda.org
Home ....................... http://ixda.org/
Resource Library ........... http://resources.ixda.org

10 Jul 2006 - 8:16am
Priya Prakash
2004

How about 2 scenarios:
1. At the end of a single UI field you have a button with label text:
+ Add
On each click it automatically adds another UI field.
You have a global buttons:
Done and Cancel at the bottom of the fields

2. Have 'x' number of mutiple empty fields eg: 5 to start of from
User has option to add more and leaves the ones they don't need blank.
This also prevent user from having to click +Add multiple times.
Clicking Done at the end of each entry or globally should be the same
result.

Is this being built within a browser?
See Linkedin 'Add connections' for example.

Priya Prakash
Senior Interaction Designer
>Broadcast Centre BC4 C6, Media Village,
>201 Wood Lane London W12 7TP
>United Kingdom
>W: 02080085392
www.bbc.co.uk/imp

-----Original Message-----
From: discuss-bounces at lists.interactiondesigners.com
[mailto:discuss-bounces at lists.interactiondesigners.com] On Behalf Of
Wilson, Russell
Sent: 10 July 2006 14:56
To: discuss at lists.interactiondesigners.com
Subject: [IxDA Discuss] IxD for building a list

[Please voluntarily trim replies to include only relevant quoted
material.]

I'm looking for a mechanism to build a list through user input.
Basically, the user should be able to add one item and stop, add
multiple items in sequence, or cancel.

What we are considering is user input fields followed by buttons with:

Add | Add & New | Cancel

Does this seem like the best solution? Is there something else to
consider?

Thanks,
Russ

Russell Wilson | Director of Product Design NetQoS, Inc. | 5001 Plaza on
the Lake, Austin, TX 78746
512.334.3725 | russell.wilson at netqos.com

NetQoS: Performance Experts
www.netqos.com

________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... discuss at ixda.org List Guidelines
............ http://listguide.ixda.org/ List Help ..................
http://listhelp.ixda.org/ (Un)Subscription Options ...
http://subscription-options.ixda.org/
Announcements List ......... http://subscribe-announce.ixda.org/
Questions .................. lists at ixda.org Home .......................
http://ixda.org/ Resource Library ........... http://resources.ixda.org

http://www.bbc.co.uk/

This e-mail (and any attachments) is confidential and may contain
personal views which are not the views of the BBC unless specifically
stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in
reliance on it and notify the sender immediately. Please note that the
BBC monitors e-mails sent or received.
Further communication will signify your consent to this.

10 Jul 2006 - 8:28am
Juan Lanus
2005

I'd also consider if it's the case of a user who already has pieces of
the list in his local computer and would like to copy and paste.
It's like Cecily's suggestion plus some inteligence for to recognize
other separators like newlines and the like. May change depending on
the OS.
The user MUST have an instance for the revision of her work before
clicking an "accept forever" button. Also, the user has to be aware
that the button is there and that nothing irreversible will happen as
long as the button is not touched.

Wha't the length of the list, does it have many columns or only one?
This changes the scenario.
> "... add multiple items in sequence, ..."
The timing is important. Is it a web application with a server trip
for each item? (This is my assumed scenario). If so then doing it in
an ajaxian way would help a lot, bacause of the server trip time, but
specially because this way you let the user work without pause,
catering on the "asynchronous" side of AJAX, and specially without
moving the form and the focus.
--
Juan Lanus
TECNOSOL
Argentina

10 Jul 2006 - 8:55am
Juan Lanus
2005

Hmmm ... multiple columns per entry ...

The copy and paste ability still applies, if it's the case of a user
that already built the list into a spreadsheet.

There are many more questions, like:
+ a few columns, or many;
+ 10 rows, 100 rows, or more;
+ has to be sorted or not;
+ can use sub-forms or is not advisable;
+ rather techie users or not;
+ the list is created, used and abandoned or persists and gets updated;
+ can data be checked as it's being entered?

Depending on volume and importance of the data one can buils a use
case for "maintain the list" including it all, ala traditional web
form, or making separate use cases for "loading the list" and
"updating the list".

Assuming what I assume, my solution would be a table with the list data in rows.

Update:
Rows are clickable: "click in a row for to change it". This tekes the
user to a form (maybe in the same window or a new one) with the data
separated in fields, preloaded. If any item is "key" then it's
protected. The user can edit and accept, return, or check "delete this
entry" and accept (the accept button caption changed to "delete").

Add new:
Same as above, no protected data items, no delete option.

Of course, in both cases each element is checked and the form can't be
accepted if something is wrong. Using AJAX I'd check entered data
against the server where appropriate.

Some assumptions:
+ web application
+ not many fields, so that an entry can be displayed in a table row
+ some lists will have more than a few rows and the data in important
+ users are normal people

Syndicate content Get the feed