talk@lists.collectionspace.org

WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org

View all threads

CollectionSpace autocomplete - your chance to help shape it!

AR
Aron Roberts
Wed, Jun 19, 2013 3:00 AM

The next CollectionSpace release is currently planned to introduce
changes to the way that you search for authority terms - persons,
organizations, storage locations and more - by typing partial matches
into autocomplete fields.  This is your chance to help shape this
behavior, before these changes go into that release and directly
affect your current or prospective users.

Staff at several museums here at UC Berkeley have found it
difficult, at times, to find terms they're looking for.  Sometimes
known-to-exist terms don't appear in search results, leading to the
creation of duplicate terms.  In response to their feedback, two
changes we're proposing:

  • You can insert one or more wildcards, anywhere within a search
    expression.  These match any run of zero or more characters.
  • You can insert an 'anchor' character at either end of a search
    expression, or even at both ends.  These find only matches that begin
    with and/or end with your search expression.

How it works:

http://wiki.collectionspace.org/x/GQCKBw

You can try this out "live," searching for the same example Person
names appearing on the wiki page above, by logging in at:

http://qa.collectionspace.org

One quick place to start: create a Group record, and experiment with
using wildcards (*) and anchor characters (^) in the Group Owner
field.

Some feedback needed:

  • Is any of this confusing or counter-intuitive?  Or can you see it
    working well for your needs?
  • What's your reaction to using two identical 'anchor' characters,
    rather than, say, a different 'start' and 'end' anchor character?
  • Do either of the two characters used (* and ^) have any drawbacks?
    If so, what might be better and why?
  • Is the behavior appropriate when you use wildcards and/or anchors,
    but no terms are matched?  (Try searching for "^Norris*foo".)  For
    instance, should the "Add {term} to" section of the dropdown menu be
    disabled or removed?

You can also view existing feedback, received to date from others,
in the comments on the wiki page linked above.

Thanks!
Aron Roberts
UC Berkeley

The next CollectionSpace release is currently planned to introduce changes to the way that you search for authority terms - persons, organizations, storage locations and more - by typing partial matches into autocomplete fields. This is your chance to help shape this behavior, before these changes go into that release and directly affect your current or prospective users. Staff at several museums here at UC Berkeley have found it difficult, at times, to find terms they're looking for. Sometimes known-to-exist terms don't appear in search results, leading to the creation of duplicate terms. In response to their feedback, two changes we're proposing: * You can insert one or more wildcards, anywhere within a search expression. These match any run of zero or more characters. * You can insert an 'anchor' character at either end of a search expression, or even at both ends. These find only matches that begin with and/or end with your search expression. How it works: http://wiki.collectionspace.org/x/GQCKBw You can try this out "live," searching for the same example Person names appearing on the wiki page above, by logging in at: http://qa.collectionspace.org One quick place to start: create a Group record, and experiment with using wildcards (*) and anchor characters (^) in the Group Owner field. Some feedback needed: * Is any of this confusing or counter-intuitive? Or can you see it working well for your needs? * What's your reaction to using two identical 'anchor' characters, rather than, say, a different 'start' and 'end' anchor character? * Do either of the two characters used (* and ^) have any drawbacks? If so, what might be better and why? * Is the behavior appropriate when you use wildcards and/or anchors, but no terms are matched? (Try searching for "^Norris*foo".) For instance, should the "Add {term} to" section of the dropdown menu be disabled or removed? You can also view existing feedback, received to date from others, in the comments on the wiki page linked above. Thanks! Aron Roberts UC Berkeley