Custom Search Button

Mini-Spec from Team Discussion

Philosophically we are about community creation of content, which means that multiple people can update metadata (comments, tags, etc.) for a search button (like on delicious), rather than just the "creator" (like on Flickr)

Here are the details around each button type:

• Keywords:
  • Anyone can create a Keyword button
  • The "Keyword" (or keywords) is the unique identifier for every button
  • The author of the Keyword button should be hidden when users search for the button in the library (i.e., no one is considered the author)
  • Once the button is created, it cannot be modified by any user, including the author. Only tags can be added.
  • Any user who finds or tries to create a Keyword button that already exists can go ahead and add tags to the button during the process of adding the button to their device
  • Only Dash can delete keyword buttons
  • Dash can block the creation of a keyword button
  •  

• GeoRSS / KML
  • Anyone can create a GeoRSS / KML button
  • The "URL" is the unique identifier for every button
  • The "creator" (person who created the button) provides the following:
    • Button name
    • Description
    • Note: Since GeoRSS and KML are beginning to support the Author Attribute, if a feed has Author information we should retain this
  • A person who finds (or tries to add a button that already exists) is able to do the following when adding the button to their device:
    • Tag the button
    • Comment on the button
  • Dash admin can delete a GeoRSS / KML button. The author can delete the GeoRSS button only if he is the only subscriber. If there are other subscribers, the author can only remove the button from his device and from the search index from that point forward; he cannot delete it from other users' devices (and he should get a message indicating that)
  • Dash has the ability to block the creation of GeoRSS / KML buttons (block the URL for the feed)
  • Here is a list of ContentLinks for GeoRSS/KML

• GeoLists (aka - personal lists)
  • Anyone can create a Geolist
  • Geolists are either private or public
    • Private - ONLY the creator can find the button and add it to their device
    • Public - ANYONE can find and add the button to their device
  • The creator of the list controls the content in the list... and this means that all other users are dependant on the user for updates or if the creator removes all data.
  • The creator gives the Geolist the following:
    • Button name
    • Description
    • The username should be automatically filled in as the "Author" for the content
  • A person who finds a public Geolist should be able to do the following when adding the button to their device:
    • Tag the button
    • Comment on the button
  • Only the creator can edit the addresses in the GeoList
  • Here is the behavior if the creator deletes a their Geolist:
    • If the list is public:
      • The list is removed from the users device
      • the list is removed from the "search index"... meaning that no new people can find and add the list
      • users who already have the button on their device can still access the button and the data on the backend
    • If the list if private:
      • The list is removed from the users device
  • Dash should have the ability to delete and remove Geolist buttons and content across the system as it deems necessary
  • Outstanding question: how do buttons refresh on devices? (e.g., if the user changes addresses on a GeoList, do all users buttons get updated or only the new subscribers?)

  • 	Creator	Other User	Dash Admin	Content Owner
    Create	V > Label V > Private/Public V > Tags V > Description V > Location V > Category V > Add Addresses	-	V > Label V > Private/Public V > Tags V > Description V > Location V > Category V > Add Addresses	TBD
    View on Map	V	V	V	TBD
    Modify	V > Label X > Private/Public V > Tags V > Description V > Location V > Category V > Add, Modify, Delete, Map Addresses	X > Label X > Private/Public V > Tags X > Description V > Add Comment X > Location X > Category X > Add, Modify, Delete, Map Addresses	V > Label X > Private/Public V > Tags V > Description V > Location V > Category V > Add, Modify, Delete, Map Addresse	TBD
    Delete	V	X	V	TBD
    Remove	V	V	V	TBD
    Block Creation	X	X	V	TBD

• POI Buttons:
  • ONLY Dash can create POI buttons
  • Dash provides:
    • The button name
    • Description
  • When a user adds a POI button to their device they should be able to:
    • Tag the button
    • Comment on the button
  • Only Dash has the ability to delete a POI button from the system

  • 	Other User	Dash Admin	Content Owner
    Create	-	V > Label V > Tags V > Description V > Location V > Category V > Add Addresses	TBD
    View on Map	V	V	TBD
    Modify	X > Label V > Tags X > Description V > Add Comment X > Location X > Category X > Add, Modify, Delete, Map Addresses	V > Label V > Tags V > Description V > Location V > Category V > Add, Modify, Delete, Map Addresse	TBD
    Delete	X	V	TBD
    Remove	V or X  (depending the type of POI?)	V	TBD

Mockups screens

Saved Search Library

Here is the flow between screens:
CSB_search_v3.pdf 

Home Page

Entry screen - search & browse

Preview

Manage Saved Search

Edit keyword

comment keyword

create Keyword saved search

keyword already in existing

confirmation

GEO RSS/KML button

Geolist button

Geolist_enterlabel

GeoList_Lookupaddress

GeoList_SaveAddress

GeoList_Editgeolist

GeoList_SaveList

GeoList_ConfirmationMessage

Documentations